Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44853 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6311 invoked from network); 9 Jul 2009 02:50:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jul 2009 02:50:41 -0000 Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 209.85.198.238 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 209.85.198.238 rv-out-0506.google.com Received: from [209.85.198.238] ([209.85.198.238:12056] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 23/A2-27938-FFA555A4 for ; Wed, 08 Jul 2009 22:50:41 -0400 Received: by rv-out-0506.google.com with SMTP id l9so1888872rvb.23 for ; Wed, 08 Jul 2009 19:50:36 -0700 (PDT) Received: by 10.140.144.20 with SMTP id r20mr137677rvd.274.1247107836768; Wed, 08 Jul 2009 19:50:36 -0700 (PDT) Received: from monster.local ([76.84.30.125]) by mx.google.com with ESMTPS id g14sm4435182rvb.4.2009.07.08.19.50.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 08 Jul 2009 19:50:35 -0700 (PDT) Message-ID: <4A555AF9.1090403@chiaraquartet.net> Date: Wed, 08 Jul 2009 21:50:33 -0500 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: Richard Lynch CC: PHP internals References: <52252.99.18.1247074235.squirrel@www.l-i-e.com> In-Reply-To: <52252.99.18.1247074235.squirrel@www.l-i-e.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] bug tracker planning From: greg@chiaraquartet.net (Greg Beaver) Richard Lynch wrote: > On Tue, July 7, 2009 12:54 pm, Philip Olson wrote: >> - Reclassification : Discuss how we handle this, like should old/new >> lists both receive emails? > > Both lists should receive reclassifaction notification, and nothing > more, imho. > >> - Consider different captcha (like reCaptcha) for anonymous users > > Yes, please. The current one takes 3 tries to get right, for me. The PEAR bugtracker has been using a no-captcha-necessary method that to catch spam, and it is working great now. The only caveat was that it took a little while to work out the kinks. It works by creating named user accounts and requests a password after you click a link in an email sent to you. Bugs that don't get confirmed by the user within 2 weeks get purged, and unvalidated bugs can be viewed by folks logged into the tracker with their pear accounts. This tends to cut down on both spam and poorly thought-out bug reports. The disadvantages are obvious: everyone has to have an account and give their email address to report a bug. The advantages are also obvious: much more disability-friendly, tracking reports by users is easy, and upgrading a frequent reporter to a developer is also easier, no captchas ever again and easy per-reporter statistics. We use this in PEAR just to see who is active reporting and fixing bugs. Greg