[Zope3-dev] Re: Selecting a code name

Martin Aspeli (sent by Nabble.com) lists at nabble.com
Tue Feb 7 05:46:46 EST 2006

Hj Jeff,

Okay - I'd like to restate my position. :-)

I think you're right - having different names for each release (Zope 3.2 = Blah, Zope 3.3 = Foo) *is* a bad idea, it creates confusion, especially in a framework with frequent releases. So -1 on that from me from now on. :)


Jeff Shell wrote: 
> Beyond that, I think that 'Zope 3' is a good looking set of characters
> and can be a strong brand in and of itself. Just always, always,
> always refer to it as Zope 3. It doesn't need to be Zope on Zydeco or
> something like that. 'Zope 3' has a lot of strong brand potential.
> It's crisp, it's clear, it builds on something established yet can
> differentiate itself from it.
>> The secondary brand name (the Zomething in my example above) was the
>> original example - and I personally think this is a good idea, just to
>> give the clear message that this is distinct but building on Zope 2.
> Zope 2 is seldom referred to as Zope 2. Zope 2.x maybe, but I seldom
> notice it referred to as Zope 2, except now that Zope  3 is on the
> scene. By just adding emphasis to the 3, and it doesn't even need to
> be a strong emphasis, I think we can capture a lot.
> A fancy name isn't going to give the message that this is distinct,
> especially if the experience of finding out what Zope 3 is and how to
> use it starts bringing back painful memories of prior Zopes, or starts
> to mirror the stories people have heard about Zope - "yeah, it's great
> if you can figure it out... good luck figuring it out..."

if you don't mind me using your argumentation to argue my point:

There are a lot of people out there, it seems, that hate Zope. Maybe they hate Zope 2, maybe they even tried Zope 3.0 and got burnt. Somehow, it just seems it's got some bad stigma around it (e.g. look at the average flaming reply to a blog posting about Zope 3). Now, for those people, putting a new name in their heads may be a good way of suggesting that indeed, there is something new and something better here. It's not just the same old Zope with a few more bells and whistles, it's something entirely different. It deserves a second look.

As Stephan pointed out, denying the Zope legacy is denying the work of those who took it from Zope 2 to Zope 3, and denying that we've learnt a lot of lessons from Zope 2. 

Which is why, in my reading, the original proposal for all this was to include all of them: The Zope, the 3 and the new name. And with that, as you identify, some more branding, in terms of resources, in terms of a clear, concise message and tag line, in terms of a good logo that people recognise, and in terms of an outward-facing orientation.

That name should stay the same, across releases!

Let's say we adopted the brand "Zope 3 Singularity", zope3singularity.org, a slogan ("Zope 3 Singularity - Be Adaptive), a logo, a colour scheme, a web site that's simple and on-message.... and a download box that says: Download version 3.2. When version 3.3 comes out, you'd say - NEW! Version 3.3, now with these cool new features, click here to see them in action. The brand stays "Zope 3 Singularity", though. The message stays. The logo stays. And for new adopter that raves about Z3 Singularity being the best thing since sliced bread, people will take note that it's something new, not just the same dreary Zope (2) they tried before.

So why the name, why not just "Zope 3"? You say that for Zope 3 to become a strong brand, people should "Just always, always, always refer to it as Zope 3". What about the ones who didn't get the memo? What about J. Random Blogger who goes on and rants or raves about "the latest version of Zope", forgetting the 3 and people either ignore him as a Zope Zealot (heh) with his head in the sand, or start arguing vigorously against him because they used Zope once in 1998 and didn't like it.

As you said - this isn't easy. We need to be opinionated, proud, clear on our message. We need to take marketing seriously, because at the moment, a beautiful framework is obscured by an awful web site and an absent brand.

View this message in context: http://www.nabble.com/Selecting-a-code-name-t1063275.html#a2798918
Sent from the Zope3 - dev forum at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/zope3-dev/attachments/20060207/6a61ba2d/attachment.htm

More information about the Zope3-dev mailing list