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? -- Robin Becker
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 distribution that he uses. Other than that, there could be other reasons, we, for example, do not provide a mechanism for community checkin privledges, Sourceforge does. I don't think we have a ZODB specific mailing list, sourceforge offers this. That being said, I'm pretty sure we've allways kept up with Andrew's patches and suggestions, and we'd be happy to create a mailing list. Andrew has also extended any developer at DC checkin privledges at the sourceforge project; although I suspect we'll just continue to check into our CVS and he'll "sync" with us that which he wants. I am, in particular, barely not lazy enough to check stuff into branches, much less whole other repositories. ;)
I really liked the ZEO examples, but where's this going?
It's just open source. More power to him in my opinion. He's definatly taking Zope and ZEO to new levels and audiences. -Michel
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 Pelletier wrote:
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 distribution that he uses.
Other than that, there could be other reasons, we, for example, do not provide a mechanism for community checkin privledges, Sourceforge does. I don't think we have a ZODB specific mailing list, sourceforge offers this.
That being said, I'm pretty sure we've allways kept up with Andrew's patches and suggestions, and we'd be happy to create a mailing list.
Andrew has also extended any developer at DC checkin privledges at the sourceforge project; although I suspect we'll just continue to check into our CVS and he'll "sync" with us that which he wants. I am, in particular, barely not lazy enough to check stuff into branches, much less whole other repositories. ;)
I really liked the ZEO examples, but where's this going?
It's just open source. More power to him in my opinion. He's definatly taking Zope and ZEO to new levels and audiences.
-Michel
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- . . . . . . . . . . . . . . . . . . . . . . . . John D. Heintz | Senior Engineer 1016 La Posada Dr. | Suite 240 | Austin TX 78752 T 512.633.1198 | jheintz@isogen.com w w w . d a t a c h a n n e l . c o m
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 public view. It is useful code in its own right, and looking at it can only help people understand what's going on inside Zope. jon Jonathan Corbet Executive editor, LWN.net corbet@lwn.net
"RB" == Robin Becker <robin@jessikat.fsnet.co.uk> 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 to a larger audience of developers. Andrew's project will focus primarily on packaging, testing, and documentation. In the short term, the easiest way to accommodate his needs are to have his own SF project. The plan is to have the two different CVS repositories integrated at the level of working directories. Developers will probably end up with checkouts of both CVS trees, knit together so that Andrew's setup scripts and the like encapsulates the source code from the DC tree. (This setup makes the initial checkout a little complicated, but cvs update should work normally.) Andrew, Jim, and I and the rest of the PythonLabs team chatted about these plans over Chinese food on Wednesday. PythonLabs plans to get much more involved in ZODB development. One goal of that involvement is to promote ZODB's use within the Python community, and Andrew's work is an important part of that promotion. Jeremy
In article <14897.18005.7253.235830@bitdiddle.concentric.net>, Jeremy Hylton <jeremy@digicool.com> writes
"RB" == Robin Becker <robin@jessikat.fsnet.co.uk> 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 to a larger audience of developers. Andrew's project will focus primarily on packaging, testing, and documentation. In the short term, the easiest way to accommodate his needs are to have his own SF project.
The plan is to have the two different CVS repositories integrated at the level of working directories. Developers will probably end up with checkouts of both CVS trees, knit together so that Andrew's setup scripts and the like encapsulates the source code from the DC tree. (This setup makes the initial checkout a little complicated, but cvs update should work normally.)
Andrew, Jim, and I and the rest of the PythonLabs team chatted about these plans over Chinese food on Wednesday. PythonLabs plans to get much more involved in ZODB development. One goal of that involvement is to promote ZODB's use within the Python community, and Andrew's work is an important part of that promotion.
Jeremy ... Thanks! -- Robin Becker
participants (5)
-
corbet-zope＠lwn.net -
Jeremy Hylton -
John D. Heintz -
Michel Pelletier -
Robin Becker