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

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

> 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...

Yes, I understand the important of group development, especially in
this situation where there are a lot of people interesting in lending
a hand but with little individual free time.

I'm just afraid that people will start viewing PEAR as a large
collection of classes in varying stages of development.  There is also
the danger of users writing code that references the classes in
PEAR/PHPLIB/, which (as I understand it) will only be their temporary
location.

As a side issue (and I've mentioned this before), PEAR really should
have its own source respository.  I don't really like the idea of PEAR
being distributed with the PHP releases.
 
> 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... ;)
 
Chuck and I just happen to agree on a lot of project management and
engineering points.  We're also pretty vocal about them.  For the most
part, my opinions, at least, are based on years of experience with the
Horde project (both coding and support).

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