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.
|Role||Brief Description||Example Responsibilities||Typical Qualifications||Defined by||Elected by|
|TSC||The 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:
||Technical Charter||Active Community Members|
|CC||A 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.||
The SPC Representative is ONAP's official delegate on the LFN Governing Board's Strategic Planning Committee. The SPC is a representatives from LFN TAC Projects and members of the Governing Board or their appointees.
The focus of the SPC is primarily about portfolio management across the LFN
||the LFN Governing Board||TSC Members|
|PTL||The PTL is formal liaison, spokes person and leader for their individual project||
||Technical Community Coordinators||The Committers of that project|
|Committer||A Committer is any code contributor that has been given formal permission to merge code into the main branch||
Promotion is recommended by the existing Committers based upon merit.
See here for examples:
|Technical Community Document and Technical Community Coordinators||
Current project Committers
by the TSC in the case of new projects only
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.
||Technical Community Document||Members of the Subcommittee|