Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated some terminology, took out names of initial members and instead pointed to web pages.

...

  • technical meritocracy because technical teams manage themselves to do what is technically right for the community. People who make the most contributions to their teams have the most influence. In addition, technical project leaders and steering team members are elected by active contributors.

  • benevolent stewardship because ON.lab’s board of directors retains the right to select the chairman of the ONOS advisory board and the leaders of the technical steering team, release management team, and community team. ON.Lab anticipates that it will rarely exercise this right, and that the project will operate autonomously; however, it retains this right in order to ensure that the project is successful. The ONOS project resides with is a collaborative project in the Linux Foundation. Funding for the core engineering team comes from the ONOS partnership set up by the Open Networking Laboratory ("ON.Lab"), a nonprofit public benefit corporation.

     

...

The ONOS project is governed by four teams and a board of advisors. 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.


ONOS Board

...

The board of advisors is a group of representatives from the member partner organizations. It is governed by the Chairman of the Board. The board of advisors has the following roles and responsibilities:

  • Strategic direction

  • New member recruiting

  • Conflict resolution between teams

  • Ambassadors for ONOS

  • ONOS trademark management 

  • Elect the lead of the Use Case Steering Team

The board of advisors leaves all technical decisions to the technical steering team in the spirit of open source technical meritocracy practice.

The governance document for the board of advisors can be found here.

Steering Teams

...

  • Open Networking Lab - the board of directors and employees of Open Networking Laboratory
  • Service Providers - the primary end users of the ONOS derived products
  • Vendors - the companies who build products based on ONOS for consumption by the service providers
  • Community - independent members of the community

...

ONOS Board

Composition of the Board

...

The Board of Advisors is composed of a chairman and one member from ON.Lab 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 15. Each organization may only have one member on the board. The initial current board is

 

  • Chairman - Guru Parulkar

  • AT&T - Al Blackburn

  • NTT Communications - Yukio Ito

  • Ciena - Francois Locoh Donou

  • Cisco - David Ward

  • Ericsson - Anita Frisell

  • Fujitsu - Masayuki Seno

  • Huawei - Jun Zha

  • NEC - Shunichiro Tejima

  • SK Telecom - TBD

found here.

Elections

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 of the board must approve the nomination. Board members are (re) elected every year. The first election will be in February 2015Elections 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 Board of Directors will select a new Chairman.

...

Initial Membership of Technical Steering Team

...

The membership will initially be the following people:

...

Thomas Vachuska, Team Lead

...

Ali Al-Shabibi - southbound maintainer

...

Madan Jampani - core maintainer

is found on the home page.

Roles

  • Submitter - submits code to Gerrit. Submissions must be reviewed and approved by a committer. Anyone, who has signed the CLA, can be a submitter. Submitters do not have voting rights.

  • Committer - allowed to move code submissions from Gerrit into the official ONOS repository. Submitters may be nominated at any time, by any person, to become a committer. Approval to change role from a submitter to a committer is given by the technical steering team.

  • Maintainer - is a committer with responsibility for the integrity of some portion of the ONOS core codebase. Maintainers volunteer, but must be approved by the technical steering team. A list of maintainers and their area(s) of responsibility is kept on the technical steering team wiki page.

  • Team leader - is a committer with the responsibility for the integrity of the the overall ONOS core codebase. May also be a maintainer.

...

The technical steering team members will be elected on a yearly basis. The first member election will be held in February 2016. At Elections are held in the first quarter of each calendar year. At the time of election the following occurs:

...

  • If the ONOS Chief Architect leaves ON.Lab for any reason the ON.Lab 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 the ON.Lab board of directors reserves the right to remove them from their role on the technical steering team.

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

Technical Advisory Group (currently not used)

The Technical Steering Team may organize a technical  advisory group of 3-5 architects that are leading SDN. They do not have to have any affiliation with the ONOS project. The goal of this group is twofold: solicit input from other experts in the field to guide the ONOS architecture and generate advocacy in the larger ecosystem for the work being done with ONOS. The people on the technical advisory group are all chosen by the technical steering team. 

...

Each service provider has one representative on the use case steering team.

The team will initially include the following people:

  •  AT&T - Tom Anschutz, team lead

  • NTT - Yoichi Sato

  • SK Telecom - TBD

members are found on their home page.

Membership Additions

The team representatives will be appointed 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 Advisors. How each service provider chooses their representative is outside the scope of this document. The first election of team lead and members will be held in February 2015Elections 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 nominated by anyone, including themselves, to be the team lead.
  • The Advisory Board votes on the candidates to select the team lead.

...

The membership will initially be the following people:

  • Bill Snow, Team Lead

  • Patrick Liu

  • Mingeun YoonPrajakta Joshi

Team Lead Election

The team lead is initially Bill Snow. Starting Elections are held in February 2016 the the first quarter of each calendar year. The team lead of the release management team will be (re) elected by the technical committers. In February 2016during 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.

...

The membership will initially be the following people:

  • Prajakta JoshiDavid Boswell, Team Lead

  • Bill Snow

Team Lead Election

The team lead is initially Prajakta Joshi. Starting in February 2016 the David Boswell. 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. In February 2016an 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.

...

When conflicts cannot be resolved in a subproject, the appropriate steering team will take responsibility to make the decision for the subproject. If the steering team cannot reach agreement then the board of advisors will Board  will make the decision.