Page History

...

 version 1.0 ratified at 2/9/15 board meeting 

version 1.1 (below) has been edited for the following:

Remove listing of initial team members. Instead point to the steering team pages.

Clarify voting processes. For example, there is no need to vote for use case steering team members. By definition they are the board members from the service providers.

Clarify definition of roles to be consistent with the roles defined by the technical steering team.

Governance of the ONOS™ project is a hybrid. It attempts to take what has worked well for open source projects and leave out what didn’t work so well. Mostly, it is governed as a technical meritocracy – those who contribute the most have the most influence on the technical direction and decisions. There is also an element of benevolent stewardship. This is what gives the project its strong vision, goals, and technical shepherding. More specifically, ONOS governance is

...

The ONOS project is governed by four teams and a board of advisorsof directors. The four teams are the technical steering team, the use case team, the release management team, and the community team. ONOS subprojects are formed as part of one of the four teams.

...

The use case steering team is responsible for choosing and prioritizing the use cases worked on by the community.

...

Each service provider has one representative on the use case steering team.The current team members are found on their home page.

Membership

...

The team representatives will be appointed are by definition the group of board members from the service providers. The lead is elected on a yearly basis by their organization, or when they join ONOS, except for the team lead who will be elected every year by the Board of Advisorsthe board. How each service provider chooses their representative is outside the scope of this document. Elections are held in the first quarter of each calendar year. At the time of the election, the following will take place:

• Members of the team are The team lead is nominated by anyone, including themselves, to be the team lead.
• The Board votes on the candidates to select the team lead.

...

• Requirements database maintenance (Jira)

• Requirements acceptance process

• Requirements prioritization process

• Release content prioritization

• Release process (how subprojects get project code integrated)

Initial Membership

The membership will initially be the following people:

• Bill Snow, Team Lead

• Patrick Liu

• Mingeun Yoon

Team Lead Election

The team lead is initially Bill Snow. Elections are held in the first quarter of each calendar year. The team lead of the release management team will be (re) elected by the technical committers. during an election, the following will occur: 

...

• proactively checking in with members to see what can be improved

• starting projects to improve the community

• providing a structured way to handle conflict in the community

• making sure communication tools work well for the community

• owning the on-ramp process for the community

...

Team

...

The membership will initially be the following people:

• David Boswell, Team Lead

• Bill Snow
  

Team Lead Election

The team lead is initially David Boswell. Elections are held in the first quarter of each calendar year. The team lead of the community steering team will be (re) elected by the technical committers. In an election, the following will occur:

• Lead candidates are nominated by anyone, including themselves.
  
• The technical community of committers and maintainers votes to elect the lead. Each voter has one vote.

Membership

Anyone may volunteer to be a member of the team. It is up to the team lead to decide how large the team is and who is accepted onto the team.

...