5662d84690
- no need to refer to github; point to the main repositories on git.openstack.org and remove the requirement for a github account in order to contribute; - update few links which have been moved around and fix at least the associated message of a link; - link to the website for HTTPie. Change-Id: Ib310815d346e2364de1a2282f3f1e2d94590c3d2
2.4 KiB
2.4 KiB
How to Participate
Getting started
- Make sure that your local git is properly configured by executing
git config --list. If not, configureuser.name,user.email - Create account on Launchpad (if you don't have one)
- Subscribe to OpenStack general mail-list
- Subscribe to OpenStack development mail-list
- Create OpenStack profile
- Login to OpenStack
Gerrit with your Launchpad id
- Sign OpenStack Individual Contributor License Agreement
- Make sure that your email is listed in identities
- Subscribe to code-reviews. Go to your settings on http://review.openstack.org
- Go to
watched projects - Add
openstack/sahara,openstack/sahara-extra,openstack/python-saharaclient, andopenstack/sahara-image-elements
- Go to
How to stay in touch with the community
- If you have something to discuss use OpenStack
development mail-list. Prefix the mail subject with
[Sahara] - Join
#openstack-saharaIRC channel on freenode - Attend Sahara team meetings
- Weekly on Thursdays at 1400 UTC and 1800 UTC (on alternate weeks)
- IRC channel:
#openstack-meeting-alt(1800UTC) or#openstack-meeting-3(1400UTC) - See agenda at https://wiki.openstack.org/wiki/Meetings/SaharaAgenda
How to post your first patch for review
- Checkout Sahara code from its repository
- Carefully read http://docs.openstack.org/infra/manual/developers.html#development-workflow
- Pay special attention to http://docs.openstack.org/infra/manual/developers.html#committing-a-change
- Apply and commit your changes
- Make sure that your code passes
PEP8checks and unit-tests. Seedevelopment-guidelines - Post your patch for review
- Monitor the status of your patch review on https://review.openstack.org/#/