openstack/governance
Code Issues Proposed changes
8b3c83f281
governance/reference/new-projects-requirements.rst
Russell Bryant 5c4ff20b3c Note that the TC expects some project history. 
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>
2015-09-30 11:10:30 -04:00

3.1 KiB
Raw Blame History

Requirements for new OpenStack Projects applications

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.

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 follows the OpenStack way ("the 4 opens"):
    • Open Source:
      • The proposed project uses an open source license (preferably the Apache v2.0 license, since it is necessary if the project wants to be used in an OpenStack trademark program)
      • Project must have no library dependencies which effectively restrict how the project may be distributed or deployed
    • Open Community:
      • The leadership is chosen by the contributors to the project
      • The project has regular public meetings on IRC and those meetings are logged and published (moving to official OpenStack meeting channels once the project's application is accepted, if they're not held there already)
    • Open Development:
      • The project uses public code reviews on the OpenStack infrastructure
      • 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 rather than gratuitously competing or reinventing the wheel
      • Where appropriate, the project adopts technology and patterns used by existing OpenStack projects
    • Open Design:
      • The project direction is discussed at the Design Summit and/or on public forums
      • The project uses the openstack-dev ML to discuss issues
  • The project ensures basic interoperability with the rest of OpenStack: User-facing API services should support Keystone for discovery and authentication.
  • The project should have an active team of one or more contributors
  • The project meets any policies that the TC requires all projects to meet. For instance, the 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 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.