Reinhold Kainhofer wrote Sunday, February 06, 2011 10:41 PM
Another aspect to consider is that the developer bestk knows what
a new feature is about and how and in which musical context to use
it.
A doc writer, on thze other hand might not have any idea where the
feature can be used (because it is from an area where he is not
proficient) and how important it really is. So I would prefer it
if the
developer writes some raw documentation, which can then be
improved by a dedicated doc writer. That way, the dev ensures that
all important information about the feature is in the docs, while
the
doc writer ensures that users will understand it.
I agree.
To make it easier the raw documentation could be posted on
Rietfeld as a separate patchset, with a note in the tracker pointing
to it. Then it doesn't even need to be properly formatted.
Trevor
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
