Re: [Zope-dev] Stepping back as Zope 2 release manager
2010/1/11 Andreas Jung li...@zopyx.com: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I would like to inform you that I intent to retreat from the Zope 2 release manager position soon. I have been serving the Zope community in this position for almost seven years and now it is time to move on and hand over the responsibility to some other person. The reasons for stepping down are pretty easy: I am too busy with other things and I would like to shift my focus on other Zope-related projects but I will remain part of the Zope and Plone community. The Zope community has no official process for choosing a new release manager so I assume some volunteer has to speak up or someone may suggest a honorable person of the Zope community for the position. Thanks for the years of contributions and time! Many people and parties have appreciated it. Good luck with the new endeavors, Kit -- Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Annce] Silva 2.2 alpha Released
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. ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] PyPI mirrors available
2008/11/13 Andreas Jung [EMAIL PROTECTED] Hi there, I would like to point out that we have started the PyPI replication project some months ago during the Blackforest sprint: http://www.openplans.org/projects/pypi-mirroring/project-home As an outcome we are now able to provide in phase one of the project some mirrors of PyPI index. Currently we have three mirrors up and running and some more mirrors will join the project soon. Right now we provide all packages of PyPI that are directly hosted on PyPI (no packages with external download URLs). This project should bring a lot of ease to buildout users because PyPI is no longer a single-point-of-failure. Currently you have to choose a PyPI mirror manually. For the next project phase we think about a smarter mirror selection mechanism that is more transparent to setuptools and zc.buildout. Suggestions and further support in terms of hardware resources and bandwidth are highly appreciated. Credits go to Josip Delic and Gottfried Ganssauge of Haufe Mediengruppe for their contributions to the original codebase of z3c.pypimirror and to Daniel Kraft of D9T for being doing most of the coding of the package. Congrats to all! -- Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051 ___ 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 2.12 features / roadmap
Andreas Jung [EMAIL PROTECTED] From what I know of other consumers of Zope 2, it seems Haufe doesn't have a need for any of the Zope 2.12 features at this point, but is using Zope 2.11 / Zope 3.4 as a development base. There is no special need for a Zope 2.12 release from the Haufe side - we still have to catch up :-) Ditto for Silva (the catch up as well) -- Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051 ___ 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-Annce] Silva 2.1 alpha, plus Firefox 3 Compatibility Releases
Silva 2.1 alpha, plus Firefox 3 Compatibility Releases 21 june 2008 – Infrae announces an alpha release of Silva 2.1, plus three releases for Silva versions that fix problems with the Firefox 3 web browser. There are Silva 2.0.8, 1.6.3, and 1.5.12 versions available. New features of the Silva 2.1 alpha will be announced on the silva-general mailing list: https://lists.infrae.com/mailman/listinfo/silva-general In the 2.x series the key improvements are: * Added support for ‘elaborate’ Code Sources, which are editable in a pop-up window instead of a toolbox. * When SMTP errors occur while sending notifications, we log them, but no longer abort the process. * When PDF/Word file conversion for indexing results in errors, the converted text is indexed anyway. Various other minor issues have been fixed. For details see the history file included with each version. 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. Download The packages can be downloaded from: Silva 2.1 alpha: http://infrae.com/download/Silva/2.1a2 Silva 2.0.8: http://infrae.com/download/Silva/2.0.8 Silva 1.6.3: http://infrae.com/download/Silva/1.6.3 Silva 1.5.12: http://infrae.com/download/Silva/1.5.12 Info about svn access and using a buildout to install Silva is available at http://infrae.com/download/Silva. Contact FMI contact Eric Casteleijn, eric at infrae com, +31 10 243 7051. ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Using zoperoot.misc_.MyProduct
2007/12/14, Peter Bengtsson [EMAIL PROTECTED]: As far as I can see, an advantage with attaching static stuff to OFS.misc_.MyInstalledProduct is that it becomes available globally which makes sense to avoid loading a different icon URL for each www icon in the ZMI of a product. Makes sense also for example if you have one Zope with 10 different instances because then there's just one on /misc_/MyProduct/screen.css to cache and download for the browser if you've placed a static file there called that. A drawback seems to be that errors happening in /misc_/MyProduct/static-content isn't reported in the error_log. This makes it hard to spot bugs in objects in there and, more commonly, NotFound errors. Is there anything I can do about that or should I not expect so much and instead use the instance? Just curious, are you also creating '.metadata' files for these assets to be used with an HTTP Cache Manager? -- Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051 Hoevestraat 10 · 3033 GC · Rotterdam + The Netherlands OpenPGP 0xE67AD0F2 · Contact = http://xri.net/=kitblake ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Annce] Silva issues now tracked in Launchpad
3 april 2007 – Infrae is pleased to announce that Silva’s issue tracking is now in Launchpad. This move is part of an effort to enhance collaboration with other components in the software stack. Besides being the home of the GNU/Linux distribution Ubuntu, Launchpad also hosts Zope3 issues, Grok issues, SchoolTool, and has been the development hub of the dLCMS (dynamic Learning Content Management System, developed at ETH Zurich) for the last year. Many Silva users have used Launchpad to translate Silva’s interface languages. Translations are linked with 2,700 other projects on Launchpad, and the website offers suggestions of possible wordings from those projects. This inter-connecting of open source communities is a prime example of the potential of the Launchpad service. Yesterday the Launchpad team announced the release of their 1.0 beta, sporting a redesigned interface and features to link data from a variety of project-specific sources. In the press release was a quote from Infrae: ”Launchpad connects us to our most important communities, and brings synergy to issue tracking for Silva, where problems in one component of the stack affect another up or downstream. Key components of our stack were already there: Infrae’s developers run Ubuntu, we develop with Zope3, and the dLCMS product (which is built on top of Silva) has been using Launchpad for over a year. Locating the Silva issues on Launchpad was like finding ideal office space, hooked into the grid, loaded with amenities, and ripe for networking.“ Using Launchpad Now and in the future, all Silva issues will be tracked at: https://bugs.launchpad.net/silva Users will need to create an account on Launchpad, and adjust to the new environment. A good overview is at: https://help.launchpad.net/FeatureHighlights There is also a Silva Project that groups the Silva CMS and its related products: https://bugs.launchpad.net/silva-project The Silva translations are at: https://launchpad.net/silva/+translations Soon to be in place is a redirecting facility, where bugs from the old tracker will be automatically redirected to the corresponding Launchpad issue. Given an old issue number , you’ll get to the new page on Launchpad at: https://bugs.launchpad.net/bugs/silva- Other projects Note that the Launchpad development team will import bugs from existing bug trackers for projects that want to move to Launchpad. What is Silva? Silva is an enterprise-class CMS designed for large organizations that manage multiple or complex websites. Content is stored in clean and future-proof XML, independent of layout and presentation. Features include a multi-version workflow system, XSLT rendering support, content reuse in multiple publications, sophisticated access management, extensive import/export facilities, fine-grained templating, and hi-res image storage and manipulation. Silva and its extensions are open source software. For more complete information, see the Silva Product Pages at http://www.infrae.com/products/silva. Download The package can be downloaded from http://www.infrae.com/download/Silva. Contact FMI contact Eric Casteleijn, eric at infrae com, +31 10 243 7051. ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Annce] Silva 1.5.9 Released
Infrae has just released version 1.5.9 of the Silva content management system. This is a maintenance release that improves performance, exposes Firefox spellcheck capability, and fixes various minor issues. Changes in Silva and related products An abridged list of changes follows. For complete details of the fixed issues see HISTORY.txt in the packages. Silva - Changed calls from getMetdata to getMetadataValue where possible, resulting in a significant performance gain. - Fixed unicode bug in Indexers. - Fixed a number of minor bugs. SilvaMetadata - Bugfix for empty strings in aqcuirable metadata fields blocking acquisition. Thanks to Nico Grubert for the bug report and fix. Kupu - When images exist in a document and the author scales one, the display in Kupu can be cached by the browser and doesn't update properly. The editor frame is now reloadable with the right-mouse button so authors can force a reload. - Previously Kupu had a right-mouse button menu. This has been disabled, with the intention of exposing spellcheck functionality that is built into Firefox 2.0. This means, if you are using FF 2.0, text in Silva is automatically checked. Dictionaries for all major languages are simple to install. SilvaLayout - The modification time shown when viewing a folder is now taken from the default document. What is Silva? Silva is a powerful CMS for organizations that manage 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/. Download The package can be downloaded from: http://infrae.com/download/Silva. Links to developer mailing lists, the Silva issue tracker, and info about SVN access can be found on the Silva intro page. Contact FMI contact Eric Casteleijn, eric at infrae com, +31 10 243 7051. ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope at universities?
2006/9/17, Andreas R. Johnsen [EMAIL PROTECTED]: Hei, I'm looking for information about the use of Zope at universities. Most large universities have a very heterogeneous infrastructure and I guess many of them utilize Zope in a way or another. I'm looking for references to universities where Zope is part of a central strategi or in other ways plays an important role for several of the web sites at the university. Two examples are ETH Zürich and University of Bristol. All the universities listed on this page use Zope: http://www.infrae.com/about/references kit -- kit BLAKE · Infrae · http://infrae.com + 31 10 243 7051 Hoevestraat 10 · 3033 GC · Rotterdam + The Netherlands Contact = http://2idi.com/contact/=kitblake ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Announcing the release of Zope version 2.8.8
Hi Tres, - Extension Classes were rewritten as Python new-style classes making all features of Python new-style classes available in Zope objects. This includes support for cyclic garbage collection. Does this mean that the following is fixed? Quoting from the Zope 2.9.4 CHANGES.txt: To-do * Add cyclic-garbage collection support to C extension classes, especially to acquisition wrappers. 1. B: ExtensionClassType already declares that it supports GC (via the Py_TPFLAGS_HAVE_GC flag), but does not appear to conform to the rules for such a type laid out in the Python docs: http://docs.python.org/api/supporting-cycle-detection.html I don't see the same note in the 2.8.8 CHANGES.txt, but I'm sure it was there in earlier versions. kit -- kit BLAKE Infrae · infrae.com + 31 10 243 7051 Hoevestraat 10 · 3033GC · Rotterdam · The Netherlands ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] Re: favicon.ico for 2.10?
2006/4/24, Jens Vagelpohl [EMAIL PROTECTED]: Yeah, that's nice. Does it work as a PNG, though? I was under the impression (and thought the spec requires) that favicons must be *.ico files. A PNG favicon will work in the Mozilla family, but not in IE. kit -- kit BLAKE Infrae · infrae.com + 31 10 243 7051 Hoevestraat 10 · 3033GC · Rotterdam · The Netherlands ___ 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] Re: favicon.ico for 2.10?
2006/4/24, Jens Vagelpohl [EMAIL PROTECTED]: A PNG favicon will work in the Mozilla family, but not in IE. OK, that would be unacceptable, IMHO. However, the awesome power of Graphic Converter helped me produce a ICO file from the PNG, which I am attaching to this email (no idea if the list lets it through, though). Works for me (although I'm on an Apple, someone please test with Win/IE)) kit -- kit BLAKE Infrae · infrae.com + 31 10 243 7051 Hoevestraat 10 · 3033GC · Rotterdam · The Netherlands ___ 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] Re: [ZF] ANNOUNCE: Zope Foundation is incorporated!
2006/3/25, Rob Page [EMAIL PROTECTED]: At long last the Zope Foundation is incorporated! Thanks to everyone who has helped get the Foundation to this point!! Congratulations! I can only guess at the enormous amount of work that took. kit -- kit BLAKE Infrae · infrae.com + 31 10 243 7051 Hoevestraat 10 · 3033GC · Rotterdam · The Netherlands ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope and OAI-PMH
2006/1/27, Luciano Ramalho [EMAIL PROTECTED]: I've been assigned to integrate an existing academic portal in Plone with the OAI-PMH protocol as a data provider. Searching through this list I found the message below, but no response. On 2/4/05, Yuri [EMAIL PROTECTED] wrote: There are several (at least two...) products to manage OAI with Zope. Can someone share his experiences in this list? Thanks :) The products I've found were: - OAI Pack from Infrae http://www.infrae.com/products/oaipack - ZOpenArchives from Pentila http://www.pentila.com/produits/ZOpenArchives Is anyone here using these (or other) products to implement OAI in Zope or Plone? Which is the more actively supported product? Hi Luciano, The OAI Pack product is actively supported (I don't whether it's 'more' :-) We've had contact with the ZOpenArchives guys. AFAIK, the main functional difference is ZOpenArchives provides storage for the 'server' in the ZODB, whereas we have assumed (and built) separate storage servers for the documents, and implemented the harvesting/search in Zope. Currently we're completing a Document Library application, written in Zope3, that supports metadata harvesting with OAI-PMH. This was presented at the PloneConf in Vienna in september. It'll be released in the next month or so. kit -- kit BLAKE Infrae · infrae.com · +31 10 243 7051 Hoevestraat 10 · 3033GC · Rotterdam · The Netherlands ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-dev] Re: [Z3lab] Nuxeo supports Zope Corp announces
Wow, what a difference two days makes. I heard about the ZF announcement by telephone two mornings ago, and I breathed a huge sigh of relief. It solves a problem we've been worrying about for years. It means we can sit across from a nervous IT director, and when he asks dubious questions about the steering and future of the Zope platform, we can say with certainty, It's in good hands. Reviewing the thread, I'm astonished at the negativity. C'mon, this is a *breakthrough*. It's a move that can ensure the future of Zope. Granted, it's prudent to be cautious, and there's a lot of work to be done, but it's a major step. Shouldn't we be using an Agile approach? As for structure and neutrality, I think decisions should be left up to the developers. If they're not on board, there won't be anything. I'm not much of a developer, I'm a manager, and I know that attempting to pull developers 'over a bridge' is a bad idea. Actually, I'm a vendor too. So wearing all these different stakeholder hats, I'm looking forward to the process. To be explicit: I'm prepared to invest in the future of Zope. kit -- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Infrae . . . kit blake . . . infrae.com . t +31 10 243 7051 Hoevestraat 10 . 3033 GC Rotterdam . NL . f +31 10 243 7052 ___ 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 )
