At 03:14 PM 10/15/01 -0400, Barry A. Warsaw wrote: >Make it so list moderators can set or unset the per-user moderate > bit (right now only list admins can do that).
Generically, there's a lot of things that should be done with list moderators... Really, I think we need to redesign large chunks of the admin page, and set up multiple access classes. Off the top of my head, I think we need a siteadmin, listmaster, listowner, and list moderator category; siteadmin is the current possessor of the master and can do everything. listmasters can create and delete lists (and potentially get junior siteadmin privs.) listowners can monkey with most, but not all of the settings. For instance, I thnk listowners should be allowed to make their archives private or not. But not be allowed to change whether or not they have archives; that's a site decision. And list moderators should be able to do not only approvals, but be able to get to all the subscribe/unsubscribe things. Perhaps more generically, we need to make a list of all the things people are allowed to do, and set up a user class page, where you can flip the bit for any individual class, so a site admin could let list owners turn on and off archives if he wanted, but the default config might not let them. With a true userdb this could just be applied to a particular person; granting them privileges. Until then, we could just define N categories, and some sane defaults... _______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
