Re: Template Proposal

On Fri, Nov 09, 2001 at 02:01:18PM -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's an interesting idea. We could, in theory, have "officially-sanctioned" PEAR code that lives in cvs on cvs.php.net. That would have to follow all of our guidelines. Then, we could have all of the other "contributed" code. The main PEAR package browser on pear.php.net should still list all of the packages, but some would be marked "official" (or some other term that doesn't necessarily assume everything else is less official or inferious) or "contributed". -- Jon Parise (jon@csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member