Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 12 Next »

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 NameArea DescriptionCoordinator Role DescriptionReporting CadenceDate ApprovedStatusCoordinator

Infrastructure

Coordinating
with LF-IT on issues pertaining to LF
infrastructure

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

periodic reports to the TSC, as
necessary, with the status of repository creations and other issues that
may arise		Jan 25, 2018ActiveConcurrent with the Release Manager at this time

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.)

WeeklyMay 31, 2017ActiveFormer user (Deleted)

Security Coordinator

Security Coordinator Coordinate the creation of security related processes and policies for the ONAP communityWork 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).Weekly5/4/2017ActiveConcurrent 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:

  • 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.
05/11/2017

Active


Hui Deng -

 denghui12@huawei.com


 https://lists.onap.org/pipermail/onap-tsc/2017-May/000348.html

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 DescriptionBiweekly05/11/2017In-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

  • No labels