2021-09-23 Doc project meeting
- Thomas Kulik
Attending
@Eric Debeau @Andy Mayer @Timo Perala @Kenny Paul @Thomas Kulik
Topic | Notes / Status / Follow-up |
|---|---|
AGENDA FOR TODAY | |
Current JJB/RTD Build Problems | @Eric Debeau , @Bengt Thuree (Unlicensed) , @Thomas Kulik are working to fix the issue. We will shorten the meeting to spend more on problem solving. |
Doc Procedures | Procedure "P01: Create documentation for an ONAP main release" is currently under development by @Thomas Kulik A dedicated procedure related for Maintenance Release: P02: Create documentation for an ONAP maintenance release (doc project team) has been created |
Architecture Documentation in RTD | 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): Evaluation started; Confluence has now a new functionality to export a page to markdown format; lets see if/how this can help (attachements unfortunately are not included) Pending pach: https://gerrit.onap.org/r/c/doc/+/123946. @Eric Debeau did some comments TASKS:
|
Backlog Clean/Sort/Reorder | We will do it in jira! TASKS: @Thomas Kulikhas prepare a deduplicated and sorted list of open tasks. Next step is to go through the list and remove outdated/unwanted entries. |
Issue with RTD TOC | TASKS: @Andrea Visnyei / @Thomas Kulik check RTD TOC for https://docs.onap.org/en/latest/guides/onap-developer/how-to-use-docs/templates.html |
Doc Templates | TASKS: @Andrea Visnyei and @Andreas Geißler to check current component template and improve if needed |
API Documentation | @Andy Mayer presentation, Developing ONAP API Documentation @Andy Mayer gave us a good introduction to API documentation TASKS: @Eric Debeau to check available API documentation in RTD and how to update with material proposed by @Andy Mayer doc team; next steps: (update) description how to include it in RTD; prepare sample config files; check if we need to create a procedure for this (like we have it for creating main/maintenance release documentation) example RTD link: https://docs.onap.org/projects/onap-ccsdk-oran/en/latest/offeredapis/pms-api.html |
Doc Guideline | TASKS: 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) |
Istanbul Release | #doc team: Review Istanbul release notes and project content @Eric Debeau and @Andreas Geißler reviewed and document the results in Istanbul Documentation => some comments from @Andreas Geißler Some projects to move on "Unmaintained" mode (ExternalAPI, VID) TASKS: @Eric Debeau Still clarification required for Architecture section (Architecture subcommittee) @Eric Debeau Modeling update to be checked @Eric Debeau clarification on MSB status @Eric Debeau @Andreas Geißler Eric Update conf.py file |
Honolulu Maintenance Release | @Andreas Geißler started to create release notes based on Jira tickets Still a bug fix for Honolulu to be fixed and documented TASKS: @Andreas Geißler will ask SO and CDS projects to finalize the Docker creation and documentation it is also important to document the process (later on used in a procedure) => P02: Create documentation for an ONAP maintenance release (doc project team) |
Usage of Confluence "Tasks" in Meeting Notes | Please do not use "Tasks" in this meeting note. The meeting note is planned to be copied for the next meeting. Unfortunately all "Tasks" are also copied and a NEW INSTANCE of this tasks is created. This leads to multiple duplicated of a single tasks. |
Other | TASKS:
|
Vacations & Upcoming Meetings |
|