nanog mailing list archives
Re: Knowledge tracking tools
From: dsr () tao merseine nu
Date: Wed, 24 Mar 2004 18:20:13 +0000
On Wed, Mar 24, 2004 at 10:06:19AM -0800, Steve Francis wrote:
e.g. an easy way to dig up what the changes that occured on a system were for, who did them, etc. Obviously rancid et al shows us what changed when, but not the change plan that was responsbile or what problem it solved.
An internal Wiki with a page dedicated to each machine or machine-class. There's good integration between TWiki and Bugzilla, but we have the classic dichotomy of ticket systems vs bug-trackers: Bugzilla is better for software, RT is better for hardware and networks. Wikis greatly increase the retention and availability of knowledge: they are easy to use, so people *do* use them; they are easy to search, so people do that, too. -dsr-
Current thread:
- Knowledge tracking tools Steve Francis (Mar 24)
- Re: Knowledge tracking tools dsr (Mar 24)
- Re: Knowledge tracking tools Steve Gibbard (Mar 24)
- Re: Knowledge tracking tools Kevin Oberman (Mar 24)
- Re: Knowledge tracking tools Stephen Stuart (Mar 24)
- Re: Knowledge tracking tools Randy Bush (Mar 24)
- Re: Knowledge tracking tools esm (Mar 24)