Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44831 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97869 invoked from network); 8 Jul 2009 12:01:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jul 2009 12:01:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=jani.taskinen@sci.fi; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=jani.taskinen@sci.fi; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sci.fi from 204.13.248.71 cause and error) X-PHP-List-Original-Sender: jani.taskinen@sci.fi X-Host-Fingerprint: 204.13.248.71 mho-01-ewr.mailhop.org Received: from [204.13.248.71] ([204.13.248.71:57042] helo=mho-01-ewr.mailhop.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E9/A3-12124-B8A845A4 for ; Wed, 08 Jul 2009 08:01:16 -0400 Received: from a88-112-30-186.elisa-laajakaista.fi ([88.112.30.186] helo=localhost.localdomain) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1MOVpp-0006JJ-1P; Wed, 08 Jul 2009 12:01:13 +0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 88.112.30.186 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/ja8LZry3rNRFysG7f6kAx/zm9K2CDA3Q= Message-ID: <4A548A79.20700@sci.fi> Date: Wed, 08 Jul 2009 15:00:57 +0300 Reply-To: jani.taskinen@iki.fi User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Philip Olson CC: PHP internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] bug tracker planning From: jani.taskinen@sci.fi (Jani Taskinen) Philip Olson wrote: > The new system[1] is based off the pear.php.net bug system (via Jani), > which long ago was a fork of our current (bugs.php.net). Because of Pear folks forked it for http://pear.php.net/bugs/ and pecl folks took the same at some point..(?). > this, some of these items are already available via the pear geeks. The Patches, roadmap, etc. > plan is to have one bug tracker that includes PEAR+PECL+Core+GTK+Etc. At #1 stage it's was supposed to be separate installation for each using same codebase but different templates. > First stage: [cut] > - Deal with bug id clashes from current PECL/PEAR/PHP bug trackers, and > associated links This belongs in #2 stage since there won't be any clashes when each have their separate installation and database. > - Importing Of what..? > Second stage: > - Additional history : When a bug was opened/closed etc. Currently we > don't log this except in emails > - Reclassification : Discuss how we handle this, like should old/new > lists both receive emails? > - Consider different captcha (like reCaptcha) for anonymous users > - Voting : Do we use or care about this? Improve? Not used, but would be useful as indicator whether lot of people have same problem. Should be improved and used for search / listings as some sort of "weighting". (more votes -> higher on list..or something :) > - nofeedback improvements : People assume this means closed, when it > does not Like what improvements..? Note in the email / report ? > Third stage: > - Subscriptions : Allow people to subscribe to RSS and/or receive emails > per bug/package RSS feeds already exists, AFAICT: http://cvs.php.net/viewvc.cgi/pear/Bugtracker/bugs/rss/ Just needs to be extended to have feeds per package / project / etc. > - Tagging : Allow people to optionally attach tags to bugs What tags..? > And as always, additional volunteers are welcome. Yup. More than welcome. All the stuff is in cvs with README containing info how to setup it yourselves. :) --Jani