Re: Re: Rejected packages
| From: | Craig Constantine | Date: | Thu, 19 Apr 2007 15:06:51 +0000 |
| Subject: | Re: Re: Rejected packages | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-46301@lists.php.net to get a copy of this message | ||
--On April 19, 2007 4:59:29 PM +0200 Arnaud Limbourg <arnaud@limbourg.com>
wrote:
>> I would suggest we ditch PEAR-wide PEPr and instead allow collectives to
>> make decisions about whether a related package should be accepted. This
>> will make it a lot more attractive to propose packages, and the folks
>> who actually have some active knowledge of the package's innards will be
>> making the acceptance decision.
>
> Keeping PePr for RFC ?
i think we should leave pepr the way it is. The problem seems to be lack of
general participation by pear developers. If we feel the members of the
collective will active enough to decide via a collective-specific pepr,
then they'll be active enough to decide via a global pepr [as is now.]
We could add a "collective" selection in the pepr proposal to make it
easier for everyone see where the proposal relates. The collective's web
area could then have a "show all pepr proposals related to this collective."
-c