2017-11-26 Doc Project Meeting

• Amsterdam doc project branch created and tracking updates in any other repo providing documentation  that has an Amsterdam branch. For those that did not have an Amsterdam branch, we are using head of the master branch as of ~11/24 4pm EST.
• Project repos that still need to be tagged:
  • Integration
  • Logging
  • Modeling Modelspec
  • OOM
  • Portal
  • SDC
  • VNF Guidelines
  • VNF Requirements
  • VNF SDK Model
• Where Amsterdam changes are expected and should be automatically published when merged, an Amsterdam branch may be created.

• Both master and amsterdam are being published at read the docs.  The default when someone enter http://docs.onap.org is master and the the developer wiki download link currently points to master.    Should we change this?

• Submit Request(s) to LF to tag project repos for Amsterdam (per LF must come from project Committer or PTL?)
  

Sub Tasks for:

• Setting Up ONAP
• Integrating with ONAP
• Using ONAP
• Architecture
• Documenting ONAP
• Developing ONAP

• Developing ONAP:   Structure and Headings clean-up

• "Carrier Grade" usability - what does that mean for Documentation?
• Insuring standards/consistency across projects (e.g. terminology, monitoring, clustering)
• Usability (e.g. Designer, VNF Providers, Operations)

• Differentiate:

1. REST API
2. HealthCheck API
3. Components API (eg Java class API)

Modeling team responsible

• Definitions to RsT
• Indexing / tagging to enable Searching

Address during Release 2

Create JIRA issue - Greg follow up

How to:

• Gerrit guide
• Guidelines (Builds, etc.)
• Utilities:  Jenkins, Conversion tools (e.g. LFPandocs)