User Tools

Site Tools


documentation_projects:opnfv_documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
documentation_projects:opnfv_documentation [2015/03/17 13:46]
Christopher Price
documentation_projects:opnfv_documentation [2016/02/26 04:31] (current)
Ryota Mibu [Backlog]
Line 1: Line 1:
 +NOTE: This is an old page not being maintained any more. This page was used for the initial project proposal.
 +
 +This page will be removed after a few weeks (in May 2015).
 +
 ==== Project Name: ==== ==== Project Name: ====
  
Line 10: Line 14:
     * Installation guide     * Installation guide
     * User guide     * User guide
 +    * Any relevant references and interface specifications for OPNFV projects or components.
   * Include any architecture diagrams or specifications,​ reference to OPNFV requirements list.   * Include any architecture diagrams or specifications,​ reference to OPNFV requirements list.
 +  * Provide guidelines and tooling for documentation handling across all OPNFV projects ​
  
 ==== Scope: ==== ==== Scope: ====
  
-  ​Set up a structure, and a template, for document development with source control (same as source code). ​We may take the main input from Openstack ​documentation structure and tools, and also consult odl+  ​Set up a structure, and a template, for document development with source control (same as source code). ​Leveraging upstream ​documentation structure and tools. 
-  ​- Same source ​contribution process ​like source code +  ​* Following as close as possible the same contribution process ​& tools as our source code 
-  ​- Write an introduction note to prospective contributors +  ​Structure OPNFV documentation logically 
-  - Structure OPNFV documentation logically +  ​Develop initial set of release ​documents:  
-  ​Develop initial set of documents:  +    ​* ​(A) Release note 
-  ​- ​(A) Release note +    ​* ​(B) Install guide 
-  ​- ​(B) Install guide +    ​* ​(C) User Guide 
-  ​- ​(C) User Guide +    ​* ​(D) API reference (if there is content in release 1) 
-  ​- ​(D) API reference (if there is content in release 1) +    ​* ​(E) Interface specification ​ (if there is content in release 1) 
-  ​- ​(E) Interface specification ​ (if there is content in release 1) +  ​* Provide language options for documentation where applicable: ​In first release English only, Wiki (via HTML scraping from Gerrit), ​and PDF. 
-  ​In first releaseEnglish only, Wiki and PDF. +  * Provide tooling ​and processes for OPNFV projects to implement ​and follow ​for consistency
- +
-  * Describe the problem being solved by project +
-  * Specify any interface/​API specification proposed,  +
-  * Specify testing ​and integration:​ +
-  * Debugging ​and Tracing  +
-  * Unit/​Integration Test plans +
-  * Client tools developed ​for status shows etc.  +
-  * Identity a list of features and functionality will be developed. +
-  * Describe how the project is extensible in future+
  
 ==== Dependencies:​ ==== ==== Dependencies:​ ====
Line 39: Line 36:
   * All OPNFV projects participating in a release.   * All OPNFV projects participating in a release.
   * Upstream project documentation to be referenced ​   * Upstream project documentation to be referenced ​
-  * Are there any external fora or standard development organization dependencies. If possible, list and informative and normative ​reference ​specifications.+  * Where there are external fora or standard development organization dependencies,​ list informative and normative ​references & specifications.
  
 ==== Committers and Contributors:​ ==== ==== Committers and Contributors:​ ====
  
-  * Name of and affiliation of the project leader ​ +{{scrape>​https://gerrit.opnfv.org/​gerrit/​gitweb?​p=opnfvdocs.git;​a=blob_plain;​f=INFO;​}} 
-    * Christopher Price: christopher.price@ericsson.com +
-  * Names and affiliations of the committers +
-    * Christopher Price: christopher.price@ericsson.com +
-    * Wenjing Chu (Dell): ​ wenjing_chu@dell.com  +
-    * Ashiq Khan (NTTdocomo):​ khan@nttdocomo.com +
-    * Fatih Degirmenci: fatih.degirmenci@ericsson.com +
-    * Rodriguez, Iben: Iben.Rodriguez@spirent.com +
-    * Malla Reddy Sama: sama@docomolab-euro.com+
   * Any other contributors   * Any other contributors
     * Bryan Sullivan (AT&T)     * Bryan Sullivan (AT&T)
Line 58: Line 48:
 Description of roles in the documentation project: Description of roles in the documentation project:
  
-  * Committers (Editors): has overall responsibility of document structure, editing, style +  * Committers (Editors): has overall responsibility of document structure, editing, style and toolchains 
-  * contributors:​ individual section will have contributors who are domain experts in those areas, other contributors may simply help out working on the documentation and tools as needed. +  * opnfvdocs ​contributors:​ individual section will have contributors who are domain experts in those areas, other contributors may simply help out working on the documentation and tools as needed. 
-  * Other reviewersreview language/​syntax/​styling,​ general text quality+  * other projectsCommitters will be responsible for maintaining documentation artifacts in project repositories.
  
 ==== Planned deliverables ==== ==== Planned deliverables ====
  
   * Project release documentation for OPNFV   * Project release documentation for OPNFV
-  ​If project ​deliverables have multiple dependencies across other project categories, described linkage ​of the deliverables.+    ​Including collation of all release relevant ​project ​documentations 
 +  * Establishment and maintenance ​of the OPNFV documentation processes and toolchains
  
 ==== Proposed Release Schedule: ==== ==== Proposed Release Schedule: ====
  
   * opnfvdocs will follow each OPNFV release and produce needed documentation   * opnfvdocs will follow each OPNFV release and produce needed documentation
 +    * Release 1 will provide basic documentation including revision control.
 +    * By release 2 a multi-project toolchain will be in place with processes and version control
 +    * Iterative improvements to the processes and toolchains are expected on a release by release basis.
 +
 +==== Backlog ====
 +
 +  * https://​etherpad.opnfv.org/​p/​opnfvdocs_b_release_issues
 +  * update docu manual: [[http://​artifacts.opnfv.org/​opnfvdocs/​docs/​enable_docu_gen.html]]
 +
  
  
documentation_projects/opnfv_documentation.1426599985.txt.gz · Last modified: 2015/03/17 13:46 by Christopher Price