openstack/governance
Code Issues Proposed changes

New projects have to meet all existing policies.

Browse Source 
Also be clearer that the gate we want has to be on the OpenStack
infra, not in some random other place, and finally, move the ability
to make new repos from being a 'requirement' to being separate prose.

Change-Id: I38e545f8539195d79d6dfb42a8ec0d8eca435ccd
This commit is contained in:
Robert Collins 2015-07-15 08:40:03 +12:00
parent 3df3521dc1
commit 127389fa43
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
reference/new-projects-requirements.rst
View File

@ -34,7 +34,8 @@ When considering new projects for addition, the TC will check that:
* Open Development: * Open Development:
* The project uses public code reviews on the OpenStack infrastructure * The project uses public code reviews on the OpenStack infrastructure
* The project has core reviewers and adopts a test-driven gate for changes * The project has core reviewers and adopts a test-driven gate in the
OpenStack infrastructure for changes
* The project provides liaisons that serve as contacts for the work of * The project provides liaisons that serve as contacts for the work of
cross-project teams in OpenStack cross-project teams in OpenStack
* Where it makes sense, the project cooperates with existing projects * Where it makes sense, the project cooperates with existing projects
@ -54,8 +55,11 @@ When considering new projects for addition, the TC will check that:
* The project should have an active team of one or more contributors * The project should have an active team of one or more contributors
* Once a project has joined OpenStack, it may create additional source * The project meets any policies that the TC requires all projects to
code repositories as needed at the discretion of its Project Team meet. For instance, the :doc:`project-testing-interface`
Lead (PTL) without prior approval from the TC as long as the
additional source code repositories fall within the scope of the
approved project mission statement. Once a project has joined OpenStack, it may create additional source code
repositories as needed at the discretion of its Project Team Lead (PTL) without
prior approval from the TC as long as the additional source code repositories
fall within the scope of the approved project mission statement.