Attending
Topics, Notes, Status and Follow-Up Tasks
| Topic | Notes / Status / Follow-up |
|---|---|
| Upcoming milestones and release planning for docs | Documentation hackathon for Guilin - dates needed Make sure you attend the second doc hackathon scheduled during the event next week. We will focus on reviews |
| Status of the ONAP Component Document | see: DOC-672 - Getting issue details... STATUS Andreas Geißler |
| Discussion about "ONAP Active Project" page | see: DOC-671 - Getting issue details... STATUS Andreas Geißler |
| Virtual event | Discussion on session proposed by Thomas Kulik |
Documentation guide | Thomas Kulik : Documentation Developer Guide (https://docs.onap.org/en/latest/guides/onap-developer/how-to-use-docs/index.html) extention planned for Beginners and restructure extisting Guide ( DOC-602 - Getting issue details... STATUS ) Jakob Krieg : Created ticked about Testing instructions DOC-651 - Getting issue details... STATUS |
Update "Documentation improvements for end to end usage of ONAP" @Aarna Networks | MS2 to start next week. Sriram gives an update in TSC meeting following this meeting ****************************************************** MS1 close to finished. MS2 in review for prioritization (work starting in next 2 weeks) Status update page: Documentation improvements for end to end usage of ONAP An update to the TSC will be done within a couple of weeks. |
Local environment to write RST files Eric Debeau | 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 |