Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18968 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75752 invoked by uid 1010); 15 Sep 2005 12:34:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 75733 invoked from network); 15 Sep 2005 12:34:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Sep 2005 12:34:32 -0000 X-Host-Fingerprint: 203.41.13.159 unknown Received: from ([203.41.13.159:19190] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 64/14-41173-65A69234 for ; Thu, 15 Sep 2005 08:34:30 -0400 Message-ID: <64.14.41173.65A69234@pb1.pair.com> To: internals@lists.php.net Date: Thu, 15 Sep 2005 22:34:21 +1000 User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 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> In-Reply-To: X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 203.41.13.159 Subject: Re: Bogusing bot (Was: [PHP-DEV] Reference handling change and PHP 4.4.0) From: leigh@eon.com.au (Leigh Makewell) 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 Ask them what their issues have been, what can be done to improve the process. Most of all don't *ever* just dismiss a bug report the way you do. Comments like the one here http://bugs.php.net/bug.php?id=34196 are not acceptable. This comment of yours amazes me! "2) I'm not bogusing automatically anything (except for few exceptions [1])" You just admited that you do automatically bogus bugs if you don't like the person. You should never EVER be doing that under any circumstances. Tell them it's a duplicate and link them to the relevant open bug, and then close it. The people who submit bugs are helping you make the product better. You should never insult a person for trying to help you. Tell them you are unable to reproduce the error and then point them to the relevant documentation on how to give you better information. In other words, help them help you! If you are getting that much hate mail then you are doing it wrong. Leigh. Jani Taskinen wrote: > On Thu, 15 Sep 2005, Leigh Makewell wrote: > >> joke. People critisise and joke about PHP's automatic "Bogus" bot that >> just trolls through the database and marks any submitted bugs as >> "Bogus". What is the point of making the bug database public? > > > 1) I'm not a bot. > 2) I'm not bogusing automatically anything (except for few > exceptions [1]) > 3) I spend a LOT of my free time, without getting paid > testing hundreds of wierd code pieces people send, > configuring and compiling PHP with wierd configure lines, > etc. > > Never forget: MOST of us (me included) do NOT get paid for this. > And handling bug reports is propably the most ungrateful "jobs" > there is. > > I can count the times I've been thanked personally with one hand. > Most of the time people send me hate email. :) > >> highlights it. Why should we bother to continue to support the >> community when the community doesn't support us? We owe PHP nothing. >> There are plenty of alternatives out there. > > > It's the community who should support the developers, not the other > way around. We owe the community nothing, the community owes us > everything. > >> Now don't get me wrong. This is not aimed at everyone. I believe you >> Rasmus > > > Don't lie. You aimed quite well. :) > > --Jani > > [1] People seem to think their problem is the most important one > and even if it's been reported before, still send it as new one.. > in which case their report gets very quickly bogused. :) > There are several other reasons why to do that, but for _valid_ > bug reports this happens VERY rarely. (Try piss me off and you'll see)