RE: [phplib] To PEAR Or Not To Pear From: Jeffrey A. Stuart (jstuart-php <email protected>)
Date: 03/09/01

Ok, here's the deal. :) I'm gonna do the work. If the phplib folks want it,
they can have it. If the pear folks want it, they can have it. If one
doesn't want it... OK... If both don't want it... well... I've wasted my own
time... :)

This is my point... I'm going to work on a possible merge... I was told (and
RIGHTLY so) that if the merge was wanted, then someone had better step up to
the plate. And if I didn't like what was going on or how it was moving, well
then... DO something about it. So I have. :)

And I give you the same challenge... If you want to have a say in how the
merge that I've started is going to go, PLEASE join the source forge project
(http://sourceforge.net/projects/pear-phplib/).

And EVERYONE, PLEASE understand, I am NOT saying "It's my way or the highway."
HELL no... I'm simply offering my time to work on doing this merge. Which
IMNSHO is a GOOD thing. It gets phplib out into the greater masses, helps
pear, and helps PHP. 

--
Jeff Stuart
jstuart <email protected>

> -----Original Message-----
> From: Richard Archer [mailto:rha <email protected>]
> Sent: Friday, March 09, 2001 4:48 PM
> To: phplib <email protected>
> Subject: RE: [phplib] To PEAR Or Not To Pear
>
>
> At 2:34 PM -0500 9/3/01, Jeffrey A. Stuart wrote:
>
> >  far as the merge, it's happening... nothing is going to stop
> >that... That is unless the pear folks say no or the phplib
> >developers say no.
>
> Do you really think the hundreds of PHPLib users have no say in this?
>
> Personally what I like about PHPLib is the speed, efficiency and
> quality of the code. If a condition of the merge with PEAR means all
> three of these advantages must be destroyed, then I (and I suspect
> many other PHPLib users) will continue to use a stream of PHPLib
> developed from the current PHPLib tree.
>
> Whether this happens at all depends on the attitude of the PEAR
> people. If PEAR is indeed a Repository then PHPLib should be added to
> the repository and this future development can happen within the PEAR
> framework.
>
> If PEAR insists on breaking up PHPLib and merging it with their
> bloatware then PHPLib will continue to be developed in it's own right
> -- either within the Netuse environment or as a new SourceForge
> project.
>
> The future of PHPLib depends on the attitude of the both the PHPLib
> and PEAR developers, but one thing is for sure -- PHPLib is going to
> continue in it's own right either within PEAR or on it's own.
>
>   ...Richard.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: phplib-unsubscribe <email protected>
> For additional commands, e-mail: phplib-help <email protected>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>