Official OpenStack projects
Official OpenStack projects
- Requirements for official OpenStack projects
- Projects improve and grow independently but also strive to improve one collaborative framework: OpenStack
- Projects APIs are documented within the project
- Testable on its own
- Dashboard (horizon) and DevStack provide plugin interface for easy integration
- Core and mature Big Tent projects are tracked in the Project Navigator
- Big Tent is a code name for the official OpenStack projects
Nota
- Not all projects are currently tracked in Project Navigator. The goal, however, is for it to be an ever growing list.
Benefits of being an Official OpenStack project
- Contributors get to vote in the Technical Committee election
- Can publish to docs.openstack.org and developer.openstack.org
- The teams get space at OpenStack Summits and Project Team Gatherings (PTG)
- Get marketing from the OpenStack Foundation
- Can participate in common programs, like mentoring and internship to help with on boarding
- Get guidance from community members and leaders
- Its activities are under the oversight of the TC
Nota
- PTG: https://www.openstack.org/ptg/
- Mentoring is run by the Women of OpenStack group, where mentees are guided through the OpenStack processes.
- The OpenStack Foundation participates in internship programs as Outreachy.
- Official OpenStack projects can participate by offering topics and mentors for the interns who sign up for this program.
Core and Optional Services
- Core services are OpenStack projects and essential in every OpenStack-powered IaaS cloud or product
- Optional services are also OpenStack projects but not necessarily need to operate OpenStack depending on use cases
Nota
- Full list of Official OpenStack Project Teams: https://governance.openstack.org/tc/reference/projects/index.html
Core and Optional Services
Esercizio
- Find the requirements that must be met to be an official OpenStack project
- Tags can be associated with projects. Find out what tags are and find the current list of available tags.
Nota
- https://governance.openstack.org/tc/reference/new-projects-requirements.html
- An official project is aligned with the OpenStack Mission if it
- has a clear and defined scope
- provides a cloud infrastructure service or directly builds on an existing OpenStack cloud infrastructure service
- Follows/observes the four opens: Source, Community, Development, Design
- Describe the artifacts created by an OpenStack community team
- Processes followed, release management, etc.
References
Nota
- This slide is for reference links in case people want to get more information later. Presenters do not need to spend time on this.