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

Compare with Current View Page History

« Previous Version 22 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 Name and DescriptionCoordinator Role DescriptionReporting CadenceDate Approved/disapprovedStatusCoordinator

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



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

WeeklyJanuary 14, 2019Active
Jim Baker

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


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) areaCoordinate activities aroinf AI (ML/DL) including Acumos, ETSI ENI etc.
  • Report progress periodically to ONAP on key area related open source & standards initiatives
  • Drive collaboration with ONAP on key edge open source & standards initiatives
  • Concrete near-term & long-term recommendations based on above and other inputs to
    • ONAP architecture subcommittee
    • ONAP modelling subcommittee
    • ONAP usecase subcommittee
    • ONAP security subcommittee



5G areaCoordinate activities around 5G, including but not limited to 3GPP, ORAN, ORAN-OSC, IEEE


Cloud Native areaCoordinate activities around cloud native e.g. K8S + other open source solution linked to container management


Edge Computing areaCoordinate Edge Computing Activities


Generic network management activities areaCoordinate 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

  • No labels