On 2/7/06, Martin Aspeli [EMAIL PROTECTED] wrote:
1. This is new different platform, based on Zope ideas but with
absolutely different code bases
Indeed. This is why I think that if a proper moniker (e.g. Zope3 Zimba)
would be better.
No, it would only make people go What, first Zope 2,
On Monday 06 February 2006 12:33, Dieter Maurer wrote:
No it is not. Explicit is better then implicit. declareSite creates a
new site in the sites mapping. We use this pattern for layers and skins
already.
If it *creates* something why itn't its name createSite
(rather than declareSite).
Lennart Regebro wrote:
On 2/7/06, Martin Aspeli [EMAIL PROTECTED] wrote:
No, it would only make people go What, first Zope 2, then Zope 3, now
Zope Zimba? thinking it's three different things.
But always writing it Zope3 might be helpful.
Telling that there is a difference between Zope 2
On Monday 06 February 2006 19:18, Roger Ineichen wrote:
Does somebody know if there is a method for check if
a teardown get called after a test? Some hints?
No, this is usually painful tracking down. You could check for test setup code
that assigns AttributeAnnotatable to File. Also note that
On Tuesday 07 February 2006 00:31, suresh wrote:
No it is not. Explicit is better then implicit. declareSite creates a
new site in the sites mapping. We use this pattern for layers and skins
already.
Can you have site... directives without a corresponding
declareSite...? What would that
On Monday 06 February 2006 20:49, Gary Poster wrote:
How about we have a marketing competition? :-)
+1 from me plus everything else you said below.
Regards,
Stephan
--
Stephan Richter
CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and
Stephan Richter wrote:
On Monday 06 February 2006 20:49, Gary Poster wrote:
How about we have a marketing competition? :-)
+1 from me plus everything else you said below.
Yep, it's a good idea.
--Paul
___
Zope3-dev mailing list
Gary Poster wrote:
[snip a few things that we think would be nice and useful for the packages]
Sure. I'd love to. I'm happy if I at least get the stuff open-
sourced, though. Life is full of compromises.
I understand the spirit in which these were donated to the community,
and it's
Hi there,
Just to drop a note that I think a discussion about a potential brand
name for Zope 3 is far less important than actually fixing our website
and presenting Zope 3 (and Zope 2 for that matter) in a better way.
Perhaps we can better redirect our energies to that than to have long
Hi there,
Gary Poster wrote:
[competition]
+1. I think the requirement to have enough people submitting is very
important, though. No competition anounced unless we get some idea that
we'll actually have enough competitors, otherwise we end up looking
silly (what happened to the Zope
On 2/6/06, Martin Aspeli [EMAIL PROTECTED] wrote:
Guys ... from my reading of the z3-user discussion, there were two subtly
different things that came out:
- Have funky release codenames. Okay, good - makes it easier to talk
about Zope 3.2 vs. 3.3. However, I think this is secondary (by
On Monday 06 February 2006 11:53, Shaun Cutts wrote:
I've thought of several things I'd like to see in it The biggest
would obviously be (optional) type checking of method calls, together
with a more robust Method definition.
Yes, there has been suggestions in this direction before.
On Tuesday 07 February 2006 05:09, Jeff Shell wrote:
Alright, I've stayed up way too late on this.
Jeff,
you always make great points! I would like to nominate you as the Zope 3
Propaganda Minister! :-) No seriously, you have a great way of explaining
why Zope 3 is better than the latest
On Sunday 05 February 2006 17:15, Craeg Strong wrote:
Is there a way to provide an ignore pattern for the installation scripts?
I don't think there is. Maybe bugging Fred directly might help.
If someone can point me in the right direction to get started, I can
provide a patch.
Cool.
Stephan Richter wrote:
Okay, I am giving in on this. There is a three step process that will have to
be fullfilled to assign a codename to the Zope 3.3 release.
Surely codenames are only really useful or meaningful for software that
is going to be branded, but the marketing/branding
Paul Winkler wrote:
Mac OSX in itself, on the other hand, was brilliant.
With one letter they managed to establish:
[...]
Right... but that is a brand, not a codename.
As I understand it, people are discussing things like Tiger, and
Panther, to follow your example.
rob
Stephan Richter wrote:
On Tuesday 07 February 2006 05:09, Jeff Shell wrote:
Alright, I've stayed up way too late on this.
Jeff,
you always make great points! I would like to nominate you as the Zope 3
Propaganda Minister! :-) No seriously, you have a great way of explaining
why Zope
On Tuesday 07 February 2006 05:42, Igor Stroh wrote:
Just curious - has anyone already thought about the ressource organization?
Is there any place we can paste our marketing slogans into? Some
repository which could host design proposals for the brand new Zope3
advocay site?
Join the
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. :)
However...
Jeff
Max M wrote:
Lennart Regebro wrote:
On 2/7/06, Martin Aspeli [EMAIL PROTECTED] wrote:
No, it would only make people go What, first Zope 2, then Zope 3, now
Zope Zimba? thinking it's three different things.
But always writing it Zope3 might be helpful.
Telling that there is a difference
Ursprüngliche Nachricht
Tue, 7 Feb 2006 11:01:23 +0100
von: Martijn Faassen
[EMAIL PROTECTED]
Alternatively, we could use our energy to actually work together on a
new website instead of competing. There's a zope-web mailing list, after
all, so go and talk there. This would have my
Max M wrote:
If you want to fix the Zope 2 website at the same time as branding Zope
3, I fear it is a monumental task that will never happen.
The Zope 2 website is so big, and has so much content that it should
have somebody working on it full time if it needs changing.
Perhaps this
Martijn Faassen wrote:
If we do manage to build a new website and are a good way done with it,
*then* is the time to discuss possible branding options.
... except if that website is to incorporate a given brand and have a big launch. :)
But you're absolutely right - presenting it properly,
On Tuesday 07 February 2006 05:55, Martin Aspeli (sent by Nabble.com) wrote:
If the adopted brand name for the new sexy Zope 3 thing is e.g. Zope 3
Singularity, we'll have http://zope3singularity.org. That site will be
small and well-focused, it will be sexy and well-designed, it will have the
Martin Aspeli (sent by Nabble.com) wrote:
Martijn Faassen wrote:
If we do manage to build a new website and are a good way done with
it, *then* is the time to discuss possible branding options.
... except if that website is to incorporate a given brand and have a
big launch. :)
Which is
Max M wrote:
Martijn Faassen wrote:
Alternatively, we could use our energy to actually work together on a
new website instead of competing. There's a zope-web mailing list,
after all, so go and talk there. This would have my preference.
If you want to fix the Zope 2 website at the same time
Martijn Faassen wrote:
Max M wrote:
Martijn Faassen wrote:
Alternatively, we could use our energy to actually work together on
a new website instead of competing. There's a zope-web mailing list,
after all, so go and talk there. This would have my preference.
If you want to fix the Zope
Stephan Richter wrote:
On Tuesday 07 February 2006 00:31, suresh wrote:
No it is not. Explicit is better then implicit. declareSite creates a
new site in the sites mapping. We use this pattern for layers and skins
already.
Can you have site... directives without a corresponding
On Tuesday 07 February 2006 07:08, suresh wrote:
Probably not. In this case the site name=foo directive would raise an
exception saying that no site with name foo exists.
In which case I tend to agree with Dieter that declareSite ... is
redundant and ZCML ceremony that we can without! If
Mikhail Kashkin wrote:
2. When users searchin' in search engines 'Zope 3', Google or other
throw away 3 and search only for Zope
Google doesn't throw away the 3.
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
On Tue, Feb 07, 2006 at 09:42:31PM +1100, Rob Jeschofnik wrote:
Paul Winkler wrote:
Mac OSX in itself, on the other hand, was brilliant.
With one letter they managed to establish:
[...]
Right... but that is a brand, not a codename.
As I understand it, people are discussing things like
On Tue, Feb 07, 2006 at 03:09:01AM -0700, Jeff Shell wrote:
and this, which I absolutely love:
http://www.python.org/doc/2.4/whatsnew/whatsnew24.html
+1. I think we really need something like that.
I know that even I would care a lot less about new Python releases if
--
Paul Winkler
On Feb 6, 2006, at 9:52 AM, Chris McDonough wrote:
BTW, how impending is impending? Days, weeks, months? Anybody
know?
The word on the street is a pretty small number of weeks.
(I believe the general idea at ZC is to not announce any precise
guess as to exactly how impending we think
Tarek Ziadé wrote:
Martijn Faassen wrote:
Yes. Rest assured my ambition is to keep ambitions as low as possible.
:) Otherwise nothing will happen.
The front page of Zope.org doesn't show the activity around Z3 at all.
That wouln't cost anything to start to add a few z3 links in Zope Exits
On 2/7/06, Paul Winkler [EMAIL PROTECTED] wrote:
As I said before, I'm +0 on enhancing the brand,
-1 on adding release codenames.
IMO codenames make it harder, not easier, to talk about releases.
Which came first - Cheetah or Puma? I submit that nobody but
a certified mac geek can answer
You're right, googling Zope 3 works well surprisingly enough.
For the record, I'm +.9 on sticking with Zope 3 for the moment, not
ruling out adding a codename or marketing tagline in future if we found
one that really fit. There *is* some bad feeling associated with Zope
- but also a lot of
Stephan,
By delegation support I mean support for being a proxy for an interface,
and
delegating its fulfillment to a subobject. For instance (by example):
class ISomeContainer( Interface ):
...
class ISoup( Interface ):
...
class SomeContainer:
implements( ISomeContainer )
class
Am Dienstag, 7. Februar 2006 10:31 schrieb Stephan Richter:
On Monday 06 February 2006 19:18, Roger Ineichen wrote:
Does somebody know if there is a method for check if
a teardown get called after a test? Some hints?
No, this is usually painful tracking down. You could check for test setup
On 2/7/06, Stephan Richter [EMAIL PROTECTED] wrote:
On Tuesday 07 February 2006 05:09, Jeff Shell wrote:
Alright, I've stayed up way too late on this.
Jeff,
you always make great points! I would like to nominate you as the Zope 3
Propaganda Minister! :-) No seriously, you have a great way
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
Mikhail Kashkin wrote:
1. This is new different platform, based on Zope ideas but with
absolutely different code bases
2. When users searchin' in search engines 'Zope 3', Google or other
throw away 3 and search only for Zope
3. Zope3 (or zope3) is more pythonic, you cann't name your module
On Tue, 07 Feb 2006 09:37:08 -0800, Fred Drake [EMAIL PROTECTED] wrote:
On 2/7/06, Paul Winkler [EMAIL PROTECTED] wrote:
As I said before, I'm +0 on enhancing the brand,
-1 on adding release codenames.
IMO codenames make it harder, not easier, to talk about releases.
Which came first -
On Tue, 07 Feb 2006 00:32:52 -0800, Martin Aspeli [EMAIL PROTECTED] wrote:
Like it or not, Zope (2) seems to have a lot of stigma out there; Zope 3
has been around a while. In actual fact, for a while I thought Zope 3.x
was still just unfinished vapourware, waiting for the fabled Zope2
Hi Florian
[...]
No, this is usually painful tracking down. You could check
for test setup
code that assigns AttributeAnnotatable to File. Also note
that there is no
good way for tearing down classImplements() statements. So
this issue
potentially exists in many places. I think
Alexander Limi wrote:
The original discussion never suggested code names for releases, but a
brand name to help Zope 3 separate itself from Zope 2 - since it is a
*completely* different beast.
Random thought... hehe... Zope Cubed. It's only a typographical change
from Zope 3. The tagline
Hi Stephan
[...]
No, this is usually painful tracking down. You could check
for test setup code
that assigns AttributeAnnotatable to File. Also note that
there is no good
way for tearing down classImplements() statements. So this
issue potentially
exists in many places. I think for
On Tue, 07 Feb 2006 22:37:45 -, Shane Hathaway [EMAIL PROTECTED]
wrote:
Alexander Limi wrote:
The original discussion never suggested code names for releases, but a
brand name to help Zope 3 separate itself from Zope 2 - since it is a
*completely* different beast.
Random
On 2/8/06, Chris Withers [EMAIL PROTECTED] wrote:
Yes, but then we end up with Zope3 3.2.5, which is exactly what caused
us to drop the X3 previously ;-)
Thinking about the X it is unfortunate it was used to indicate
compatibility with Zope2 and the experimental version of Zope. It was
On Tue, 07 Feb 2006 14:37:45 -0800, Shane Hathaway [EMAIL PROTECTED]
wrote:
Alexander Limi wrote:
The original discussion never suggested code names for releases, but a
brand name to help Zope 3 separate itself from Zope 2 - since it is a
*completely* different beast.
Random
On 2/7/06, Alen Stanisic [EMAIL PROTECTED] wrote:
upcoming marketing campaign :). The X can send this message better
than any other single character and it's not as obtrusive as adding or
changing a name. I believe to certain extent there is already
understanding out there that X could mean
2006/2/7, Shane Hathaway [EMAIL PROTECTED]:
Alexander Limi wrote:
The original discussion never suggested code names for releases, but a
brand name to help Zope 3 separate itself from Zope 2 - since it is a
*completely* different beast.
Random thought... hehe... Zope Cubed. It's only a
On Tue, 07 Feb 2006 22:11:31 -0800, kit BLAKE [EMAIL PROTECTED] wrote:
(Are you going French style with your last name in all caps, Kit? :)
2006/2/8, Martin Aspeli [EMAIL PROTECTED]:
Zope^3 :)
That's brilliant. It works in ASCII, or in normal text in a paragraph
of a magazine. Now, try it
52 matches
Mail list logo
