MM3 WUI :: Memberships Management
Hiya,
I've had a search through the Wiki, and can't see an answer to this, and don't recall anything in the archive/can't get the right search terms.
I'm wondering if with MM3, admins will be able to delegate the various aspects of admin-tasks to owners/other users -- e.g., I want to be able to allow person X to just be able to add/remove users from a given list; I want to allow person Y to be able to change archiving policies for list B.
Is that something that's in the pipeline, already?
If not, could it be? (my python really is quite terrible.)
-- ``What lawyers call intellectual property is no more than theft from the public domain.'' (Andy Mueller-Maguhn)
Adam McGreggor writes:
I'm wondering if with MM3, admins will be able to delegate the various aspects of admin-tasks to owners/other users -- e.g., I want to be able to allow person X to just be able to add/remove users from a given list; I want to allow person Y to be able to change archiving policies for list B.
Is that something that's in the pipeline, already?
If not, could it be? (my python really is quite terrible.)
You seem to know what you want. So why don't you write a spec, maybe design and even mockup screenshots? This is really important.
One of the things I really hate about Zope 2 is the complexity of the delegation mechanism (the "security" tab in the ZMI). Let's please avoid that!
On Fri, Apr 02, 2010 at 11:17:18AM +0900, Stephen J. Turnbull wrote:
You seem to know what you want. So why don't you write a spec, maybe design and even mockup screenshots? This is really important.
Inspired by http://wiki.list.org/display/DEV/Web+UI+Mockups, here's my annotated mock-up screen-shot:
<http://www.flickr.com/photos/adamamyl/4484703864/>
(I think my photostream's been marked as safe, again. Damned Burning Man/Nowhere[1] photos.)
As for a spec, I think the loosely written comments, might explain it, rather than me going through it wholly. That said, I'm more than happy to elaborate/clarify.
I think the idea is:
"I trust these people to admin that feature, so let them only do
that (on this list: although the idea of having *global*
permissions may be useful, in some cases, or indeed, the notion of
grouping lists together (by domain, or site-administratively), and
allowing these permissions for all lists within that group)".
Design isn't my strong point, either ;)
One of the things I really hate about Zope 2 is the complexity of the delegation mechanism (the "security" tab in the ZMI). Let's please avoid that!
I've not used the ZMI for about 3 years.
[1] http://www.goingnowhere.org
``Bernard: It's another of those irregular verbs. I hold confidential briefings, you leak, he's been charged under section 2A of the Official Secrets Act. ''
Adam McGreggor writes:
Inspired by http://wiki.list.org/display/DEV/Web+UI+Mockups, here's my annotated mock-up screen-shot:
<http://www.flickr.com/photos/adamamyl/4484703864/>
Looks good as a rough cut. What I worry about is that there are a lot of options, and maybe a lot of classes that site owners or even list owners might want to differentiate. The notes on the diagram will be helpful there, I think.
(I think my photostream's been marked as safe, again. Damned Burning Man/Nowhere[1] photos.)
heh heh heh.
participants (2)
-
Adam McGreggor
-
Stephen J. Turnbull