Page Comparison

• ONAP Web Based Architecture Navigation Solution
• Architecture Navigator page @doc project: Architecture Navigator (ArchNav)
• contribution of Nicholas Karimi currently scheduled until the end of July 2021
• Ultimate goal is to have a good structure to get information easily findable.
• ArchNav is used also in the process of architecure reviews and holds additional information about ONAP uses cases
• POC/Proposal for a architecture map natively designed in Inkscape has started. The SVG format has capabilities to add links, additional text and mouse-over effects to elements. Presentation in the ARC subcommittee meeting as well in the TSC are planned.
• The idea is that this SVG-map is handed over to architecture team to be maintained in the future. Also it is planned to use it in RTD for a user-friendly entry-point for navigation.

•  First: Identify Maintenance Model (who is able to maintain it in production / for all the upcoming releases of ONAP)
•  Identify the use cases currently applied to ArchNav and use cases for the Doc team's needs
•  Look at the potential use of LF Landscape 
•  Look at the potential use of Inkscape for a clickable graphic (Eric Debeau has done a PoC of the functionality)

There is the need to move finalized ONAP architecture documentation from DevWiki to RTD. Especially the following section are from interest (examples from the Istanbul release):

• Architecture Map
• Component Descriptions (incl. sub-pages)

•  Andrea Visnyeito support the process of transferring the information from DevWiki to RTD
•  Thomas Kulikto support here and check how this process can be automated. Especially the embedded draw.io diagrams (special confluence macro) may cause problems if we use confluence2md to export pages). Shedule a meeting with Chaker Al-Hakimand team.
•  Chaker Al-Hakimand team to support the transfer.
•  Chaker Al-Hakim, Thomas Kulikand teams to create a process to transfer information to RTD also for upcoming releases.

• 12.07.2021 until 23.07.2021: Vacation Andrea Visnyei
• next #doc meeting sheduled for 22.07.2021

• We went through the open gerrit issues for Honolulu (Maintenance)  / Istanbul release

• We went through the open Jira issues for Honolulu (Maintenance)  / Istanbul release

•  Thomas Kulik : Propose that every project should use tox.ini (incl. link check)? Create a new Epic for this? conf.py must be updated as well!

• Should we structure our (doc) work in sprints?

•  Thomas Kulik : Ask for DT-internal help to set up this structure. Eric Debeauand Andreas Geißlerwill help as well.

•  Kenny Paul  Session with Andy Mayer  needed to clarify how we continue on the API documentation (swagger). The API docs are part of the ARC docs.
•  Nicholas Karimi join Kenny in the discussion with Andy Mayer .

• Released and updated; Timo Perala volunteers for review.

Jira ticket walkthrough,

The team will investigate further with the OOM team on how to enable a non-voting job for warnings. 

•  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.
•  Discuss with architecture team, how the following docs can be transfered to RTD:
  see:

Documenting ONAP Architecture (New)

Istanbul-R9 Architecture General Description

Istanbul-R9 ONAP Architecture Component Description

•  Link management in RTD Eric Debeau

Andreas Geißler showed a solution to create project docs manually within gerrit in case a project has branched but not changed any doc file in the new branch afterwards. There are extended right in gerrit needed ("