On Fri, Apr 20, 2012 at 07:14:24AM -0600, Colin Campbell wrote: > To amplify my reply to Federico: if developers create similar > tracker items and attach a trivial patch without creating a Rietveld > issue, it would be very helpful if they would update the tracker > item as "patch-new" or perhaps even as "patch-review".
I disagree; it would be very helpful if they realized that their patch will not be considered for inclusion in lilypond. There's a handy git-cl script. Use it. http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers We simply do not have the resources[1] to be nice about this. If you notice a new contributor making this mistake, then by all means explain how to submit a patch in our desired manner. [1] time, energy, and attention from senior developers. If it sounds like I'm cold-heartedly throwing away potential contributors in favor of established developers, then yes, I am. My plan for improving lilypond development is: 1. make it easy for established developers 2. make it easy for new experienced developers 3. make it easy for new inexperienced developers 4. recruit new inexperienced developers (similar to GDP) We're currently at step 1. Patchy and staging are great steps forward, and if 2.18 (yes, a full stable release after the next one) comes out without any big problems, then I'll start working on step 2. - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
