[Zope-dev] Maintainer position for the Zope Windows builds vacant
Hi, Christian Theune, the current maintainer of the windows builds, announced to step down as maintainer. This means that this position is vacant. So this is your chance to become famous :-) To be honest, doing Zope releases is a bit of work and not always fun but it is work that has to be done by someone. So if you are interested and if you have the resources, raise your finger. Since new Zope 2 releases are scheduled for October I would like to see this position filled asap. I will definitely continue on the source releases but I have not enough Windows know-how to do it myself. Since there are lot of *serious* Zope-on-Windows users I do expect that someone takes over this great job. Having no volunteer for the Windows builds would mean that only source code releases would be available in the future. I'm fine with that but possibly not all Zope-on-Windows users...so if you depend on Zope-on-Windows you should do something for your dependency to be fulfilled. Cheers, Andreas pgpTH2d0qs9He.pgp Description: 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] Maintainer position for the Zope Windows builds vacant
My hope is that, starting with Zope 2.9, the Zope 2 releases will, like the Zope 3 releases, be built with zpkg. zpkg is a system for assembling components (basically packages) based on dependency information and automatically creating python distutils-based distributions. This approach has some advantages and disadvantages: + Much more of the process is automated, + Binary releases can be built automaticall - The releases include just Zope - The binary releases install into Python -- meaning that only one release of Zope can be installed for a given Python release. My thought for windows is that we'd provide a *simple* combined installer that installs Python and Zope by invoking separate Python and Zope installers. This won't affect Zope 2.8 and earlier versions of Zope 2. Jim Andreas Jung wrote: Hi, Christian Theune, the current maintainer of the windows builds, announced to step down as maintainer. This means that this position is vacant. So this is your chance to become famous :-) To be honest, doing Zope releases is a bit of work and not always fun but it is work that has to be done by someone. So if you are interested and if you have the resources, raise your finger. Since new Zope 2 releases are scheduled for October I would like to see this position filled asap. I will definitely continue on the source releases but I have not enough Windows know-how to do it myself. Since there are lot of *serious* Zope-on-Windows users I do expect that someone takes over this great job. Having no volunteer for the Windows builds would mean that only source code releases would be available in the future. I'm fine with that but possibly not all Zope-on-Windows users...so if you depend on Zope-on-Windows you should do something for your dependency to be fulfilled. Cheers, Andrea s ___ 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 ) -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] Allowing @ in object ids
Today @ is forbidden in object ids. That's controlled by the bad_id regexp in OFS.ObjectManager, which tries to ensure that ids will be useable as URL components. However, there's no reason to disallow this, as the URL spec (http:// www.ietf.org/rfc/rfc1738.txt) says: An HTTP URL takes the form: http://host:port/path?searchpart [...] Within the path and searchpart components, /, ;, ? are reserved. The / character may be used within HTTP to designate a hierarchical structure. Note that somewhere else in the spec, it says that @ (and others) MAY be reserved by some schemes, but HTTP doesn't actually make it reserved. Furthermore, many projects have monkey-patched bad_id to allow @ and see no ill-effects. Having @ in ids is very useful for various things, one of them being to have email-like identifiers (think jabber for instance). There are other uses. Unless there's opposition, I'll change the code to allow it. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ 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 )