[FM Discuss] Beyond manuals

[mick at mcin.net]

>
> The tone interests me a lot actually. Both the circumvention manual and
> the command line manual have a very friendly voice, and I'm wondering
> how much of that is a product of the type of community writing effort we
> are encouraging.
>
> adam
>

This is what I wrote in the FAQ

Why should you write another manual when other manuals are available?

Sometimes the documentation written by software devellopers isn't the best
for end users. We may be able to create docs that are much more user
friendly for people approaching the software for the first time.

Clearly you shouldn't try to copy the documentation of a project like Open
Office. It's well documented and you would be duplicating a lot of effort.

However, that is not to say that software like Open Office shouldn't have a
FLOSS manual. It may be that you can provide a clear introduction to the
software, a summary of the most vital aspects of the software or step by
step guides which are lacking in other documentation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/attachments/20090325/9a6bca52/attachment-0001.htm>