openstack/governance
Code Issues Proposed changes
Files
3ca051c746cfbb1e6d149ab0b0592a68fe92028b
governance/reference/new-programs-requirements.rst
Sean Dague 3ca051c746 begin conversion to rst 
This converts 2 of the reference documents to rst, and fixes the
tox.ini so that tox -e docs creates a pretty html version of these
documents. While the publish target location has still not been
sorted this moves the ball forward in generating nicer output
for the documents.

The incubation-integration-requirements document was intentionally
left out, because it's much more active, and we should decide this
is the right approach before we impose the merge conflicts on
everyone in flight.

Change-Id: I2fefdb5efe196cdbda4555141b09e7e771e20bdd
2014-04-15 08:24:17 -04:00

1.2 KiB
Raw Blame History

Minimal requirements for new programs applications

Teams in OpenStack can be created as-needed and grow organically. As the team work matures, some technical efforts will be recognized as essential to the completion of the OpenStack project mission. By becoming an official Program, they place themselves under the authority of the OpenStack Technical Committee. In return, their contributors get to vote in the Technical Committee election, and they get some space and time to discuss future development at our Design Summits. When considering new programs, the TC will look into a number of criteria, including (but not limited to):

  • Scope
    • Team must have a specific scope, distinct from others teams scope
    • Team must have a mission statement
  • Maturity
    • Team must already exist, have regular meetings and produce some work
    • Team should have a lead, selected by the team contributors
    • Team should have a clear way to grant ATC (voting) status to its significant contributors
  • Deliverables
    • Team should have a number of clear deliverables