Oslo Documentation
TABLE OF CONTENTS
**** Work in Progress for Oslo ****
Short Explanation
Table: Maintained Repositories
Containing documentation repositories for the upcoming release
Table handled commonly by the ONAP projects and the Documentation team.
In the column header you find the responsibility for this column (DOC|PROJECT).
Table: Non-Relevant Repositories
Containing documentation repositories no longer relevant for the upcoming release
Maintained Repositories Table
# | Project Name (common abbreviation of the project or subcommittee) Responsibility: | Repository Name (contains documentation to be published with the upcoming release) Responsibility: | ReadTheDocs Link (link pointing to RTD 'latest' main index.rst; main title used in index.rst) Responsibility: | Core Project (is the project a core component of ONAP?) | Repository Status (new | changed | remove ; status of documentation; needed to e.g. identify changes in the intersphinx linking) Responsibility: | Documentation Owner(s) (responsible for documentation in this repo; please use @ notation for the name) ( see also History of PTL ) Responsibility: | Documentation available: (relevant for new repos which are participating the first time) docs config up-to-date Responsibility: | Documentation available: release branch exists Responsibility: |
|---|---|---|---|---|---|---|---|---|
RC0 | ||||||||
01 | AAI | yes | no PTL since 2022-12-02 | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
02 | AAI | yes | no PTL since 2022-12-02 | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated (aai/aai-common) | |||
03 | CCSDK | yes as an ONAP common shared utility
| @Dan Timoney | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated (ccsdk/distribution) | |||
04 | CCSDK | yes as an ONAP common shared utility for:
| @Dan Timoney | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated (ccsdk/distribution) | |||
05 | CCSDK | yes as an ONAP common shared utility for:
| @Dan Timoney | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
06 | CCSDK | yes as an ONAP common shared utility for:
| @Dan Timoney | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated (ccsdk/distribution) | |||
07 | CCSDK | yes as an ONAP common shared utility for:
| @Dan Timoney | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
08 | CPS | yes | @Toine Siebelink | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
09 | CPS | yes | @Toine Siebelink | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
10 | DCAE | yes | no PTL since 2022-12-01 | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
11 | DOC | Open Network Automation Platform | to be defined | @Thomas Kulik (doc) | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes (doc) available in RTD and updated release notes (composite) available in RTD and updated | ||
12 | ARCCOM | Yes; it is a committee and defining over ONAP architecture | @Byung-Woo Jun | Architecture updated | Architecture updated | |||
13 | INTEGRATION | to be defined | @Marek Szwałkiewicz | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
14 | MULTICLOUD | to be defined | no PTL since 2023-04-24 | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
15 | MULTICLOUD | to be defined | no PTL since 2023-04-24 | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated (multicloud/framework) | |||
16 | OOM | yes for:
| @Andreas Geißler | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
17 | POLICY | yes | @Ramesh Murugan Iyer | docs config up-to-date repo 'master' exists 'latest' available in RTD | release branch exists release branch available in RTD release notes available in RTD and updated | |||
18 | Portal-NG |