ACM mailing lists
From JhuAcmWiki
rolroltrocd
Contents |
Mailman
We use the Mailman package to serve our mailing lists. We have mailing lists for other clubs, but we also have some for ACM use. Here's where we document which mailing list to use when.
When people sign in to meetings
On signing in to an ACM meeting, you get subscribed to acm@acm.jhu.edu and announce@acm.jhu.edu. We send you an email explaining:
We will send event announcements to announce@acm. Recent subject lines include "Google meeting on Nov 3" and "Centaur had a short outage due to power failure; problem fixed". This is an announcements-only mailing list, so you'll only get emails from officers on it. We send out meeting announcements once a week plus any other critical announcements, usually not more than one or two a month.
You can chat with other ACMers on our general discussion list, acm@acm.jhu.edu. Recent subject lines include "My power supply is dead" and "I hate using email; clay tablets were much better"." Anyone on the acm@acm list is free to post to it.
If you're an alumnus, it might make sense to unsubscribe from announce@ and stay on acm@. If you're a current student not looking for a lot of email traffic but you want to hear about ACM's upcoming events, it might make sense to unsubscribe from acm@ but stay on announce. We'd rather you stay on both, of course!
acm@
General discussion. "I broke my leg last night" or "My computer melts when I insert a rubber chicken into the DVD-RW drive".
acm-users@
Not actually a Mailman list, it's a manually updated list of all the centaur accounts.
members@
The list of all the members. (How is this different from acm-users?)
announce@
Announcements of club meetings, other events, and important server news. Try to bother these people fairly little ;-).
officers@
Current and past officers. Policy discussions, I guess. It's a private list with private archives.
admins@
When you need to contact an ACM admin, but you don't know who, email this list. It's all of us.
Maybe it should be phased-out and replaced by our BugTracker, though.
