Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Attending

Timo Perala Thomas Kulik Eric Debeau   Andreas Geißler

Topics, Notes, Status and Follow-Up Tasks


TopicNotes / Status / Follow-up

AGENDA FOR TODAY


Open gerrit issues
Open Jira tickets
  • We finally went through the open Jira issues for Honolulu release
Architecture documentation


Wiki 2.0 - New Task Force
  • Led by Timo Perala, Ranny Haiby. Goal: Redefine the structure of the ONAP wiki, to identify the relevant pages, to create onboarding for newbies, etc.
  • Timo Perala Taskforce is started. A proposal for a community vote can be found here: What Do You Think We Should Improve? . Please add your ideas to the proposal.


OPTIONAL (IF TIME ALLOWS)


All

Collection of topics not started

  • Dedicated repo for every subcommittee (that creates and maintains formal ONAP documentation)? To be discussed.
  • Fix ReadTheDocs starting page to the last official release (and not 'latest')
  • add tracking information to the new docs tracking page (currently WIP!!!) To be discussed.
  • Objectives for Honolulu (and onwards)

Jira ticket walkthrough,

key summary type created updated due assignee reporter priority status resolution
Refresh

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

  • Check why closes ticket show up even when the filter is set to "Open" or "In progress"
  • Guilin Maintenance Release 

All done for the doc project (date in the release note might need to be updated). Still lacking some project updates

  • Architecture documentation 

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

  • local links within a repo
  • inter-project links using inter-links from sphinx
  • links to code repo
  • external links to web sites

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 ("



  • No labels