Development issues part 2: Bug tracking

"So, while bug trackers are a useful tool for ensuring that problems do not fall through the
cracks, it seems that one of the most potent anti-bug tools we have - discussing the problem
via a widely-distributed email list - is the same tool we have been using for decades."

The bug tracker of Ruby is a mailing list (ruby-talk).
But when you use a ml like a bugtracker, with more than 100 bugs every day, it's clearly too
big for anyone to keep up the pace. And so is this mailing list. At the end, it was really
used like a bugtracker and discussion about development were on other mailing lists. 
IMHO, the problem is not the mean, bugtracker, mailing list, irc or whatever, it's mainly a
lack of ressources. Everyone in the world can post a bug report. But a small tiny part of
"everyone" is able to read this report and say if it's really a bug or not. And a more smaller
tiny part of them know how to fix it.