Closed Bug 501242 Opened 16 years ago Closed 16 years ago

Create new MozService-related mailing list

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mary, Assigned: fox2mike)

Details

Hi there: We need a new newsgroup related (i.e. marketing@lists.mozilla.org) for MozService to manage communications with partners and other supporters. Can we get: mozservice-friends@lists.mozilla.org? If there is a simple way to set this up, let me know and I'll do it! Thanks!
Maybe mozilla.marketing.mozservice ?
Assignee: server-ops → gerv
Group: infra
Component: Server Operations: Account Requests → Newsgroups
QA Contact: mrz → justdave
I'd really prefer the more simple and general one of mozservice-friends :)
Then maybe you just want a mailing list instead of a newsgroup, or do you want the power of a newsgroup, too?
Mary wants a mailing list instead. mozservice-friends@mozilla.org
Assignee: gerv → server-ops
Component: Newsgroups → Server Operations
QA Contact: justdave → mrz
Summary: Create new MozService-related news group → Create new MozService-related mailing list
Assignee: server-ops → shyam
Status: NEW → ASSIGNED
Mary, This is done, you should have an email with the list admin password and other details :)
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
We have a policy of making Mozilla discussion forums available as mailing lists, newsgroups and over the web to maximise participation. This does not create any additional complexity for list users or owners - and, in fact, reduces complexity because every list can be treated in the same way. Code, such as that which auto-generates the list of forums at http://www.mozilla.org/community/developer-forums.html, assumes that groups fit into this pattern. I seem to remember that in the past, when we've created mailing-list-only forum, we've had to shift them over to the normal pattern, causing additional hassle. Additionally, all groups are @lists.mozilla.org, not @mozilla.org. Having stuff @mozilla.org sends a different message about it. Lastly, was it so urgent that this had to be done in 5 hours while I was asleep? Frankly, I'm rather surprised at how this bug has developed. I would hope it's not too late to backtrack and go the standard route. If MozService is Mozilla Services Week, then I would suggest mozilla.community.mozservice. I presume we want to present it as a way of helping the community rather than a marketing exercise? :-) Gerv
Thank you, Shyam :)
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.