Questions about Questions
How to coordinate thousands of developers?
Who decides where to go?
How can you join in there?
Why should you do this?
Board of Directors
Overview about finance and strategy
Protects trademark rights for OpenStack
Consists of
Representative of Platin Sponsors
Elected representative of Gold Sponsors
Elected Individuals
Public Board Meetings ~4 times the year
Technical Committee
Overview about technical matters and upstream open source developement
13 members elected by Active Technical Contributor (ATC)
Published Guiding Principles like 4 O's: Open Source * Open Design * Open Developement * Open Community
Maintains OpenStack Project Teams
User Committee
Represents Downstream Users of OpenStack
3 elected members
6 Teams/Working Groups
75+ User Groups worldwide
OpenStack Project Teams
Maintain a OpenStack Project (e.g. Nova, Neutron)
Report to Technical Comitee
Over 60 Project Teams
Meetings on a weekly base
New teams on demand
Project Team Lead (PTL)
Elected for each cycle
Leads the Project Team
Fights for Release Goals
Fights for Release Cycle
Monitor Bugs and Blueprints
Plan Team Meetings
Participate TC Meetings
Core Reviewer
Proposed and set-in by PTL
PTL Support
Review Proposals
Rate and solve bugs
Develop new functions
Able to merge code
Participate Team Meetings
Support others
Active Technical Contributors (ATC)
Part of Foundation Individual Members
Contributed in an official project in the last two release cycles
Common Source-Code, Translations and Documentation as well
Mentioned in the Release Notes
We note
Decision makers on all levels elected
Tasks clearly defined
For each problem is a solution
OpenStack Release Zyklus
Each 6 months a new Release
Milestone 1/2 Spec Freeze (~ 6 weeks - 3 months)
Milestone 3 Feature Freeze/Soft String Freeze (5 months)
RC1 Hard String Freeze (3 weeks before Release)
Final RC (1 week before Release)
Release (0) + Deadline (+2 weeks) = Current
Maintenance Phase 2 (+6 months)
Maintenance Phase 3 (+12 months) - EOL
++ long term support
Communication
Mailing-Lists for announcements and discussions
http://lists.openstack.org
Wiki for permanent information storage
https://wiki.openstack.org
IRC for real time communication
http://eavesdrop.openstack.org/
Motivation
Full-time developer with mandate
Interested leisure programmer
Guides
The 4 O (Open Source, Open Design, Open Developement, Open Community)
Summit
Project Teams Gathering
Guides 2
Peer Review (Gerrit)
Gate checks (Zuul)
ChatOps (Gerritbot)
References
https://governance.openstack.org/tc/reference/opens.html
https://docs.openstack.org/infra/manual/developers.html
https://zuul-ci.org/
What did we learn?
From the community, many working methods can be learned
The tools used are open source
This only works through participation
Chodźmy!
Made with Slides.com