Re: RFC: PEAR Changes / Scope
| From: | Alexander Merz | Date: | Sun, 11 Nov 2001 23:35:56 +0000 |
| Subject: | Re: RFC: PEAR Changes / Scope | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2825@lists.php.net to get a copy of this message | ||
> can download them from SF or wherever (we want mirrors, right?) But
> without registration in our database, it'll all fall apart with name
> conflicts and chaos.
i've no problem with registration them in a database, but Lux has such a thing
like PHP-Sourceforge in mind. Anybody mentioned that CPAN have more than 100
template classes - how many of them are maintained, well documentated and
evaluted? CPAN concept is Quality by Quantity. Is this your goal?
His idea of EXT isn't the idea of PEAR. Coding Standards are essential to keep
quality and make the reviewing process as easily as possible. The question is
to be more restrictive to keep quality or to do the CPAN way.