You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The ONAP Community functions as most opensource projects do, with a set of rules and leaders elected and approved from within the participants of the Project. 

For clarity in interpretation, typically Project referrs to the ONAP Project itself, whereas project will refer to the individual development efforts approved as part of ONAP.

This document serves as a high-level summary of rules, roles and responsibilities only. The sources cited serve as the official "Source of Truth" for ONAP Governance.

Official Governance includes the following:

  • Technical Charter which defines the mission, scope and key provisions of the Project
  • Technical Community Document which defines the essential business operations of the Project
  • Policies which are the agreed upon norms of technical execution and operations of the Project

Leadership Areas:

  • The Technical Steering Committee (TSC) is responsible for all technical oversight of the Project
  • Community Coordinators (CC) are usually specific job roles within the Community 
  • Project Technical Leads (PTLs) are the official spokespeople for an individual project 
  • Subcommittee Chairs who lead subcommittee content & deliverables
  • Committers who are individuals permitted to approve and merge code into the main branch

All of the above are subject to the annual election process with the exception of the Committers. 

Related Links

RoleBrief DescriptionExample ResponsibilitiesTypical QualificationsDefined byElected by
TSCThe TSC is responsible for all technical and operational oversight of the Project

TSC Members are directly accountable for coordinating the technical direction of the Project. At a minimum they are required to be regular participants on the weekly TSC meetings and expected to be regular participants at the weekly PTL meetings, on the onap-tsc mailing list and wiki. In addition:

  • Defining release dates, content and quality standards

    project or system proposals and scope changes

  • Defining technical best practices, community norms, workflows, issuing releases, and security issue reporting policies

  • Creating sub-committees or working groups to focus on cross-project technical issues and requirements
  • Establishing, maintaining and modifying policies to ensure the integrity, vetting and security of the Project code base
  • Improving and implementing policies and processes for contributing to the Project
  • Fostering discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affects multiple projects
  • Coordinating any marketing, events, or communications regarding the Project with the LF Projects Manager or their designee
  • Mediating technical conflicts between Committers and PTLs

TBD no later than June 31, 2018

  • Driven by collaboration
  • Highly engaged and involved in the workings of the project teams and subcommittees
  • More typically would also be active as a PTL or Committer, but not a prerequisite
Technical CharterTBD no later than June 31, 2018
CCA CC is ensures Project alignment across many parties that need to work together to identify, characterize, and solve a particular class of problems. Typical examples a Community Coordinator role would be release management, security and other open source communities. These are liaison positions and unless specifically called out do not have decision making authority. A CC is expected to provide regular readouts to the TSC.
  • A strong passion for the particular area of specialization
  • Recognized as a respected leader in that area
  • Excellent communication verbal and written skills
  • An existing network of relevant contacts in the area

Technical Community Document and Technical Community Coordinators

TSC Members
PTLThe PTL is formal liaison, spokes person and leader for their individual project

PTLs are required to be regular participants on both the weekly TSC and PTL meetings, and be active on the onap-tsc, onap-discuss and onap-release mailing lists at a minimum. In Addition:

  • Maintain, prioritize and communicate business requirements (with contributors), ensuring the code being merged in to their project is held to the highest standards of quality
  • Regular reports to the TSC and Release Manager as requested
  • Maintain the project's JIRA, wiki page and documentation
  • Conduct project development meetings and ensuring that the meeting minutes are posted to the wiki in a timely fashion
  • Ensure that all project milestone templates are completed on schedule
  • Resolving conflicts within the project's Development Community
  • Coordinating technical and non-technical engagement with other PTLs, CCs and Steering Committees
  • Providing support for marketing, demonstration and education purposes as requested
  • Must be a Committer on that project
  • Must be willing to fulfill the responsibilities
Technical Community CoordinatorsThe Committers of that project
CommitterA Committer is any code contributor that has been given formal permission to merge code into the main branch
  • Providing constructive code reviews of repo contributions
  • Merging code into the appropriate branch
  • Working with the PTL and contributors to help keep the project running smoothly


Promotion is recommended by the existing Committers based upon merit.

See here for examples:

Technical Community Document and Technical Community Coordinators

Current project Committers

or

by the TSC in the case of new projects only

Subcommittee Chair

A Subcommittee Chair is the formal liaison, spokes person and leader for their individual subcommittee

Subcommittees are advisory-only bodies to assist the TSC with its responsibilities and provide expert guidance in a technical subject area.

  • Leading meetings and ensuring minutes are made available in a timely fashion.
  • Representing the subcommittee to the TSC, providing regular reports as requested
  • Coordinating PTL input to their subject area


  • Highly collaborative
  • Excellent communication verbal and written skills
Technical Community Document Members of the Subcommittee



  • No labels