5. #rackstackatl
• Be part of growing community
• Build your expertise
• Work with some really great people
• Find a job: everyone is hiring!
• Learn new skills
• Come to the OpenStack Summit (Paris!)
• Join the rebel alliance to help build Planet Scale Cloud!
RACKSPACE® HOSTING | WWW.RACKSPACE.COM 5
Why Contribute?
10. #rackstackatl
• Testing:
– Report issues
– Triage issues: prioritize, confirm, review incomplete or stale bugs
• Security:
– Join mailing lists, review code reviews, look for security issues, fix code
• Documentation:
– Fix documentation bugs
– Write documentation
• Designers/UIX:
– Review current features as a user,
– Design new features
• Developers:
– Keep testing, security, documentation, designers, operators, and everyone else busy
Find Something To Contribute
11. #rackstackatl
• Launchpad Account: https://login.launchpad.net/+new_account
– Add SSH keys to Launchpad account
– Launchpad and Gerritt accounts are the same
• Join OpenStack Foundation: https://www.openstack.org/join/
• Sign Contributor’s License Agreement: https://review.openstack.org/#/settings/agreements
– https://review.openstack.org/static/cla.html
• GitHub Account: https://github.com/
– Install and configure git locally
– Install and configure git-review locally
• Use the same email address for all your accounts!
• https://wiki.openstack.org/wiki/HowToContribute
Do This Once
11
13. #rackstackatl
1. Find some work to do.
2. Create a local git branch based on master.
3. Work work work.
4. Create a single commit based on your local branch.
5. Make a patch using git review that’s pushed to gerrit (review.openstack.org).
6. Wait for reviews (work on other patches).
7. Address reviews (work work work).
8. Encourage two core members give it a +2 vote and click Approved (work on other patches).
Basic Workflow
13
14. #rackstackatl
• Keep line length at 80
• No period at the end of the first line
• Insert special text:
– Closes-Bug: nnnnnnn
– Partial-Bug: nnnnnnn
– Bp:<text-from-Launchpad-URL>
– DocImpact
– Co-Authored-By: <name@example.org>
Commit Messages Guidelines
14
15. #rackstackatl
• Log in to http://review.openstack.org.
• Enter comments inline.
• Click Review button to publish comments.
Review Issues
15
16. #rackstackatl
1. Get the six-digit patch number from review.openstack.org, copy it.
2. At the command line, change to the directory where the repo is stored.
3. Enter:
$ git review -d nnnnn
Reviewing Locally
16
17. #rackstackatl
• Mailing lists:
– 12 major lists (General, Announcements, Operators, QA, Foundation, Security, Community, Translation, etc.
– Sign up to as many as you want to
– Lurk or participate, up to you
– Tip: setup filters
• IRC
– Freenode
– 42 different channels
• Ask OpenStack: ask.openstack.org
• Design Summit
• Meetups
RACKSPACE® HOSTING | WWW.RACKSPACE.COM 17
Communications
20. #rackstackatl
• Get a copy locally
git checkout master; git remote update; git pull origin master
git review –d nnnnnn
• Work work work edit edit
• Push back up to gerrit (review.openstack.org)
git commit -a --amend
git review -v
Demo Patching a Patch
20
21. #rackstackatl
• In the Devstack-env Cloud Server:
git checkout master; git remote update; git pull origin master
git checkout -b bug-1188073
• (You’ll need to add a public key and install git review again.)
• Work work work work edit
git commit -a
git commit -a --amend
git review -v
Demo Working on a Bug
21
Notas do Editor
OpenStack is cloud. We are at theOpenStack summit. Make a joke.
Since the beginning of time, OpenStack hadall those contributions
Need to do these things only onceAll are freeCLA different for companies and government peopleUse the same email EVERYWHERE!