Re: open bugs
| From: | Stefan Neufeind | Date: | Wed, 24 Mar 2004 19:20:10 +0000 |
| Subject: | Re: open bugs | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-26751@lists.php.net to get a copy of this message | ||
On 24 Mar 2004 at 17:38, Lukas Smith wrote:
> Joe Stump wrote:
>
> > Can anyone with CVS access and a PEAR account sift through and fix
> > things or is that considered a no-no? I know that Ian and I both found
> > bugs in a couple of packages we used for Payment_Process (one Ian had
> > known about for months and submitted a patch long ago).
> >
> > I'd be happy to fix bugs on other packages, but I fear getting yelled at
>
> No. Basically only the maintainer, or anyone they have given explicit
> ok, may make commits to a given package. Therefore the proper course of
> action is to work with the maintainer. You can also provide patches in
> the bug report.
>
> However at the moment we dont have any formal process defined for when
> the maintainer doesnt react to bzug reports and/or patches.
Note in this respect that some might not be reachable or interested
any longer. We need to make sure that they are not on vacation or
somewhere and can't pick emails. But there have been several people
from whom you haven't heared on the mailinglists for quite a while.
And I've heared from a few people that they haven't gotten any email-
reaction (and even if it's a "I'm still alive but busy") after 2 or 3
month. We need to find a good way to deal with this.
But that shouldn't be discussed on pear-dev, but in the pear-qa-team.
And therefor we now really need a "core qa-team", as Helgi suggested
in his excellent RFC imho.
Stefan