OpenStack is a community. It takes a community to develop such a massive ecosystem, but the sheer size of it also presents a barrier. This session will present two aspects of OpenStack Contributions. From a Developer's perspective you will learn how to make your first OpenStack contribution, from your creating your account to identifying low hanging fruits, or even trying to push a new project to the ecosystem. From the Operator's perspective, we have not yet reached the pot of gold at the end of the rainbow. Operators are still not yet accepted as equal members of the OpenStack community. We will go over some of the history, current issues, what is considered a contribution to OpenStack, and how this should, and can change.

1. How it All Started in Tel Aviv?
“We Need Three OpenStack
Development Scrum Teams Up and
Running by the End of March”

2. What Did We Do?

3. A Tale of Two OpenStack Contributors: A
Newbie Developer and a Frustrated Operator
(part I)

4. A Few Words about AT&T

5. AIC – AT&T Integrated Cloud

6. What Did We Do?
•
•
•
•
•
•

7. I Want to Contribute!
•
•
•
•
•

8. Joining the Community

9. Communication

10. Contribution

11. Choose Your Change

14. It’s Time to Code!

15. So What Have We Learned Today?
•
•
•

16. Thank You

17. Maish Saidel-Keesing
msaidelk@cisco.com
June 1, 2016
A Newbie Developer and a Frustrated Operator (Part II)
A Tale of Two OpenStack
Contributors

18. 18
Background
• Cisco
• Global Services company
• OpenStack Contributor
@maishsk
• Cloud Platform Architect
• Author
• Active since Havana

19. 19
The Current Lay of the Land

20. 20
Active Technical Contributors
• People contributing Code
User CommitteeOperators
• Users
• Operators
Foundation Board

21. 21
Why Frustrated??
Justanotherhuman
(flickr)

22. 22
Feedback
Loop is
Broken
Trying to get feedback
from an operational
perspective back into the
OpenStack projects has
always been challenging

23. 23
Dev vs. Ops
mattmflickr (flickr)

24. Influence is everything
HumongoNationphotogallery (flickr)

25. 25
Foundation Board of Directors
▪ Have influence on the commercial aspect of OpenStack
Project Team Leads (PTL)
▪ Technical direction in each project
Technical Committee
▪ Overall technical leadership for ALL OpenStack Projects

26. 26
How Operators contribute
to OpenStack today

27. 27
chriszak (flickr)
OPs repositories
melswindow(flickr)
Working Groups
longitudelatitude (flickr)
OPs
Tags

28. 28
Does any of
this count as
contributions
to OpenStack? martinjhoward2 (flickr)

29. 29
Why Does this
Matter?
Operators are the ones
that suffer the pain, daily.
They have a different
perspective on an overall
solution.
They should have a say in
the technical direction
Community contribution is
NOT ONLY CODE!!!

30. 30
•Elections twice a year
• Any foundation member can run
• ATCs are the only ones allowed to vote
To date No Operator has ever been
elected!
Technical committee

31. 31

32. 32

33. 33

34. 34

35. 35
• OPs contributions – fully recognized
• ATC eligibility
• TC elections
• UC contributions – fully recognized
• ATC eligibility
• TC elections
https://wiki.openstack.org/wiki/NonATCRecognition
Future – Where Should the Community Go?

36. We Are All OpenStack!
Are We Really????