Hi,
Did you all see this? I was CCed and it didn't hit the list. ..... I
think it has some clever ideas.
Mark
---- snagged snip comes below. ----
> >For the purposes of this research, we are making a distinction among the
> >following roles: list owner, list monitor and list moderator.
With our program, we decided to break up the responsibilites and came up
with the
following different security roles:
* server admin: has rights to all lists on the server, can do anything
using the web interface or email commands. Doesn't receive any mail
from
any list. Receives software update notifications from us.
* site admin: has rights over all the lists in their "site" (ie: a
grouping
of lists), similar responsibilities as a server admin. Can change
virtual site settings (such as hostname, look & feel, etc).
* list admin: can add/delete members, moderate, change FAQs, action
phrases, autoresponders & change all list settings. Has no rights to
anything but their own list.
Members can also have any of the following extra rights, which are single
yes/no parameters:
* moderator: receives moderated message notifications, and can approve
them
* owner: receives mail sent to the owner-listname@... address
* error mail receiver: has opted to receive notifications of error mail
that Lyris has processed
* announcer: can send messages to the list, no matter what the
moderation
settings are
* poster: is allowed to send contributions when a list is set to reject
non-posters (for example, a magazine with an author pool might use
this)
This works pretty well for us. However, we do get a lot of requests for a
more limited list admin role, where the server administrator could remove
specific functions from the list admin's menu. Usually, the server
administrator fears that the admin is a danger to themselves, and will
tinker
with the wrong things, thus screwing up their own list (mucking with the
open/closed/private/password security setting, for instance)
> To take this one step further, I'm not even happy with the term, "LIST." The
> LIST term is one that is getting old, IMHO, but should get dropped in the
> next round of changes.
Agreed. Several years ago, when we used to sell InfoMagnet (a windows
front
end to L.) we called them "Email Discussion Groups". However, the term
"Discussion Groups" has now been coopted by the Newsgroup folks (that's
what
DejaNews calls them). And besides, "Discussion Groups" doesn't do justice
to
announcement lists and moderated-edit lists, which in many cases is what
people are more familiar with.
Nowadays, we simply call them "email lists" and say that there are several
kinds of "email lists", such as "owner-controlled announcement lists",
"moderated discussions", "moderated user-contributed announcements", and
"open
discussions". Recently, a new type has become popular, which we call
"DocBots", as in "Document Robots". Surveys, document repositories, and
other
"email databases" fall into this general category, where there is an
active
relationship between the user and the list server.
PS: I sent this message to the list several days ago, but it never was
distributed. If Majordomo suddenly decides to distribute my week-old
post,
my apologies for sending two -err- now three copies.
John
jbuckman@shelby.com
http://www.shelby.com
Developers of *an other* Email List Server
end mudged snip ----
|
|
