[Collective-versioning] Re: [houston-sprint] Focus & Direction

[alan r. <al...@en...>]

> I certainly agree that versioning has been done a number of times.  I'm
> not a developer but it looks to me like the Collective-Versioning team
> has just done this at their Pisa sprint and are currently wrapping it
> up.  I'm cross-posting this reply to get their comments because I'm
> confused about which of the various versioning branches is going to live
> and it seems silly to duplicate all of this work constantly.

I understand what it looks like - and I'm not trying to be inconsiderate.
Basically the versioning in CMFEditions looks like what we will be using.
There is an awful lot in there that covers their use-cases that isnt
generic enough for Plone.  Search for 'portal_multisite' in CMFEditions.

Some of the code needs to be cleaned up and factored out.  The basic
versioning scheme is all the same across all of these projects -
ZopeVersionControl.  I am more interested when ZVC is *not* appropriate.
We have nailed down the ZVC parts.  We are going to sync up with
CMFEditions guys - I hope.  They are busy working on their code for a
delivery.

What I am hoping is possible is that we can say here are the tools and
CMFEditions can call our API's instead of using their own.  Does that
make sense?  They may not be able to participate.  We have very competent
people.  Enfold is sponsoring Kapil to come to Houston.  Rice has some use
cases.  Some coders from Comp. Associates will be there.

I am trying to lead people into something that everyone can use.  So its
basic.  Something that we can potential port our code over to using as
well.
We want the most basic case.  Then we can add on to it.

-- 
Alan Runyan
http://www.enfoldsystems.com/
p. +1.713.942.2377
f. +1.832.201.8856