RE: [PEAR-DEV] Template Proposal

On Fri, 9 Nov 2001, Martin Jansen wrote: > On Fri, 9 Nov 2001 14:01:18 -0500, Chuck Hagenbuch wrote: > > >Personally, the way to break it out seems to be not to merge them, but to have > >two layers: A core set of classes like DB, Log, Mail, etc, that have been > >adopted by pretty much everyone and aren't duplicated inside the core. They > >have consistent style, strict standards, and are actually kept under reasonable > >API control, etc. > > That sounds like an interesting plan. But via which kind of criteria > do you want to decide if something becomes member of the core set or > not? > What about a simple consensus of case by case scenarios ? I would believe that a good criteria would be the adoption of the current PEAR coding standard and a semi-decent review of the codeset (which most people already do anyway here on pear-dev before adding new packages to the system). What is being proposed is basically 'php4/pear' staying as the CVS space for the core set of libraries (or even putting it all on 'pear', doesn't matter much) and then having more control of what happens to the CORE package of PEAR libraries. Joao -- João Prado Maia <jpm@phpbrasil.com> http://phpbrasil.com - php com um jeitinho brasileiro -- Precisando de consultoria em desenvolvimento para a Internet ? Impleo.net - http://impleo.net/?lang=br