Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
Governance Model - DRAFT FOR REVIEW ONLY - NOT FINAL
Governance of the ONOS 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 dictatorship. This is what gives the project its strong vision, goals, and technical shepherding. More specifically, ONOS governance is
A 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.
A benevolent dictatorship 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.
...
Provide an environment that thrives on technical meritocracy. Merit is based on technical contribution, not on financial contribution.
- Have strong technical vision and shepherding. This ensures architectural integrity of the codebase.
Provide a framework for ONOS teams and projects – how they are started, how they are managed, how members are elected, how conflicts are resolved, how they are disbanded when no longer needed.
Be clear on how ONOS software evolves – how code is code added to (or removed from) the project.
Be clear on how decisions are made and conflicts resolved in the community.
Make it easy for community members to participate.
Avoid bureaucracy.
- Create a great codebase.
...
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 is the team lead of the technical steering team. The ON.Lab board of directors reserves the right to remove and replace the lead of the technical steering team at any time.
Email: onos-tech-steering-team@onosproject.org - Archive
...
The use case steering team is responsible for prioritizing the use cases that will be developed. They are responsible for the prioritization of all use cases and for all capabilities within those use cases. The use case steering team provides the customer requirements to the ONOS technical team. The use case steering team is lead by an elected representative nominated from the group of members who are customers (in this case, service providers).
Email: onos-use-case-team@onosproject.org - Archive
...
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 lead elected by the ONOS product manager, or the person appointed by the technical committers. The ON.Lab board of directors reserves the right to approve or veto this selection, and to appoint the team lead.
Email: onos-release-team@onosproject.org - Archive
...
The community advocacy team is responsible for the care and feeding of the community. They are It is responsible to address community issues, to grow the community and to make sure that the community thrives. The community advocacy team lead is lead by the ONOS community manager, or the person appointed by the elected by the technical committers. The ON.Lab board of directors reserves the right to approve or veto this selection, and to appoint the team lead.
Email: onos-community-team@onosproject.org - Archive
...
The Board of Advisors is composed of a chairman and one member from ON.Lab and each partner organization. The maximum number of board members is 15. Each organization may only have one member on the board. The initial board is
Chairman - ON.Lab Executive DirectorGuru Parulkar
AT&T - Al Blackburn
NTT Communications - Yukio Ito
Ciena - Francois Locoh Donou
Ericsson -
Fujitsu - Seno Masayuki
Huawei - Jun Zha
Intel -
NEC - Shunichiro Tejima
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 December February 2015. 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.
...
There are three classes of voting: ON.Lab, Vendors and Service Providers. Each receives voting chits votes according to the following allocation of 100 chitsvotes. Chits Votes may be fractional.
ON.Lab - 10 chitsvotes
Vendor - 40/(number of vendors)
Service Provider - 50/(number of service providers)
...
The technical steering team is responsible for all technical decisions having to do with the ONOS core codebase. The ONOS core codebase is the set of modules that is software distribution represented by the ONOS trademark. Use case applications, southbound plug-ins for non-OpenFlow devices, sample applications, vendor proprietary extensions may or may not be part of the ONOS core. It is entirely up to the technical steering team to decide what constitutes the ONOS core codebase.
...
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 December 2015February 2016. At the time of election the following occurs:
- The lead is (re) appointed by the board of Open Networking Laboratory.
- The lead decides the appropriate size of the technical steering team. The ON.Lab board of directors has veto power on the choice of size.
- Technical members are nominated by anyone, including themselves. They must already be active committers/maintainers.
- The technical community of committers and maintainers votes for the number of approved steering team membersto elect steering team members. Each voter has one vote for each position (if steering team is 3 members, then each voter has 3 votes). A voter may only cast 1 vote per candidate.
- Ties are broken by the technical steering team leader.
...
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. The following people are the first candidates
...
...
(Ciena)
...
TBD (Google) -
The technical steering team will meet with the technical advisory group 2-4 times a year.
...
The team will initially include the following people:
AT&T - Tom Anschutz, team lead
NTT - Yoichi Sato
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 January February 2015. At the time of the election, the following will take place:
...
The membership will initially be the following people:
Bill Snow, Team Lead
Prajakta Joshi
TBD, additional team members
Team Lead Election
The team lead is initially Bill Snow. Starting in December 2015 February 2016 the team lead of the release management team will be (re) appointed by the ON.Lab board of directorselected by the technical committers. In February 2016, 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.
Members
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. If you would like to volunteer for one or more of the above teams, please send an email to the email address of the team (see above).
...
Prajakta Joshi, Team Lead
Bill Snow
- TBD, additional team members
Team Lead Election
The team lead is initially Prajakta Joshi. Starting in December 2015 February 2016 the team lead of the release management team will be (re) appointed by the ON.Lab board of directors.elected by the technical committers. In February 2016, 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.
...