-
Notifications
You must be signed in to change notification settings - Fork 21
Tendrl Documentation Scope Overview
Martin Bukatovič edited this page Jul 20, 2017
·
3 revisions
This is work in progress, I just want to sum up the current state before we can decide on next move. I will send an announcement on tednrl-devel when this page is ready for wider discussion.
This purpose of this wiki page is to clarify:
- scope of each type of documentation we have
- responsibilities among all tendrl contributors wrt the docs
- which docs are no longer up to date and needs to be dropped/updated
- which docs needs to be relocated
- Documentation repository: https://github.com/Tendrl/documentation
- README - scope clarification needed
- Provisioning Ceph Cluster On CentOs - dev notes about setting up Ceph cluster (no end user impact)
- Deploying Tendrl - description of installation (no longer up to date), also overview of architecture (no longer up to date)
- Tendrl Project Development Workflow - description of development, no longer up to date
- Glossary - looks good (minor improvements would help)
- Provisioning with Tendrl - details about the provisioning internal desing (not sure if up to date)
- Tendrl Architectural Guidelines - dev guidelines (revisiting needed)
- Tendrl Core Components Overview - description of components, useful for end user, needs update
- Wiki: https://github.com/Tendrl/documentation/wiki
- list of tendrl talks
- How to file bugs against the Tendrl stack - dev and qe details, useful to end users who like to report a bug
- How to send alerts from inside Tendrl for devs - internal dev details
- Information required for debugging issues on the Tendrl stack - qe details, useful for end users reporting bugs
- Labels on repositories - dev details
- Tendrl Governance and Community
- Tendrl Package Installation Reference - official installation guide, end user scope
- Tendrl profiling - dev details
- and few wikipages for release notes and release installation docs - end user scope
- doc projects of particular components: TODO: list important component docs
- README files (TODO: list important README files)
So to sum this up:
- documentation repository contains mostly dev information
- very few sections from documentation repository are still up to date
- nobody seems to care about documentation repository recently
- there is no html build of documentation repository
- documentation repository is not referenced from tendrl.org page
- wikipages looks more useful and up to date compared to documentation repository (from both devel and user point of view)
The questions we need to answer before going forward:
- Where should dev details go? To documentation repo or wiki?
- Should documentation repo contain dev details?
- Where should end user (storage admin using tendrl) docs go?
- Do we want to maintain html builds of user/hight level dev documentation in the similar way ceph or gluster does?
- Do we want to resurrect currently dead documentation repository or do we want to use wiki only?