Re: [Framework-Team] changing name of plone.app.event?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 plone.app.calendar is even more misleading since plone.app.event provides only the event core implementation but not calendar functionality (or?). I think plone.app.event is fine since Plone developers know of ATEvent and speaking of plone.app.event as a replacement seems more logical than renaming it to .calendar. My 2cents, Andreas Johannes Raggam wrote: > Dear Framework Team! > > The name plone.app.event for the event improvement package (see: > http://dev.plone.org/plone/ticket/10886 ) was proposed by me at the > cathedral sprint in Cologne. But since then I often think that this > wasn't the best possible name. It's too ambiguous because it may impose > some zope.event like event-machinery as purpose. > > Would the FWT agree to change it to plone.app.calendar and eventually > create an additional package called plone.calendar for general purpose > tools and interfaces? > "calendar" seems a good name to me because among other reasons some > parts are modeled after the RFC2445 (iCalendar) specification. > > This is the last possible moment to change the name before > plone.app.event would possibly released with plone4.1. > > Thanks and all the best, > johannes raggam > > ___ > Framework-Team mailing list > Framework-Team@lists.plone.org > http://lists.plone.org/mailman/listinfo/framework-team - -- ZOPYX Limited | zopyx group Charlottenstr. 37/1 | The full-service network for Zope & Plone D-72070 Tübingen| Produce & Publish www.zopyx.com | www.produce-and-publish.com - E-Publishing, Python, Zope & Plone development, Consulting -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJMoLHuAAoJEADcfz7u4AZjWFULv0WEWyzJvSp6rrns9W9Vr6aw q1OcgDfJClL5Zy0MMNeOzS1r9ZOAv9WxR/Xo79Dax7d3pBN9aMZnUciRBRyvnzQx no6yJHtnrRRrNDrBubtwK+Soyu0HpoL+LtX4tVw3WAAmtzUwqO4dU4KrHYN0pMlx UnXR/ajQZMThJl9wC94JH+rXhZ3sEoQluOJLLHvUOqfo6tJYK/flwBEOnty0esye WSsvTIgLh+wmhC9kDReIXWSUhf0cyypjQLZMYyuz74F7wnVxeHqhV4+pl1qWwTtN OrvW/82f0Gv7BRxg9VFTQQ9FGctTLA9k0EgwU37idWRYhIZjIORFBYbdzYmZrNI5 4Oxi8a7oj52Lo3RWthM1AJZEpgjZ19+A9xUnd46dZCNi7SPo8CRs4ZKrnMn7hgUQ zJkL6YGq1ZR4929pzlGrzlv4/YwMkRsONEsaKcXIP4WWJpjv8oRqWbP42ZGVitR7 i2c/6UON/JhWqxWSIUvVsBjRjbv5OkY= =MLyt -END PGP SIGNATURE- <>___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone roadmap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Limi wrote: > I think we should envision a future without WebDAV and FTP as core > components of our stack. They never worked well in practice, and are > unlikely to ever reach mainstream usage because of the extra steps, > concept abstraction, and setup knowledge required. > > +1 Robust support for uploading/download for multiple files through a ZIP archive is often good enough and can be handled by most users and in addition something like PloneFlashUpload for uploading multiple files in one run (I think HTML5 has some special support for doing this). - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJMjaoVAAoJEADcfz7u4AZjk2sLv2y50LZcnAbcjAl8In5Jxabs 5R2p7Mk8BogdXKfFAzineFrIDlQwp+0u0jhoV3kEp7jwfsoZHxdB9bew9etxhnQP i+E4cCKhxPrAHtBaP2mbdRHztliOriJUgl/vk+9n6FpkyGPh1g8TDXLkR2JlaYEY b4Xql1ItMKfQxz7uu0MJk1tgTJLLDuBNbkpjRKiy9gdNdiH5msYElY8XIZkpzeqZ T31EVS/zQyHn0ClsDno+fV77IOfvcMxLo6zzl7Okmdpqf+K6KRINQim5fyE+vY+A CgFhtsiBAzkqWno8X+H6zf+CDdiZ3qVgdZn+R6xOR0kVTEPq+nfXgxY6qTEY4OvC 7oFDviIEZA9CwMtTnjpwVrx4NjAQnJKQmT7eoxMfjU0VM1TruCEmN8wirUnr5Bja 2Ucb1yfHq93O9VA3ux3u5yd/CUFfLhkE7cwd4B++XD5gAGfhdEM6YH2lKxB761Qn 1J/8xapAaPNEtOC/CsBmT7Bw8ekGlxg= =q8js -END PGP SIGNATURE- <>___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] PLIP submission for Plone 4.1 - #9302 - plone.app.event
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I propose to include PLIP #9302 for Plone 4.1 The original proposal (integration of vs.event) is here: http://dev.plone.org/plone/ticket/9302 plone.app.event as replacement for ATEvent was implemented during the Cologne sprint. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxFzhYACgkQCJIWIbr9KYxNXwCgpbCDeUlely7VaKt8AIqE2rHe xAsAoJfd3qNLkrZz/WT3A12eKOHyGNG4 =sIbW -END PGP SIGNATURE- <>___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Zope Summit in September 2010 in Halle, Germany
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, on behalf of Christian Theune I would like you to take notice of the Zope Summit scheduled for September in Halle, Germany just before the German Zope conference in Dresden - one week full of Zope! https://mail.zope.org/pipermail/zope-dev/2010-June/040822.html Andreas - -- ZOPYX Limited | zopyx group Charlottenstr. 37/1 | The full-service network for Zope & Plone D-72070 Tübingen| Produce & Publish www.zopyx.com | www.produce-and-publish.com - E-Publishing, Python, Zope & Plone development, Consulting -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw27loACgkQCJIWIbr9KYw++ACg3Tn8WxgTLrNHYBFYghRgBzS8 hIEAn0dldB+Ve5pkBnOD2VGmIai5xGD3 =kzEi -END PGP SIGNATURE- <>___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Accouncement for updated Zope versions due to XSS vulnerability
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sivan Green wrote: > So we should issue an informed warning and encourage to update > together with update instructions. Have we tested that to no break > current installs / buildouts ? > Full disclosure is available: https://bugs.launchpad.net/zope2/+bug/491224 I would not expect any issues with upgrading the Zope version. I updated a bunch of Plone 3.2 and 3.3 sites from various Zope 2.10 versions to the latest one - no issues - especially because the fix is a one-liner somewhere in the handler for the error messages. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktOA3oACgkQCJIWIbr9KYxXOwCgutkoudJ8AyiwKiv3KU0G4XsG eMYAoKgJY6+IDiDawy5OoJnj+qZ1wAaM =hxl3 -END PGP SIGNATURE- <>___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Accouncement for updated Zope versions due to XSS vulnerability
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I think Plone users should get information about the updated Zope versions (2.8-2.12) released yesterday in order to fix the XSS vulnerability reported by Alex Limi. Is this on someone's radar? Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktN9oAACgkQCJIWIbr9KYzoVQCgzZosjhEkvHvJxlIy2II6DBM/ eVgAnREx2AJr4aAybchznz8CuHxxzIu3 =RGxj -END PGP SIGNATURE- <>___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: [Zope-dev] MailHost Improvements
On 13.08.09 01:03, Alec Mitchell wrote: > Hello, > > I've been working on making Plone use the standard Zope MailHost in > place of the custom Products.SecureMailHost we've been using since > Plone 2.1 (See: http://dev.plone.org/plone/ticket/8814). During this > process I've run into a couple bugs in the MailHost implementation and > I believe it is missing some essential functionality. > > The most significant issue is that if you call send() with a > messageText containing just the message body, and that body has a ':' > in it (e.g. a url) the body will be treated as a header and you'll > send a nonsense message. The current implementation of send() also > puts a fairly large burden on developers who want to generate simple, > correctly encoded messages. Finally, send() relies heavily on the > long deprecated 'rfc822' and 'mimetools' modules which have been > removed from Python 3.0. > > I've attached a patch that updates MailHost to use the 'email' module > for parsing and generating messages. In addition to fixing the issues > that I ran across, and maintaining compatibility, it provides a number > of new features: > > * send and sendTemplate accept an optional charset argument. Using > this will set the content-type charset, as well as trigger appropriate > encoding if needed. > > * send and sendTemplate accept an optional msg_type argument which > will set the content type header for the message. > > * The messageText, mfrom, mto, and subject arguments may now be > unicode or encoded non-ascii strings, provided a charset is given. > Any unicode input will be automatically encoded to the provided > charset (or the default charset). Headers will be further encoded in > compliance with rfc2822. The message body will be further encoded > using a transfer encoding determined by the email.Charset registry > (e.g. 7bit for us-ascii, quoted-printable for utf-8 and iso8859, > base64 for most other encodings). > > * The messageText argument now accepts email.Message.Message objects > directly. > > I'm attaching a patch that includes these changes as well as tests for > all new functionality. I hope to integrate these changes into Zope > 2.12 before final release, but would like to hear the opinions of Zope > developers before committing. Though these are fairly significant > changes, I believe they provide very useful functionality as well as > at least one critical fix, while maintaining 100% compatibility. This comes very, very late. We are pretty close to a release. Please put the changes on the trunk only. We will check after my vacation if we can move it into the 2.12 beta. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: Plone 4 dependencies
On Wed, May 27, 2009 at 22:47, Matthew Wilkes wrote: > > On 26 May 2009, at 10:59, Hanno Schlichting wrote: > > I think someone has to try and see what kind of changes are acutally >> required to make a current Plone 3.3rc3 run on Zope 2.12 or even better >> a real client side with a collection of add-ons. >> > > I doubt it's very hard, a concerted effort by me and Sidnei at the last > Summer of Code summit left us with Plone trunk working on Zope trunk, and > that was only a few weeks after the conference. Zope really was where most > of the changes needed to be, I do think targeting 4.0 to Zope 2.12 is > feasible and proper. > +1 Andreas ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] HTTP parameter polution
On 20.05.09 06:23, Steve McMahon wrote: > The paper mentions Plone, but all they found is that Plone rejects the > bad input but "Since this error generates > ~100 lines in the log file, it may be used to obfuscate other > attacks." I found no serious vulnerability claim. Thanks Steve for cross-checking...another security marketing argument for promoting Zope & Plone. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] HTTP parameter polution
Hi there, just read this article (in German) about a new attack pattern called HTTP parameter polution and they mention Plone: http://www.linux-community.de/Internal/Nachrichten/Webanwendungen-mit-HTTP-Parameter-Pollution-angreifen Anyone heard of this? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] "Unladen Swallow" -- possibly worth keeping an eye on
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27.03.2009 21:37 Uhr, Sidnei da Silva wrote: > On Fri, Mar 27, 2009 at 6:21 PM, Jon Stahl wrote: >> Google's Python folks have started an effort to significantly speed up >> Python. >> http://code.google.com/p/unladen-swallow/ >> >> Should be interesting to keep an eye on. > > For the record, if they speed up cPickle, that will contribute a lot to ZODB. Only is cPickle is a real bottleneck (I doubt that). > > Another thing that might be worth looking at, to make Chameleon even > faster, is to use Cython to generate some type annotations. There first thing would be an unladen-swallow version running with Zope 2.12. This fails right now. Andreas - -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: i...@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK - E-Publishing, Python, Zope & Plone development, Consulting -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknNlHEACgkQCJIWIbr9KYzyBwCeN9Hj9x+4qTnzNWacCwYqBjs0 3W8AnAqo2VSx6O1RSQIuJpYe+7cp7dof =P/zb -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. & Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: PLIP 177 - Content indexing
--On 17. August 2007 13:10:25 + "Andrzej (nickSamotnik)" <[EMAIL PROTECTED]> wrote: * When using TextIndexNG3 for indexing ExternalSiteCatalog the HTML code is not removed; this indicates a serius archietcture error, probably in ExternalSiteCatalog. There should be a standard of componentisation or pluggization of the pipeline. Likely because there is no proper adapter available for hooking ExternalSiteCatalog with the capabilities of TXNG3. Writing an adapter should be trivial. * There is not unified way of loading and configuring lexicons, not clear division of processing tasks between program and lexicon, and not unified location of lexicon loading/initiation/configuring; for example: where is the lexicon of TextIndexNG3? It's part of the index implementation - and it is there by-design. -aj pgpx4vCUCQo5r.pgp Description: PGP signature ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plip : indexing files
--On 29. Januar 2007 13:23:18 +0100 [EMAIL PROTECTED] wrote: Hi, - we don't need all the TING mechanics in order to get the fulltext indexing : we only need the UnicodeLexicon as far as portal transforms send unicode results (tested in france ; you can imagine ;-) ) My two cents: TXNG is a working solution since years and working successfully since years in large installations. Any need to reinvent wheels (from scratch)? Andreas pgppVNZGlZ2O1.pgp Description: PGP signature ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
