...
In doing research for Infra Dashboard I've found that among the biggest common requests have been:
...
infra-doctype
tags to track / organize:- Policy documents
- Project management pages
- Administration / Process pages
- Configuration documents
- Runbooks / Troubleshooting documentation
- Notes and internal conversation documentation
-
infra-review
tag to keep documentation updates and organization rolling.
Questions:
- Should we have an
infra-service
umbrella tag instead of labeling service related documentation with the name of the service directly e.g. infra-mail
?- Andrew: I THINK the labels are universal for our instance of the wiki, so any other space can use a tag like "mail" (and can also delete it, I think). I thought that's why we were using the infra-X formulation.
- Would we have an
internals
or tlp-service
(or something of the like) tag to differentiate ASF services versus TLP services?- Andrew: That's covered by the access permissions. You only see what you have permission to see. For indexing, that's why I thought of putting them in two stacks.
- Drew: That's fair. I was under the impression that we're trying to push infra.a.o as the point of entry for project facing documentation. That would leave the INFRA:Index to us (more or less)
...
- Administration (infra-doctype-admin)
- process based documentation with how-to's and general overviews
- Configuration (infra-doctype-config)
- Flow diagrams and solution maps
- Installation and setup documentation
- Runbook (infra-doctype-runbook)
- Troubleshooting documentation for the on call person
- Policy (infra-doctype-policy)
- Project Management (infra-doctype-project)
- project management pages should be tagged with their respective service
- can be navigated by anyone and should be targeted at infra.
- Notes (infra-doctype-notes)
- largely informal
- primarily for internal consumption
- good for discussion documents
Proposed 'infra-review' label – IMPLEMENTED
...