[Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Documentation

New issue 3051 by address@hidden: [DOC]Update Contributor’s Guide 5.2  
to mention use of LSR
http://code.google.com/p/lilypond/issues/detail?id=3051

Reported by Arle Lommel:
http://lists.gnu.org/archive/html/bug-lilypond/2012-12/msg00155.html

Section 5.2 of the Contributor’s Guide currently states that all
suggested changes to the documentation be submitted as bugs. However,
suggestions for documentation of overrides should generally be submitted
to the LSR, per this email from Trevor Daniels:

> The correct way to add [changes like this] to the documentation is to
> submit your example, with appropriate explanatory text, to the LSR,
> tagging it for docs, rhythms and tweaks and overrides [or the
> appropriate place]. This is the way users can add material to the
> documentation - it will then appear automatically in the Snippets list.

> Once that is done, the doc writers can easily add it to the selected
> snippets in the position you suggest.  Overrides such as the one you
> suggest are (with very few exceptions) not included in the main text of
> Chapter 1 of the Notation Reference; there would simply be far too many
> equally useful candidates.

Section 5.2 needs to be updated by someone knowledgeable about the
proper procedures to accurately reflect the different kinds of
documentation contributions and where they should be reported as bugs
versus being submitted to the LSR. (I am unable to produce this text,
but the guidance from Trevor’s mail should help someone who knows enough
to do it and thereby help steer people to the right actions.)