Re: [binarycloud-dev] checkin to pear

[Alex B. <en...@tu...>]

For those of you interested why I decided to do this, for a couple reasons:

    -I am very much interested to see their reaction
    -We adhere to the coding standards, so "why not?"
    -We may end up merging some of the classes, but if we'' only do that if
we get the features we need - so I'm happy to do that. (I.e. we had
discussed adding some things to PEAR_Error, instead of writing a binarycloud
error class from scratch.)
    -Those doing pear are competent, experienced coders, and it can never
hurt to have 'em looking at the code.

It's sort of a whim, very much a political experiment. We'll see what we
see, eh :)

_a



> I think you stand to meet some significant resistance here. One of PEAR's
> goals
> is synergy and non-replication. You'll effectively be giving PEAR its second
> database abstraction layer, as well as some other things..
>
> The exposure is good though.
> 
> John
> 
> On Thu, 12 Jul 2001, Alex Black wrote:
> 
>> hi all,
>> 
>> I'm going to establish a subdir in the pear core cvs: binarycloud/
>> 
>> I'm _not_ going to move primary development to php cvs, but from now on I
>> intend to maintain a fairly up-to-date synch to the pear repository.
>> 
>> :)
>> 
>> _alex
>> 
>> 
>> 
>> --
>> alex black, ceo
>> en...@tu...
>> 
>> the turing studio, inc.
>> http://www.turingstudio.com
>> 
>> vox+510.666.0074
>> fax+510.666.0093
>> 
>> 
>> 
>> _______________________________________________
>> binarycloud-dev mailing list
>> bin...@li...
>> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>> 
>> 


--
alex black, ceo
en...@tu...

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093