[89] in Moira
Re: moira and discuss
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Sat Apr 28 17:49:58 1990
Date: Sat, 28 Apr 90 17:49:31 -0400
From: Ken Raeburn <Raeburn@MIT.Edu>
To: marc@ATHENA.MIT.EDU
Cc: jfc@ATHENA.MIT.EDU, mar@ATHENA.MIT.EDU, moiradev@ATHENA.MIT.EDU,
I'm not familiar with moira, but how hard would it be to be able to
tag an entry with an arbitrary string, or even an arbitrary list of
tags and strings. That way, I could take a mailing list, and tag each
one with the ordered pair (discuss-acl,aorsw), except the chairman,
who would get tagged with (discuss-acl,acdorsw). This is coming
directly from my fingers now, so don't expect something perfect. This
way, the discuss server update could build the correct acl, and leave
it somewhere for the meeting's admin to copy in. If you trust moira,
you can just have it copied in automatically via crontab.
Not flexible enough. I make a policy of not giving myself delete access
to meetings I chair except when I do want to delete transactions, and
then only temporarily. Other people prefer it otherwise.
Although it would mean more work, the way that sounds best to me is to
deal in lists of pairs of strings. This amounts to basically the same
format for an acl as discuss uses, only more flexible because non-users
would be permitted. Also, you might need to generalize on "Kerberos
principal", if the current code doesn't deal with such things as
"raeburn.*@ATHENA.MIT.EDU" and "*@*".
While we're on a related subject, it would be nice if meetings could
be pointed at by hesiod pointers. It's just a Better Way of Doing It
(tm).
Only if it is carefully done in such a way as to have the necessary
information always available to sites without Hesiod. This would mean
keeping two systems in sync.
I do have some thoughts on changing the naming/accessing scheme to
handle something like this, but I haven't had any time lately to develop
them.
