|
|
(8 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | == Getting started ==
| + | This page has migrated to [https://docs.openstack.org/blazar/latest/contributor/contribution.html here]. |
− | | |
− | 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 [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 weekly meetings on #openstack-meeting freenode IRC channel at [https://wiki.openstack.org/wiki/Meetings/Blazar 15:00 UTC]
| |
− | | |
− | == Your first commit to Blazar ==
| |
− | | |
− | * 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)
| |
− | * 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/#/
| |
Latest revision as of 07:21, 7 February 2018
This page has migrated to here.