> Work on Critical issues has pretty much wound down. Carl asked > about the status of 1474 recently; I'd like to take that a step > further and ask for a dedicated volunteer to act as "shepherd" for > each issue. > - you *don't* need to program, or even understand programming > (but that would be a plus) > - you *do* need to read all emails on the subject > - you *do* need to keep the issue up-to-date. If there's a large > discussion happening, just follow it, but when the discussion > dies down, make sure that you post a summary and/or links to > the main emails in the issue. > - you should be ready to give a status update if somebody asks for > one, but that shouldn't be necessary because you should have > already updated the issue with that info. > > There's three Critical issues: 1472, 1474, and 1475. Any takers? > (again, to be the "shepherd" or "secretary", not to handle all > programming tasks yourself)
I'll take 1475. p _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel