Difference between revisions of "Governance/NewProjectTeams"

Revision as of 14:20, 9 February 2015

As the OpenStack community grows, new teams 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.

Teams and efforts

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. Teams should generally discuss on the openstack-dev mailing-list and hold IRC meetings.

As the team work matures, some technical efforts will be recognized as key parts in the completion of the OpenStack mission. By becoming an official Project Team, they 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

Working groups and efforts which want to become an OpenStack Project Team 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].

@@ Line 1: / Line 1: @@
 __NOTOC__
-As the OpenStack community grows, new teams 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 [[Governance/Foundation/TechnicalCommittee|OpenStack Technical Committee]].
+As the OpenStack community grows, new teams and efforts will emerge and aspire to become official OpenStack [[Project_Teams|Project Teams]]. This page describes the the process those efforts can follow to become a project team. This process is fully driven by the [[Governance/Foundation/TechnicalCommittee|OpenStack Technical Committee]].
 == Teams and efforts ==
-Work in the OpenStack project is organized around teams of people working in the same area. Those grow naturally and organically, and no permission is needed to create a team. Teams should generally discuss on the openstack-dev mailing-list and hold IRC meetings.
+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. Teams should generally discuss on the openstack-dev mailing-list and hold IRC meetings.
-As the team work matures, some technical efforts will be recognized as ''essential'' to the completion of the OpenStack project mission. By becoming an official ''Project Team'', they 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.
+As the team work matures, some technical efforts will be recognized as key parts in the completion of the OpenStack mission. By becoming an official ''Project Team'', they 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 ==
-Teams and efforts which want to become a project team should file a motion to the Technical Committee (email to openstack-dev ML with a heads-up email to the openstack-tc ML pointing to the -dev thread), including:
+Working groups and efforts which want to become an OpenStack Project Team should file a motion to the Technical Committee:
-* Detailed mission statement (including why their effort is essential to the completion of the OpenStack mission)
+* Propose a change to the reference/projects.yaml file in the openstack/governance repository, including:
-* Expected deliverables and repositories
+** Team name
-* How 'contribution' is measured within the project team (by default, commits to the repositories associated to the program)
+** Proposed initial PTL name (and IRC nickname)
-* Main team members
+** Team mission
-* Proposed initial project team lead (PTL)
+** 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].