Re: Template Proposal

On Friday, November 9, 2001, at 02:26 PM, Chuck Hagenbuch wrote:

Quoting jim winstead <jimw@apache.org>:

i think this distinction between 'core' and 'not-core' is rather arbitrary. the control over a piece of code should lie with the people who are developing it. that group should be responsive to the people using the code. (directly, or through other pieces of code that rely on it.)

I would hope PEAR-izing my code wouldn't be handing over my control of it. I mean, I have a responsibility to my clients with respect to my code, and I wouldn't be necessarily comfortable passing that buck on to others. I think the CORE and EXT difference would be that CORE would be distributed/maintained/etc. by PEAR developers, while EXT would be a distribution situation only. So you control your code, and you commit your code, and PEAR provides an automated distribution mechanism. Lux

decentralization and federation is where it is at, not centralization. with centralization, you just get crap like coding standards that worry about tabs versus spaces. or people who aren't even responsible for developing smarty telling those that are that they have to name their method calls a certain way to have smarty distributed through pear.

That's one vote for CPAN-style. -chuck -- Charles Hagenbuch, <chuck@horde.org> "What was and what may be, lie, like children whose faces we cannot see, in the arms of silence. All we ever have is here, now." - Ursula K. Le Guin -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net For additional commands, e-mail: pear-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net