• Documentation process 

  • minimum scope for participating projects (planning, reviews, branching etc) 

• Getting started with your documentation

  • Suggestion to schedule a session for the upcoming virtual event

• Cleaning up outdated content

  • Continuously clean up out dated content from RTD. How to do this in a structured way?

• Enable a voting job -1 for warnings (te be excluded long line) Invite Jessica to the next meeting for discussion. 

Ensure that documentation is added as a requirement for the release. Bring to the TSC 17/12 (@Eric Debeauor @Andreas Geißler)

To propose having a hands-on hacking session. How to get started and write documentation 

Final task for doc https://lf-onap.atlassian.net/browse/DOC-693

For future collaboration and facilitation we will ask for a time slot in the arch subcommittee meeting to inform and educate how to work with docs.

Follow up with Jessica. Any news from RTD on feature adding 

Bring discussion to the PTL call early Honolulu release cycle.  

@David McBride will join to discuss this further. 

Active projects vs maintenance projects. 

Problem statement:

The conf.py with the intersphinx mapping has different settings/configurations. Some projects refer to the latest branch and some stable/Frankfurt. 

After migrating we did see that some projects refers to latest even when choosing Frankfurt on RTD. Could this be because of the configuration or is the configuration based on whether the projects have created a release branch or not?

@Sofia Wallin  From what I learned from Aric, we do not need to change the branch in each repo whenever a project creates their branch. The branch= foo in the conf.py only applies to the default rtd theme, it doesn't do anything for the theme ONAP is using. 

All projects need to have build the stable branch before we can switch the main doc to be the next release branch. 

@Aarna Networks

Summary report is ongoing. Work is planned to run throughout December. 

@Eric Debeau presented local documentation testing. We will document a basic for version for local RST rendering. Further extensions will be available if needed/wanted (such as spell checker + Linter) but this requires a more extensive set of tools. To be presented in the PTL call for feedback.

 ************************************************************************************

Local environment to write RST files and detect

Visual Studio Code IDE + Extensions (Spell Checker + Linter)

Automatic preview aligned with ONAP documentation schemes

Status Notes: Eric has all information and will put it to Wiki, when he finds the proposed location

@Sofia Wallin to create a wiki page and send to Eric

DOC Local environment to write and test RST files

Eric requests the team to try the instruction before bringing it to the community.

Many links ara managed in RTD

• local links within a repo

• inter-project links using inter-links from sphinx

• links to code repo

• external links to web sites

There is a problem when a documentation linkes to a repo => the branc is not indicated. As result, the link points to the latest release

Propostion to provide guidelines to be then presented for PTL

Many links are broken => need to include a test in JJB and provide information about broken links

Feedback has been given, positive output. Next step, bring to PTL 

Sill required from the project to test