DOC Task List
- Thomas Kulik
Motivation
Due to issues in confluence we had multiple duplicated task in our list. To get rid of this problem, those tasks were collected, sorted and deduplicated in a seperate list. Also, all tasks were 'checked' in all our confluence documents (mainly project meeting notes).
The result of this activity is the list below. This and other sources are now used to build up two task lists:
Jira task list (dev backlog) to group and store doc 'development' related tasks
Confluence task list (project mgmt) (single page, continously maintained) for project management related tasks.
Source
Old Confluence Tasks (to be checked and migrated)
TaskDescr | DueDate | Owner | Source | Status |
|---|---|---|---|---|
#doc team: Review Istanbul release notes and project content; extra session required; to be planned. | ||||
add tracking information to the new docs tracking page (currently WIP!!!) To be discussed. | ||||
Andrea Visnyei and Andreas Geissler to check current component template and improve if needed | ||||
Andrea Visnyeito support the process of transferring the information from DevWiki to RTD | ||||
Architecture documentation | ||||
Ask users to add always the original file of grafics to the repo (plus the bitmap version of course which is used in wiki/RTD) | ||||
Branching strategy Eric Debeau and Sofia Wallin (all doc project) | ||||
Chaker Al-Hakim to set up a series of knowledge transfer meetings on ArchNav 16 Jun 2021 | 16. Jun 21 | |||
Chaker Al-Hakim, Thomas Kulikand teams to create a process to transfer information to RTD also for upcoming releases. | ||||
Check why closes ticket show up even when the filter is set to "Open" or "In progress" | ||||
cleaning up old patches | ||||
Copyright notice an RTD still shows the wrong year. | ||||
create Jira ticket for istanbul / cleanup doc first | ||||
create Jira ticket to evaluate 0.6.0 for istanbul | ||||
Dedicated repo for every subcommittee (that creates and maintains formal ONAP documentation)? To be discussed. | ||||
Discuss with architecture team, how the following docs can be transfered to RTD: | ||||
Documentation build issues | ||||
February virtual event | ||||
First: Identify Maintenance Model (who is able to maintain it in production / for all the upcoming releases of ONAP) | ||||
Fix ReadTheDocs starting page to the last official release (and not 'latest') | ||||
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. | ||||
Guilin Maintenance Release | ||||
Honolulu Maintenance Release | ||||
Identify the use cases currently applied to ArchNav and use cases for the Doc team's needs | ||||
Kenny Paul , Eric Debeau Session with Andy Mayer needed to clarify how we continue on the API documentation (swagger). The API docs are part of the ARC docs. See also in DevWiki. | ||||
Look at the potential use of LF Landscape | ||||
Nicholas Karimi join Kenny in the discussion with Andy Mayer . | ||||
Objectives for Honolulu (and onwards) | ||||
PTL election | ||||
Slack channel for doc | ||||
The next doc weekly is dedicated to the Architecture Navigator. See also ONAP Web Based Architecture Navigation Solution. Invite Chaker Al-Hakim . | ||||
Thomas Kulik : Ask for DT-internal help to set up this structure. Eric Debeauand Andreas Geisslerwill help as well. | ||||
Thomas Kulik Chaker Al-Hakim Nicholas Karimi Figure out the maintenance model as first area of focus 30 Jun 2021 | 30. Jun 21 | |||
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. | ||||
Upcoming milestones and release planning for docs | ||||
Update "Documentation improvements for end to end usage of ONAP" | ||||
Update "Documentation improvements for end to end usage of ONAP" |