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.
External Standard Coordination
External Open Source Community Coordination
ONAP Liaisons
| Area Name | Area Name and Description | Coordinator Role Description | Reporting Cadence | Date Created | Status | Coordinator |
|---|---|---|---|---|---|---|
Marketing Liaison | Point of contact for ONAP marketing efforts |
| As Required | Project launch | Active | Pawel Pawlak |
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 | Project Launch | Active | David McBride |
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 | Project Launch | Active | Concurrent assignment to the Seccom Chair position |
4 Comments
Michael O'Brien
Acumos/ONAP coordination - TSC-15 - Getting issue details... STATUS
CD, Security infrastructure with LF - TSC-25 - Getting issue details... STATUS , TSC-32 - Getting issue details... STATUS
Brian Freeman
Should the area coordinators have a specific list of Opensource communities they are responsible for coordinating with on behalf of the ONAP TSC ?
Alla Goldner
yes, absolutely
Hui Deng
1 Speaking for ex-SDO coordinator, we learned that there are too many SDOs in this world, they all want to build the relationship with ONAP community, but when we come to the community to ask whether you have any issues related to SDO, there are only 2-3 SDOs (ETSI NFV / 3GPP SA5), here is the example for this year: Collect issues in ONAP related to M-SDOs. why we need so many coordiantors but without any issues from ONAP communities.
2 some SDOs who just come to ONAP community and made the contribution without any coordinations like TMF API which shows very good example in the open source community, we need more coders other than too many coordiantors.
3 When we talked about 5G, there are always 3 pillars, Radio PNF/ Slicing/ Mobile Edge computing, it seems current proposal are trying to divide 5G into 3 parts, network management which is key component of slicing in 5G