On Thu, Apr 16, 2009 at 06:06, Gary Poster gary.pos...@gmail.com wrote:
So, again, in sum, I propose that this discussion should simply be reduced
to a rename to start with: Zope 3, as defined by the KGS - Zope Toolkit.
As I understand it (but Martijn may correct me) the Zope Toolkit will
have
I'am an almost passive reader of this list and typical 'user', or lets
say, software I write is a consumer of all this useful Zope-SOMETHING.
I observed your discussion and read all the threads and I wasnt sure all
the time if its the right direction. Writing code is better than
discussing
Hi there,
Just so we don't lose track of who are interested in maintaining Zope 3
(and/or the ZMI). I've distilled the following list of people who are
interested in helping maintain Zope 3. This might mean making sure
existing apps work, maintaining or replacing the ZMI, and working on
Jens W. Klein wrote:
[snip]
I would divide the Zope Toolkit in two parts:
(1) The real core which has to be mature. I doubt its all current 50-70
packages (dont ask me which parts this are, most of the active authors
here are knowing it better)
(2) The more loose ends where more agility
Hey,
Gary Poster wrote:
[snip]
So, again, in sum, I propose that this discussion should simply be
reduced to a rename to start with: Zope 3, as defined by the KGS -
Zope Toolkit. The software switch that this name change implies has
started quite some time ago, with the eggification,
Summary of messages to the zope-tests list.
Period Wed Apr 15 12:00:00 2009 UTC to Thu Apr 16 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-trunk Python-2.4.6 : Linux
From: Zope Tests
Date: Wed Apr 15 20:52:43 EDT
Thank you for saying this so well.
+1
Jim
On Apr 16, 2009, at 12:06 AM, Gary Poster wrote:
On Apr 15, 2009, at 11:28 AM, Lennart Regebro wrote:
Here are a list of things I have seen that you may mean when you say
Zope 3. I'm sure I missed several:
1. Whatever is included in the Zope 3
Chris Withers wrote:
Chris Withers wrote:
Any ideas what this means or where it's coming from?
Module ZODB.Connection, line 808, in setstate
Module ZODB.Connection, line 876, in _setstate
Module ZODB.serialize, line 604, in setGhostState
Module ZODB.serialize, line 597, in getState
On Thu, Apr 16, 2009 at 12:06 AM, Gary Poster gary.pos...@gmail.com wrote:
This message seems like a reasonable start to me: Zope 3 has become
focused on supporting frameworks and applications, rather than trying
to be one itself. It is now called the Zope Toolkit. Parts of it are
used by
Lennart Regebro wrote:
On Thu, Apr 16, 2009 at 06:06, Gary Poster gary.pos...@gmail.com wrote:
So, again, in sum, I propose that this discussion should simply be reduced
to a rename to start with: Zope 3, as defined by the KGS - Zope Toolkit.
As I understand it (but Martijn may correct me)
This message seems like a reasonable start to me: Zope 3 has become
focused on supporting frameworks and applications, rather than trying
to be one itself. It is now called the Zope Toolkit. Parts of it are
used by Zope 2, Plone, Grok, Repoze.bfg, and by many other different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Lennart Regebro wrote:
On Thu, Apr 16, 2009 at 06:06, Gary Poster gary.pos...@gmail.com wrote:
So, again, in sum, I propose that this discussion should simply be reduced
to a rename to start with: Zope 3, as defined by the
Hey,
Simon Michael wrote:
[snip]
Insiders know that the Toolkit going forward will be much more focussed than
old Zope 3 was, but outsiders don't need
those details; outsiders certainly won't understand subtle intra-project
renamings and dyings. If some of those details
are positive
Hey,
Martijn Faassen wrote:
[snip]
I put a mark in my calendar for October to reconsider the future of the
name Zope 3 then.
Given the responses to this thread I'm starting to lean towards pushing
the message to the outside that Zope 3 has become Zope Toolkit, has a
different focus,
Dan Korostelev wrote:
Log message for revision 97660:
Adapt to the move of IDefaultViewName from zope.component.interfaces to
zope.publisher.interfaces.
Changed:
U zope.container/trunk/CHANGES.txt
U zope.container/trunk/src/zope/container/traversal.py
-=-
Modified:
Gary Poster wrote:
This message seems like a reasonable start to me: Zope 3 has become
focused on supporting frameworks and applications, rather than trying
to be one itself. It is now called the Zope Toolkit. Parts of it are
used by Zope 2, Plone, Grok, Repoze.bfg, and by many other
Martijn Faassen wrote:
If we want to do this right we need to come up with a good way to get
the message out.
I think the only way you're going to manage to do that, is if you have a
website with a clear and unambiguous message on it.
It's like deja-vu all over again...
Martin
--
Author
Rob Miller wrote:
Gary Poster wrote:
This message seems like a reasonable start to me: Zope 3 has become
focused on supporting frameworks and applications, rather than trying
to be one itself. It is now called the Zope Toolkit. Parts of it are
used by Zope 2, Plone, Grok, Repoze.bfg,
18 matches
Mail list logo
