Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29957 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87635 invoked by uid 1010); 30 May 2007 16:39:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 87620 invoked from network); 30 May 2007 16:39:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 May 2007 16:39:01 -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 66.79.163.178 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 66.79.163.178 bluga.net Linux 2.5 (sometimes 2.4) (4) Received: from [66.79.163.178] ([66.79.163.178:57025] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7A/00-20580-1A8AD564 for ; Wed, 30 May 2007 12:38:58 -0400 Received: from mail.bluga.net (mail.bluga.net [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 7A1D58742B for ; Wed, 30 May 2007 09:41:40 -0700 (PDT) Received: from [192.168.0.106] (CPE-72-133-60-138.neb.res.rr.com [72.133.60.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id 41233873DC for ; Wed, 30 May 2007 09:41:40 -0700 (PDT) Message-ID: <465DA8F9.2020001@chiaraquartet.net> Date: Wed, 30 May 2007 11:40:25 -0500 User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: internals Mailing List X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: bug tracker merging From: greg@chiaraquartet.net (Gregory Beaver) Hi all, I'm a bit concerned by the headlong rush to refactor phpbugsweb to include PEAR and PECL bugs. The concept is fine by me, but starting with phpbugsweb as the starting point is a big mistake if you plan to include PEAR bugs. The PEAR bug tracker has several killer features that you will have to pry from my cold dead fingers before I would accept a merge with the phpbugsweb 1) patch tracker complete with versioned patches 2) roadmap support with auto-generation of package.xml based on closed bugs/features 3) limited-privilege accounts eliminate the need for CAPTCHA altogether (all you need is the ability to check email and fill in a form with name and password after the fact). We haven't had any spam bugs since implementation and it is more handicapper-accessible. http://pear.php.net/bugs/report.php?package=PEAR_ErrorStack to see an example, all that is required is a valid email address and the ability to add or subtract numbers between 1 and 100 The main problem with the codebase of pearweb/bugs is that it depends on the core of pearweb (bad) and so needs to be independentized, but we are doing this ASAP. roadmap for the website is at http://pear.php.net/bugs/roadmap.php?package=pearweb Of course, it's also in the process of being refactored along with the rest of pearweb (unit tests *gasp*) so please don't discount a look at this codebase, no matter how bigoted against PEAR you might be ;) Greg