...
- Describe the functionality to be provided by the project.
- Documentation artifacts for an ONAP release that contain
- original content created by contributors to the documentation project and
- integrate source material from any project that the documentation depends to be consistent with an ONAP release.
- CI/CD Documentation Tool Chain
- The tool chain to create document artifacts will use gerrit, jenkins, and nexus the same as software projects and add specific tools appropriate for documentation.
- Where published documentation depends on source in any repository, the tool chain will support the automated integration - e.g. to propagate changes in APIs into the documentation.
- Documentation artifacts for an ONAP release that contain
- Please provide the full intended scope of the project; not just what is intended for the project's first release.
- The first release establishes best practices and patterns for managed documentation as well as the documentation for ONAP release 1.
- Subsequent releases maybe required for all projects to comply with best practices, to complete content for all audiences, to address how documents might be tailored or translated for use in different ONAP instances, etc.
- Specify any interface/API specifications proposed
- TBD the documentation tool chain selected may impose some requirements on how source material is structured in repositories that will be integrated.
- Please provide the full intended scope of the project; not just what is intended for the project's first release.
- Identity a list of features and functionality will be developed.
- Documentation managed with the same pattern as source code including gerrit, jenkins, artifacts published in nexus or readthedocs.org, etc.
- Output documentation format TBD - likely static html and .pdf versions with hyperlinks between the different documents as appropriate..
- Depending on the volume of documentation, some indexing/ search capabilities may be provided.
- Identify what is in or out of scope. During the development phase, it helps reduce discussion.
- In scope - Best practice tool chain and CI/CD pattern for documentation, Release 1 documentation.
- Out of scope -
- Training is not part of this project
- VNF Requirements is a separate project
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
A parallel thread to create documentation artifacts with dependencies on the capabilities, configuration, and interfaces provided by software projects as illustrated below.
- Dependencies on all projects providing source material for documentation.
- Code changes may drive documentation changes.
Some documentation e.g. VNF Requirements may need to be traceable to code modules (e.g. test cases)
- Target use cases drive the user audience and task requirements for a release.
- Dependencies on all projects providing source material for documentation.
- How does this align with external standards/specifications?
- Project will identify best practices for a documentation tool chain by looking at other open source projects (eg. open daylight, opnfv)
- Are there dependencies with other open source projects?
- Evaluate use of readthedocs.org as way of publishing documents.
- Evaluate the use of swagger.io for API documentation
...