Closed
Bug 643486
Opened 14 years ago
Closed 14 years ago
Creation of mozilla.reps.council discussion group (note special info in comment #1 and #2)
Categories
(mozilla.org :: Discussion Forums, task)
mozilla.org
Discussion Forums
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pierros, Assigned: jlaz)
Details
In order to accommodate the operations of ReMo Council we would like to have a mailing list/discussion group under the handle :
reps-council@ists.mozilla.org
Also, just for reference although the archives will be public, we will restrict the membership only to members of the council. But that is something that should be done by the list administrator, right?
List administrator should be me (pierros@mozilla.com) and William Quiviger (william@mozilla.com)
Comment 1•14 years ago
|
||
This would be mozilla.reps.council, and therefore reps-council@lists.mozilla.org.
But I'm not certain you can restrict the group posting privileges in the way you want.
justdave: is it possible to have one of our standard groups which has the following properties:
- Whitelist of permitted posters
- all other mail bounced
?
If the archives are public in news and GG, there's no point in stopping people _joining_ the list and receiving the messages via email. But we want people who try and post to get a polite message explaining that this is not possible.
Gerv
Comment 2•14 years ago
|
||
yes, that can be done. See announce@lists.mozilla.org for example setup.
Comment 3•14 years ago
|
||
OK, great. Lets go ahead with mozilla.reps.council, then.
Gerv
Summary: Creation of Mozilla Reps Council mailing list → Creation of mozilla.reps.council discussion group (note special info in comment #1 and #2)
Assignee | ||
Comment 4•14 years ago
|
||
List and newsgroup created, Google group should be set up shortly. I'll mimic the settings on announce@
Assignee: gerv → jlazaro
Assignee | ||
Comment 5•14 years ago
|
||
reps-council should now mimic the settings of announce@
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•