Governance/OldModel

Obsolete governance model
 * 1) !wiki caution

This governance model was replaced in September 2012 by a new Governance under the umbrella of the !OpenStack Foundation.

= Previous OpenStack Governance Model =

Governance for the Individual OpenStack Projects
This applies to Compute (Nova), Storage (Swift) and Image Repository (Glance) and any future projects added by the OpenStack Project Policy Board.

Each of the projects under OpenStack will be guided by the following principle:

"Each project community should be self-managing by the contributors, and all disputes should be resolved through active debate and discussion by the community itself."

However, there will be times that a debate cannot be clearly resolved. In those times, definitive action is preferable to stalemate. We believe that the person best positioned to rally the community to a decision is a developer anointed by their respective community to do so based upon their expertise and contributions to the project. Therefore, each project shall elect a Project Technical Lead ("PTL") every 6 months. Those elections will be held 4 weeks prior to each design summit, with nominations due 5 weeks prior to the summit and elections held open for no less than three days. Anyone who has submitted code which has been accepted into the respective project’s trunk is eligible to run for a PTL seat, and to vote for the PTL. Sitting Project Technical Leads are eligible to run for re-election each cycle, provided they continue to meet the criteria.

The PTLs are also entrusted with the responsibility for determining if other governance models are more appropriate for their project. For example, having additional elected positions or formal technical committees – or none at all. The PTLs should actively and continually engage with their project's community to determine how to evolve their governing model.

Each of the elected PTLs will hold seats on the OpenStack Project Policy Board ("PPB"). Note: The role of the OpenStack Project Policy Board (formerly "Project Oversight Committee") is defined in detail in the next section.

The active leadership of the PTLs is paramount if each project is to succeed. Should the community express concerns about the leadership of their respective PTLs, the PPB can remove them and call a new election. This should be reserved only for dire situations in which a PTL is significantly failing in their duties and commitments to the project.

Should a debate arise between the various projects, it is expected that the PTLs will get together and resolve it to their satisfaction. Should they not be able to come to a resolution, they may at their option and as members of the PPB ask for that body to vote to resolve.

The OpenStack Project Policy Board (formerly known as the "Project Oversight Committee")
The goal of OpenStack is to deliver "open source software to build private and public clouds." Delivering on this mission will require active planning and thought from all members of the community – the developers, the users and the participating organizations. It will also require regular consideration of additional affiliated and core projects being added to OpenStack, and maximizing efficiency and compatibility across them as they grow.

The PPB is being established to manage this effort. It has the following primary responsibilities:


 * 1) Definition and ownership of the OpenStack mission and vision.
 * 2) Coordination and alignment across OpenStack projects and community driven requirements.
 * 3) Managing the process for adding additional projects both to the incubation program and to the core set of projects, assuring compatibility with OpenStack's mission.
 * 4) Ensuring inter-project architectural consistency and coherent API definition.
 * 5) Establishing policies to maximize efficiency across projects and assuring compatibility across projects.

The PPB is not tasked with overseeing the architectural or other technical decisions of the individual projects. As stated under "Governance for the Individual OpenStack Projects", each project community is entrusted with the responsibility for making the best technical decisions for their respective project and no other governance body is being established to assume that responsibility.

The composition of the PPB will be as follows:


 * 1) One PTL from each project as elected by the respective project development communities.
 * 2) Five General Members, elected to 1 year terms.  To stagger the elections, elections for two of the seats will be held prior to the annual Spring Design Summit, while the other three seats will be up for election prior to the annual Fall Design Summit. As with PTLs, elections will be held 4 weeks prior to the applicable design summit, with nominations due 5 weeks prior to that summit, and elections held open for no less than three days.  Any registered member of an OpenStack Launchpad group is eligible to run and vote in these elections.  The five individuals receiving the most votes will assume these seats.  If an individual should happen to be elected as both a PTL and General Member of the PPB, then they will take their PTL seat only and the elected General Member seat will go to the next highest vote getter in the most recent election.
 * 3) Four General Members will be appointed by the OpenStack's primary sponsor Rackspace.  One will be appointed Chair and bear responsibility for maintaining the PPB's agenda, schedule, and engaging the broader community regarding key decisions to inform and solicit feedback.

As OpenStack grows, the structure of elected and appointed seats will be recalibrated. It is our intention to ensure that the PPB contains the appropriate mix of representatives from the development communities, participating organizations, users and other active OpenStack constituents.

The PPB is required to convene regular meetings, which are open to the public. These regular meetings are open to the public in the IRC channel #openstack-meeting. PPB members are expected to participate in at least 75% of these meetings during their term. Details regarding the PPB and its meetings can be found here: http://wiki.openstack.org/Governance/PPB

The Advisory Board
Many commercial and public entities are investing significant resources in OpenStack. Fostering its mission is very important, and, given their sponsorship, they should be represented in the governance structure. In addition, OpenStack would like to take advantage of the expertise of technical and open source experts in achieving its mission.

The Advisory Board (“AB”) is being established to represent these groups. It has the following functions:


 * 1) Provide guidance on the OpenStack mission
 * 2) Provide guidance on the OpenStack governance structure
 * 3) Provide guidance on the OpenStack brand usage guidelines
 * 4) Provide guidance on increasing OpenStack adoption
 * 5) Evangelize on behalf of OpenStack

The initial board will be appointed by Rackspace. Rackspace is appointing the initial members using its best judgment. Following the initial appointment, the Advisory Board will have authority for adding members according to the following principles:


 * Entities who have a major commercial commitment to OpenStack
 * Experts who can provide relevant guidance to OpenStack

All members selected for the Advisory Board will retain their seats unless a majority of the board votes for their removal.

The Advisory Board will meet at every Design Conference. Should a member not be able to attend, they are expected to send an alternate representative from their organization. Additional meetings will be held as needed.