Re: casual contributors (was: patch going unpushed)
Graham == Graham Percival gra...@percival-music.ca writes: Graham On Thu, Mar 22, 2012 at 11:40:43PM +, James wrote: Graham We don't really have a frog meister, so nobody is taking Graham responsibility for pushing Graham We should have somebody who takes care of contributors without Graham dedicated mentors. In mathematical/logical terms, we need a Graham barber who shaves everybody who does not shave themselves. I Graham shouldn't need to get involved when there's a new contributor, Graham much less a known+experienced contributor like Peter! One issue is that the `How to participate' webpage at http://lilypond.org/web/devel/participating/ doesn't point people at Rietveld -- it just tells them (slightly incorrectly: there's a typo in git format-patch) to send a patch to lilypond-devel. -- Dr Peter Chubb peter.chubb AT nicta.com.au http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
On Wed, Apr 4, 2012 at 1:31 AM, Peter Chubb l...@chubb.wattle.id.au wrote: One issue is that the `How to participate' webpage at http://lilypond.org/web/devel/participating/ doesn't point people at Rietveld -- it just tells them (slightly incorrectly: there's a typo in git format-patch) to send a patch to lilypond-devel. Oh no. n... You were hit by the Curse of The Old Website. We are sorry that we haven't found a counter-spell yet... http://lilypond.org/web is an old version of our website, not updated since 2 or 3 years. The current website is http://lilypond.org/index.html - please use this. :( I would at least try to fix this myself - but i really cannot do anything else than GSoC now :( Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
On Wed, Apr 04, 2012 at 05:49:24PM +0200, Janek Warchoł wrote: On Wed, Apr 4, 2012 at 1:31 AM, Peter Chubb l...@chubb.wattle.id.au wrote: One issue is that the `How to participate' webpage at http://lilypond.org/web/devel/participating/ doesn't point people at Rietveld -- it just tells them (slightly incorrectly: there's a typo in git format-patch) to send a patch to lilypond-devel. True. There's also at least two places in the CG where it tells people to send patches to lilypond-devel. Oh no. n... You were hit by the Curse of The Old Website. We are sorry that we haven't found a counter-spell yet... Don't be silly, we know exactly how to fix it. In fact, I think that Julien has finished doing all the pre-requisite steps. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
On Fri, Mar 23, 2012 at 12:37 AM, Graham Percival gra...@percival-music.ca wrote: On Fri, Mar 23, 2012 at 08:18:26AM +1100, Peter Chubb wrote: Hi Graham, Graham We don't really have a frog meister, so nobody is taking Graham responsibility for pushing I have another patch waiting, that depends on the first. Is there supposed to be a procedure for casual contributers to follow? No. If that sounds scary, then you have the right reaction. Or rather -- yes, there *is* a procedure. You're supposed to show up, then the frog meister should contact you with any details you missed (such as using our git-cl). Then you're supposed to upload a patch, and the frog meister should keep track of your patch and take care of all the details. But since we don't have a frog meister, this falls down. So yes, you've been doing everything right. We simply don't have anybody who is willing to do ~30 minutes of admin work per week to help casual contributors. For the record, i was frog meister for some time and i have to say that depending on quantity and skill of new contributors, frog meister work can take significantly longer than 30 minutes a week (if you want to give your contributors more attention than send me a patch for pushing). I'm sorry that i cannot help here now; my LilyPond time is irregular now and that doesn't make me a good candidate for frog meister. For example, i have an important math test on university in a week, and no free time to prepare myself for it - i'll have to cease LilyPond activity for several days. no cheers :( Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
casual contributors (was: patch going unpushed)
On Fri, Mar 23, 2012 at 08:18:26AM +1100, Peter Chubb wrote: Hi Graham, Graham We don't really have a frog meister, so nobody is taking Graham responsibility for pushing I have another patch waiting, that depends on the first. Is there supposed to be a procedure for casual contributers to follow? No. If that sounds scary, then you have the right reaction. Or rather -- yes, there *is* a procedure. You're supposed to show up, then the frog meister should contact you with any details you missed (such as using our git-cl). Then you're supposed to upload a patch, and the frog meister should keep track of your patch and take care of all the details. But since we don't have a frog meister, this falls down. So yes, you've been doing everything right. We simply don't have anybody who is willing to do ~30 minutes of admin work per week to help casual contributors. (and for the record: no, I am not willing to do that role. I know that I'm the expert on this subject, having mentored over 20 people in lilypond in the past, but I am not at willing to do that job right now) The other open-source projects (QEMU, Linux Kernel, uClinux) I contribute to set up a Maintainer for each subsystem, and patches are submitted to that person to get pushed. In lilypond development, the frog meister is our name for maintainer. But without somebody willing to do that job, we're SOL. I don't really want to get much more involved in LilyPond than I am already --- I'm involved in two other open source projects (QEMU and Linux Kernel at present) that take up most of my (little) free time. --- but if you wanted to give me commit access, I could undertake to maintain articulate. Quite understandable. I'll probably give you push access in a few weeks, but that won't solve the general problem faced by casual contributors. To be frank, I'm using you to highlight this problem. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
Hello On 22 March 2012 23:37, Graham Percival gra...@percival-music.ca wrote: On Fri, Mar 23, 2012 at 08:18:26AM +1100, Peter Chubb wrote: Hi Graham, Graham We don't really have a frog meister, so nobody is taking Graham responsibility for pushing I have another patch waiting, that depends on the first. https://lists.gnu.org/mailman/listinfo/lilypond-devel I've offered to shepherd this new patch. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: casual contributors (was: patch going unpushed)
On Thu, Mar 22, 2012 at 11:40:43PM +, James wrote: Graham We don't really have a frog meister, so nobody is taking Graham responsibility for pushing I have another patch waiting, that depends on the first. https://lists.gnu.org/mailman/listinfo/lilypond-devel I've offered to shepherd this new patch. That doesn't solve the general problem, though. I mean, ok. Peter is now taken care of. James is Peter's mentor in lilypond terms [1]. But what happens when the next casual contributor comes along, and we all stand around whistling with our hands in our back pockets? We should have somebody who takes care of contributors without dedicated mentors. In mathematical/logical terms, we need a barber who shaves everybody who does not shave themselves. I shouldn't need to get involved when there's a new contributor, much less a known+experienced contributor like Peter! [1] http://lilypond.org/doc/v2.15/Documentation/contributor/mentors - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
