2017-12-05 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   INT-349 - Getting issue details... STATUS
  • Logging   LOG-108 - Getting issue details... STATUS
  • Modeling Modelspec  MODELING-47 - Getting issue details... STATUS
  • OOM  OOM-471 - Getting issue details... STATUS
  • SDC  SDC-713 - Getting issue details... STATUS
• 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?

• Create JIRA ticket(s) for each item below  Rich Bennett

• Each PTL committer for the repos list in column 2, to identify the hash and create a release branch "amsterdam".
• Sync up the doc project amsterdam branch submodule references with created amsterdam branches,  DOC-210 - Getting issue details... STATUS

• Switch DW download link to RTD amsterdam when branches above are completed Rich Bennett   

• What needs to change for the latest vFW instructions? Eric Debeau
• Do we need something for new users (not developers) that want to understand use cases, try higher level service/policy scenarios, etc?  Eric Debeau

DOC-179 - Getting issue details... STATUS

• Start with (oom kubernetes,  quickstart, heat template ), set example / define a best practice for collecting/refining documentation on wiki, following a process with wiki labels, JIRA tickets, etc that keeps everyone aware of state and transition to change controlled documentation in gerrit