Re: [Framework-Team] changing name of plone.app.event?
Andreas Jung wrote: -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. On the other hand it provides to Plone what CMFCalendar provides to CMF - I think at least. Personally, I have no particular preference. And never ever ask or listen to a German when it comes to naming things in English ;-) Raphael 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 ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] changing name of plone.app.event?
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
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- attachment: lists.vcf___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
