...
- Business Coordination
- Oversight
- TSC
- Marketing
- Release Mgmt
- Work intake (Al Morton what is this called in OPNFV? Answer: The Requirements Working Group, which is part of our JERMA Release Process)
- Specifications
- Development
- Arbitrage
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
- Purpose/Value
- What we achieve
- What we don't achieve
Reference Architectures
- Purpose/Value
- What we achieve
- What we don't achieve
Reference Implementations
- Purpose/Value
- What we achieve
- What we don't achieve
Reference Conformance Documentation
- Purpose/Value
- What we achieve
- What we don't achieve
Test Frameworks
- Purpose/Value
- What we achieve
- What we don't achieve
Specific Test Cases (Do we need to divide btwn benchmarking and functional?)
- Purpose/Value
- What we achieve
- What we don't achieve
Conformance Programs – Links to CVC Need to be Considered
- Purpose/Value
- What we achieve
- What we don't achieve
Proof of Concepts
- Purpose/Value
- What we achieve
- What we don't achieve
Other Development Projects
- Purpose/Value
- What we achieve
- What we don't achieve
Tooling Activities and Projects
- Purpose/Value
- What we achieve
- What we don't achieve
Additional Activities – Doing the Journey Together
- Purpose/Value
- What we achieve
- What we don't achieve
TSC Composition/Roles/Expectations
...