Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

3.
Agenda
● Why contribute to OpenStack?
● Ways in which you can contribute
● Steps to contribute
● Questions?

4.
Why should You contribute to Openstack?
● Beginner friendly and active contributor community
● Work on the project being used by millions
● Get to learn from experienced developers around the world
● Rich set of guidelines and documentation
● Huge bunch of interesting things to learn

6.
Ways in which you can contribute?
You can work on a wide range of things:
● Documentation
● A New Feature
● Help Fix Bugs
● Report Bugs
● Bug Triaging
● Translation
https://wiki.openstack.org/wiki/How_To_Contribute

9.
2. Sign Up for Foundation Membership at the OpenStack Foundation
● Complete The Individual Member Application
● Read and Sign the terms of becoming an OpenStack Foundation Individual Member.
https://www.openstack.org/join

10.
3. Gerrit Review System
● Log into with your Launchpad account.
● Use the same username for Gerrit as the Launchpad username.
● Sign the appropriate Individual Contributor License Agreement
● Upload your Public SSH Key to review.openstack.org

20.
Step 4: Fixing the bug
● Try to reproduce the bug using Devstack.
● In case of doubts, add a comment to the bug report.
● If you need more assistance, you can seek help on IRC or Mailing List
● IRC Channel List : https://wiki.openstack.org/wiki/IRC
● Mailing Lists : https://wiki.openstack.org/wiki/Mailing_Lists

24.
Step 6: Sending the patch upstream for review
1. $ git review
You will get the link where your patch is uploaded for review on review.openstack.org
2. Address the review comments and resend the patch if required.