Page Comparison

...

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 
   
4. OPNFV vision & evolution
Release process overhaul (there maybe an updated view on OPNFV key deliverables & audiences based on maybe refined OPNFV vision/mission statement noted above)working

1. Define a release process that addresses the needs of our key user groups
   
2. Dynamic hardware/lab resource allocation for CI pipeline
   
5. Improving the OPNFV output/artifacts so that OPNFV is more use-case driven (e.g. for easier consumption, etc.)
   1. Scenario consolidation
   2. LaaS evolutionInvestigate an "Official" OPNFV installer?
   3. Better packaging/consumability of test tools
      
6. Closer collaboration with other LFN projects
   
7. New initiatives for OPNFV (e.g. cloud native, new HW environments incl. Edge, etc.)Technical direction of OPNFV Verified Program
   
   1. Broaden reference platform scope towards cloud native
   2. Support a variety of hardware environments including Edge
      
8. Drive the evolution of the OPNFV Verified Program and support creation of LFN-level umbrella program