For the August Governing Board meeting, we need to cover 3 specific areas (the first three headings below). Additional material has also been captured.
Suggested Wording for the Slides
Description
Desired outcome of the merge
To create a single organization where the telecom operators can work together with vendors and other interested organizations and individuals to define, implement and test the cloud architectures that fulfill the requirements of telecom applications.
Implementation considerations
- CNTT and OPNFV agree to participate in the merger as two equal communities
- Decision is needed about the name of the organization
- Create a new name for the merged organization
- Find a way to keep existing organization names
- Ensure all leadership needs and project activities are covered in the organizational structure
- (If it's not too many details we can list the options here about the work streams as OPNFV projects, Technical Steering Committee, a potential Architecture Committee, etc)
- Desire to reduce governance complexity and number of meetings within the two organizations if possible
Work Product, Interfaces and Dependencies
Dependencies
- Upstream projects
Approximate Timeline
Factors
- Governing Board Decision in October 2020?
- OPNFV JERMA meta-Release Calendar: December 2020 Release date
- CNTT Baraque Release in September 2020 (insert additional releases planned...)
- Current CNTT officer term ends in December 2020
- Intermediate tasks to flesh-out, post GB decision, such as the structure of the new organization
- Nomination periods and Elections take about 6 weeks - propose to start the Election Calendar in November 2020 (half of December is unavailable).
- NewName selection: Community and Marketing
Estimate
New org in operation in January 2021
Recent discussions
Description
- Full Merger of equal communities: both activities are needed for success.
- OPNFV+CNTT=NewName (Community and Marketing determine NewName, if communities want it).
- No Customer-Supplier relationships within NewName, recognition of shared fate.
- OPNFV Release process already allows for frequent project self-releases, so any CNTT release schedule can be accommodated.
- CNTT Work Streams become individual Projects, with PTLs, Committers, Contributors, and Project descriptions.
- This can be a structure where the existing workstreams have 1:1 mapping to new formal projects, or some restructuring is possible/optional.
- This can be a structure where the existing workstreams have 1:1 mapping to new formal projects, or some restructuring is possible/optional.
- Build new WGs according to CNTT’s need for tiered structure (if any WG are needed).
- Existing OPNFV projects could choose to continue to be independent projects or choose to combine with new projects being formed
- New TSC Elections and Officers (when organizations combine, possibly in January 2021?).
- Commitment from all OPNFV+CNTT members to supply a fixed amount of resources to both requirements and code development.
- New project to Integrate all relevant project outputs into a cohesive deliverable for automated Conformance testing.
- Reduce overall governance structure of OPNFV+CNTT, where possible. Reduce the overall number of meetings related to former CNTT activities.
...
- Continue "Working Upstream": Open Stack, CNCF, other LFN projects (FDIO, ODL, ONAP, ...), ETSI NFV, IETF, others
Approximate Timeline
Factors:
- Governing Board Decision in October 2020?
- OPNFV JERMA meta-Release Calendar: December 2020 Release date
- CNTT Baraque Release in September 2020 (insert additional releases planned...)
- Current CNTT officer term ends in December 2020
- Intermediate tasks to flesh-out, post GB decision, such as the structure of the new organization
- Nomination periods and Elections take about 6 weeks - propose to start the Election Calendar in November 2020 (half of December is unavailable).
- NewName selection: Community and Marketing
...