You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Constitute the Merger Task Force

  • 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)

Community – Org Structure

  • 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?
  • 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
  •  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
  • 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

Marketing/Creative/PR

  • Branding - merger of equals/non-acronym name
    • Yes/No Decision
    • Determine new name
    • Work with Creative Services to create brand brief and design new branding and logo
    • Create revised branding guidelines document
    • Brandon Wick to provide detail sub task list
  • Website updates
    • Acquire new domain/github
    • Revised .org webpage
    • Revised content on LFN.org website
  • Positioning statement for merge
  • Updated mission statement, elevator pitch, and value prop document - 
  • Communications Plan – Public Launch 
    • Press release
    • FAQ
    • Social Plan
    • Blogs/webinars
    • Mini-conference?
    • Press/Analyst outreach and briefings
    • Early 2021 public launch target?
  • Mod OPNFV Technical Charter to accommodate changes (expand scope of OPNFV)
    • Based on above agreements re: voting, TSC composition, etc. 
    • IP Policy
      • Revise OPNFV IP policy?
        • Assume Apache license for code
        • Revisit CLA policy?
      • Revise CNTT IP policy?
        • Currently Creative Commons; could consider a spec license (initial Legal guidance – remain Creative commons)
        • Should OPNFV CLA apply to CNTT repos?
    • OPNFV tech charter revision for name change and community governance model
    • Committee structure changes (TSC and election policy)
  • Revise GSMA/LFN Terms of Reference
  • File for appropriate trademarks for new brand name and logo

Other – OVP/Compliance Updates and Plan

  • Branding impact on CVC/OVP
  • Any updates to workflow, interaction, badging requirements, etc.

2021 Planning - due:  

  • Create combined budget request to the Board
  • Create combined input/feedback to 2021 Strategic Marketing Plan
  • Any combined feedback to SPC re: 2021 LFN strategic plan


  • No labels