RE: [PHP-PEAR] RFC on merge of PHPLib and Pear

Well, it's called team development. :)  Ideally, I'm not going to be the
only one working on it... that's why I want to temporarily move it into
Pear::PHPLib and then move it around... Now if you're saying, don't commit
the code into pear well... OK.. I guess... I can do the work somewhere else
(like sourceforge) but... then I don't see as many of the pear folks going
over to SF to work on it there when it could be worked on here...

If you have a better idea, PLEASE post it... but this came about today
because Ulf was right... people are asking but not submitting... So... I
decided today to get off my ass and submit... :)  If I'm completely wrong on
this, I hope that entire list will tell me so... :)  So far, I'm seeing just
you and Chuck saying no... Or maybe there's a miscommunication.  I'm not
sure which... ;)

Anyway, I'm out of here for about 5 hours.  I look forward to all of the
email. ;-)

--
Jeff Stuart
[email protected]

-----Original Message-----
From: Jon Parise [mailto:[email protected]]
Sent: Wednesday, March 07, 2001 12:10 PM
To: [email protected]
Subject: Re: [PHP-PEAR] RFC on merge of PHPLib and Pear

On Wed, Mar 07, 2001 at 12:06:42PM -0500, Jeffrey A. Stuart wrote:

> But chuck, the whole idea here IMHO is to at least get code IN and let
> people look at it... ala Pear::DB...

I don't understand why people can't look at the code outside of PEAR?

I don't mean to be a pain here, but it seems silly to import code just
to throw it into a staging area.  Interest parties should work on the
code outside of PEAR and import it when it's ready.

--
Jon Parise ([email protected])  .  Rochester Inst. of Technology
http://www.csh.rit.edu/~jon/  :  Computer Science House Member

--
PHP Extension and Add-on Repository (PEAR) mailing list.
Documentation can be found at http://pear.php.net/doc/pear.html
To unsubscribe, e-mail: [email protected] from the
mail address you subscribed with.