Jump to: navigation, search

Difference between revisions of "Governance/NewProjectTeams"

(Created page with "__NOTOC__ As the OpenStack community grows, new teams and efforts will emerge and aspire to become official OpenStack Programs. This page describes the the process those e...")
 
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
As the OpenStack community grows, new teams and efforts will emerge and aspire to become official OpenStack [[Programs]]. This page describes the the process those efforts can follow to become a program. This process is fully driven by the [[Governance/TechnicalCommittee|OpenStack Technical Committee]].
+
As the OpenStack community grows, new workgroups 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 ==
+
== Workgroups ==
  
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. Workgroups 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 ''Program'', 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 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 a program ==
+
== Becoming an OpenStack Project Team ==
  
Teams and efforts which want to become a program 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:
+
Workgroups which want to become an OpenStack Project Team should read the [http://docs.openstack.org/project-team-guide/ Project Team Guide] first. Then check the current [http://governance.openstack.org/reference/new-projects-requirements.html requirements].
  
* Detailed mission statement (including why their effort is essential to the completion of the OpenStack mission)
+
If they feel like they qualify, they should file a motion to the Technical Committee:
* Expected deliverables and repositories
+
 
* How 'contribution' is measured within the program (by default, commits to the repositories associated to the program)
+
* Propose a change to the reference/projects.yaml file in the openstack/governance repository, including:
* Main team members
+
** Team name
* Proposed initial program lead (PTL)
+
** 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].

Latest revision as of 13:36, 16 June 2016

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].