Re: Something about PEAR policy

On Sat, 21 Jul 2001, Jon Parise wrote: > On Sat, Jul 21, 2001 at 08:51:46PM +0200, Bjrn Schotte wrote: > > > Personally, I would like to see PHPLIB's Template, Auth > > and DB class migrating into PEAR. So what's the point > > against PEARifying these classes and integrating them > > into PEAR? This is, I think, the point of the whole > > discussion. (Correct me, please, if I miss the point.) > > I don't think anyone is objecting to the inclusion of PEAR-ified > PHPLIB components. The only outstanding issue is for someone to > actually do the work (i.e. convert them to the established PEAR > standards). > That would be wonderful in the end. There are a few practical problems with that line of thinking though. Specficily, what about everyone who depends on the exsisting PHPLib API? > I believe the original "problem" (at least, from my viewpoint) > was that some people wanted to import PHPLIB wholesale (without > conversion) into the PEAR cvs tree. I argued for their > separation into individual components (e.g. 'template', 'auth'), > but, once again, no one has done to work. Yes, but that breaks all of the PHPLib API. Good for PEAR, bad for evey person and app using PHPLib -- hence the notion of a wholesale import of PHPLib as an App Framework with the understanding of a gradual PEAR-ification of the API, or something to that effect (a wrapper class, etc..), as it would allow a gradual process for phplib users and a better porting process for PEAR, allowing the classes to be not only ported but improved upon as well with the PEAR community's input and suggestions. Again, that kind of thinking [just components] is what I mean when I say "insular pratices." It offers PHPLib (or BinaryCloud or phpSlash, etc..) no incentive to port over to PEAR becasue there is little flexibility to make people other than PEAR users / developers happy. It seems that it's PEAR's way or the highway. This is all further complicated by the fac that PEAR's way is a constanly moving and amorphus target to which few people can divine. I don't really want to sound mean and I'm not trying to start a flame war, but really, there are some implementation problems with PEAR that haven't gone away and make it hard for others to extend and contribute. In time that will all pass. All I really want is for phplib to continue doing it's own thing until such time that all of these question can be answered (and documented) for all and they are upheld over time. That won't happen in a day, or a weekend or a month, and as such phplib needs to be continued in development. -n -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- nathan hruby / digital statement nathan@dstatement.com http://www.dstatement.com/ Public GPG key can be found at: http://www.dstatement.com/nathan-gpg-key.txt ED54 9A5E 132D BD01 9103 EEF3 E1B9 4738 EC90 801B -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-