On 08/10/2010 23:48, Dana Quinn wrote: > One question i have - sorry for the top post - how much of these > documentation problems are because people think they have to write > incredibly comprehensive, really good documentation? Someone saying > they aren't a good enough writer to do SA documentation makes me think > they are aiming too high. > > One thing I've talked to my team about is that *some* documentation is > better than *no* documentation. Write *something* down, and then > start evolving it. I heard way too much of people saying things like > "I need to take a day off by myself to write the documentation". > Since the "day off by myself" never happened, we never got > documentation. Start by writing a basic checklist, and have people > fill it in with more detail as they work through the processes.
One thing I've tried to do is use the template capabilities of mediawiki to create templates for documenting servers, services, websites, etc. This should mean they don't have to think about what to write as much as just fill in all the fields. Unfortunately that still hasn't succeeded in getting people to actually fill in the fields. -- Thanks Jefferson Cowart [email protected] _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
