Ticket #608 (closed enhancement: fixed)

Opened 13 years ago

Last modified 13 years ago

Create a moderator role

Reported by: jukka Owned by: jukka
Priority: critical Milestone: 0.7 Búri
Component: generic Version:
Keywords: Cc:
Time planned: 1h Time remaining: 0h
Time spent: 1.0h

Description

(Story #541, #) Create a new security role 'moderator' and modify workflows so that moderators, managers and authors are allowed to delete objects. Deletion is implemented in other ticket.

Change History

comment:1 Changed 13 years ago by hans

Hi, stop it!!!

#541 is not enough to create moderator role. There are still too many open questions:

  • how can user become a moderator?
  • how to take away moderators's rights if he uses his rights too much?
  • ...

I'm thinking that we need at least two levels: moderator and co-moderator...

comment:2 Changed 13 years ago by hans

Have a look how it works for groups: #512

Moderator can:

  • change members to co-moderators
  • change co-moderators to members

Manager must create moderators.

I see the following scenario:

In case of lemill.net Tarmo is a manager and he will make me, Teemu and other active users from our team moderators. If there are active users whom we know and trust, then we will give them co-moderator role. In some rare cases we will ask Tarmo to change some co-moderator to a moderator.

comment:3 Changed 13 years ago by jukka

This ticket just creates the moderator role in technical sense, everything in #512 kind of requires this to exist. This doesn't yet create any way in LeMill interface to actually assign moderators; these are (for now) created solely in Zope management screens.

Ok, I'll try to explain the current security model so we are on the same page: From Zope's point of view there are after this (these role names are not visible outside):

  • Managers, who can do anything
  • Members, who can do what allowed for Members in that place
  • Owners, who can do almost anything
  • Moderators, who can do something in between managers and members. Basic Plone has Reviewers who are quite similar in-betweeners as what we're trying to achieve.

The clever bit is that Owner role. When you create something, you're Owner of it and everything inside it. Because when creating a group leads to member creating a GroupFolder? object she becomes automatically Owner of it with and can do Owner-stuff to all inside that group. This suggests mapping like this:

  • Owner of the group = Moderator (In LeMill sense)
  • Moderators set by owner = Co-Moderators (In LeMill sense)

Similarly if some (manager) sets somebody to moderator in lower levels of LeMill's hierarchy, he becomes a moderator everywhere above it. I think that manager is the role for main moderators of LeMill site, and the co-moderators are the moderator-roles given by managers. Because these roles can be given in certain levels of object hierarchy, it is possible to have many managers in LeMill without capability to go down to Zope root and mess things badly. So:

  • Managers inside LeMill instance = Moderators (In LeMill sense)
  • Moderators inside LeMill instance = Co-Moderators (In LeMill sense)

Currently Tarmo is manager of the whole Zope instance and others of us developers are probably managers too, but inside LeMill instance. Moderators are the next step, but I don't see why we'll need co-moderators as a real role.

comment:4 Changed 13 years ago by vahur

I agree with Jukka - I think we don't need co-moderators. And I don't like the word eighter.

comment:5 Changed 13 years ago by jukka

  • Owner changed from anonymous to jukka
  • Status changed from new to assigned

comment:6 Changed 13 years ago by jukka

  • Status changed from assigned to closed
  • Time spent set to 1.0h
  • Resolution set to fixed
  • Time remaining set to 0h

(In [591]) Closed #608, spent 1h. Moderators (reviewer role in plone's inner workings) are now allowed to delete/restore stuff. There is no way to make moderators yet outside ZMI.

Note: See TracTickets for help on using tickets.