Page Comparison

[NOTE: These goals are a summary of community discussions at https://etherpad.opnfv.org/p/TSC-backlog] 

1. Maintaining a healthy community
2. Continuing to have venues/events (both face-to-face and virtual) for OPNFV community members to collaborate effectively 
   
Growing the contributor communityAddress new use cases and hardware deployments (e.g. cloud native, Edge, C-RAN/vCO)

1. Support cloud native apps in the reference platform (integrate and test Kubernetes & related components)
   
2. Create/integrate Edge-specific stacks (e.g. Akraino, OpenStack Edge) and define & obtain appropriate hardware environments for testing them in Pharos and LaaS
   
3. Create/integrate C-RAN and vCO specific stacks and test them on appropriate hardware environments in Pharos and LaaS
   
3. Re-evaluate, and if needed update and & communicate, OPNFV's mission and deliverables, deliverables and ways of working/processes
   
   1. Update our understanding of key user groups and their needs
   2. Identify which artifacts and deliverables OPNFV should produce
   Continuous improvement in our processes & ways-of-working
   1. Define a release process that addresses the needs of our key user groups
      
   2. Dynamic hardware/lab Use lab resources more efficiently through dynamic resource allocation for CI pipeline
      
4. Improving the Refine OPNFV output/artifacts so that OPNFV is more use-case driven (e.g. for easier consumption, etc.)and easier to consume
   
   1. Scenario consolidation
   2. LaaS evolution
   3. Better packaging/consumability of test tools
      
5. Closer collaboration with other LFN projects
   
6. New initiatives for OPNFV
   
   1. Broaden reference platform scope towards cloud native (integrate and test Kubernetes & related components)
      
   2. Create/integrate Edge-specific stacks (e.g. Akraino) and make appropriate hardware environments for testing them available in Pharos and LaaS
      
   3. Create/integrate C-RAN and vCO specific stacks and test them on appropriate hardware environments in Pharos and LaaS
      
7. Drive the evolution of through e.g. XCI, Lab-as-a-Service
   
8. Evolve the OPNFV Verified Program and support creation of LFN-level umbrella program
9. Maintain and grow our healthy community
   1. Continuing to have venues/events (both face-to-face and virtual) for OPNFV community members to collaborate effectively 
      
   2. Growing the contributor community

High-level budget needs:

• Two Plugfests/Hackfests
• Two developer summits (not counting ONS North America)
  
• Running cost of LF-owned hosted hardware (LF CI pods and servers for general IT)
• Software licenses for currently used IT services (git/Gerrit, Confluence/Jira, Bitergia, etc.)
• Support Project and IT support staff as current