M.-A. DARCHE wrote: > Jean-Luc Bonduel a �crit : > >> >> |/ Basically the problem is that we have too many identical roles. We / >> |/ should change: / >> |/ / >> |/ WorkspaceManager -> LocalManager (or something like that) / >> |/ WorkspaceMember -> Contributor/ >> |/ WorkspaceReader -> Reader / >> |/ SectionManager -> LocalManager / >> |/ SectionReviewer -> Reviewer / >> |/ SectionReader -> Reader/ >> >> For me, they must one more role. i will call it:* SectionContributor* >> > > Don't worry, we actually plan to have the Contributor role also > available in sections :-) But it will not be called SectionContributor. > It will simply be called Contributor. This role already exists in > CPS 3.3.3 and has been introduced because of CPSWiki. > > Florent's way of presenting things could not show the presence > of the Contributor role in sections. > > So using another presentation we will have: > > Roles available in workspaces: > * LocalManager (or something like that) > * Contributor > * Reader > > Roles available in sections: > * LocalManager (or something like that) > * Reviewer > * Contributor > * Reader > > > Thank you for your interest, >
Hi! Concerning the "local roles" form, is there any way of making it more user-oriented? by introducing the idea of 'permissions', since this is what users are eventually interested in, i.e. "what can I do in this folder?", "who can get access to the folder?", etc. For instance the current screen assumes that users already know what the 'role:anonymous' group mean, and that they know what it implies to be manager, member, reader, etc... in relation to the folder. Assigning the reader's role to the 'role:anonymous' group on a given folder, basically means: "everyone can read the documents in this folder" but it is such a complicated way of saying it... The same with roles blocking: it can take some time before users understand what blocking the acquisition of roles implies, if they are not acquainted with Zope already. I've done a mockup for a project, I have no idea if this is generic enough to be implemented for any roles and any folder, but here it is anyway: http://www.medic.chalmers.se/~jmo/CPS/folder_access.png /JM _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
