Attending
...
Topic | Notes / Status / Follow-up | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AGENDA FOR TODAY | |||||||||||||
Open gerrit issues |
| ||||||||||||
Open Jira tickets |
| ||||||||||||
Sprints |
| ||||||||||||
New Doc Tracking Page |
| ||||||||||||
Guide Doc Dev System |
| ||||||||||||
Upcoming Meetings |
| ||||||||||||
OPTIONAL (IF TIME ALLOWS) | |||||||||||||
All | Collection of topics not started
| ||||||||||||
| Jira ticket walkthrough,
The team will investigate further with the OOM team on how to enable a non-voting job for warnings.
| ||||||||||||
| All done for the doc project (date in the release note might need to be updated). Still lacking some project updates | ||||||||||||
| 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. https://gerrit.onap.org/r/c/doc/+/115497
| ||||||||||||
| David McBride will join to discuss this further. Active projects vs maintenance projects. A weekly meeting was scheduled to allign doc topics with RelMgr | ||||||||||||
| Many links are managed in RTD
There is a problem when a documentation linkes to a repo => the branc is not indicated. As result, the link points to the latest release Propostion to provide guidelines to be then presented for PTL Many links are broken => need to include a test in JJB and provide information about broken links Feedback has been given, positive output. Next step, bring to PTL Sill required from the project to test | ||||||||||||
Create project docs manually with gerrit in case a project has branched but not changed any file in the new branch afterwads | 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 (" |
...