Re: Overhauling the bugtracker project
| From: | Felipe Ribeiro | Date: | Tue, 04 Aug 2009 00:37:05 +0000 |
| Subject: | Re: Overhauling the bugtracker project | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-52554@lists.php.net to get a copy of this message | ||
On Mon, Aug 3, 2009 at 7:50 PM, Brett Bieber<brett.bieber@gmail.com> 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.
>
> Within the bug system, there are two main parts that talk to each
> other. The project site hosting the bugtracker, and the bugs
> themselves.
>
> 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.
> 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.
>
> 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.
>
> 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.
>
> Thanks,
>
> --
> Brett Bieber
>
Hi,
IMHO it's a great idea. It's a nice way to avoid things like if($site
== "foo") and make it possible for the system to be extended in a much
more flexible way. I liked it. If Jani and Philip agree, I can focus
on it with you Brett.
--
Felipe Ribeiro