Nicely said, Adam. ----- Original Message ----- From: "Adam Maccabee Trachtenberg" <[EMAIL PROTECTED]> To: "Leigh Makewell" <[EMAIL PROTECTED]> Cc: <internals@lists.php.net> Sent: Saturday, September 17, 2005 1:48 AM Subject: Re: [PHP-DEV] Re: Bogusing bot (Was: [PHP-DEV] Reference handlingchange and PHP 4.4.0)
> On Thu, 15 Sep 2005, Leigh Makewell wrote: > > > Well then I suggest you get out there and find out what you are doing > > wrong because there is an increasing number of people out there who are > > not happy with how their bugs are being treated. > > This is a good place to start. > > http://www.sitepoint.com/forums/showthread.php?t=297291 > > I've filed 41 PHP bugs starting in 2001. Of those, 37 have been marked > closed, 1 won't fix, 2 bogus, and 1 no feedback. > > Of the ones not marked closed, the won't fix one was quite hard to do, > the bogus ones were bogus, and the no feedback one didn't include a > short reproducible test case, so I don't fault that reply. > > Of the 36 bugs that were fixed, they hit the entire spectrum of PHP: > Zend Engine, ftp, mysqli, SPL, SOAP, reflection, streams, iterators, > shm, DOM, SimpleXML, Tidy, arrays, SQLite, PEAR, PHPUnit, Net_Whois, > documentation, the documention system, the Web site, and even the bug > system itself. :) > > That's a lot of work from a lot of different people to fix of my > issues, and I'm quite thankful for all of their work. > > I've handled customer services issues, such as these, before. It takes > a lot of time to set up your environment to reproduce the issue. Much > more than you'd expect. > > Sometimes, people even conspire against themselves, don't give you > what you ask for making it impossible to duplicate, and then get angry > when you don't fix their problem when it's their own fault. :) > > I subscribe to the bug reports list, and I often feel bad about the > bogusing of bugs. I know some of the bug report replies aren't as > polite as they could be. I also agree that the label of "bogus" > triggers quite a bit of anger in someone who feels that their bug is > legitimate, and a differently worded label would be *much* better in > terms of not generating anger. I wish that would change. > > However, then I think about how much time I wish to spend going > through all those reports, and I hold my tongue. > > If people really want to help the community, go ahead and verify open > PHP bugs -- you don't need to actually come up with a patch -- you > just need to replicate the issue or tune the report to a short test > case. You'll probably be shocked how long that alone takes. > > It would be a great help and time saver for core developers, and you'd > get the chance to provide the community with excellent customer > service while you're at it. > > -adam > > -- > [EMAIL PROTECTED] | http://www.trachtenberg.com > author of o'reilly's "upgrading to php 5" and "php cookbook" > avoid the holiday rush, buy your copies today! > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
