Difference between revisions of "Blazar/How to contribute"
< Blazar
(→Getting started) |
|||
Line 1: | Line 1: | ||
== Getting started == | == Getting started == | ||
− | + | Read OpenStack developers guide: https://docs.openstack.org/infra/manual/developers.html#developer-s-guide | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== How to keep in touch with community == | == How to keep in touch with community == |
Revision as of 13:46, 23 February 2017
Getting started
Read OpenStack developers guide: https://docs.openstack.org/infra/manual/developers.html#developer-s-guide
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/#/