Organization Structure Exercise

In the comments section please discuss your thoughts in the context of the follow questions:

  1. Is this function needed in the new organization?
  2. How do you see the function fitting in the organization? (example: Is Oversight a role in a Business Coordination or is it a separate function unto itself?
  3. What dependencies exist between the functions? 
  4. What other discussion points can you offer regarding the Function?

on the FUNCTIONS (not groups) listed below



What do we produce?

Based on Trevor's comments below and some of last week's conversation, this can be a space to talk about what we produce and why. The How is really up to the TechOps TF, but I do think we need to wrestle with the what. And to repeat what was discussed last week, "We need to improve the ability to on-board infrastructure and network services" or some version of that is what we're trying to accomplish at the highest level. 

Reference Models

Reference Architectures

Reference Implementations

Reference Conformance Documentation

Test Frameworks

Specific Test Cases (Do we need to divide btwn benchmarking and functional?)

Conformance Programs – Links to CVC Need to be Considered

Proof of Concepts

Other Development Projects

Tooling Activities and Projects

Additional Activities – Doing the Journey Together

TSC Composition/Roles/Expectations

A place to brainstorm next level-down considerations based on outcomes from the above section. This is not meant to dictate specifics of elections policies and procedures but what rather we expect of any governing or oversight body. 

TSC Composition – Short-Term – Interim/Startup TSC

When new projects starts or in the immediate aftermath of a merger, most projects elect to have a "start-up" or "interim" TSC, where the TSC has different election procedures for a constrained period of time. An example with which we are all familiar is when new stand-alone projects start, their TSCs usually consist of the founding platinum members of the organization (ONAP, OPNFV, FD.io, ODL, and TF(?) all followed this model). Over time the TSC migrates to a fully democratic model, elected by the community according to its agreed election procedures. Since OPNFV and CNTT are both established, a modified and accelerated version of this model can likely be used.

Rationale: Although the meld process is helping the communities get to know one another, many of the individual contributors and PTLs/workstream leads don't know very many people in the other group, which makes general voting across both groups for a single TSC challenging in the short term. In addition, both groups are likely to want to feel that they have representation as the group gets off the ground and forms a cohesive whole. A TSC that is overly weighted in one direction may cause hard feelings in the less represented community. Finally, this TSC will be unique in that one of its primary job will be to see the Meld fully realized – i.e., that what put down on paper really happens in practice and that we create a successful, unified group that operates as one project. This TSC will need to lead us to build a strong culture together across all the contributors of all the work.

Proposal:


Consensus as of week of Oct 19

TSC Composition – Long-term/Steady State

Considerations

External Relationships (LFN Projects and External)

A place to brainstorm next level-down considerations based on outcomes from the above section. What  are the types of relationships we need to build with external organizations? How  do we want to build them? What metrics  do we use to measure success? What are out 2021 priorities ?

Conformance Program (OVP) Considerations

Fundamentally, this is the end goal of much of the merged group's activities, so a very strong relationship and understanding of requirements with CVC is extremely important.