On Sat, Jun 05, 2010 at 11:28:48PM +0200, Valentin Villenave wrote: > On Sat, Jun 5, 2010 at 11:16 PM, Graham Percival > <gra...@percival-music.ca> wrote: > > Well, could Kieren pick up where you left off? He probably knows > > the docs as well as you do, and he's certainly familiar with > > Internals, the snippets, and the main manuals. > > Sure, if that's the most efficient way we want to use his time :)
He offered to help with this issue. I think that's both the easiest, and most effective, way that he could help with this issue. > > Having somebody else handle the minute scouring-through-regtests > > could free your time up to handle the overall organization. > > - somebody needs to look through regtests > > - somebody needs to decide what goes to LSR, what goes to > > Documentation/snippets/new/, and what goes in Notation. > > - somebody needs to add stuff to LSR. (Phil's been doing a great > > job of this) > > - somebody needs to add stuff to D/s/n. > > - somebody needs to write English+ly examples to explain stuff > > that will go in Notation. > > - somebody needs to add stuff to Notation (i.e. make the actual > > patches) > > - somebody needs to make sure all these jobs are covered, train > > any volunteers that need training, etc. > > > > It doesn't make sense to ask everybody to wait around while you > > work on the first item if that could be handled by somebody else. > > That's not at all what I am asking. I'd just like to finish through > before *Verifying* what has been properly documented or not. So, jobs > #2 to #6 look perfectly available to me in the meantime :-) Job #2 is not suitable for new doc helpers. Jobs 3-6 can't be done unless jobs 1,2, and 7 are done. Who's going to do 2 and 7? Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
