Re: Overhauling the bugtracker project

On 08/04/2009 01:50 AM, Brett Bieber wrote:

Hi, I've been looking through the Bugtracker project, examining the feasibility of using it for PEAR2, and it seems like a lot of work would need to be done to use it with a site that does not have roots in phpbugs or pearweb. Currently it is difficult to change how the bugtracker interacts with the site/project/package it's collecting bugs for. If I want to customize how my site functions I have to add in if ($site=='pear2') … at every instance where info about a package is gathered. Currently there are quite a few similar checks for if $site=='php', because a lot of pecl/pear package specifics don't apply to php bugs.

You forgot the main goal totally here which is to get ONE single bugtracker that handless ALL bugs in ALL our sites. The first stage was to come up with some kind of unified code base.

Within the bug system, there are two main parts that talk to each other. The project site hosting the bugtracker, and the bugs themselves.

Why do they need to "talk" to each other? Define "talk" ?

I've no real problem with the bugs db or the forms, but I do have some problems with the expectations of what the bugtracker considers a site, package, releases etc and would like to handle this all myself.

See above, main goal!

So I'm proposing revamping quite a bit of the functions.inc file. Moving everything related to the bugs to a class Bugtracker, and everything related to the site/project as a class that implements interface Bugtracker_Site.

What does this give us over plain functions? Except for another extra file to be included.

Then we would have one class for each of the sites, PECL, PEAR, PHP, PEAR2, and each of these would have the details of what the site considers a valid package, pseudo package, etc. PEAR and PECL are so similar one could extend the other, and I could supply all the details for PEAR2 as I see fit.

*sigh*, see above..

I've started some work on this, and I have a patch that just scratches the surface. But, before I go much further I'd like to know if the leads think this is the correct direction to go. Any feedback would be appreciated as well. Basically I want to know if I can make the modifications I need for using the Bugtracker with PEAR2, or if I should start my own project using the same schema.

No more separate trackers. This thing is supposed to be eventually on one site, on one database. --Jani