Page History

...

1. Maintaining a 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
2. Re-evaluate, if needed update , and communicate, OPNFV's mission and deliverables
   
   1. Update our understanding of key user groups and their needs
   2. Identify which artifacts and deliverables OPNFV should produce
3. 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 resource allocation for CI pipeline
      
4. Improving the OPNFV output/artifacts so that OPNFV is more use-case driven (e.g. for easier consumption, etc.)
   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 LaaSSupport a variety of hardware environments including Edge
      
7. Drive the evolution of the OPNFV Verified Program and support creation of LFN-level umbrella program
   

High-level budget needs:

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