The Tale of 2 OpenStack contributors
•Download as PPTX, PDF•
0 likes•81 views
The second half the presentation from the #OpenStackIL event in Israel 2016
Recommended
Recommended
More Related Content
Similar to The Tale of 2 OpenStack contributors
Similar to The Tale of 2 OpenStack contributors (20)
Recently uploaded
Recently uploaded (20)
The Tale of 2 OpenStack contributors
- 1. Maish Saidel-Keesing msaidelk@cisco.com June 2, 2016 A Newbie Developer and a Frustrated Operator (Part II) A Tale of Two OpenStack Contributors
- 2. Background • Cisco • Global Services company • OpenStack Contributor @maishsk • Cloud Platform Architect • Author • Active since Havana
- 3. The Current Lay of the Land
- 4. Active Technical Contributors • People contributing Code User Committee• Operators • Users • Operators Foundation Board
- 6. Feedback Loop is Broken Trying to get feedback from an operational perspective back into the OpenStack projects has always been challenging
- 7. Dev vs. Ops mattmflickr (flickr)
- 9. 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
- 10. How Operators contribute to OpenStack today
- 11. chriszak (flickr) OPs repositories melswindow(flickr) Working Groups longitudelatitude (flickr) OPs Tags
- 12. Does any of this count as contributions to OpenStack? martinjhoward2 (flickr)
- 13. 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!!!
- 14. • 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
- 19. • 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?
- 20. We Are All OpenStack! Are We Really????
Editor's Notes
- Openstack contributions Neutron Horizon Heat Ceilometer Kolla Magnum Foundation
- This part is ‘slightly’ different than the first half Give a slight overview of why Process for contributors is defined Recognition Sense of belonging to a community
- Elaborate briefly a bit on each of these – covered in more detail in a future slide.
- This is coming from my perspective, and Operators perspective I am sure that most of the Code contributing community will disagree. There is a clear disconnect between the developer and Operator community
- Submitting bugs – simple process. Prioritizing – the only way to do that is to throw coding time at it.
- It is a put up or shut mentality. You want to make a difference – then contribute code.
- So what kind of influence do Operators have actually have on OpenStack?
- What about the UC? The UC (User Committee) has to request to be invited to attend the BOD (Board of Directors) meeting. The UC has to request to attend the TC (Technical Committee) regular meetings and will be given at maximum 4 hours a year to give recommendations and report. There is not a single word about what the UC actually can do besides participate in meeting and pass recommendations. Do these recommendations have to be accepted? Can they change anything? That is at the discretion of the TC and the Board. Operators are considered part of the User committee
- OPs repositories Monitoring Config applications Working Groups Telco Enterprise Packaging Fault toleration Large deployment Product Ops Tags
- martinjhoward2
- I have personally run Others have run The reason being – is that the ATC’s only see those who contribute code as equals One absurd is that even though I can run for a member of the committee – I cannot vote
- OpenStack stands by the Four Opens. It is the foundation on which the whole community and culture is built
- The question here which is what is a contributor. Today that is defined as code in a repo. I propose that and hope that this will change in the future.
- I have a dream. http://technodrone.blogspot.com/2016/03/we-are-all-openstack-are-we-really.html