Re: bug tracker planning

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