We use doku...partly because its supposed to still be usable in a disaster (though nobody is maintaining such copies or have ever tested such.)
We have some customization work to have auto updating wiki pages. Like a map of our what's on all our digis. Or what zone is on what global. We at one time used a planner plugin, to list/schedule recurring work, special tasks, etc. But, we continued to have weekly staff meetings were we would repeat the information of our coming week. Former $boss said it was more for the benefit of co-workers, though $boss was the only one taking notes. New $boss ended the weekly staff meetings and wiki usage dropped off....though I try to throw stuff in there when I can, because its habit I keep working on (I joked that we should have an internal blog....because that's where my habit started from....) our wiki happens to also be running on our loghost.... so occasionally some kind of integration is investigated. Perhaps when our student get's up to speed.... ----- Original Message ----- > Not to appear to be too much "Mr.Obvious" - but a well-structured > wiki > is cheap and easy to set up - but hard to keep structured. You might > also look at systems like Trello - which aren't as flexible and > impose > more structure. I'm sure there are also better tools. But that's my > 2 > cents worth (or maybe a little less)... > > On 05/06/2013 12:59 PM, Craig Constantine wrote: > > Anyone care to recommend a knowledge base/tracking/journaling > > solution? > > > > Something for system journals, run logs, change tracking, > > procedures... that sort of internal stuff. I'm currently running a > > home-grown solution but I'm running out on the fuzzy edges trying > > to wrangle open issues/tickets, scheduling recurring work, and > > some other bells-n-whistles. This is purely for > > within-our-organization use; So I don't need, for example, a > > public-facing customer request system. > > > > Also interested in any case studies or similar on best practices > > for setting up these sorts of system. > > > > --Craig Constantine, http://constantine.name > > > > _______________________________________________ > > Discuss mailing list > > [email protected] > > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > > This list provided by the League of Professional System > > Administrators > > http://lopsa.org/ > > > -- > Alan Robertson <[email protected]> - @OSSAlanR > > "Openness is the foundation and preservative of friendship... Let me > claim from you at all times your undisguised opinions." - William > Wilberforce > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System > Administrators > http://lopsa.org/ > -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: [email protected] Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
