[Zope-dev] Re: Re: Two visions
Geoff Davis
geoff at phds.org
Thu Mar 2 09:24:53 EST 2006
On Thu, 02 Mar 2006 09:43:03 -0330, Rocky Burt wrote:
> Anyway, this still keeps things very confusing from a naming perspective
> (mostly for new adopters). So .... having said all of that, I am
> actually +1 on Jim's proposal #2. What I see from that (someone correct
> me if I'm wrong) is the following:
>
> 1) rename zope 3 the framework as Z or zopelib or Zed or something
> sensical that doesn't confuse the early adopter's conquest of trying to
> figure out which zope to start with
> 2) Make zope 2 the application server acquire the name "zope" once
> again and be the only app server. This could only work (from a new
> adopter's perspective) if either the application server is given a new
> name or given a version number higher than 3.
I agree with Rocky's assessment. +1 on Jim's suggestion #2.
However, if I am understanding things correctly, it doesn't really sound
like door #2 entails a huge deviation from from our current course of
bringing Zope 2 and Zope 3 together gradually. I don't really care what
the converged product is called, Zope 2.250 or Zope 3.99 or Zope 5.
My take is that Jim is not really proposing anything all that
different from what Martijn wants -- a gradual convergence of Zope
2 and 3. Rather, it sounds like the biggest changes in Jim's proposal #2
entail
1) a change in how we _talk_ about what we are doing, and
2) an explicit attempt to factor out some of the Zope 3 goodness into a
more generic, less-monolithic-app-server framework, Zed.
(am I right here, Jim?)
I think that the idea of giving Zed its own, distinct identity is great.
Zope 3 is a _huge_ overhaul and it needs to be obvious to the world that
it is dramatically better than crufty old Zope 2. Zope 3 then becomes the
Zed application server; Zope 2 is getting Zed retrofits via Five, and the
two will eventually converge into Zope 5.
A distinct Zed distribution could bring in developers who are just
interested in using the component architecture but not necessarily a
big app server stack. It would be cool to see Zed popping up in random
python products or perhaps in TurboGears / Django internals. And more
than just cool -- the more people we can get using Zed, the more code we
will be able to mix in easily to Zope (2/3/5) applications.
Geoff
More information about the Zope-Dev
mailing list