Page Comparison

...

VNFRQTS Project in relation to Documentation Project

The documentation project compiles and publishes the final version of the documentation source material produced by this project.

The basic process to compile the documents at ONAP is to use the Sphinx / ReadThe Docs tool  driven by a Jenkins job to pull the latest files from the repos and generate the output document format. The Documentation project will  maintain the Sphinx/ Jenkins configs to generate the documents and have them hosted at onap.readthedocs.io. The VNF RQTS project is mainly responsible for generating the files in the VNF RQTS repos.  Sphinx can accept documents in either reStructuredTexT (.rst) or Markdown (.md, .markdown, .txt, .text) formats. An example with ReStructuredTxT and corresponding html generated by Sphinx is provided by the documentation project. An example of developing and contribution markdown source documents is also available here. 

Essentially, ONAP will treat the requirements documentation as code. To compile the complete documents, The documentation project will maintain a Jenkins job that:

...

-          If successful issues a RestAPI (webhook api at Readthedocs) to pull the new build into http://onap.readthedocs.io

Committers  & Contributors

You will need to check in/out  your changes to the requirements documentation using git/gerrit. To use Git & Gerrit, ( assuming you do not already have them) will require you to set up your environment.  You will need to clone the ONAP repos from The requirements documentation must follow the rules defined by the Documentation project: http://gerrit.onap.org to your local machine to make your changes as a contributor. The ONAP community is tracking progress using the JIRA system. So please remember to create and close the jira tickets for the tasks you are completing so that the progress we make is visible. The workflow of the ONAP development process and policies are summarized in this figure

Image RemovedImage Removed

Committers

ONAP uses the Gerrit review system for committing changes to the code - including our documentation source files.   Please recall the ONAP policy is that committers cannot merge their own changes. The documentation project has a review checklist for general documentation.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html#testing

- compliant with Doc8 https://pypi.python.org/pypi/doc8

Project Responsibilities 

...

• Where our documentation needs to fit in the overall documentation structure, as well as
• The structure of our documents .(We need to clarify what a Document is)
  
  • Chapters
  • .rst files
    • start with assuming one chapter per .rst file
    • if chapters too big then chunk smaller by document sections
    • objective is to keep manage-ably sized, coherent chunks of content together for review/commit purposes  
  • The structure of our documents should be reflected as within the repo structure of our project.
    • directories
      • all the .rst files of one document in one directory
      • only one document per directory

...