openstack
/
governance
Code Issues Proposed changes

Be less proscriptive about new team size/maturity 

The new project requirements previously contained prose which was
ambiguous or misleading about when it's okay to apply to the TC for
creation of a project team. New projects with any size team working
on software at any stage of development are welcome to apply.

Change-Id: I8d80681caccee7570303c46fe603426f76254af0
This commit is contained in:
Jeremy Stanley 2015-06-19 13:37:35 +00:00
parent cd3692312f
commit b76792d816
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2,9 +2,8 @@
Requirements for new OpenStack Projects applications
======================================================
Teams in OpenStack can be created as-needed and grow organically. As the team
work matures, some technical efforts will be recognized as being part of the
OpenStack community. By becoming an official OpenStack Project, they place
Teams in OpenStack can be created as-needed and grow organically.
By becoming an official OpenStack Project, they place
themselves under the authority of the OpenStack Technical Committee. In return,
their contributors get to vote in the Technical Committee election.
@ -53,7 +52,7 @@ When considering new projects for addition, the TC will check that:
User-facing API services should support Keystone for discovery and
authentication.
* The project should have an active team of contributors
* 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