From 127389fa43c7d35924a8ed7528084b1f9eff7b8a Mon Sep 17 00:00:00 2001 From: Robert Collins Date: Wed, 15 Jul 2015 08:40:03 +1200 Subject: [PATCH] New projects have to meet all existing policies. 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 --- reference/new-projects-requirements.rst | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/reference/new-projects-requirements.rst b/reference/new-projects-requirements.rst index 129229a9a..265e9f31a 100644 --- a/reference/new-projects-requirements.rst +++ b/reference/new-projects-requirements.rst @@ -34,7 +34,8 @@ When considering new projects for addition, the TC will check that: * Open Development: * 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 cross-project teams in OpenStack * 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 -* 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. +* The project meets any policies that the TC requires all projects to + meet. For instance, the :doc:`project-testing-interface` + + +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.