Re: Separate bugs list?

On Sat, Jun 10, 2000 at 11:34:42AM +0300, Andi Gutmans wrote: > b) Our situation with bug reports isn't that great right now. Not > many people take the time to close bug reports. Right now wanting > to be on php-dev brings along with it a side-effect of having to > look at the bug reports. I'm sure even some people who don't > really want to receive them have already looked at some bug > reports. It would make the bugs database situation much much > worse. Look how many entries we have now. If you want to be on > php-dev and be part of the development you should also be a part > of the bugs. Why have all the fun and not try to contribute with > the annoying part? A lot of the bug reports can be handled by > people who are not core developers. Valid points, but I think that those interested in fixing bugs would take the extra few seconds to subscribe to the bugs list, too. It seems like a waste of bandwidth and list processing power to emplode such a large list (php-dev) to so many folks who just end up deleting the majority of the messages (I'd guess that bug reports account for over 60% of the traffic here). Anyway, it seems like the better approach in the logical perspective is to split the list, but there are good arguments either way, so I have a feeling we'll never reach a clear decision and things will just stay the way they are. -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member