On Tue, Jun 21, 2011 at 03:01:37PM +0200, Jan Warchoł wrote: > 2011/6/18 Graham Percival <gra...@percival-music.ca> > > Here's the responsibilities for mentors. Do any of these seem too > > heavy? We can relax/remove any that are a sticking point for many > > people. > > I see that these are the same that we have in CG plus one new, about > weekly checks.
Yes, that is correct. > > 5. Keep track of patches from your contributor. If you’ve sent a > > patch to -devel, it’s your responsibility to pester people to > > get comments for it, or at very least add it to the google > > tracker. > > I suggest to write about Rietveld reviews explicitely. Good point, done. > I also think it should be mentor's responsibility, not a "very > least option", to add patch to google tracker. err, I think this is an English expression. Saying "or at the very least add it to the google tracker" means that it is indeed responsibility. I've reworded that sentence. > I suggest one more: if you are working on something not very > difficult, ask your 'apprentices' to review *your* patches! In this > case "please review" would mean "please check if you can understand > what is going on here". Good suggestion, added! Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
