Difference between revisions of "Blazar/How to contribute"
< Blazar
m (Sergey Lukjanov moved page Climate/How to contribute to Blazar/How to contribute: Climate project has been renamed to the Blazar project due to the possible trademark issues.) |
|||
| Line 1: | Line 1: | ||
== Getting started == | == Getting started == | ||
| − | * Create [https://github.com/stackforge/ | + | * Create [https://github.com/stackforge/blazar Github] account if you don't have one |
* Make sure you have git options user.name and user.email set in git by typing '''''git config --list'''''. If not, configure them. | * Make sure you have git options user.name and user.email set in git by typing '''''git config --list'''''. If not, configure them. | ||
| − | * Create [http://launchpad.net/ | + | * Create [http://launchpad.net/blazar Launchpad] account if you don't have one |
* Create [https://www.openstack.org/profile/ OpenStack profile] | * Create [https://www.openstack.org/profile/ OpenStack profile] | ||
* Login to [https://review.openstack.org/ OpenStack Gerrit] using your Launchpad ID | * Login to [https://review.openstack.org/ OpenStack Gerrit] using your Launchpad ID | ||
** Sign up your [https://review.openstack.org/#/settings/agreements OpenStack Individual Contributor License Agreement] | ** Sign up your [https://review.openstack.org/#/settings/agreements OpenStack Individual Contributor License Agreement] | ||
** Check that your email is listed in [https://review.openstack.org/#/settings/web-identities Gerrit identities] | ** Check that your email is listed in [https://review.openstack.org/#/settings/web-identities Gerrit identities] | ||
| − | * Subscribe to | + | * Subscribe to Blazar-related projects on [https://review.openstack.org/ OpenStack Gerrit]. Go to your settings and in the '''''watched projects''''' add '''''stackforge/blazar''''', '''''stackforge/blazar-nova''''' and '''''stackforge/python-blazarclient''''' |
| − | As all bugs/blueprints are listed in [https://launchpad.net/ | + | As all bugs/blueprints are listed in [https://launchpad.net/blazar Blazar Launchpad], you may keep track on them and choose some to work on. |
== How to keep in touch with community == | == How to keep in touch with community == | ||
| − | * If you're not subscribed to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack OpenStack general mailing list] or to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack development mailing list], do that. | + | * If you're not subscribed to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack OpenStack general mailing list] or to [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 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- | + | * All questions may be asked on our IRC channel #openstack-blazar on [http://freenode.net freenode] |
| − | * We also have weekly meetings on #openstack-meeting freenode IRC channel at [https://wiki.openstack.org/wiki/Meetings/ | + | * We also have weekly meetings on #openstack-meeting freenode IRC channel at [https://wiki.openstack.org/wiki/Meetings/Blazar 15:00 UTC] |
| − | == Your first commit to | + | == Your first commit to Blazar == |
| − | * Checkout corresponding | + | * Checkout corresponding Blazar repository from [https://github.com/stackforge/blazar Github] |
* 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) | * 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 | * Apply and commit your changes | ||
| − | * Make sure all code checkings and tests have passed. See [https://wiki.openstack.org/wiki/ | + | * 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) | * 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/#/ | * Monitor status of your change on https://review.openstack.org/#/ | ||
Revision as of 20:53, 5 June 2014
Getting started
- Create Github account if you don't have one
- Make sure you have git options user.name and user.email set in git by typing git config --list. If not, configure them.
- Create Launchpad account if you don't have one
- Create OpenStack profile
- Login to OpenStack Gerrit using your Launchpad ID
- Sign up your OpenStack Individual Contributor License Agreement
- Check that your email is listed in Gerrit identities
- Subscribe to Blazar-related projects on OpenStack Gerrit. Go to your settings and in the watched projects add stackforge/blazar, stackforge/blazar-nova and stackforge/python-blazarclient
As all bugs/blueprints are listed in Blazar Launchpad, you may keep track on them and choose some to work on.
How to keep in touch with community
- 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 on #openstack-meeting freenode IRC channel at 15:00 UTC
Your first commit to Blazar
- Checkout corresponding Blazar repository from Github
- Take a look on how Gerrit review process goes on in OpenStack (read carefully committing changes part)
- 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/#/
