In article <[EMAIL PROTECTED]>, Jeremy
Hylton <[EMAIL PROTECTED]> writes
>> "RB" == Robin Becker <[EMAIL PROTECTED]> writes:
>
> RB> Anyone know why AM Kuchling needs to split off a Sourceforge
> RB> project based on ZODB? I really liked the ZEO examples, but
> RB> where's this going?
>
>It
> "RB" == Robin Becker <[EMAIL PROTECTED]> writes:
RB> Anyone know why AM Kuchling needs to split off a Sourceforge
RB> project based on ZODB? I really liked the ZEO examples, but
RB> where's this going?
It is the most expedient way to start opening ZODB development,
including ZEO, up
> Anyone know why AM Kuchling needs to split off a Sourceforge project
> based on ZODB? I really liked the ZEO examples, but where's this going?
I think it was a great move, myself. He has taken a really cool piece of
the Zope infrastructure that tends to remain hidden and brought it out for
pub
The Sourceforge exposure gives people like me with an itch to scratch a
place to work on a publicly visible branch of ZODB for my two proposals
without breaking anything or relying on patch files continually.
John Heintz
PS My proposals are ExplicitTransactions and PersistentBlob ;-)
Michel P
Michel Pelletier <[EMAIL PROTECTED]> writes:
> I am, in particular, barely not lazy enough to check stuff into
> branches, much less whole other repositories. ;)
Nicely put. Posted on zwiki.org so I can use it later. :)
-Simon
___
Zope-Dev maillist -
On Fri, 8 Dec 2000, Robin Becker wrote:
> Anyone know why AM Kuchling needs to split off a Sourceforge project
> based on ZODB?
I don't think it's a "split", but AMK is using ZODB internally at his
job, and externally with his own projects, so I can see him wanting to
have some control over the
