Page History

This page is for DRAFTING proposals re. an Anuket org structure and deliverables. deliverable proposal

• Proposals are WIP and both OPNFV and CNTT communities are encouraged to provide input and participate in the discussions (all ideas are welcome and good)
• This page is not intended to capture discussions about proposed Anuket release process (also an important topic for discussion)other topics which are being worked such as:
  • Governance 
    • Technical charter
    • Ops guidelines
    • TSC election process
  • Marketing
    • Mission
    • Scope
    • Value prop
  • Operations
    • Tooling
    • Release process
    • etc.

Bin list of opens from raised in discussions (may be related but not part of proposals being not limited to the specific proposals discussed here)

1. How to structure Anuket repos
2. Handling variations of an RA
3. Release topics e.g. frequency, artifacts, process (planning → release), dependencies, etc.  
   • Dependencies between specifications (RM, RA) and implementations / tests (RIs/RCs) ... must allow for lag
   • etc. 
4. ?

Anuket Org Structure

A diagram representing the new Anuket org and relationships with other entities will continue to evolve per discussionsis shown below and likely to evolve. This is a high level picture to help clarify how Anuket will be organized and some relationships deemed important. Many details re. process and artifacts still need to be decided to allow the projects (specifications, implementations, conformance) to deliver on Anuket objectives. 

1. Original strawperson presented in 2020-10-22 Meeting Notes - Anuket Strawman Top level Structure v0.2.pptx
2. Updated and presented in 2020-10-29 Meeting Minutes - Anuket Strawman Top level Structure v0.5
3. Updated after meeting discussion  Meld Ops and Org 2020-11-12 Meeting notes - Anuket Strawman Top level Structure v0.6.pptx

...

Consensus points:

• A single TSC
• Marketing committee separate from the TSC
• ?

Anuket Deliverables

What Anuket delivers as an RI

Key question - should there be only one RI?

• The RI is a known (good) instantiation of the RA
• The RI project  could conceivably implement more than one known good instantiation that is faithful (conforms) to the RA. Each implementation may
  • have different performance because they are each running on different hardware (
  • use different install tools but end up with an identical setup and configuration

...