Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44935 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91294 invoked from network); 11 Jul 2009 10:11:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jul 2009 10:11:47 -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:59676] helo=mho-01-ewr.mailhop.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D6/34-37812-265685A4 for ; Sat, 11 Jul 2009 06:11:46 -0400 Received: from cs181029147.pp.htv.fi ([82.181.29.147] helo=[127.0.0.1]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1MPZYV-0000Ds-Ab; Sat, 11 Jul 2009 10:11:43 +0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 82.181.29.147 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/1kgvz7hhxl2vRC072DSGPJSahm+RdLK8= Message-ID: <4A586561.5030506@sci.fi> Date: Sat, 11 Jul 2009 13:11:45 +0300 Reply-To: jani.taskinen@iki.fi User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Sriram Natarajan CC: Philip Olson , PHP internals References: <4A5664A3.6000604@GMail.COM> In-Reply-To: <4A5664A3.6000604@GMail.COM> 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) Please don't top post! And what you ask for is already there. --Jani Sriram Natarajan kirjoitti: > Hi > I very much miss the ability to add my email address to the bugs that I > am interested in. This used to allow to me to track its progress. I > wasn't not sure, if that is what you meant within Subscriptions.. > > - sriram > > > Philip Olson wrote: >> >> The bug system today works fine but improvements are being made. I've >> gone through the lists and details from past attempts and will list >> ideas here. Please do not vote, but if a particular item appears like >> a bad idea then please explain. Or, discuss additional (or modified) >> ideas that will be useful to the PHP project. >> >> 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 >> this, some of these items are already available via the pear geeks. >> The plan is to have one bug tracker that includes >> PEAR+PECL+Core+GTK+Etc. It's also planning to go live after Stage #1 >> is completed, and also Jani and 2009 GSoC student Felipe Ribeiro are >> working on this project. Soonish a test system will be setup for all >> to break. Yes, this really is happening. >> >> Most people like the current system because it's simple, and I don't >> foresee this changing. >> >> First stage: >> - Cleanup code (in progress) >> - Attachments : For a diff, test, backtrace, screenshot, whatever. (done) >> - Package/Type separation : Packages (like extensions) and Bug Types >> (like feature requests) are separate (done) >> - Defined/Documented permissions : For example, so we all know if a >> random person can comment on a bogus bug >> - Preview button, instead of only submit (almost done) >> - Deal with bug id clashes from current PECL/PEAR/PHP bug trackers, >> and associated links >> - Importing >> - Testing >> >> 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? >> - nofeedback improvements : People assume this means closed, when it >> does not >> >> Third stage: >> - Subscriptions : Allow people to subscribe to RSS and/or receive >> emails per bug/package >> - Tagging : Allow people to optionally attach tags to bugs >> - IRC integration : Allow bot integration to an IRC channel, like a >> #php.bugs resurrection >> - Optional milestones (in pearweb today) >> - Integrate with VCS. Research this, KISS. Ex. A commit containing >> "PHP Bug #42" automagically appends info to the bugs db >> - Befriend systems like http://bts-link.alioth.debian.org/ >> - OpenID support, see also http://wiki.php.net/ideas/phpnetauth >> - Username finder for the 'assigned' boxes, see also >> http://people.php.net/ >> >> And as always, additional volunteers are welcome. >> >> Regards, >> Philip >> >> [1] http://cvs.php.net/viewvc.cgi/pear/Bugtracker/ >> >> >