Re: [phplib] CVS Account From: Fred Yankowski (fred <email protected>)
Date: 03/08/01

On Thu, Mar 08, 2001 at 08:33:44PM +0100, Ulf Wendel wrote:
> for all those that want CVS accounts, please mail to Kristian
> (mailto:kk <email protected>), he's managing the CVS at NetUSE.

OK, done.

But I'm starting to have reservations about doing the work on the
NetUSE server, since we'll depend on people there to pull together
distributions and do other administration, and you make it sound like
we'll get only begrudging support.

> Let me also clearify my "use the NetUSE infrastructure" statement. I'll
> finish the Form work in the PHPLib CVS and provide bug fixes for my
> code, but future commits of mine will go into PEAR. If you want to go
> for a "final", stable CVS please use the NetUSE infrastructure and do
> not copy the CVS to Sourceforge or whereever. Thanks!

I don't understand your condition on our use here. I am most
interested in bug fixes to the current PHPlib, not some grandiose plan
of enhanced features, but I'm not ruling out some evolution of new
features either, or trickling-in of later bug fixes.

You seem to want to both wash your hands of PHPlib, never to bother
with it again, and to also control its future. I mean, if you're not
interested in keeping PHPlib alive, why do you care whether it gets
moved to SourceForge? One big advantage of Open Source, and PHPlib
does use the GNU LGPL license, is that if the original "vendor"
abandons the code then others can take it up and keep it alive. That
seems to be happening here, and I don't think the vendor has the right
to say, "no, we want this code dead, never to change".

I'm not actually all that interested in being a champion of "PHPlib
forever". PHP and PHPlib work for me, but I have no great affection
for either of them. I'm not joining the PEAR project, at least now,
because it's of no immediate value to me and doesn't interest me. As
I've said, however, I would like to keep PHPlib alive, if not growing,
and incorporate a few patches that make PHPlib applications more robust.

Does NetUSE support such limited but ongoing evolution of PHPlib, or
not? If you insist on some drop-dead point where further changes to
PHPlib will be disallowed, please let us know. If PHPlib does become
permanently frozen at NetUSE, which by all appearances has already
happened, expect that PHPlib _will_ be resurrected somewhere else.

If it's the name itself, "PHPlib", on which you insist on retaining
control, we could certainly choose something else. "Son of PHPlib"?
"PHPlib2001"? "eXtreme Phplib?" [Yet another "XP", just to confuse.] 

-- 
Fred Yankowski           fred <email protected>      tel: +1.630.879.1312
Principal Consultant     www.OntoSys.com       fax: +1.630.879.1370
OntoSys, Inc             38W242 Deerpath Rd, Batavia, IL 60510, USA

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