On Sun, 11 Jul 2010 14:59:14 -0400 Glyph Lefkowitz <gl...@twistedmatrix.com> wrote: > > Guido proposes to give someone interested in IDLE commit access, and > hopefully that will help in > this particular area. But, as I recall, at the > last language summit there was quite a bit of > discussion about how to address the broader issue of patches falling into a > black hole. Is > anybody working on it?
I think the best way to "work on it" is to work on having more core developers, possibly with a more diverse range of interests. > (This seems to me like an area where a judicious application of PSF funds > might help; if every > single bug were actively triaged and responded to, even if it weren't > reviewed, and patch > contributors were directed to take specific steps to elicit a response or a > review, the fact that > patch reviews take a while might not be so bad.) The operative word being "judicious". It is not obvious who should get funded, and for what tasks. Some specific issues (like email in 3.x) are large enough that they can be the sole focus of a fund grant. But I'm not sure triaging can apply. (besides, I am wary of making the job of interacting with our users and contributors a paid position, rather than a collective task.) > > FWIW, I don't consider a few months as a "long" time for a patch review. > > It may not be a long time compared to other patch reviews, but it is a very > long time for a > volunteer to wait for something, especially if that "something" is "any > indication that the > python developers care that this patch was submitted at all". Agreed. Also, the later the response arrives, the likelier it is to be along the lines of “the patch doesn't apply cleanly anymore, can you write another one?”. Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
