...

• the only source for released documentation
• ambition: no build errors
  • at least no errors which are causing content not showing up at RTD

Content

RTD: ONAP Software related

...

• TODO: search for an expert in tooling / doc writing that can support
• TODO: support from LF?
• TODO: evaluate tooling and best-practice process for open source documentation and increase acceptance of developers
• TODO: reactivate / update doc team liaisons (as we had it in earlier times)?
• PROPOSAL: Complete restart with the above discussed QA processes in place to build up a new documentation and using only validated / approved and therefore valid content. Even if we are expecting, that the upcoming doc releases will be incomplete or empty in large areas in the beginning.

Questions

 What   What is the value of more and more ONAP features without having them - and other, important basics - not well documented?

Example: SDC usage

 Are   Are we (developers, PTL, members of the doc project, TSC, ...) able to master the current challenges for ONAP doc without spending much (!) more time and effort for documentation?

 Are   Are we willing to spend much (!) more time and effort for documentation?

 How   How can "we" incentivize "good" documentation?

...