Re: Integrating PEAR bug reporting into bugs.php.net
| From: | Gabor Hojtsy | Date: | Sun, 26 May 2002 18:58:53 +0000 |
| Subject: | Re: Integrating PEAR bug reporting into bugs.php.net | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-10495@lists.php.net to get a copy of this message | ||
Well, I think it would be a bit better to have types
of bugs. Sometime later documentation guys may come up
with needs for "language" or "format" input fields.
A much better way would be a wizard, where first you only
need to select what type of bug you would like to report,
then the specialized bug reporting form should come up.
The types I can think of are: PHP, PEAR, Documentation, Website
There can be more in the future (eg. Smarty, PHP-GTK, etc).
The reason for this is that website bugs do not need
PHP version, and only need OS info in rare cases (browser
rendering issues). But it may need the "browser" info.
Docbugs are discussed earlier.
I know that this kind of redesign of the bugs system is a
huge work, and I cannot volunteer to do it, but it would
be The Right Way [tm] to do it, I think.
Goba
> Hi,
>
> I've taken over the job to set up a bug reporting system for PEAR.
> Stig and I think that the best solution would be to integrate the
> system into the existing one on bugs.php.net.
>
> In order to do this, we think that the following points need to
> be made:
>
> * Bugs.php.net fetches a list of the available PEAR packages and
> their versions once per hour via XML-RPC from pear.php.net.
>
> * Currently there is only the bug type "PEAR related". We suggest
> to split this up into "PEAR feature request", "PEAR performance
> problem", "PEAR bug" and "PEAR critical bug".
>
> * If one chooses one of this types on report.php, several text
> fields are activated via javascript:
>
> - PEAR Package name
> - PEAR Package version
> - Output from "pear list" [optional]
>
> Unless you don't select one of the PEAR bug types, this fields
> will be either deactivated or hidden via some CSS tweaks.
>
> * When searching for PEAR bugs, the additional fields I mentioned
> in the previous point will also be shown.
>
> If you have more suggestions, we are happy to hear them. If
> you finally agree, I will apply this changes to php-bugs-web in
> the next weeks.
>
> For the long term we are also planning to export the functions
> from bugs.php.net via XML-RPC or SOAP, so that we can build
> our own bug reporting forms on the PEAR website and don't need
> to bug you with our wishes :-).
>
> - Martin
>
> --
> Martin Jansen, <mail@martin-jansen.de>
> http://www.martin-jansen.de/
>
>
>