[Python-Dev] No response to posts (original) (raw)

Brian Curtin brian.curtin at gmail.com
Mon Aug 2 18:54:45 CEST 2010

On Mon, Aug 2, 2010 at 11:39, Ralf Schmitt <ralf at brainbot.com> wrote:

Benjamin Peterson <benjamin at python.org> writes:

> Please, let's stop messing with the tracker for everything. I think > the current set up works reasonably well, and we should focus on the > real problem: manpower Ignoring issues (probably even with some patches attached) will drive contributors away. That's not the way to increase manpower. - Ralf

Overall the "no response" query just passes the buck. Let's say we get that query down to zero issues. What does that give us? Now we have 500 issues with 2 responses. Sure, it makes further correspondence more likely, but it's not solving any real issues and making any measurably significant impact.

While I do think the "no response" query can be helpful, let's not attribute too much value to tiny tweaks of the tracker and reporting. Benjamin is right -- manpower is where we'll benefit the most, not in the manner we paint the current issue situation. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100802/b79361f2/attachment.html>

More information about the Python-Dev mailing list