Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19066 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99148 invoked by uid 1010); 17 Sep 2005 02:37:23 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 99133 invoked from network); 17 Sep 2005 02:37:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Sep 2005 02:37:23 -0000 X-Host-Fingerprint: 192.38.9.232 gw2.emini.dk Linux 2.4/2.6 Received: from ([192.38.9.232:8896] helo=gw2.emini.dk) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id D5/0F-43379-0618B234 for ; Fri, 16 Sep 2005 22:37:21 -0400 Received: from foxbox (1Cust243.tnt102.lnd4.gbr.da.uu.net [213.116.52.243]) by gw2.emini.dk (Postfix) with ESMTP id 57DF184275; Sat, 17 Sep 2005 04:37:15 +0200 (CEST) Message-ID: <13d701c5bb30$b99fa940$4dd86751@foxbox> Reply-To: "Steph" To: "Adam Maccabee Trachtenberg" , "Leigh Makewell" Cc: References: <43276022.6020702@encode.net.au> <7C.1C.41173.4D828234@pb1.pair.com> <63.BA.41173.BB6E8234@pb1.pair.com> <4328EFC1.3030500@lerdorf.com><38.3D.41173.B58F8234@pb1.pair.com> <64.14.41173.65A69234@pb1.pair.com> Date: Sat, 17 Sep 2005 03:37:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: Re: [PHP-DEV] Re: Bogusing bot (Was: [PHP-DEV] Reference handlingchange and PHP 4.4.0) From: steph@zend.com ("Steph") Nicely said, Adam. ----- Original Message ----- From: "Adam Maccabee Trachtenberg" To: "Leigh Makewell" Cc: 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 > > -- > adam@trachtenberg.com | 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 >