bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0.


From: lilypond
Subject: Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0.
Date: Wed, 08 Jun 2011 15:43:47 +0000


Comment #5 on issue 1217 by percival.music.ca: clean up undocumented regtests in 2.14.0.
http://code.google.com/p/lilypond/issues/detail?id=1217

I agree in principle, but I'd prefer a tweak: I want James to be supervising the regtest stuff. He can copy&paste stuff into the docs, but I want other people to be doing the legwork.

PREPARATION
- James makes sure he can edit the wiki. If relevant, James also gets admin on the wiki, so that he can authorize new users to edit pages. (that may or may not be necessary) - James emails lilypond-user, asking for volunteers to work on this. He explains that we need people to look through regtests, we need people to explain how a regtest works (in 2-3 sentences), we need people to make minor changes to the .ly files to make them more doc-friendly.

WORKLOAD
- people add "missing regtests" to the wiki
- other people, or maybe the same people, write (in email form) documentation for each feature. - James dumps them in Notation, adds whatever minor formatting is required, maybe adds a few @seealso if necessary -- but no more than 15 minutes of work for each new feature. Anything that would take longer than that gets kicked back to volunteers.


We need fresh blood in the documentation stream, and I cannot supervise them without abandoning GOP and/or GLISS. Since each new feature here is very limited in scope, this is an ideal task for him to start supervising people.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]