[Zope-CMF] CMF Collector: Open Issues
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 Pending / Deferred Issues - Wrong cache association for FSObject, [Pending] http://www.zope.org/Collectors/CMF/255 - CMFSetup: Windows exports contain CR/LF, LF and even CR newlines, [Pending] http://www.zope.org/Collectors/CMF/266 - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Deferred] http://www.zope.org/Collectors/CMF/271 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - CMFSetup: Workflow Tool export fails with workflows which have scripts, [Pending] http://www.zope.org/Collectors/CMF/373 - CMFCore.Skinnable.SkinnableObjectManager can merge skin data, [Pending] http://www.zope.org/Collectors/CMF/375 - Proxy Roles does't work for a Script using portal_catalog.searchResults, [Pending] http://www.zope.org/Collectors/CMF/380 - WorkflowAction deprecated warning should not printed for WorkflowMethod, [Pending] http://www.zope.org/Collectors/CMF/388 - workflow notify success should be after reindex, [Pending] http://www.zope.org/Collectors/CMF/389 - Implicitly acquiring allow_discussion in isDiscussionAllowedFor, [Pending] http://www.zope.org/Collectors/CMF/398 - Legal chars not permitted in email addresses, [Pending] http://www.zope.org/Collectors/CMF/401 Pending / Deferred Features - Favorite.py: queries and anchors in remote_url, [Pending] http://www.zope.org/Collectors/CMF/26 - DefaultDublinCore should have Creator property, [Pending] http://www.zope.org/Collectors/CMF/61 - path criteria on Topic should honor VHM, [Pending] http://www.zope.org/Collectors/CMF/111 - Document.py: universal newlines, [Pending] http://www.zope.org/Collectors/CMF/174 - Add condition for transition's action like other action, [Pending] http://www.zope.org/Collectors/CMF/207 - Major action enhancement, [Pending] http://www.zope.org/Collectors/CMF/232 - portal_type is undefined in initialization code, [Pending] http://www.zope.org/Collectors/CMF/248 - CMFTopic Does Not Cache, [Deferred] http://www.zope.org/Collectors/CMF/295 - Wishlist: a flag that tags the selected action., [Pending] http://www.zope.org/Collectors/CMF/301 - CMFDefault should make use of allowCreate(), [Pending] http://www.zope.org/Collectors/CMF/340 - Nested Skins, [Deferred] http://www.zope.org/Collectors/CMF/377 - CatalogVariableProvider code + tests, [Pending] http://www.zope.org/Collectors/CMF/378 - manage_doCustomize() : minor additions, [Pending] http://www.zope.org/Collectors/CMF/382 - First Day of Week, [Pending] http://www.zope.org/Collectors/CMF/400 ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] RFC: PAS and the (non?) future of members
hi all, i'm wondering if it's not time to rethink the entire idea of members as they currently exist in CMF. members were originally a necessary evil, because the user folder implementation of users didn't allow for enough flexibility to support CMF's needs. now, however, PAS makes it possible to encapsulate all of the necessary behaviour in the user objects themselves, and it should be possible to eliminate the complexity of wrapping the user object altogether. over the last few days at the snow sprint here in austria i've been working on a Plone-based product called Membrane. Membrane implements PAS plugins which allow portal content to be used as the authentication, property, group, role, etc. providers for users. it's quite nice, i think, very flexible and powerful, and i think it contains ideas that might do well in CMF itself. even if the content-based plug-ins are not desireable, i think it's still worth investigating the use of PAS and the idea of deprecating the member/user duality altogether. anyone else interested in this approach? -r ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] RFC: PAS and the (non?) future of members
On 2 Feb 2006, at 15:35, Rob Miller wrote: even if the content-based plug-ins are not desireable, i think it's still worth investigating the use of PAS and the idea of deprecating the member/user duality altogether. anyone else interested in this approach? It does sound interesting, unless the user folder all of a sudden gets overloaded with all kinds of APIs that it doesn't need for normal Zope operation. jens ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] RFC: PAS and the (non?) future of members
Rob Miller wrote: i'm wondering if it's not time to rethink the entire idea of members as they currently exist in CMF. members were originally a necessary evil, because the user folder implementation of users didn't allow for enough flexibility to support CMF's needs. now, however, PAS makes it possible to encapsulate all of the necessary behaviour in the user objects themselves, and it should be possible to eliminate the complexity of wrapping the user object altogether. over the last few days at the snow sprint here in austria i've been working on a Plone-based product called Membrane. Membrane implements PAS plugins which allow portal content to be used as the authentication, property, group, role, etc. providers for users. it's quite nice, i think, very flexible and powerful, and i think it contains ideas that might do well in CMF itself. even if the content-based plug-ins are not desireable, i think it's still worth investigating the use of PAS and the idea of deprecating the member/user duality altogether. anyone else interested in this approach? The whole wrapped-Member thing is indeed quite nasty, and PAS should let us bypass it quite easily. I suspect a 1:1 replacement of members with users from a special PAS UserFactory plugin would be quite easy. And, like members, it would be specific to CMF. Hooray for plugins. PlonePAS doesn't do this (yet) since it aims to be minimally invasive. But I think Membrane would be even better, provided it works out well and doesn't turn out to be quite so strangely behaved as CMFMember; members-as-content seems a quite natural thing to do. --jcc -- Building Websites with Plone http://plonebook.packtpub.com/ Enfold Systems, LLC http://www.enfoldsystems.com ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: RFC: PAS and the (non?) future of members
On 2 Feb 2006, at 23:01, Rob Miller wrote: On Thu, 02 Feb 2006 18:14:15 +, Jens Vagelpohl wrote: On 2 Feb 2006, at 15:35, Rob Miller wrote: even if the content-based plug-ins are not desireable, i think it's still worth investigating the use of PAS and the idea of deprecating the member/user duality altogether. anyone else interested in this approach? It does sound interesting, unless the user folder all of a sudden gets overloaded with all kinds of APIs that it doesn't need for normal Zope operation. i don't understand what you mean by overloading the user folder w/ all kinds of APIs. i'm not proposing any additions to the user folder at all. i'm talking about a custom user class, along w/ custom user factory, authentication, and user property decoration plugins that move the behaviour that is currently in the member object down into the user object. no additional features, less complexity, more flexibility. I mean sticking Plone-only stuff onto something that's a simple user folder and should be completely agnostic of how it is used. jens ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: Re: RFC: PAS and the (non?) future of members
On Thu, 02 Feb 2006 23:33:49 +, Jens Vagelpohl wrote: On 2 Feb 2006, at 23:01, Rob Miller wrote: On Thu, 02 Feb 2006 18:14:15 +, Jens Vagelpohl wrote: It does sound interesting, unless the user folder all of a sudden gets overloaded with all kinds of APIs that it doesn't need for normal Zope operation. i don't understand what you mean by overloading the user folder w/ all kinds of APIs. i'm not proposing any additions to the user folder at all. i'm talking about a custom user class, along w/ custom user factory, authentication, and user property decoration plugins that move the behaviour that is currently in the member object down into the user object. no additional features, less complexity, more flexibility. I mean sticking Plone-only stuff onto something that's a simple user folder and should be completely agnostic of how it is used. oh, i see. did i imply that Plone-only behaviour should be dropped into the CMF? i'm not detecting some prejudice that might possibly be causing certain readers to jump to conclusions about my proposal, am i? ;-) of course i don't want to put Plone-specific code into the CMF. i'm talking about PAS (i.e. PluggableAuthService... see http://www.zope.org/Members/urbanape/PluggableAuthService) and a set of custom plug-ins that migrate the existing CMF member behaviour down into a standard Zope user folder implementation. nothing Plone-specific at all. Membrane, to which i referred, _is_ Plone-specific. but i'm not implying that it be used in the CMF, just that there are some good ideas being expressed there, that are worth considering in a CMF-only context. -r p.s. i've written a blog entry on Membrane (http://www.theploneblog.org/archive/2006/02/02/membrane-componentized); it's intended for Plone developers and is quite Plone-centric, but provides a high-level overview of the approach i'm talking about. ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: Re: RFC: PAS and the (non?) future of members
On 3 Feb 2006, at 00:31, Rob Miller wrote: I mean sticking Plone-only stuff onto something that's a simple user folder and should be completely agnostic of how it is used. oh, i see. did i imply that Plone-only behaviour should be dropped into the CMF? i'm not detecting some prejudice that might possibly be causing certain readers to jump to conclusions about my proposal, am i? ;-) Did I say CMF? No, I did not. I said PAS. Both Plone or CMF-specific stuff have no place in PAS, only in modules, which seems to be your goal, so that's good. jens ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: Re: Re: RFC: PAS and the (non?) future of members
On Fri, 03 Feb 2006 00:38:07 +, Jens Vagelpohl wrote: On 3 Feb 2006, at 00:31, Rob Miller wrote: I mean sticking Plone-only stuff onto something that's a simple user folder and should be completely agnostic of how it is used. oh, i see. did i imply that Plone-only behaviour should be dropped into the CMF? i'm not detecting some prejudice that might possibly be causing certain readers to jump to conclusions about my proposal, am i? ;-) Did I say CMF? No, I did not. I said PAS. whatever. i still don't think that justifies a back-handed insult when there was nothing in my proposal that implied that i wanted to move inappropriate behaviour anywhere into the stack. or maybe i should just be prepared for random snide comments to be the response to every future proposal, since i happen to have come from the Plone community? i greatly respect your opinions, and your design and coding skills. i would appreciate, however, that you respond to my proposals based on their content. if i have a dumb idea, fine, but there's no need to give me grief for bad ideas that i haven't even had. -r ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: Re: Re: RFC: PAS and the (non?) future of members
Rob Miller wrote: On Fri, 03 Feb 2006 00:38:07 +, Jens Vagelpohl wrote: On 3 Feb 2006, at 00:31, Rob Miller wrote: I mean sticking Plone-only stuff onto something that's a simple user folder and should be completely agnostic of how it is used. oh, i see. did i imply that Plone-only behaviour should be dropped into the CMF? i'm not detecting some prejudice that might possibly be causing certain readers to jump to conclusions about my proposal, am i? ;-) Did I say CMF? No, I did not. I said PAS. whatever. i still don't think that justifies a back-handed insult when there was nothing in my proposal that implied that i wanted to move rob, we German native speakers are used to word our opinions much more directly that Americans. I believe for a German speaker there is not a trace of insult in what jens expressed. just trying to bridge a cultural gap robert ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
