The TSC Charter identifies individuals to aid the TSC and TSC Chairperson in coordinating various activities for the technical community. This page lists the area of coordination and the person currently fulfilling the role.
| Area Name | Area Description | Coordinator Role Description | Reporting Cadence | Date Approved/disapproved | Status | Coordinator |
|---|---|---|---|---|---|---|
Infrastructure | Coordinating with LF-IT on issues pertaining to LF infrastructure | The infrastructure coordinator, as TSC delegate, is | Periodic reports to the TSC, as necessary, with the status of repository creations and other issues that may arise | Jan 25, 2018 | Active | Concurrent with the Release Manager at this time |
Release Manager | To facilitate, monitor and report on all aspects of project development, cross project coordination, and the timely creation of release artifacts according to the ONAP Release plan(s) and schedule(s). | - Work with the ONAP TSC and Project PTLs to create and evolve the ONAP release process. - Communicate with Project Technical Leaders, Technical Steering Committee and community at large regarding the status of the release. - Help identify release-blocking issues to keep release process on schedule | Weekly | January 14, 2019 | Active | |
Security Coordinator | Coordinate the creation of security related processes and policies for the ONAP community | Work with community to identify what security processes and procedures are needed to ensure the security posture of the ONAP Project. Drive the the creation and documentation of those processes, policies, and supporting structures (such as needed subcommittees etc). | Weekly | 5/4/2017 | Active | Concurrent assignment to the Seccom Chair position |
Standards/SDOs | Open source and standard are compliementing each other. Opensource is playing an increasing important role in SDO practice, which could help to gain industry concensus and adoption. The potential standard bodies and topics include:
|
|
| 05/11/2017 ONAP TSC voted in January 2019 to have area coordinators, not overall SDO/ Open source coordination | Active | |
External Open Source Community Coordination | The External Open Source Community Coordinator is responsible for identifying members of the ONAP community with existing relationships to external open source communities, coordinating with them to expedite interactions between members of the ONAP community and those external communities, and reporting to the TSC on those activities. | See Area Description | Monthly | 05/11/2017 ONAP TSC voted in January 2019 to have area coordinators, not overall SDO/ Open source coordination | In-active | TBD - https://lists.onap.org/pipermail/onap-tsc/2017-May/000349.html Logging in ONAP works with Acumos TSC-15 - Getting issue details... STATUS |
| AI (ML/DL) area | Coordinate activities aroinf AI (ML/DL) including Acumos, ETSI ENI etc. |
| ||||
| 5G area | Coordinate activities around 5G, including but not limited to 3GPP, ORAN, ORAN-OSC, IEEE | |||||
| Cloud Native area | Coordinate activities around cloud native e.g. K8S + other open source solution linked to container management | |||||
| Edge Computing area | Coordinate Edge Computing Activities | |||||
| Generic network management activities area | Coordinate all network management activities happenning in 3GPP SA5, ETSI NFV, ETSI ZSM, IETF, BBF, MEF, TMF |
Note: each area includes both relevant standards and open source organizations