Subject: The mailing list for listmasters using Sympa
List archive
- From: address@concealed
- To: address@concealed
- Subject: A lessor listmaster
- Date: Tue, 6 May 2003 14:13:38 +0800
Hi,
We are going to deploy sympa in a company with several departments.
Each department demand several lists, and they are for various
purpose. A central small group of listmasters couldn't possibly
understand all their needs and decide if the reasons are qualified
on their own.
Opening the creat_list permission to the intranet would solve part
of the problem, but we're looking for a better solution. Some of
the departments still want to moderate their list creation, possibly
by someone(the chief maybe) inside the department.
Making the chief one of the listmasters is not feasible, because
there are many departments with many lists and their own read/write
permission, but a listmaster can always read/write anything. We
want to limit the chief's admin right to installing pending lists,
possibly removing closed lists, but no more. You might call it
``moderators/editors on list creation.''
Since the listmaster and server admin right part of sympa seems
not ``scenarilized'' yet, I guess we'll have to patch the code
a bit to achieve this. The question is, how should we do this
appropriatly, i.e. without writing too much code.
Any suggestion?
# pm5
-
A lessor listmaster,
pm5, 05/06/2003
-
Re: [sympa-users] A lessor listmaster,
Olivier Salaun - CRU, 05/06/2003
- Re: [sympa-users] A lessor listmaster, pm5, 05/06/2003
-
Re: [sympa-users] A lessor listmaster,
Olivier Salaun - CRU, 05/06/2003
Archive powered by MHonArc 2.6.19+.