...
- Joint committee for defining the FMO
- Determine the right composition for the task force?
- Team building - create a cohesive team
- Determine structure, meeting times and schedule, any sub task forces - TAC advise
- Determine reporting commitments/schedule to leadership (CNTT, OPNFV, TAC, MAC, GB)
- Kick of meeting with Oversight and 3 workstreams
Organization/Governance
...
Operational/TSC
- 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
- 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)
- Reconcile meetings and schedule management for all concerned parties
- Agree on recording meetings and minute taking processes
- 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
...
{"serverDuration": 440, "requestCorrelationId": "d17e652141d4af55"}
