openstack/governance
Code Issues Proposed changes

Note that the TC expects some project history.

Browse Source 
The recent application by the Kosmos project [1] prompted a discussion
on whether or not a project should apply to the TC right away or if it
should have some amount of history of operating as an OpenStack project
first.  The consensus on that application was that we should wait and
let the project get going first.

This patch updates the new projects requirements to clarify this point.
As noted by ttx on [1], this guideline will henceforth be known as
"the Kosmos jurisprudence".

[1] https://review.openstack.org/#/c/223674/

Change-Id: Ifc964d09ea2107e3ecd95f9579543bcb77f457d0
Signed-off-by: Russell Bryant <rbryant@redhat.com>
This commit is contained in:
Russell Bryant
2015-09-30 10:29:28 -04:00
parent d239d76ec6
commit 5c4ff20b3c
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -58,6 +58,10 @@ When considering new projects for addition, the TC will check that:
* The project meets any policies that the TC requires all projects to * The project meets any policies that the TC requires all projects to
meet. For instance, the :doc:`project-testing-interface` meet. For instance, the :doc:`project-testing-interface`
In order to do an evaluation against this criteria, the TC expects the project
to be set up and have some history to evaluate. A few months of operating and
following these project requirements is a rough guideline for how long
to wait before applying to be approved by the TC.
Once a project has joined OpenStack, it may create additional source code 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 repositories as needed at the discretion of its Project Team Lead (PTL) without