This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
documentation:opnfvdocs [2015/04/10 15:48] Iben Rodriguez |
documentation:opnfvdocs [2016/03/07 13:07] Christopher Price |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== OPNFV documentation project ==== | ==== OPNFV documentation project ==== | ||
- | |||
=== Project description: === | === Project description: === | ||
Line 10: | Line 9: | ||
* 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 | * Provide guidelines and tooling for documentation handling across all OPNFV projects | ||
+ | |||
+ | === Current OPNFV documentation library === | ||
+ | |||
+ | [[https://wiki.opnfv.org/documentation/opnfvdocs/library]] | ||
=== Current plans: === | === Current plans: === | ||
Line 34: | Line 37: | ||
* Bryan Sullivan (AT&T) | * Bryan Sullivan (AT&T) | ||
* Trevor Cooper: trevor.cooper@intel.com | * Trevor Cooper: trevor.cooper@intel.com | ||
+ | * Victor Laza <vlaza@cloudbasesolutions.com> | ||
+ | * Natasha Peters: natasha.c.peters@gmail.com | ||
Description of roles in the documentation project: | Description of roles in the documentation project: | ||
Line 40: | Line 45: | ||
* 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. | * 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 projects: Committers will be responsible for maintaining documentation artifacts in project repositories. | * other projects: Committers will be responsible for maintaining documentation artifacts in project repositories. | ||
- | |||