OpenStack was started with the belief that a community of equals, working together in an open collaboration, would produce better software, more aligned to the needs of its users and more largely adopted. It was therefore started from day 0 as an open collaboration model that includes as many individuals and organizations as possible, on a level playing field, with everyone invited to design open infrastructure software.
It was from these conditions that “The Four Opens” were born:
How we practiced the Four Opens has evolved over time and incorporates many practices: public code reviews, design summits, technical committee, and lazy consensus. The Four Opens, as practiced by the OpenStack Project, is described and officially maintained in the OpenStack governance website.
After eight years, the Four Opens proved pretty resilient, consistently managing to capture the “OpenStack Way” of doing upstream open source development. They are instrumental in the success, the quality and the visibility of the OpenStack software. Earlier this year, the OpenStack Foundation started the Four Opens Book as a way to share these learnings and how the Four Opens were initially intended for upstream, and how they proved applicable to downstream activities such as user feedback gathering, marketing, or event management. As the OpenStack Foundation grows to more generally support Open Infrastructure, the Four Opens will grow alongside it.
We welcome you to contribute and share your open source learnings as this book continues to evolve and reflect our values.