Version 2.0, Bill Snow (ON.LabONF), Scott Nicholas (Linux Foundation)

Ratified at ONOS board meeting 17 June 2016

Changed ON.Lab references to ONF August 4, 2017 after the assets of ON.Lab were transferred to ONF.

Governance Model

Governance of the ONOS^® project is intended to foster a technical meritocracy within the context of stewardship by the ONOS Chief Architect and the ON.Lab ONF Board of Directors.  ON.Lab ONF is a nonprofit public benefit corporationorganization, and provides engineering resources on behalf of the ONOS Project. 

...

The technical steering team is responsible for all technical decisions in the project. They are responsible for the content and structure of the code base and for all technical priorities with respect to the code base. The ONOS chief architect (“Chief Architect”) is the team lead of the technical steering team. The ON.Lab ONF board of directors reserves the right to remove and replace the Chief Architect at any time.

...

The release management team owns the release management process and is responsible to make sure that releases happen on time with the highest quality. The release management team owns the responsibility for determining the priority of features targeted for a particular release. The release management team lead is elected by the voting community. The ON.Lab ONF board of directors reserves the right to approve or veto this selection, and to appoint the team lead.

...

The community steering team is responsible for the care and feeding of the community. It is responsible to address community issues, to grow the community and to make sure that the community thrives. The community steering team lead is elected by the voting community. The ON.Lab ONF board of directors reserves the right to approve or veto this selection, and to appoint the team lead.

...

The Board is composed of a chairman and one member from ON.Lab ONF and each partner organization. In addition, each partner may name one alternative member to attend meetings in case the primary member is unable to attend. The maximum number of partner board members is 20. Each organization may only have one member on the board. The current board is found here.

...

The Chairman of the Board is chosen by the Open Networking Laboratory Board of Directors. Each organization is responsible for nominating their board member. The Chairman must approve the nomination. Board members are (re) nominated/approved every year. Nominations/approvals are held in the first quarter of each calendar year. If any board member must leave before the end of their term, their organization will nominate a new member and that member must be approved by the Chairman of the Board. If the Chairman of the Board must step down, then the ON.Lab ONF Board of Directors will select a new Chairman.

...

There are three classes of voting: ON.LabONF, Vendors and Service Providers. Each receives votes according to the following allocation of 100 votes. Votes may be fractional.

...

• The Chief Architect is (re) appointed by the board of Open Networking Laboratory.
• The Chief Architect decides the appropriate size of the technical steering team. The ON.Lab ONF board of directors has veto power on the choice of size.
• The voting community elects TST members to the open positions.
• The full election procedures are documented here.

...

• If the ONOS Chief Architect leaves ON.Lab ONF for any reason the ON.Lab ONF board of directors reserves the right to appoint a new ONOS Chief Architect.

• If any member of the technical steering team changes their corporate affiliation during their tenure and, as a result, joins an organization that already has (on a consolidated basis) direct representation on the TST, the ON.Lab ONF board of directors reserves the right to remove them from their role on the technical steering team.

• The ON.Lab ONF board of directors reserves the right to select a new Chief Architect at any time.

...