- Zope-Announce - Zope lists

Announcing: Zope 4.0 project
by Tres Seaver 01 Apr '09

01 Apr '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On behalf of the Zope community, I am pleased to announce the creation of the "Zope 4.0" project. After extensive discussion with the Zope wizards in conclave at PyCon 2009, the new project's website has been launched: http://zopefour.org/ Enjoy! Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ01VR+gerLs4ltQ4RAiljAKCACB9aMtI3YnsXPZss4hdEDrA7FACgsqv7 3jR6FQeEy0qpX4D4NOX+HsA= =q8Fu -----END PGP SIGNATURE-----

1 0

CORRECTION: Zope Foundation General Meeting time
by Jens Vagelpohl 17 Mar '09

17 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I sent an incorrect time for the Zope Foundation General Meeting earlier today, my apologies for any confusion caused. The meeting is held at 17:00 UTC (not 18:00 UTC) this coming Thursday, March 19: When: Thursday, March 19, 17:00 UTC[1] Where: irc://irc.freenode.net/#zope-foundation Jens Vagelpohl Member, Zope Foundation Board of Directors [1] 17:00/5 PM UTC is... 18:00/6 PM CET (Central European Time) 13:00/1 PM EDT (Eastern Daylight Time) 10:00/10 AM PDT (Pacific Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkm/7uMACgkQRAx5nvEhZLL1AQCeODKugDXH8U0+G5nPDkBwcoiB 0+4AoJ6NSGqSYawMxubmPKxfRTq29gyl =vPbF -----END PGP SIGNATURE-----

1 0

Zope Foundation Board of Directors election results
by Jens Vagelpohl 17 Mar '09

