Date: Fri, 29 Mar 2024 13:08:56 +0000 (UTC) Message-ID: <1866849610.1119.1711717736733@ip-10-30-146-46.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1118_584082379.1711717736730" ------=_Part_1118_584082379.1711717736730 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Version 3.0, Bill Snow (ONF)<= /span>
Version 2.0 can be found here.
Ratified TBD
Governance of the ONOS=C2=AE project is intended to foster a technical meritocracy within= the context of stewardship by the ONOS Chief Architect and the ONF Board o= f Directors. ONF is a nonprofit organization, and provides engineerin= g resources on behalf of the ONOS Project.
The goals of ONOS project governance = are to:
Provide an environment that thriv= es on technical meritocracy. Merit is based on technical contribution, not = on financial contribution.
Provide a framework for ONOS team= s and projects =E2=80=93 how they are started, how they are managed, how me= mbers are elected, how conflicts are resolved, how they are disbanded when = no longer needed.
Be clear on how ONOS software evo= lves =E2=80=93 how code is added to (or removed from) the project.= p>
Be clear on how decisions are mad= e and conflicts resolved in the community.
Make it easy for community member= s to participate.
Avoid bureaucracy.
The principles of ONOS governance are= in line with these community values:
Serve our Customers.
= li>Practice true Meritocracy.=
Operate with Transparency.=
Strive for Quality, consistently.=
Value and enable Innovation.
Respect others in all Interaction= s.
In addition, the over-arching governa= nce principle is To act in the best interest of the broade= r community.
The ONOS project is governed by the T= echnical steering team and the ONF board of directors.
Email: = onos-tech-steering-team@onosproject.org - Archive
The technical steering team is responsible for all technical decisions h= aving to do with the ONOS project and the ONOS core codebase (=E2=80=9CONOS= Core=E2=80=9D). The ONOS codebase is the 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 steer= ing team to decide what constitutes the ONOS Core. Projects within th= e ONOS Project follow the project lifecycle document which can be found&nbs= p;here. The TST may= amend the project lifecycle document (=E2=80=9CProject Lifecycle= =E2=80=9D) with the approval of the Chief Architect. The ON= OS chief architect (=E2=80=9CChief Architect=E2=80=9D) is the team lead of = the technical steering team. The ONF board of directors reserves the right = to remove and replace the Chief Architect at any time.
As per the Project Lifecycle, incubated projects may graduate to either = Mature-state or Core-state status. It is intended that threshold for having= projects graduate to Mature-state will be lower and the process streamline= d relative to having projects graduate to Core-state. The TST is intended t= o be an oversight body, and is not intended to have responsibility for patc= h-level project decisions.
The membership is found on the <= a href=3D"https://wiki.onosproject.org/display/ONOSST/Technical+Steering+Te= am" rel=3D"nofollow">home page.
The definitive section describing tec= hnical roles can be found here= a>. The TST, with approval of the Chief Architect, shall have authority to = modify, delete and create new technical roles from time to time.
Voting member: Any contributor, a module owner= , or a project owner who has submitted (and/ had accepted) or reviewed, as = applicable, at least two patchsets in the prior twelve (12) months.
There are several ways to become a member of the TST.
New technical steering team members will be elected on a yearly basis.&n= bsp;Elections are held in the first quarter of each calendar year. At = the time of election the following occurs:
If a team member leaves the team during the year, it is up to the Chief = Architect to decide whether or not to hold an election to put someone else = into the position before the next scheduled election.
If any member of the technical steering tea= m changes their corporate affiliation during their tenure and, as a re= sult, joins an organization that already has (on a consolidated basis) dire= ct representation on the TST, the ONF board of directors reserves the right= to remove them from their role on the technical steering team.
The ONF board of directors reserves the rig= ht to select a new Chief Architect at any time.
2020 Elections Process and Information can be found here
2019 Elections Process and Information can be found here
20= 18 Elections Process and Information can be found here.
2017 Elections Process and Informatio= n can be found here.
2016 Elections Process and Informatio= n can be found here.