openstack
/
governance
Code Issues Proposed changes

Clarify scope of new projects 

Now that we have the OpenStack project map, it is clear that our
description of the required scope for new projects really only
encompasses the main 'OpenStack' bucket on the map, when we have in
practice included several other classes of projects and always intended
to continue doing so.

https://www.openstack.org/assets/software/projectmap/openstack-map.pdf

This change documents the allowed purposes of new projects, using the
categories defined in the project map to describe them.

Change-Id: I02e91254fea83acbdb694dffefc7d864f0bad105
This commit is contained in:
Zane Bitter 2018-11-01 12:00:51 -04:00
parent 02f6c59590
commit bc44703a06
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -14,9 +14,16 @@ change, propose the corresponding `projects.yaml` file change for review.
When considering new projects for addition, the TC will check that:
* The project aligns with the OpenStack Mission:
The project must have a clear and defined scope. It should help further
the OpenStack mission, by providing a cloud infrastructure service, or
directly building on an existing OpenStack infrastructure service.
The project must have a clear and defined scope. It should either:
* help further the OpenStack mission by providing a cloud service;
* help further the OpenStack mission by providing a service for operators of
OpenStack clouds;
* provide deployment and lifecycle management tooling for OpenStack;
* provide packaging recipes to be used when deploying OpenStack;
* provide client-side tools to enable users to interact with OpenStack; or
* provide integration to enable adjacent systems to interoperate with
OpenStack.
* The project follows the OpenStack way ("the 4 opens"):