Technical Community Coordinators

The infrastructure coordinator, as TSC delegate, is
responsible for deciding repository creation requests and coordinating with LF release engineering staff on other issues pertaining to LF infrastructure
and the verification of new Committer requests

Release Manager

ONAP Release Manager Election (2018)

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.
- Develop document, and maintain release automation tools and tracking artifacts as needed
- Coordinate the cross project release cycle, including intermediate milestones and release candidates, final releases, stable and security updates.

- 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
- Deliver timely release artifacts (executable(s), documentation, testing output, etc.)

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:

• IETF YANG/NETMOD/NFVRG
• TMF OSS/API/ZOOM
• MEF LSO
• ETSI NFV/MEC
• OASIS TOSCA
• 3GPP
• BBF

• External Responsibilities:
  • Identify members of the ONAP community with existing relationships to external SDOs, and work with them to identify and follow the overlap in interest or practice from standard bodies related to ONAP’s implementation and report to TSC regularly or on demand.
  • Develop ONAP collaboration strategy with, coordinate ONAP presence, delegation and participation to identified SDO practices and report to TSC regularly or on demand.
• Internal Responsibilities:
  • Work with individual projects in soliciting and identification of related SDO practices.
  • Coordinate between implementation project in ONAP and identified SDO practice and report to TSC regularly or on demand.
  • Coordinate among multiple implementation projects in ONAP which fall into scope of a given SDO spec and report to TSC regularly or on demand.

• Regularly each TSC F2F meeting.
• On-demand report based on urgency of the event.

Active