Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image Added


Let's go make this happen!

Oversight Committee

Task report
pages40372844
columnsdescription,duedate,assignee
pageSize40

Image Removed

"My mind to your mind....your thoughts to my thoughts"

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)
    •  Kick of meeting with Oversight and 3 workstreams  


Organization/Governance

Task report
pages

...

40372838

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

columnsdescription,duedate,assignee
pageSize40
labelsorggov

Operational/TSC

Task report
pages40372840
columnsdescription,duedate,assignee
pageSize40
labelsoptsc

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
    •  Pitch Deck
    •  Brandon Wick  to provide detail sub task list
  •  Website updates
    •  Acquire new domain/github
    •  Revised .org webpage
    •  Revised content on LFN.org website
  •  Positioning & Messaging
    •  Mission Statement + Messaging Doc (elevator pitch)  
    •  Messaging Doc value prop document
    •  Positioning statement for press
    •  Talking Points fo community: Building momentum, member quotes, etc. 
  •  Communications Plan – Public Launch 
    •  Initial Basic Statement at ONES  
    •  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
      •  Currently CNTT work is done under Creative Commons and OPNFV is done under Apache license + CLA 
      •  Charter and repos need to be clear what work is done under what IP regime with appropriate clear header files
    •  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  
    •  Cloud Native and CVC as nested badging
  •  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
  •  Review with CNTT TSC/Gov Steering  

Task report
pages40372842
columnsdescription,duedate,assignee
pageSize40