Version 1.0

adopted as of TBD

Governance Model

Governance of the CORD® project is intended to foster a technical meritocracy within the context of stewardship by the CORD Chief Architect and the ONF Board of Directors.  ONF is a nonprofit organization, and provides engineering resources on behalf of the CORD Project. CORD is also a project of the Linux Foundation, and as such, its governance model is consistent with LF best practices.


The goals of CORD project governance are to:


The principles of CORD governance are in line with these community values:

In addition, the over-arching governance principle is To act in the best interest of the broader community.

Governance Structure

The CORD project is governed by the Technical Steering Team and the ONF board of directors.

Technical Steering Team

Technical Steering Team Page

Email: - Archive

The technical steering team is responsible for all technical decisions having to do with the CORD project and the CORD core codebase (“CORD Core”). The CORD codebase is the software distribution represented by the CORD trademark. Sample applications or virtual network functions (VNFs), vendor proprietary extensions may or may not be part of the CORD Core. It is entirely up to the technical steering team to decide what constitutes the CORD Core.  Projects within the CORD Project follow the project lifecycle document, which can be found here.  The TST may amend the project lifecycle document (“Project Lifecycle”) with the approval of the Chief Architect. The CORD chief architect (“Chief Architect”) 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 streamlined relative to having projects graduate to Core-state. The TST is intended to be an oversight body, and is not intended to have responsibility for patch-level project decisions.

The membership is found on the TST home page.


The following technical roles have been defined. The TST, with approval of the Chief Architect, shall have authority to modify, delete and create new technical roles from time to time.


Becoming a member of the TST

There are several ways to become a member of the TST.

  1. The Chief Architect is by definition a member as the lead of the TST.
  2. The voting community will elect members annually as positions open.
  3. If a core project is deemed to be important enough to the success of CORD, then the TST may choose to add the project lead to the TST. It is entirely up to the TST to make the decision on whether the project warrants consideration. This decision is made at the time the project undergoes the review to become a core project.

Membership Elections

New technical steering team members will be elected on a yearly basis. Elections are held in the third 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.

2017 Elections Process and Information can be found here.

2018 Elections Process and Information can be found here.

Other Changes