openstack/blazar
Code Issues Proposed changes

Update contributor guide

Browse Source 
Change-Id: I81275279f716026b7a10226d4b3c98c5befc4a71
This commit is contained in:
Hiroaki Kobayashi 2017-03-02 13:28:04 +09:00 committed by Pierre Riteau
parent 707452ea73
commit d444361bba
1 changed files with 13 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
doc/source/devref/how.to.contribute.rst
View File

@ -4,20 +4,8 @@ How to contribute
Getting started Getting started
--------------- ---------------
* Create `Github <https://github.com/openstack/blazar>`_ account if you don't * Read the `OpenStack Developer's Guide
have one <https://docs.openstack.org/infra/manual/developers.html#developer-s-guide>`_
* Make sure you have git options *user.name* and *user.email* set in git by
typing:
.. sourcecode:: console
git config --list. If not, configure them.
..
* Create `Launchpad <https://launchpad.net/blazar>`_ account if you don't have
one
* Create `OpenStack profile <https://www.openstack.org/profile/>`_
* Login to `OpenStack Gerrit <https://review.openstack.org/>`_ using your * Login to `OpenStack Gerrit <https://review.openstack.org/>`_ using your
Launchpad ID Launchpad ID
@ -42,24 +30,22 @@ How to keep in touch with community
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>`_ or to <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>`_ or to
`OpenStack development mailing list `OpenStack development mailing list
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>`_, do <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>`_, do
that. Blazar-related emails must be send with **[blazar]** in its subject. that. Blazar-related emails must be send with **[blazar]** in its subject
* All questions may be asked on our IRC channel #openstack-blazar on * All questions may be asked on our IRC channel #openstack-blazar on
`freenode <http://freenode.net>`_ `freenode <http://freenode.net>`_
* We also have weekly meetings on #openstack-meeting * We also have weekly meetings on #openstack-meeting-alt. Please check
`freenode IRC channel <https://wiki.openstack.org/wiki/Meetings/Blazar>`_ `meeting details <https://wiki.openstack.org/wiki/Meetings/Blazar>`_
Your first commit to Blazar Your first commit to Blazar
---------------------------- ----------------------------
* Checkout corresponding Blazar repository from `Github * Read the `OpenStack development workflow documentation
<https://github.com/openstack/blazar>`_ <https://docs.openstack.org/infra/manual/developers.html#development-workflow>`_
* Take a look on how `Gerrit review process * Checkout corresponding Blazar repository:
<https://wiki.openstack.org/wiki/Gerrit_Workflow>`_ goes on in OpenStack `blazar <https://git.openstack.org/openstack/blazar>`_,
(read carefully `committing changes `blazar-nova <https://git.openstack.org/openstack/blazar-nova>`_,
<https://wiki.openstack.org/wiki/Gerrit_Workflow#Committing_Changes>`_ part) `client <https://git.openstack.org/openstack/python-blazarclient>`_
* Apply and commit your changes * Apply and commit your changes
* Make sure all code checkings and tests have passed. See * Make sure all code checkings and tests have passed
`development guidelines <development.guidelines.html>`_ to learn more * Send your patch to the review
* Send your patch to the review (you may use `git-review
<https://github.com/openstack-infra/git-review>`_ utility for that)
* Monitor status of your change on https://review.openstack.org/#/ * Monitor status of your change on https://review.openstack.org/#/