Page tree
Skip to end of metadata
Go to start of metadata

Problem statement: 

The OPNFV community needs to get input from end user advisory group, marketing and technical communities on how to use these three types of documentation. Specifically on how to structure them in a way that best meets the needs of each group. The feeling of the technical community is that these three groups are not working together on a coordinated strategy for documentation. For example, some web pages point back to the wiki which points to artifacts pages. There wasn't an effort to coordinate them. 

Proposal

  1. Website - www.opnfv.org
    • this documentation is externaly and/or marketing focused
  2. Wiki - wiki.opnfv.org
    • this documentation should be used to drive project work within OPNFV
      • meeting agendas / minutes
      • project release planning
      • interns / recruiting
      • events
  3. User documentation - docs.opnfv.org
    • this documentation should include anything that impacts an OPNFV user
    • user include:
      • releases / end users
      • developer (projects specific)
      • test frameworks
      • infrastructure

We don't expect the above to change but we need some planning on to use them better. They need to be structures in more useful way. 

  • No labels