Governance/NewProjectTeams

As the OpenStack community grows, new workgroups and efforts will emerge and aspire to become official OpenStack Project Teams. This page describes the the process those efforts can follow to become a project team. This process is fully driven by the OpenStack Technical Committee.

Workgroups
Work in OpenStack is organized around groups of people working in the same area. Those grow naturally and organically, and no permission is needed to create a working group. Workgroups should generally discuss on the openstack-dev mailing-list and hold IRC meetings.

As the workgroup work matures, some efforts can be recognized as key parts in the completion of the OpenStack mission. By becoming an official Project Team, workgroups place themselves under the authority of the OpenStack Technical Committee. In return, their contributors get to vote in the Technical Committee election, and they get some space and time to discuss future development at our Design Summits.

Becoming an OpenStack Project Team
Workgroups which want to become an OpenStack Project Team should read the Project Team Guide first. Then check the current requirements.

If they feel like they qualify, they should file a motion to the Technical Committee:


 * Propose a change to the reference/projects.yaml file in the openstack/governance repository, including:
 * Team name
 * Proposed initial PTL name (and IRC nickname)
 * Team mission
 * Associated git code repositories
 * The commit message should optionally mention:
 * Other non-git-driven deliverables (if any)
 * How 'contribution' is measured within the project team (by default, commits to the repositories associated to the project team)
 * Send an email to the openstack-dev ML pointing to the proposed governance change, with subject prefix [tc].