- Zope-Dev - Zope lists

buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot
by buildbot＠zope.com 15 Jun '06

15 Jun '06

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6131 Blamelist: alecm,andreasjung,efge,faassen,jim,jinty,mgedmin,srichter,yuppie BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Zope 2 bugday, today (the 15th)!
by Lennart Regebro 15 Jun '06

15 Jun '06

Join #zope-dev on freenode.net and help make 2.10 the best Zope 2 ever! :) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

2 1

How do I get involved in volunteering?
by Christopher Lozinski 13 Jun '06

13 Jun '06

I am interested in volunteering, but I am somewhat lost. And I say that even though I have been developing in Zope for years, and reading this email list avidly for a year. I think that I am going to go and buy and read the Zope 3 book. Beyond that I do not know what to do. The problem is that I have no idea what direction Zope 2 is taking. Although I have poked around on the web, I do not get Zope 3. The Zope 3 class seems a bit expensive, for those of us who are self-unemployed and who want to volunteer on Zope 2. I would love to read an architectural document, if it exists. If not maybe I could write it. It would start off by describing the different target markets and competing products. It would then define the requirements for those target markets, and it would finish by describing the architecture for zope 2 and 3 that meets those target markets. Of course that is the reverse of how it actually happened, but it sure makes a good story. I even think that in the process of creating such a high level view of this industry, I might come up with an additional market or two, and an additional architecture for Zope n to meet the requirements for that market. For example, I know that I like ZClasses and versionning, and they are not part of the plan. Then I could figure out how Zope development figures in with my product plans, and could figure out the best place to apply my energies. Maybe there is a internal group of zope 2 developers who have these conversations and who know which way things are going. Maybe no one knows, and as changes get delivered, they get approved. I am not even sure who is in charge of approving the cvs changes, and who is allowed to contribute to the cvs. Is there a list of the annointed high priests somewhere? Who annoints the approved code? Maybe there is a trade show where all the key players show up once a year. I think in the Plone world, at least there are the two key players, and then the board, so there is some visible structure. In the Zope world it is not so clear. So here are my questions. How does one get involved? Who is in charge? Who approves cvs submissions? What is the target architecture? What are the target markets? Regards Chris

2 1

buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot
by buildbot＠zope.com 12 Jun '06

12 Jun '06

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6086 Blamelist: andreasjung,oestermeier,yuppie BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Re: SVN: Zope/trunk/lib/python/AccessControl/tests/framework.py added
by Florent Guillaume 12 Jun '06

12 Jun '06

Please don't, the only supported method of running tests is through test.py, and adding "framework.py" everywhere is just more cruft. Florent Andreas Jung wrote: > Log message for revision 68592: > added > > > Changed: > A Zope/trunk/lib/python/AccessControl/tests/framework.py > > -=- > Added: Zope/trunk/lib/python/AccessControl/tests/framework.py > =================================================================== > --- Zope/trunk/lib/python/AccessControl/tests/framework.py 2006-06-12 06:21:11 UTC (rev 68591) > +++ Zope/trunk/lib/python/AccessControl/tests/framework.py 2006-06-12 06:36:06 UTC (rev 68592) > @@ -0,0 +1,44 @@ > +############################################################################## > +# > +# Copyright (c) 2002 Zope Corporation and Contributors. All Rights Reserved. > +# > +# This software is subject to the provisions of the Zope Public License, > +# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution. > +# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED > +# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED > +# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS > +# FOR A PARTICULAR PURPOSE > +# > +############################################################################## > + > +###################################################################### > +# Set up unit testing framework > +# > +# The following code should be at the top of every test module: > +# > +# import os, sys > +# execfile(os.path.join(sys.path[0], 'framework.py')) > +# > +# ...and the following at the bottom: > +# > +# framework() > + > + > +# Find the Testing package > +if not sys.modules.has_key('Testing'): > + p0 = sys.path[0] > + if p0 and __name__ == '__main__': > + os.chdir(p0) > + p0 = '' > + p = d = os.path.abspath(os.curdir) > + while d: > + if os.path.isdir(os.path.join(p, 'Testing')): > + sys.path[:1] = [p0, os.pardir, p] > + break > + p, d = os.path.split(p) > + else: > + print 'Unable to locate Testing package.' > + sys.exit(1) > + > +import Testing, unittest > +execfile(os.path.join(os.path.split(Testing.__file__)[0], 'common.py')) > > _______________________________________________ > Zope-Checkins maillist - Zope-Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/zope-checkins > -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

1 0

[Reminder] Zope 2.10 Bugday on June 15th
by Andreas Jung 12 Jun '06

12 Jun '06

Just to remind you all :-) -------------------------------------- The next Zope bugday will be held on June, 15th 2006 on the IRC channel #zope-dev at irc.freenode.net. Join us and grab a bug from http://www.zope.org/Collectors/Zope to improve the quality of the upcoming Zope 2.10 release. --- Andreas

1 0

buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot
by buildbot＠zope.com 12 Jun '06

12 Jun '06

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6077 Blamelist: andreasjung BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 12 Jun '06

12 Jun '06

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6074 Blamelist: andreasjung BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 12 Jun '06

12 Jun '06

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6068 Blamelist: andreasjung BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 12 Jun '06

12 Jun '06

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6074 Blamelist: andreasjung BUILD FAILED: failed test sincerely, -The Buildbot

1 0