"My mind to your mind....your thoughts to my thoughts"
Constitute the Merger Task Force
...
- Determine TSC structure - codified in the Technical Charter
- Combined TSC or separate
- Combined TSC avoids replication of silos and avoids conflicting guidance coming from two different governance groups
- Possible reserved seats per "voice"
- Possible "interim TSC" for first year (reserved seats?)
- Determine voting criteria – accommodate creators of both types of work product
- Elected positions within the TSC – Chair, SPC rep, any others?
- Combined TSC or separate
- Organization structure
- What are the projects and workstreams and how to organize?
- Possible to pair or combine groups working on similar technical areas from both "voices"
- Goal – minimize silos while enabling efficiency
- Any other sub-entities, councils, task forces, etc.?
- Holding entity for smaller OPNFV projects?
- Any GSMA relationship changes (also covered in Legal below)?
Operational/Governance
- Determine required votes, dependencies in order to execute merger
- Run the votes based on existing voting requirements and governance; once new TSC is constituted, new votes can be done by them.
- Update Operational Guidelines document based on above org structure decisions
- Execute Structural plans in alignment with org structure decisions above
- Run elections for TSC and other positions
- Refined Active Contributor calculation to ack CNTT github contributions
- New subproject creation (new entities and old entities in new home) & repo creation
- Create any additional committees, working groups, other sub-groups
- Run elections for TSC and other positions
- Tools
- Converge OPNFV/CNTT Confluence Space (wiki.opnfv.org and wiki.lfnetworking.org/CNTT respectively)
- Archive both current spaces, copy select content into new space
- Collapse the multi-space design of OPNFV into a flat-wiki - possibly a few different spaces, but not 1 per project
- Repurpose jira.opnfv.org - archive projects, rename as appropriate
- Merge CB/Insights reporting
- Initiate discussions on additional tool merges
- ReadTheDocs workflow
- Ensure header files in alignment with any IPR changes (see Legal Section below)
- Converge OPNFV/CNTT Confluence Space (wiki.opnfv.org and wiki.lfnetworking.org/CNTT respectively)
- Reconcile meetings and schedule management for all concerned parties
- Release process
- OPNFV has a newly agreed release process that references CNTT; CNTT has long had independent release process
- Any value in combining spec and code releases?
- Release naming conventions?
- TAC inform on new merge project/OPNFV name change
...