Difference between revisions of "Blazar/How to contribute"

Revision as of 13:57, 23 February 2017

If you're not subscribed to OpenStack general mailing list or to OpenStack development mailing list, do that. Blazar-related emails must be send with [blazar] in its subject.
All questions may be asked on our IRC channel #openstack-blazar on freenode
We also have weekly meetings.

Checkout corresponding Blazar repository: blazar, blazar-nova, blazar client
Apply and commit your changes
Make sure all code checkings and tests have passed. See development guidelines to learn more
Send your patch to the review (you may use git-review utility for that)
Monitor status of your change on https://review.openstack.org/#/

@@ Line 11: / Line 11: @@
 == Your first commit to Blazar ==
-* Checkout corresponding Blazar repository from [https://github.com/stackforge/blazar Github]
+* Checkout corresponding Blazar repository: [https://github.com/openstack/blazar blazar], [https://github.com/openstack/blazar-nova blazar-nova], [https://github.com/openstack/python-blazarclient blazar client]
-* Take a look on how [https://wiki.openstack.org/wiki/Gerrit_Workflow Gerrit review process] goes on in OpenStack (read carefully [https://wiki.openstack.org/wiki/Gerrit_Workflow#Committing_Changes committing changes] part)
 * Apply and commit your changes
 * Make sure all code checkings and tests have passed. See [https://wiki.openstack.org/wiki/Blazar/Development_Guidelines development guidelines] to learn more
 * Send your patch to the review (you may use [https://github.com/openstack-infra/git-review git-review] utility for that)
 * Monitor status of your change on https://review.openstack.org/#/