|
|
Line 1: |
Line 1: |
− | == Getting started ==
| + | This page has migrated to [http://blazar.readthedocs.io/en/latest/devref/how.to.contribute.html here]. |
− | | |
− | Read [https://docs.openstack.org/infra/manual/developers.html#developer-s-guide OpenStack developers guide].
| |
− | | |
− | == 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. Blazar-related emails must be send with '''[blazar]''' in its subject.
| |
− | * All questions may be asked on our IRC channel #openstack-blazar on [http://freenode.net freenode]
| |
− | * We also have [https://wiki.openstack.org/wiki/Meetings/Blazar weekly meetings].
| |
− | | |
− | == Your first commit to Blazar ==
| |
− | | |
− | * 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]
| |
− | * 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/#/
| |
Revision as of 02:58, 8 March 2017
This page has migrated to here.