Hi, 13.09.2007 17:30,, Alan Brown wrote:: > Arno Lehmann wrote: >> We really need a good technical writer to create a short, concise and >> exact "Getting Started" manual, but the necessary skills are, >> unfortunately, not very common among open source people. >> >> > > Getting started guides must not be written by those are very famliar > with the software, as that familiarity gets in the way of writing such a > guide.
Well, the specific skills for a technical writer, IMO, include the ability to look at things "from the outside". > The problem is that people who have just setup a system are seldom in a > mood to write a summary of it. I have to locally document every change > made and details of every new installation (including steps taken) and > find that hard enough... I know that... but we need much more than just a step-by-step description for a standard system, I think. Most important is that whatever gets written, the reader likes to read it, it is well structured, and of course correct for a wide variety of different setups. Unfortunately, I'm really not a good writer, myself... Arno > > > -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
