[87] in Moira
Re: moira and discuss
daemon@ATHENA.MIT.EDU (John F Carr)
Fri Apr 27 09:48:41 1990
Date: Fri, 27 Apr 90 09:47:56 -0400 (EDT)
From: John F Carr <jfc@ATHENA.MIT.EDU>
To: Mark Rosenstein <mar@MIT.EDU>
Cc: moiradev@MIT.EDU, discuss@MIT.EDU
In-Reply-To: <9004260034.AA00382@Toto.MIT.EDU>
To be fully general, a discuss meeting update would use 7 lists (1 for
each of a, c, d, o, r, s, w access). You could get away with fewer by
making assumptions about what combinations of permissions are useful
(for example, have read,write, and reply lists, with any other access
types being stored on the discuss server in a well known filename).
The interface I would like is to have a discuss meeting acl be an
ordered list of 3 to 7 (1 per type of access; the number would be a
global constant) lists, strings, or users in moira. A flag to indicate
world access (world-read, -write, -reply, etc. ) would be useful.
A discuss update could simply leave the acl files (which are text) in a
file somewhere for a human to inspect and install. I too would prefer
not to require that moira have chairman access to all updated discuss
meetings. A discuss acl looks like:
acdorsw:jfc@ATHENA.MIT.EDU
a rs :random@ATHENA.MIT.EDU
s :???@ATHENA.MIT.EDU
There are uses for this. Consulting has a large number of discuss
meetings which should be updated from lists. The sysdev meeting acl
should be the same as the sysdev mailing list. I run a discuss meeting
that I want updated from lists.
