This page lists all documentation-related projects that have been proposed as part of the Beijing release
Initiative | Description | Priority | Project Owner(s) | Doc Liaison(s) |
---|
JIRA Index Issues/TasksJIRA EPIC | JIRA Issue(s) |
---|
CONTENT-RELATED |
|
|
|
|
|
|
Beijing Content Updates
|
Work related to creating Creating or updating project-level documentation for Release 2 | Higher | All Projects | All Liaisons | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-197 |
---|
|
|
|
API's | - Define consistent Structure and Tool Chain
2. Differentiate: - REST APIs
- HealthCheck APIs
- Components APIs (eg Java class API)
| Higher | All Projects with APIs | René Robert | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-217 |
---|
|
|
|
Welcome to ONAP Flows and Text | Convert existing component level diagrams to high level flows and text. Include VNF Onboarding, Fault management, and Capacity management. One example is Istio's Concepts page: https://istio.io/docs/concepts/ | Higher | Project Leads
| | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-215 |
---|
|
|
|
Wiki "Sandbox" for novices | Create higher level sandbox for developers, SEs, architects to see E2E system / Cross component interactions Issues: How complete does the Wiki version need to be? Blocked by need for continuous deployment servers | Higher | Integration? Helen Chen ? | | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-216 |
---|
|
|
|
VNF Reference | Documentation structure for tested VNFs Issue: where should it go - include i.e. ONAP.org | Higher | VVP Steven wright ONAP Marketing | | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-28 |
---|
|
|
|
Migrate Wiki Documentation
| General Migration Issues |
|
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-21 |
---|
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-63 |
---|
|
|
Setting Up ONAP | Higher |
|
|
|
|
Integrating with ONAP | Higher | |
|
|
|
Using ONAP | Higher | Documentation / SDC, Policy, CLAMP, VID | gg2147@att.com |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-172 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-179 |
---|
|
|
Architecture - Minor edits / table conversion | Higher | Architecture / All Projects |
|
|
|
Documenting ONAP | Higher | Documentation |
|
|
|
Developing ONAP | Higher | All Projects |
|
|
|
OpenStack Interfaces | Strategic view of where and why OpenStack API's are used in ONAP, interface definitions and expectations; AI&I, DCAE (gathering information from the platform), Multi-VIM, APP-C, and SDN-C (asking the platform to do things/put itself in a certain state). | Lower | OpenStack (Dave Neary, Red Hat)? Multi-VIM Former user (Deleted) | Lisa Caywood | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC- |
---|
|
|
202 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC- |
---|
|
|
211Restructure / Clean Up existing content Restructure / Remap existing content to Developer and SDK templates Lower Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC- |
---|
|
|
148 Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-105 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-94 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-2 |
---|
|
|
Glossary | Migrate Wiki content to RsT and expand content to include: - VNF Information Modeling terms - Indexing / tagging to enable Searching | Lower | Modeling / Architecture |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC- |
---|
|
|
154UTILITIES / TOOLS | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-154 |
---|
|
|
|
|
|
|
|
|
|
TOOL CHAIN
|
|
|
|
|
|
|
Automation/Verification - Doc8+/- Coala Code Policies
- Spelling
- Grammar
- Editorial / Usability
- Sphinx directives
- Integrity of Glossary/Info Model
- Integrity of sphinx toctree
- Integrity of external references
- Acceptable file types
- CI/CD repo integration
| - Dev Edit RST File
- Unit Test
- Gerrit - Code Review/Verify Job
- Gerrit - Human Review
- Daily CSIT
- Release Integration Test
| Higher | LF Amar Kapadia ? / Documentation | |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-160 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-81 |
---|
|
|
Feedback Capabilities
| RTD |
Lifecycle • - JIRA project to report an error
|
• - Wiki or stack overflow Q&A
|
HigherLF Amar Kapadia ? /
Documentation
- Simple, more accessible link tool for editing RTD pages
Wiki Feedback
|
Establishing Establish new structure and process for: - Discussion forum
- Submitting suggestions / feedback with existing content
| Higher | |
()LF Tooling / UtilitiesRTD Edit ToolSimple, more accessible link tool for making changes on RTD pages
LowerDocumentationLF Tool Chain Documentation
| How to: - Gerrit guide
- Guidelines (Builds, etc.)
- Utilities: Jenkins, Conversion tools (e.g. LF Pandocs)
| Lower | LF Thanh Ha | |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DOC-201 |
---|
|
|
|
|
|
|
|
|
|
PROCESS ISSUES |
|
|
|
|
|
|
Branching Guidelines | Specify how and when to branch Beijing Provide clear dates to expectations to PTLs - goal is to finalize Beijing more quickly than it took for Amsterdam |
| Release Manager Gildas Lanilis Gmail |
|
|
|
VNF Certification | How and when to document: 1. Certified VNFs (when that happens) 2. Certified Platform elements |
| VVP |
|
|
|
Videos | Managing and tracking what and where videos are being posted |
| Lisa Caywood | gg2147@att.com |
|
|
Wiki vs Readthedocs | Communicate guidelines on what content should be where |
| Thanh Ha | gg2147@att.com |
|
|