17 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The results from the Zope Foundation Board of Directors election are in. The following candidates will form the new board this year: Martijn Faassen Andreas Jung Rob Page Stephan Richter Tres Seaver Christian Theune Jens Vagelpohl On behalf of the outgoing board I would like to say Thank You to the candidates, and to all those who voted in this election. The new board will be seated at the Zope Foundation General Meeting, which is scheduled for this coming Thursday, March 19, at 18:00 UTC[1]. This meeting is open to all foundation members, but also to prospective members and other interested parties. Jens Vagelpohl Member, Zope Foundation Board of Directors [1] 18:00/6 PM UTC is... 19:00/7 PM CET (Central European Time) 14:00/2 PM EDT (Eastern Daylight Time) 11:00/11 AM PDT (Pacific Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkm/vHsACgkQRAx5nvEhZLI+pgCgu/z+OvSVNjF3/b/dCnSf9XwP f0kAn1USJ4DK9BYKTazHFSU91J4KljEL =LdPH -----END PGP SIGNATURE-----

1 0

Zope 2.12.0 alpha 1 released
by Andreas Jung 27 Feb '09

27 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On behalf of the Zope developers community I am pleased to announce the first alpha release of Zope 2.12.0. Some highlights: * ships with ZODB 3.9 * runs on top of Python 2.5 and 2.6 * fully eggified - means you install Zope 2.12 directly from PyPI using easy_install or zc.buildout * lots of cleanup on the module level (e.g. ZClasses have gone) * ships with the Zope components library (aka Zope 3.4) * RESTified documentation * lots of other small details Please read the following for further information: http://docs.zope.org/zope2/releases/2.12/CHANGES.html http://docs.zope.org/zope2/releases/2.12/WHATSNEW.html Please report bugs to: http://docs.zope.org/zope2/releases/2.12/CHANGES.html The current Zope 2.12.0a1 release is intended to be used together with zc.buildout or easy_install. We do not provide a traditional source-code tar-ball in this release. The final release of Zope 2.12.0 is scheduled for later this year (summer). Andreas Jung -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmn7O8ACgkQCJIWIbr9KYze5QCgkYKE20KvsTMtm3ZPj3D6unGQ V6MAn1TNT2CBHqLAiO5e/LTbgHkA/qn0 =VJNj -----END PGP SIGNATURE-----

1 0

Zope 3.4.0 Released!
by Stephan Richter 31 Jan '09

31 Jan '09

January 29, 2009 - The Zope 3 development team announces the Zope 3.4.0 release. After 2 years of development, the Zope Foundation and the larger Zope community is proud to announce the release of Zope 3.4.0. The focus of the Zope 3.4 development effort has been the conversion from a monolithic source tree, to a set of many small packages (eggs), that can be used independently of each other. The core has been further stabilized through numerous bug fixes, and many new add-on packages have been developed to provide a richer development experience. With this release also comes a renewed commitment to a short and reliable release cycle of 6 months. Packages and Eggs ----------------- Zope 3 is now fully converted to an egg-based system. While some work still remains, it integrates very well with the rest of the Python community. The conversion to egg-based packaging also enables other Python developers to only have to use small bits and pieces of the complete Zope software system. The conversion means that Zope 3 developers do not use the classic Zope 3 tar-ball release anymore. However, for your convenience, Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well. So how are Zope 3 applications built using only eggs? The Known Good Set (KGS) ~~~~~~~~~~~~~~~~~~~~~~~~ The known good set -- or in short KGS -- is a configuration of packages and their versions that are known to work well together. The compatibility is frequently verified by running over twelve thousand tests on a daily basis [1]_. The KGS is tested against Python 2.4 and 2.5 on the 32- and 64-bit platforms. The list of controlled packages and their versions for Zope 3.4 can be found at the Zope 3 KGS site [2]_. The KGS can be used in several ways [3]_. The most common way is to "nail" the versions by downloading the version configuration file [4]_ and insert them as follows in your buildout configuration:: [buildout] versions = versions ... [versions] zope.interface = 3.4.0 ... ``zopeproject`` Project Builder ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To start building a project using a common setup, a package called `zopeproject` can be used to quickly setup the boilerplate for the project. Ample documentation is provided at the `zopeproject` home page [5]_. `zopeproject` uses Paste or ZDaemon to create a working server. The following commands get you started:: $ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground Demo Packages ~~~~~~~~~~~~~ At this point, there is no demo package demonstrating a simple Zope 3 application setup. However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, enter the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.3 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://zope3.pov.lt/buildbot .. [2] http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg .. [3] http://download.zope.org/zope3.4/intro.html .. [4] http://download.zope.org/zope3.4/3.4.0/versions.cfg .. [5] http://pypi.python.org/pypi/zopeproject Downloads --------- - Zope 3.4 KGS: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/3.4.0/controlled-packages.cfg - Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.0/versions.cfg - The classic Zope 3 source release can be downloaded from: http://download.zope.org/zope3.4/3.4.0/Zope-3.4.0.tgz Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4 or 3.5 to run. You must also have zlib installed on your system. Resources --------- - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev Retired: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net About Zope 3 ------------ Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 ~~~~~~~~~~~~~~~~~~~~~~~~~ Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3. We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however. About the Zope Foundation ------------------------- The Zope Foundation, based in Fredricksburg, Virginia, is a not-for-profit organisation that provides support for the Zope community and the Zope platform and its associated software. Its community includes the open source community of contributers as well as the community of businesses and organizations that use Zope.

1 0

Grok 1.0a1 released!
by Martijn Faassen 08 Jan '09

08 Jan '09

The Grok team is happy to announce the release of Grok 1.0a1. This is the first step on the way to the release of Grok 1.0! With Grok 1.0 we will deliver a stable, powerful, featureful framework for Python-based web development. Grok 1.0a1 is a preview of the 1.0 release and a continuation of the developments in Grok 0.14. Changes ====== Grok 1.0a1 has the following changes compared to Grok 0.14: * Grok now uses WSGI and paster out of the box. To create a project that uses paster, update grokproject (``easy_install -U prokproject``) first. * Grok's REST support now works like layers have been for a while, using a ``grok.restskin`` directive on an interface. * A new ``grok.DirectoryResource`` component is available that can be used to expose resources (CSS, Javascript, images) to the web the Grok way, similar to the way the ZCML ``resourceDirectory`` directive can be used. * We have split off a new package that Grok now depends on which contains the viewlet support (``grokcore.viewlet``). The use of viewlets with Grok remains unchanged, but this package can also be used independently. * Besides our existing documentation we have started to add docstrings to the Grok source code to make it easier to understand. This release also contains a number of bugfixes. We are continuing to fix bugs on the way to Grok 1.0. For installation instructions and much more on how to use Grok, see the Grok tutorial: http://grok.zope.org/doc/current/tutorial.html Upgrading ======== It should not be needed to change your code to upgrade an existing project from 0.14 to 1.0a1, unless you use Grok's REST support. For detailed upgrade notes on this, see http://grok.zope.org/project/upgrade-notes If you want to use the paster support, please examine a project generated with the newest version of grokproject and update your project's ``buildout.cfg`` accordingly (and help us write better instructions!). We hope to hear from you! If you enjoy Grok, please subscribe to the `grok-dev mailing list`_ and join us in the #grok channel on irc.freenode.net. .. _`grok-dev mailing list`: http://grok.zope.org/community/grok-dev-mailinglist

1 0

New Zope Foundation bylaws passed
by Jens Vagelpohl 17 Dec '08

17 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After a lot of hard work a special Zope Foundation membership meeting called for December 12, 2008 passed a new set of bylaws unanimously. The current bylaws were based on those of the Eclipse foundation, which shortly after adoption were discovered to be too heavyweight for the kind of organization the Zope Foundation aims to be. Evolving the existing bylaws into something more appropriate and manageable was attempted but failed. The proposed bylaws are based on the bylaws of the Python Software Foundation, with some additional improvements the PSF itself is intending to implement. They were also brought in line with the fact that the Zope Foundation expects to conduct most of its meetings and communication online. The major differences between the current and the proposed bylaws are: * Making changes to the bylaws becomes easier. * There will be only three classes of members: 1. Nominated Members, an individual and free membership that replaces the old 'committer' and 'associate' memberships. There will no longer be any formal relation between being a Zope Committer and becoming a Foundation Member. 2. Sponsorship Members, members who financially sponsor the Foundation. 3. Emeritus Members, members who retired from active membership. The new bylaws can be downloaded from the Zope Foundation website at http://foundation.zope.org/bylaws/zope_foundation_bylaws.pdf Jens Vagelpohl, Board Member, Zope Foundation -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAklJG0cACgkQRAx5nvEhZLKmCACgmkXf1yO4Yj1+fPS2woHJbk4G DTIAoIVjjItCjK9T2tRVnYiAxgfTWe7w =G8KW -----END PGP SIGNATURE-----

1 0

serious security issue in Grok: please upgrade
by Martijn Faassen 12 Dec '08

12 Dec '08

Security issue in Grok: please upgrade! ======================================= December 12, 2008. The Grok team encountered a serious security issue that exposes Grok installations to attacks that erase data as well as remote denial of service attacks. We *strongly* urge people to upgrade to newer versions of Grok immediately. We have supplied new bug fix releases of Grok for Grok 0.11 up to the recent release, Grok 0.14. Only projects that use Grok directly are affected by this security issue. If your Zope 3 project uses the ``grokcore.*`` libraries or if you use ``five.grok`` on Zope 2, there is no security problem. How to upgrade Grok? We give instructions that you can apply in your Grok projects. Please run ``buildout`` after making the changes - this will download the fixed version of Grok. After this restart your server! The upgrade instructions assume two possible installation methods: * Old versions of ``grokproject`` generated projects that only include the ``extends=`` line in ``buildout.cfg``, and updating that line to point to a newer version of Grok is sufficient. * Newer versions of ``grokproject`` create projects that require you to modify ``versions.cfg``. There is also a line pointing to a Grok version in the ``eggbasket`` section in ``buildout.cfg``. While this a download optimization only, we still recommend you update that line as well. Grok 0.14: upgrade to Grok 0.14.1 --------------------------------- In the file ``versions.cfg`` change the line:: grok = 0.14 to this:: grok = 0.14.1 If you have no ``versions.cfg``, go to your projects ``buildout.cfg`` and adjust this line:: extends = http://grok.zope.org/releaseinfo/grok-0.14.cfg to this:: extends = http://grok.zope.org/releaseinfo/grok-0.14.1.cfg While not strictly required, we also recommend you modify the following line in the ``[eggbasket]`` section (if present):: url = http://grok.zope.org/releaseinfo/grok-eggs-0.14.tgz to:: url = http://grok.zope.org/releaseinfo/grok-eggs-0.14.1.tgz After this change, run ``buildout`` and restart the server. This version should work properly with Python 2.4 and Python 2.5. Grok 0.13: upgrade to Grok 0.13.1 --------------------------------- In the file ``versions.cfg`` change the line:: grok = 0.13 to this:: grok = 0.13.1 If you have no ``versions.cfg``, go to your projects ``buildout.cfg`` and adjust this line:: extends = http://grok.zope.org/releaseinfo/grok-0.13.cfg to this:: extends = http://grok.zope.org/releaseinfo/grok-0.13.1.cfg While not strictly required, we also recommend you modify the following line in the ``[eggbasket]`` section (if present):: url = http://grok.zope.org/releaseinfo/grok-eggs-0.13.tgz to:: url = http://grok.zope.org/releaseinfo/grok-eggs-0.13.1.tgz After this change, run ``buildout`` and restart the server. This version should work properly with Python 2.4 and Python 2.5. Grok 0.12 and Grok 0.12.1: upgrade to Grok 0.12.2 ------------------------------------------------- In the file ``versions.cfg`` change the line:: grok = 0.12 (or 0.12.1) to this:: grok = 0.12.2 If you have no ``versions.cfg``, go to your projects ``buildout.cfg`` and adjust this line:: extends = http://grok.zope.org/releaseinfo/grok-0.12.cfg (or grok-0.12.1.cfg) to this:: extends = http://grok.zope.org/releaseinfo/grok-0.12.2.cfg While not strictly required, we also recommend you modify the following line in the ``[eggbasket]`` section (if present):: url = http://grok.zope.org/releaseinfo/grok-eggs-0.12.tgz (or grok-0.12.1.cfg) to:: url = http://grok.zope.org/releaseinfo/grok-eggs-0.12.2.tgz After this change, run ``buildout`` and restart the server. Note: the integrated REST support does not function properly on Python 2.5 in this version. It does work with the recommended version Python 2.4. Grok 0.11 and Grok 0.11.1: upgrade to Grok 0.11.2 ------------------------------------------------- In the file ``versions.cfg`` change the line:: grok = 0.11 (or 0.11.1) to this:: grok = 0.11.2 If you have no ``versions.cfg``, go to your projects ``buildout.cfg`` and adjust this line:: extends = http://grok.zope.org/releaseinfo/grok-0.11.cfg (or grok-0.11.1.cfg) to this:: extends = http://grok.zope.org/releaseinfo/grok-0.11.2.cfg We have not released a grok-eggs-0.11.2.tgz as we never maintained such tarball releases for Grok 0.11. After this change, run ``buildout`` and restart the server. Note: the integrated REST support will not function properly on Python 2.5 in this version. It does work with the recommended version Python 2.4.

1 0

Localizer 1.2.3 released
by "J. David Ibáñez" 03 Dec '08

03 Dec '08

Localizer is a Zope product for developers and web masters. Localizer solves the problem of building multilingual products and web sites, ranging from internationalization and localization of the user interface to management of multilingual content. What is new? - Compatibility fixes for Zope 2.10/2.11 (bug #381) - Other minor fixes (including bug #304) Resources --------- Download http://download.hforge.org/localizer/Localizer-1.2.3.tar.gz http://download.hforge.org/itools/itools-0.20.6.tar.gz Home http://www.localizer.org/ Mailing list http://www.hforge.org/community http://archives.hforge.org/index.cgi?list=localizer Bug Tracker http://bugs.hforge.org/ -- J. David Ibáñez Itaapy <http://www.itaapy.com> Tel +33 (0)1 42 23 67 45 9 rue Darwin, 75018 Paris Fax +33 (0)1 53 28 27 88

1 0

Silva 2.2 alpha Released
by Kit BLAKE 18 Nov '08

18 Nov '08

Silva 2.2 alpha Released Infrae is pleased to announce the alpha release of Silva 2.2. This release adds a slew of new features for developers and system administrators, and is a quantum leap with Zope 2.11 and Five/Grok technology. Also the Sphinx-driven docs.infrae.com has gone online. New features, of interest to developers * Silva has been ‘eggified’. Buildout scripts can now retrieve eggs from https://dist.infrae.com/ and the Python Package Index (formerly the Cheese Shop). * Five/Grok views are supported. This lets you define Zope 3 Views to render content. * All Silva content types and services now use five.grok for configuration and registration. * Content types are now created and edited using the z3c forms component. * Generic Formlib and z3c forms support have been added to the ZMI. * The mechanism for previewing public pages has been refactored. No additional ZCML and view definitions are needed. Importantly, a Five namespace is used so that the author stays in preview mode even when navigating. * Publications can now become a subsite, meaning that they have local services that change their local configuration. * A separate metadata set to mark publications as virtual hosts is not needed. Now to get virtual hosts working you just have to configure Apache. * Filesystem-based layout has been refactored: it’s now much easier to define a layout and extend it. You can use Zope 3 views, content providers and viewlets. * Skin templates on the file system can be easily customized, via a customization service that duplicates the template in the ZODB. Customization can apply only to selected content with the help of customization markers, or to all content implementing one given interface (for instance all documents, or all containers). Manager users can then edit at will and make changes in a live server without restart. This is not a replacement for more robust development methods, but can be a great way to make small adjustments to parts of a site. New features, of interest to system administrators * BLOB support has been implemented. This provides the Zope 2.11 option to use BLOBs for storing binary objects. The existing ExtFile implementation is still fully supported. Out-of-the-box, binaries are still stored in the ZODB. * A user interface for conversion between ZODB binary storage, ExtFile binary storage and BLOB binary storage has been created. Migrate, or revert, with a button click. New features, of interest to users * Changes have been made in SilvaLayout with skin-based components added, such as viewlets, a viewlet manager, and content providers. * When previewing, an author can now navigate throughout the site, staying in preview mode. This holds not only for content but for all links in a template. Check out docs.infrae.com Silva 2.2 code has been used to generate developer documentation using Sphinx. See http://docs.infrae.com/. This is also an alpha. What is Silva? Silva is a powerful CMS for organizations that manage multiple or complex websites. Content is stored in clean and futureproof XML, independent of layout and presentation. Features include versioning, workflow system, integral visual editor (Kupu), content reuse, sophisticated access control, multi-site management, extensive import/ export facilities, fine-grained templating, and hi-res image storage and manipulation. For more complete information, see the Silva Product Pages at http://infrae.com/products/silva . Install As this is a developer release it’s only available using buildout: https://svn.infrae.com/buildout/silva/tag/Silva-2.2a1/ or using Paster by selecting the development distribution. Contact FMI contact Sylvain Viollon, sylvain at infrae com, +31 10 243 7051.

1 0