In this session, I share a formula for becoming a highly valued contributor to an Openstack community project. As the founder and PTL of both Solum and Magnum, I have had the freedom to try a bunch of things to run projects, and to on-board new contributors. You will learn all of the things you can do to quickly become a valued and respected member of your favorite project. This is proven, and guaranteed to work!

1. Presented By: Adrian Otto
7 Habits of Highly Effective Contributors

2. Adrian Otto
•Distinguished Architect, Rackspace
•Chair of OpenStack Containers Team
•PTL of Magnum (Containers-as-a-Service for OpenStack)
•PTL of Solum (SDLC Automation for OpenStack)
•OASIS CAMP Technical Committee (Cloud Standards)

3. Spring 2010, Austin Texas
First OpenStack Design Summit

4. !4

5. !5

6. !6

7. !7
Democratic Decisions In OpenStack

8. !8
Open Community
Open Design
Open Development
Open Source
OpenStack :: We do it in the open!

9. • PTL roles are elected by all contributors to each OpenStack project
• Code is merged based on a democratic voting scheme among core reviewers (+2, +2,+A)
• Core reviewers are selected by the electorate
• Design is done in public sessions at Summit and Midcycle Meetup events, and by spec proposals
• Top level governance is handled by the Technical Committee, elected by ATCs.
• Foundation business is managed by the OpenStack Board of directors, elected by Foundation members
!9
Meritocracy and Democracy

10. !10
How Things Get Done

11. • No Sprints
• Simple Release Train
• No Card Wall
• Bug Tickets and Blueprints
• No Project Manager or Scrum Master
• PTL
• No Release Manager
• Core Reviewers and PTL
!11
How This Is Different From Agile

12. • Technical Committee (TC) decides what projects are added.
• Governance power is mostly here.
• Core Reviewers have the power to work together to merge code.
• PTLs can approve or reject blueprints, and set the project direction.
!12
Where Does Influence Come From?

13. • Fastest way to illustrate most ideas
• Most patches are merged after 2 revisions
• Patches can be abandoned
• Okay to have multiple implementations, and only merge one
• -2 vote is a special case, rarely used and extremely powerful
!13
Submitting Code For Review

14. !14

15. www.rackspace.com
7 Habits of Highly Effective Contributors
!15

16. !16
1 Use IRC
•Idle
•Greet
•Ask
•Answer

17. !17
2 Attend Meetings
•Regularly
•Actively
•Discuss

18. !18
3 Use Mailing List
•Read
•Ask
•Answer
•Open Mind

19. !19
4 Do Code Reviews
•Every Day
•Constructive
•Quality
•Open Mind

20. !20
5 Use Bug Tickets
•Subscribe
•Claim/Work
•Open Before Patch

21. !21
6 Use Blueprints
•Propose
•Discuss
•Claim/Work

22. !22
7 Contribute
•Code
•Docs
•Testing
•Consistent
•Small Patches (<400)
•Link to bugs/Blueprints

23. !23
7 Contribute
6
5
4
3
2
1
Use Blueprints
Use Bug Tickets
Do Code Reviews
Use Mailing List
Attend Meetings
Use IRC

24. THANK YOU
RACKSPACE® | 1 FANATICAL PLACE, CITY OF WINDCREST | SAN ANTONIO, TX 78218
US SALES: 1-800-961-2888 | US SUPPORT: 1-800-961-4454 | WWW.RACKSPACE.COM
© RACKSPACE LTD. | RACKSPACE® AND FANATICAL SUPPORT® ARE SERVICE MARKS OF RACKSPACE US, INC. REGISTERED IN THE UNITED STATES AND OTHER COUNTRIES. | WWW.RACKSPACE.COM

25. WE’RE HIRING!
bit.ly/RackerTalent
Expo Hall Booth P-11
Python OpenStack Engineers
C, C++ Linux Systems Engineers
Ruby DevOps Engineers
Java Frontend & Backend
DevelopersC#, .NET Software Developer in Test
JavaScript, CSS, HTML iOS/Android Development
Twisted, Backhone Data Scientist
Angular.JS, Ember.js, Node.js Field Sales Specialist
Restful/JSON/XML Strategic Account Executive
Closure, Scala, Erlang
Hadoop, MongoDB, MySQL
Solution Architect
Data Visualization