4 ms·
This is rather pointless exercise. One can have a page documenting a very rare system crash and how to fix it. If the crash don't repeat itself annually the pa
by elmolino89 6y ago
This is rather pointless exercise.
One can have a page documenting a very rare system crash and how to fix it.
If the crash don't repeat itself annually the page will be deleted. Not a great outcome, me thinks.
Instead of a forced page renewal there should be a bonus for fixing highly useful pages and a bounty for finding errors in the documentation.
Otherwise the same crappy page with few nuggets of useful links/info will be copied verbatim for ever and ever.
- lkbm 6y agoWe've used Guru[0] for some of our internal documentation, which will prompt you to re-verify the accuracy of docs on a set schedule. So every six months (configurable per doc), it will prompt the designated person to glance over the doc and say "yup, still good". I'm undecided as to how well it works, but it seems like it a better solution to the stale data problem than "let's just delete everything and hope we don't ever need it" approach. [0] getguru.com
- elmolino89 6y agoI am a fan of Markdown based wikis. Have been using GitLab for some time now. On a separate note: one can script simple link checking/verification of the fetched content. And flag all pages with dead links, or with links where PDF/html/whatever did change from a snapshot taken say every month or so.
- kholterhoff 6y agoWhat sort of bonus/bounties are you envisioning?