Re: Zope3 name

Seb Bacom wrote:
>Paul Everitt wrote:
>> IMO, Zope 3 is being positioned as appealing to people that want to 
>> start over in Zope, not really for people that want to preserve their 
>> investment.  I believe the position on the latter group is: "Stick with 
>> Zope 2".

>Right.  I think this is the approach with the most promise, which will 
>keep everyone happy.

Here's how the "backport" itch might yet arise:  a zope services
company with Zope2 sites whose customer wants a wiz-bang new feature
that is most easily implemented by backporting a Zope3 component.
(This of course assumes that the *rest* of the site would take much
longer to reimplement in Zope3).

This won't happen until Zope3x is more mature, though.

Personally I wouldn't have a problem with Zope3x getting renamed
ZopeNG, or .... hmm .... how about Zope Enterprise? <1/2 grin>.

In fact, visualizing talking about it to my boss, I think he'd
understand a lot better if I said this new thing I was occasionally
working on was Zope Enterprise (ie: a much more capable Zope platform,
albeit one that is not complete yet), but that we'd continue to run
our established clients on plain old Zope unless they had a reason
to switch (which is what is going to happen no matter what the
names are that are involved).

Of course, we *are* talking here about greatly extending that
transition period that was mentioned in the other thread.  Like to
several years, not just a couple.  But I think renaming it makes
the transition seem *voluntary*, whereas the name Zope3 makes it
feel like you *have* to switch sooner or later.  I don't think the
end result is different except for the longer expected transition
period, but I think the perceived comfort level would be.

And if there is an issue of ZC strategy (ie: ZC is going to
switch in that shorter period), ZC can always give up all
development/maintenance repsonsability for plain old Zope
(POZ? <grin>) to the community that is still actively using
it, whatever size that community turns out to be.

I'm not wedded to this idea.  I'm not even sure I'm advocating
it.  But it is certainly worth thinking about.

--RDM