[Zope-dev] possible split of zope.app.generations to zope.generations
Hi, Now when zope refactoring is in progress, would it be possible to refactor zope.app.generations package so there would be for example package zope.generations that would depend only on ZODB3 package ? I'm using zope.app.generations to upgrade the DB schema in my web project, and in future I want to use ZODB3 in my desktop-only projects. Thanks in advance Regards Roman Lacko ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
Previously Martin Aspeli wrote: Wichert Akkerman wrote: To stir things up: I would like to suggest renumbering the next Zope 2 release to Zope 4. That reflects the large refactoring that is being done to clean up the codebase and fully eggify Zope. There are enough changes to warrant a new major version bump. -100 again. We need to stop confusing people! The only way we could do this would be if we definitely, 100%, with-an-axe killed off any notion of Zope 3 as an app server or application development framework and told everyone the thing you need to be using if you like Zope, is this Zope thing that's basically Zope 2.14). We won't do that. Actually, we have already done that. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
Previously Shane Hathaway wrote: discussion type=bikeshed Tres Seaver wrote: WRT the Framework name: framework is a misleading name for the collection of packages salvaged from the new Coke effort: it is actually a *bunch* of frameworks, in the classic software engineering sense, along with some pure libraries. Zope Toolkit, perhaps? (No relationship to Portal Toolkit. :-] ) +1 Cute. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
Wichert Akkerman wrote: Previously Shane Hathaway wrote: discussion type=bikeshed Tres Seaver wrote: WRT the Framework name: framework is a misleading name for the collection of packages salvaged from the new Coke effort: it is actually a *bunch* of frameworks, in the classic software engineering sense, along with some pure libraries. Zope Toolkit, perhaps? (No relationship to Portal Toolkit. :-] ) +1 Cute. It can even be shortened to ZTool. Then we need a package ztool.sample. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
Wichert Akkerman wrote: Previously Martin Aspeli wrote: Wichert Akkerman wrote: To stir things up: I would like to suggest renumbering the next Zope 2 release to Zope 4. That reflects the large refactoring that is being done to clean up the codebase and fully eggify Zope. There are enough changes to warrant a new major version bump. -100 again. We need to stop confusing people! The only way we could do this would be if we definitely, 100%, with-an-axe killed off any notion of Zope 3 as an app server or application development framework and told everyone the thing you need to be using if you like Zope, is this Zope thing that's basically Zope 2.14). We won't do that. Actually, we have already done that. Well, except that Grok runs on Zope 3 the app server or at least Zope 3 the platform. I just think we need to stop playing with names and numbers. I have absolutely no problem with Zope 2 version numbers reaching 2.20 or whatever. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
When i speak about zope with my friends or tell about zope to my boss i allways use Zope Framework name. Zope Framework was from beginning the natural name for zope3 for me. When i thing about Zope3, i think about Zope Framework When i thing about Zope2, i think about Zope2 Just my 0.02 cents :) Regards Roman Lacko -Original Message- From: zope-dev-boun...@zope.org [mailto:zope-dev-boun...@zope.org] On Behalf Of Lennart Regebro Sent: Thursday, April 09, 2009 11:18 AM To: Martin Aspeli Cc: zope-dev@zope.org Subject: Re: [Zope-dev] naming Zope Zope Toolkit is a good name. But so is Zope Framework. And honestly, it's more a framework than a toolkit. A toolkit is a collection of reasonably independent tools. OK, so Zope Framework is actually loads of frameworks, one for components, one for security one for web forms, and this and that. But they are also designed to work together, and therefore makes a sort of megaframework. OK, fair enough, Django calls itself a framework too. It is more specifically a high level web framework. Zope Framework is NOT a web framework and certainly not high level. It's an application framework. Grok and BFG are web frameworks in the sense of Django. Is it really a big enough problem to distinguish between an application framework like Zope, and a Web Framework like Django, so that we need to rename everything again? I don't think so. Zope Framework is clear name and already in use. Changing that name just because it's not the same type of Framework as Django seems weird. So I'm +0 on Zope Toolkit. But +1 on Zope Framework. It just makes more sense to me. //Lennart ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
Zope Toolkit is a good name. But so is Zope Framework. And honestly, it's more a framework than a toolkit. A toolkit is a collection of reasonably independent tools. OK, so Zope Framework is actually loads of frameworks, one for components, one for security one for web forms, and this and that. But they are also designed to work together, and therefore makes a sort of megaframework. OK, fair enough, Django calls itself a framework too. It is more specifically a high level web framework. Zope Framework is NOT a web framework and certainly not high level. It's an application framework. Grok and BFG are web frameworks in the sense of Django. Is it really a big enough problem to distinguish between an application framework like Zope, and a Web Framework like Django, so that we need to rename everything again? I don't think so. Zope Framework is clear name and already in use. Changing that name just because it's not the same type of Framework as Django seems weird. So I'm +0 on Zope Toolkit. But +1 on Zope Framework. It just makes more sense to me. //Lennart ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 7 OK, 1 Failed
Summary of messages to the zope-tests list. Period Wed Apr 8 12:00:00 2009 UTC to Thu Apr 9 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures - Subject: FAILED (errors=1) : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Wed Apr 8 21:02:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011426.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 8 20:47:52 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011419.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 8 20:49:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011420.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 8 20:51:57 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011421.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Apr 8 20:53:58 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011422.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Wed Apr 8 20:55:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011423.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 8 20:57:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011424.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Apr 8 21:00:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011425.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Plone vs. Zope2 was: Re: naming Zope
Tres Seaver wrote: Hanno Schlichting wrote: Lennart Regebro wrote: So it's highly likely that Zope 2.12 is the last release of Zope2 that Plone is going to use. Maybe a Zope 2.13 once Python 2.7 is released might be of interest to Plone. But otherwise I don't see any reason for a new Zope 2 feature release anymore from the Plone perspective. Zope2 is the only game in town, as far as appservers go. I don't see that Plone needs an appserver anymore. A framework plus the application code on top is more than enough. Plone is going to continue to use selected Zope libraries as everyone else, but use Repoze or just general Python packages from all over. Personally I want to move Plone from zope.i18n to Babel for example. We are not bound by names or frameworks in our package choices. Note that unless you scrap the entire model of a Plone site as an application object hosted inside an appserver, you won't have a choice except to run atop Zope2: the Z3 appserver is going to be even more moribund a year from now than it is today. I don't want to switch to another application server and certainly not Zope 3. The notion of a Plone site being a local instance inside the application server is already blurry. From what I see today, we will slowly move away from it. WSGI configuration is going to be application global, more configuration and behavior will be based on things simply being available on sys.path. What Plone will get is a notion of a website or subsite inside the application with a much smaller configuration aspect to it. Maybe I'm wrong on this, but I assume the Plone Site object is going to be optional in Plone 5 (two or three years from now). Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] running all Zope 2 tests on trunk?
Hey All, Is this buildout sufficient to run all the Zope 2 tests on trunk: [buildout] parts = test extends = http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg develop = Zope # Zope is a checkout of: # svn+ssh://chr...@svn.zope.org/repos/main/Zope/trunk [test] recipe = zc.recipe.testrunner eggs = Zope2 cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Plone vs. Zope2 was: Re: naming Zope
On Apr 8, 2009, at 11:34 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: Lennart Regebro wrote: This is only mildly confusing. It can also only get better with time, as Plone seems to continue away from Zope 2 and onto the framework, which means we in the future may end up with Plone, Grok and BFG being app servers on the Zope Framework. The current line of thinking for Plone is about this: Plone 4 will still run on Zope2. Plone 5 will run on Python 3.x and not depend on Zope2 anymore at all. We can all guesstimate on what kind of timeline that will mean. There isn't going to *be* a Zope3 to run on. So it's highly likely that Zope 2.12 is the last release of Zope2 that Plone is going to use. Maybe a Zope 2.13 once Python 2.7 is released might be of interest to Plone. But otherwise I don't see any reason for a new Zope 2 feature release anymore from the Plone perspective. Zope2 is the only game in town, as far as appservers go. Plone could run on something like the Zope Framework without running on Zope 2. Alternatively, Zope (2 or whatever) could use more and more Zope framework components so that it would become what they mean by Zope 3. Plone is going to continue to use selected Zope libraries as everyone else, but use Repoze or just general Python packages from all over. Personally I want to move Plone from zope.i18n to Babel for example. We are not bound by names or frameworks in our package choices. Note that unless you scrap the entire model of a Plone site as an application object hosted inside an appserver, you won't have a choice except to run atop Zope2: the Z3 appserver is going to be even more moribund a year from now than it is today. I don't agree at all with your definition of app server. ... Z2 is at least *interesting* to work with at this point; making the Z3 appserver WSGI'fied will be hard and pointless by comparison. Zope 3 has been wsgi-based for years now. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] several zope.* libs within gae (was ZCML implementations: where should they go)
Hi, Shane Hathaway wrote: Hanno Schlichting wrote: Wichert Akkerman wrote: I'ld rather not see a whole slew of extra packagse appear. I also wonder how the extra number of packages and increasing size of sys.path influence performance and restrictions on environments like GAE. For environments like GAE you don't want setuptools and its magic to be part of your application. This is were repackaging your entire app into one zipped egg or some other flat structure comes in handy. Setuptools and eggs are a distribution format from my point of view. They are certainly not the best way to deploy your applications. The growing sys.path is affecting performance to some degree in all deployment environments. Well, zc.buildout ought to be able to eliminate this concern for GAE deployment. I haven't tried the recipe below, but it certainly seems like the right idea. http://pypi.python.org/pypi/rod.recipe.appengine I released a new version today. It's a lot easier now to use several eggs within gae. This test thingy http://zpttest.appspot.com/ uses zope.interface and zope.pagetemplate plus their dependencies. I'm planning to release another sample project maybe during easter holidays. It's much more fun since you zope people cleaned up a lot of dependencies and unveiled zc.buildout. Thanks! Cheers, Tobias ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Plone vs. Zope2 was: Re: naming Zope
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lennart Regebro wrote: On Thu, Apr 9, 2009 at 05:34, Tres Seaver tsea...@palladion.com wrote: Hanno Schlichting wrote: The current line of thinking for Plone is about this: Plone 4 will still run on Zope2. Plone 5 will run on Python 3.x and not depend on Zope2 anymore at all. We can all guesstimate on what kind of timeline that will mean. There isn't going to *be* a Zope3 to run on. Right. He didn't say that it would though. In this scenario, Plone would be one of the platforms using the Zope Framework, like Grok and BFG. Zope2 is the only game in town, as far as appservers go. So neither Grok nor BFG exist? :-) I don't know how you are thinking here. They aren't appservers: they are web frameworks. Grok muddies the lines a tiny bit, but BFG is *only* about giving you tools for building a web app to be run under an arbitrary WSGI server: it doesn't buy into the container for apps obeying some interface thing at all. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3hLL+gerLs4ltQ4RAlLMAKCqjT5V+6cYhB4xPxbfksBBIqim4ACgpe6w +TjBfaokQQAIGVX6VJFUwm8= =MkC8 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: On Apr 8, 2009, at 11:29 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Aspeli wrote: Wichert Akkerman wrote: To stir things up: I would like to suggest renumbering the next Zope 2 release to Zope 4. That reflects the large refactoring that is being done to clean up the codebase and fully eggify Zope. There are enough changes to warrant a new major version bump. -100 again. We need to stop confusing people! The only way we could do this would be if we definitely, 100%, with-an-axe killed off any notion of Zope 3 as an app server or application development framework and told everyone the thing you need to be using if you like Zope, is this Zope thing that's basically Zope 2.14). No. It would only mean that there was one Zope application thing (pluggabel application platform ...) Agreed. We already have: Le roi est mort, vive le roi! and all that. Jim has pronounced Zope3^H^H^H^HDecoy DOA. No. I was only referring to the Zope 2 wanna-be application implemented with Zope 3. That is what I meant. For branding purposes (what this discussion si about) we would like to avoid using Zope3 as a name for what is left, beecause it implies successor to Zope2. I certainly think the components that such an application is made of, including application-server components have a long and happy life ahead of them. Nobody is every going to care about Zope3-the-appserver, as opposed to the-libraries-harvested-from- Zope3 (at least, the folks who might care are a tiny minority for branding purposes). I don't think the term app server is crisp. To me app server != pluggable application. Right. There exist hoops we make typical Z2 applications jump through, mostly unrelated to the real requirements for the app: those hoops are to make the app play nice inside the bean^W^W^Wapplication container which is the ZMI. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3hPd+gerLs4ltQ4RAhKKAKCkwmS7tm8VLsjMVLkzpx+HK01pHQCfbapU Km5+H0AD3glgxKXq/DuAOB0= =wrNL -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] several zope.* libs within gae (was ZCML implementations: where should they go)
Hi Just on the zope in gae. I have been hacking away at getting a core of zope running under gae. (one example is http://baon.appspot.com/ which was a port of an old portal_toolkit/cmf 1.0 site I used as an excercise) I am currently using the following packages app (completely gutted) component configuration contenttype datetime deferredimport deprecation event exceptions i18n i18nmessageid interface lifecycleevent location pagetemplate proxy publisher schema security tal tales testing traversing Though zope.proxy and zope.security have been pretty much gutted. There is practically nothing in zope.app (basically some scaffold left to support imports from other packages withouth having to change packages) I am also using peak.util z3c.form And had to write my own wrapper for pagetemplates to get closer to zope.app.pagetemplate and a gae specific publication (based on DefaultPublication) . I have manually registered most of the parts (adapters and utilities) of the packages listed above. I had to do that to avoid all of the extra dependancies pulled in by the default zml that just won't work in gae (mainly zope.security stuff) . For z3c.form I did end up using zcml (to hard to do all the widgets by hand ;-) but had to remove all of the permission directives from the class statements (like a said it's all a bit of a hack at the moment) It's not pretty ;-) but works. I plan to revisit repose.bfg as a base for this work, but need to remove cheetah and go back to pure python zpt, and get rid of all the lxml depenancies. I put all of this together manually so far (buildout comes next - now that I know what I need to do). One question before I go. I had to replace about 90% of zope.security (well get rid of it) what would be the best way of specifying a replacement for a core package like zope.security rather than just replacing it. If I wanted to share this work it would be a but confusing to call it zope.security, and it is a bit much to monkey patch.? Should I call it something like call it something like z3c.gae.security and just tell people to install it in zope.security ? Tim On Thu, Apr 9, 2009 at 11:05 PM, Tobias Rodäbel tobias.rodae...@mac.com wrote: Hi, Shane Hathaway wrote: Hanno Schlichting wrote: Wichert Akkerman wrote: I'ld rather not see a whole slew of extra packagse appear. I also wonder how the extra number of packages and increasing size of sys.path influence performance and restrictions on environments like GAE. For environments like GAE you don't want setuptools and its magic to be part of your application. This is were repackaging your entire app into one zipped egg or some other flat structure comes in handy. Setuptools and eggs are a distribution format from my point of view. They are certainly not the best way to deploy your applications. The growing sys.path is affecting performance to some degree in all deployment environments. Well, zc.buildout ought to be able to eliminate this concern for GAE deployment. I haven't tried the recipe below, but it certainly seems like the right idea. http://pypi.python.org/pypi/rod.recipe.appengine I released a new version today. It's a lot easier now to use several eggs within gae. This test thingy http://zpttest.appspot.com/ uses zope.interface and zope.pagetemplate plus their dependencies. I'm planning to release another sample project maybe during easter holidays. It's much more fun since you zope people cleaned up a lot of dependencies and unveiled zc.buildout. Thanks! Cheers, Tobias ___ Zope-Dev maillist - zope-...@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Plone vs. Zope2 was: Re: naming Zope
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: On Apr 8, 2009, at 11:34 PM, Tres Seaver wrote: Plone could run on something like the Zope Framework without running on Zope 2. That would be feasible, except that a ton of Plone's features depend on Zope2-specific machinery. Hanno may be ambitious enough to pull that off (he is certainly capable), but I'm not sure it would be worth the effort. Alternatively, Zope (2 or whatever) could use more and more Zope framework components so that it would become what they mean by Zope 3. Zope2 has been doing just that for the past four years. We need to recognize and bless this fact, and quit using a brand name which creates an expectation that Zope2 is an evolutionary dead end. Plone is going to continue to use selected Zope libraries as everyone else, but use Repoze or just general Python packages from all over. Personally I want to move Plone from zope.i18n to Babel for example. We are not bound by names or frameworks in our package choices. Note that unless you scrap the entire model of a Plone site as an application object hosted inside an appserver, you won't have a choice except to run atop Zope2: the Z3 appserver is going to be even more moribund a year from now than it is today. I don't agree at all with your definition of app server. I'm using the term pretty much as a cognate for your pluggable application, or for bean container in the Java world; an application server is a standalone thing which has separately-developed applications installed into it. The other Python web frameworks now current don't match this pattern at all: they give you a way to build and run a custom web application under a WSGI server, but there is no notion of installing an application into the server. The server also provides almost *no* functionality to the application, by comparison with what Zope2 does. Z2 is at least *interesting* to work with at this point; making the Z3 appserver WSGI'fied will be hard and pointless by comparison. Zope 3 has been wsgi-based for years now. In a sense, yes, although the stock publisher is too policy filled to take advantage of a lot of the benefits of a WSGI-fied environment. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3haQ+gerLs4ltQ4RAu7iAJ9cVi3qe4p7tOZuN6+b7DpKu+64/wCgyGhr lT1hpyXcgU86WLGD5OsRJow= =nDBR -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 7 OK, 1 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Wed Apr 8 12:00:00 2009 UTC to Thu Apr 9 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures - Subject: FAILED (errors=1) : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Wed Apr 8 21:02:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-April/011426.html Rats, I forgot to bump the versions-zope3.cfg to pick up the new zope.tal. I don't know how the 'alltests' script is being built, or I would have run the tests myself and found the failure. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3hfX+gerLs4ltQ4RAr2DAJ45kbfAsNSRPtxrn1E1OB/0tr8PbQCePHV4 T4VFpAt8Sacr6BA9a2ACzok= =sfYY -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] possible split of zope.app.generations to zope.generations
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lacko Roman wrote: Now when zope refactoring is in progress, would it be possible to refactor zope.app.generations package so there would be for example package zope.generations that would depend only on ZODB3 package ? +1. I'm using zope.app.generations to upgrade the DB schema in my web project, and in future I want to use ZODB3 in my desktop-only projects. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3hbG+gerLs4ltQ4RAhPZAKCXttAAU/GzePZXiUjkr2HWUWx5pQCePcAc Fid+XKDHg3lif07cs62+BNo= =jWvA -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] several zope.* libs within gae (was ZCML implementations: where should they go)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tobias Rodäbel wrote: Hi, Shane Hathaway wrote: Hanno Schlichting wrote: Wichert Akkerman wrote: I'ld rather not see a whole slew of extra packagse appear. I also wonder how the extra number of packages and increasing size of sys.path influence performance and restrictions on environments like GAE. For environments like GAE you don't want setuptools and its magic to be part of your application. This is were repackaging your entire app into one zipped egg or some other flat structure comes in handy. Setuptools and eggs are a distribution format from my point of view. They are certainly not the best way to deploy your applications. The growing sys.path is affecting performance to some degree in all deployment environments. Well, zc.buildout ought to be able to eliminate this concern for GAE deployment. I haven't tried the recipe below, but it certainly seems like the right idea. http://pypi.python.org/pypi/rod.recipe.appengine I released a new version today. It's a lot easier now to use several eggs within gae. This test thingy http://zpttest.appspot.com/ uses zope.interface and zope.pagetemplate plus their dependencies. I'm planning to release another sample project maybe during easter holidays. It's much more fun since you zope people cleaned up a lot of dependencies and unveiled zc.buildout. Thanks! Cool! You should be able to use zope.component there in its latest incarnation, too: the C bits are all optional at this point. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3hcU+gerLs4ltQ4RAuG5AKCMROgDfhLcckXqNmznfEZCrolHkACgh1ua PR4pPE5Df80kGcg9RWkG0yw= =gTQ9 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] z3c.form and KGS 3.4 - can't build 1.9.x branch
Hi, I just tried to check out the new 1.9.x branch of z3c.form (thanks Stephan!), but it won't build with Python 2.4 (I need this to work with Plone, so 2.4 is a must): $ ./bin/buildout Develop: '/users/optilude/Development/Plone/Code/Products/z3c.form/.' Unused options for buildout: 'zope-directory' 'download-directory'. Installing test. Getting distribution for 'z3c.template'. Got z3c.template 1.1a1. Getting distribution for 'z3c.coverage'. Got z3c.coverage 0.1.0. Getting distribution for 'zope.app.container'. Got zope.app.container 3.7.0. Getting distribution for 'zope.security'. Got zope.security 3.6.0. Getting distribution for 'zope.publisher'. Got zope.publisher 3.5.5. Getting distribution for 'zope.pagetemplate'. Got zope.pagetemplate 3.4.1. Getting distribution for 'zope.lifecycleevent'. Got zope.lifecycleevent 3.5.0. Getting distribution for 'zope.configuration'. Got zope.configuration 3.4.1. Getting distribution for 'zope.app.testing'. Got zope.app.testing 3.6.0. Getting distribution for 'zope.app.pagetemplate'. Got zope.app.pagetemplate 3.5.0. Getting distribution for 'ZODB3'. Got ZODB3 3.9.0a12. Getting distribution for 'zope.app.publisher'. Got zope.app.publisher 3.6.0. Getting distribution for 'zope.app.component'. Got zope.app.component 3.6.0. Getting distribution for 'zope.tal'. Got zope.tal 3.5.0. Getting distribution for 'zope.dublincore'. Got zope.dublincore 3.4.2. Getting distribution for 'zope.traversing'. Got zope.traversing 3.5.2. Getting distribution for 'zope.proxy=3.4.2'. Got zope.proxy 3.5.0. Getting distribution for 'zope.deferredimport'. Got zope.deferredimport 3.5.0. Getting distribution for 'zope.app.security'. Got zope.app.security 3.6.0. Getting distribution for 'zope.app.publication'. Got zope.app.publication 3.5.1. Getting distribution for 'zope.app.authentication'. Got zope.app.authentication 3.5.0a2. Getting distribution for 'zope.app.appsetup=3.5.0'. Got zope.app.appsetup 3.9.0. Getting distribution for 'zope.contenttype'. Got zope.contenttype 3.4.1. Getting distribution for 'zope.formlib'. Got zope.formlib 3.5.2. Getting distribution for 'zope.filerepresentation'. Got zope.filerepresentation 3.5.0. Getting distribution for 'zope.dottedname'. Got zope.dottedname 3.4.5. Getting distribution for 'zope.app.form'. Got zope.app.form 3.7.1. Getting distribution for 'zope.app.exception'. Got zope.app.exception 3.4.2. Getting distribution for 'zope.app.http'. Got zope.app.http 3.5.0. Getting distribution for 'zope.error'. Got zope.error 3.6.0. Getting distribution for 'zope.session'. Got zope.session 3.8.0. Getting distribution for 'RestrictedPython'. File build/bdist.macosx-10.3-i386/egg/RestrictedPython/tests/before_and_after25.py, line 30 x.y = y.z if y.z else y.x ^ SyntaxError: invalid syntax File build/bdist.macosx-10.3-i386/egg/RestrictedPython/tests/before_and_after26.py, line 30 with whatever as x: ^ SyntaxError: invalid syntax File build/bdist.macosx-10.3-i386/egg/RestrictedPython/tests/security_in_syntax26.py, line 6 with x as _leading_underscore: ^ SyntaxError: invalid syntax File /Users/optilude/.buildout/eggs/tmpayO5gI/RestrictedPython-3.5.0-py2.4.egg/RestrictedPython/tests/before_and_after25.py, line 30 x.y = y.z if y.z else y.x ^ SyntaxError: invalid syntax File /Users/optilude/.buildout/eggs/tmpayO5gI/RestrictedPython-3.5.0-py2.4.egg/RestrictedPython/tests/before_and_after26.py, line 30 with whatever as x: ^ SyntaxError: invalid syntax File /Users/optilude/.buildout/eggs/tmpayO5gI/RestrictedPython-3.5.0-py2.4.egg/RestrictedPython/tests/security_in_syntax26.py, line 6 with x as _leading_underscore: ^ SyntaxError: invalid syntax Got RestrictedPython 3.5.0. Generated script '/users/optilude/Development/Plone/Code/Products/z3c.form/bin/test'. Installing coverage-test. Generated script '/users/optilude/Development/Plone/Code/Products/z3c.form/bin/coverage-test'. Installing coverage-report. Couldn't find index page for 'z3c.coverage' (maybe misspelled?) Generated script '/users/optilude/Development/Plone/Code/Products/z3c.form/bin/coverage-report'. Clearly, I'm getting too new a version of RestrictedPython, but this is running against the 3.4 KGS, so I don't see how that could really happen. :( Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 7 OK, 1 Failed
Tres Seaver wrote: I don't know how the 'alltests' script is being built, or I would have run the tests myself and found the failure. You run bin/buildout -c alltests.cfg and then bin/alltests Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form and KGS 3.4 - can't build 1.9.x branch
On Thursday 09 April 2009, Martin Aspeli wrote: Clearly, I'm getting too new a version of RestrictedPython, but this is running against the 3.4 KGS, so I don't see how that could really happen. This is not a problem. Ignore those errors as they happen in the Python 2.6 support code.Everything installed fine. Got RestrictedPython 3.5.0. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Why doesn't this buildout run the zdaemon tests?
Hi All, Apologies for the current test failure on trunk, why doesn't the following testrunner run the zdaemon tests? [buildout] parts = test extends = http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg versions = versions develop = Zope zdaemon [versions] setuptools = 0.6c9 zc.buildout = 1.2.1 zdaemon = Zope2 = [test] recipe = zc.recipe.testrunner eggs = Zope2 As before, Zope contains a checkout of the trunk of the Zope2 egg, and zdaemon contains a checkout of the trunk of zdaemon egg? Zope2 depends on zdaemon, so why are its tests not getting run when I do bin/test? Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zdaemon is alpha?
Jim Fulton wrote: If not, I'll change it on trunk... Please just remove that trove classifier. Done. Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
Chris Withers wrote: Apologies for the current test failure on trunk, why doesn't the following testrunner run the zdaemon tests? The testrunner recipe only puts the things in its own eggs section onto the test path, so you need to do: [test] recipe = zc.recipe.testrunner eggs = Zope2 zdaemon Look at the alltests.cfg in trunk, to see how we run the tests for Zope2 and all its interesting dependencies. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: Hi All, Apologies for the current test failure on trunk, why doesn't the following testrunner run the zdaemon tests? [buildout] parts = test extends = http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg versions = versions develop = Zope zdaemon [versions] setuptools = 0.6c9 zc.buildout = 1.2.1 zdaemon = Zope2 = [test] recipe = zc.recipe.testrunner eggs = Zope2 As before, Zope contains a checkout of the trunk of the Zope2 egg, and zdaemon contains a checkout of the trunk of zdaemon egg? Zope2 depends on zdaemon, so why are its tests not getting run when I do bin/test? bin/test no longer runs tests for separately-installed dependencies. You need to do the 'alltests' dance to run them (I just learned the chant this morning): $ bin/buildout -c alltests.cfg $ bin/alltests Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ3iwc+gerLs4ltQ4RAikZAJ40q5e14MkxS0TmowlZI4LlldvVqgCbBNKe 233njMhbS/E7y8VKMd1RxKk= =wHpT -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
Hanno Schlichting wrote: Chris Withers wrote: Apologies for the current test failure on trunk, why doesn't the following testrunner run the zdaemon tests? The testrunner recipe only puts the things in its own eggs section onto the test path, Ah, I only just got that :-) Okay, so 'eggs' inside a zc.recipe.testrunner section is for the eggs whose tests you want to run. What decides what eggs end up on the python path of bin/test? Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
Tres Seaver wrote: $ bin/buildout -c alltests.cfg $ bin/alltests Any reason alltests.cfg isn't in the root buildout.cfg? (not that I'm using the root buildout.cfg either...) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
Hey, Joy, another naming discussion. Oh well, I started it. :) Zope Toolkit is better name than Zope Framework. I'm fine with renaming Zope Framework to Zope Toolkit if: * someone goes and changes the name in: * the Zope Framework sphinx documentation in SVN * renames the SVN directory * renames the Zope Framework Steering Group to the Zope Toolkit Steering Group * bothers Jens to change the /zopeframework URL to zope toolkit. * updates the story website to talk about the Zope Toolkit, not the the framework. I.e. a great renaming action. If nobody volunteers to do this (feel free to organize more volunteers), we'll stick with Zope Framework. Let me know if you're going to do this and when you're done. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] several zope.* libs within gae (was ZCML implementations: where should they go)
Hey there, Tim Hoffman wrote: [snip] One question before I go. I had to replace about 90% of zope.security (well get rid of it) what would be the best way of specifying a replacement for a core package like zope.security rather than just replacing it. If I wanted to share this work it would be a but confusing to call it zope.security, and it is a bit much to monkey patch.? Should I call it something like call it something like z3c.gae.security and just tell people to install it in zope.security ? This is an interesting question. Would it be possible to make changes in zope.security itself so that there's is a do-nothing Python version available when you install it on GAE? zope.security is a bit like middleware in that much of your app will continue to work if you don't use it. We could simply recognize this in zope.security and have a mode for it so it doesn't actually create security proxies. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
Martijn Faassen wrote: If nobody volunteers to do this (feel free to organize more volunteers), we'll stick with Zope Framework. Let me know if you're going to do this and when you're done. FWIW, I think this particular pile of libraries is in fact best described by the name framework, because the code we're discussing often calls user code rather than the other way around. For example, looking up and using an adapter is deep in framework territory. The name framework has earned a bad name just because there are so many bad frameworks out there, but there are plenty of good ones too. Good frameworks use library-like patterns where possible, falling back to carefully designed framework-like patterns. Zope Framework will be one of the best frameworks. Shane ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
I can't believe no one's suggested Zope Mega, yet. Chris On Thu, Apr 9, 2009 at 4:25 PM, Martijn Faassen faas...@startifact.comwrote: Hey, Joy, another naming discussion. Oh well, I started it. :) Zope Toolkit is better name than Zope Framework. I'm fine with renaming Zope Framework to Zope Toolkit if: * someone goes and changes the name in: * the Zope Framework sphinx documentation in SVN * renames the SVN directory * renames the Zope Framework Steering Group to the Zope Toolkit Steering Group * bothers Jens to change the /zopeframework URL to zope toolkit. * updates the story website to talk about the Zope Toolkit, not the the framework. I.e. a great renaming action. If nobody volunteers to do this (feel free to organize more volunteers), we'll stick with Zope Framework. Let me know if you're going to do this and when you're done. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
On Thu, Apr 9, 2009 at 23:07, Chris Rossi ch...@archimedeanco.com wrote: I can't believe no one's suggested Zope Mega, yet. It sounds stupid. The Zope Ultra Component Framework Toolkit, though, THAT's a name with panache! -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] naming Zope
On 4/9/09 4:25 PM, Martijn Faassen wrote: Hey, Joy, another naming discussion. Oh well, I started it. :) Zope Toolkit is better name than Zope Framework. I'm fine with renaming Zope Framework to Zope Toolkit if: * someone goes and changes the name in: * the Zope Framework sphinx documentation in SVN * renames the SVN directory * renames the Zope Framework Steering Group to the Zope Toolkit Steering Group * bothers Jens to change the /zopeframework URL to zope toolkit. * updates the story website to talk about the Zope Toolkit, not the the framework. I.e. a great renaming action. If nobody volunteers to do this (feel free to organize more volunteers), we'll stick with Zope Framework. Let me know if you're going to do this and when you're done. All done except for the renaming of the steering group. I'm not sure where to rename that. - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
