There are sooooo many mailing lists that its hard to know where to subscribe and what to send where. Fixit.
lists.mozilla.org (public) mailing lists: firstname.lastname@example.org For everyone working on MDN-related projects email@example.com Mailing list for discussing MDN Services project firstname.lastname@example.org Discussion list for developer documentation on MDN. email@example.com Lista de correo del Mozilla Developer Center en español firstname.lastname@example.org discussion mailing list for Mozilla Developer Center Japanese (ja) email@example.com Lista de discussão sobre planejamento, autoria e tradução de documentação para desenvolvedores no Mozilla Developer Center em português. firstname.lastname@example.org MDN website development
other known lists: email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org internal list for mdn dev email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
Component: General → Collaboration
Here's what I know about some of these addresses: email@example.com Has occasional traffic firstname.lastname@example.org Unused since 2014; discussions about Japanese translation on MDN happen on https://groups.google.com/forum/#!forum/mozilla-translations-ja email@example.com Unused; full of spam firstname.lastname@example.org This was an alias used by the PHPbb forum software that was part of MDN prior to the Kuma migration; no longer used. email@example.com Publicly visible address for MDN users to reach "somebody in charge"; current members are me, Sheppy, and teoli firstname.lastname@example.org Alias for the list-administrator of the mdn-admins list email@example.com No idea what this is for, but the list admin is Stormy Peters, who is no longer at Mozilla firstname.lastname@example.org Alias for the list-administrator of the mdn-response list email@example.com People who attend Ali's weekly staff meeting (employees and contractors) firstname.lastname@example.org Alias that's used for the @MozDevNet Twitter account
Talked through how to even resolve this with the group in Madison. An acceptable resolution would be to set up clear staff anf non staff lists for both the dev and non-dev components of the mdn team. Proposal: mdn@list same dev-mdc@list same dev-mdc-staff formerly mdn-team dev-mdn same dev-mdn-staff formerly mdn-dev
CC'ing Ali since you're proposing to change the name of a list she recently created (mdn-team). I'm concerned that having prefix matching between the public and private lists will lead to autocompletion errors, where messages are sent to the wrong list accidentally. Consequences of such errors could range from unfortunate (if volunteers are excluded from discussions) to damaging to Mozilla (if confidential information is sent to public lists). BTW, dev-mdc is a name we wish we could get rid of, but there's too much history and inertia behind it to change it. I don't expect to see enthusiasm for propagating it into a private staff list name. If you want to disambiguate mdn-team, I suggest mdn-content-team or mdn-content-staff.
Yeah, I'm not comfortable with making internal, staff lists derivative of public lists, and certainly not making staff lists the go-to. I created the mdn-team one mostly for communications about internal meetings and goal-setting because it created noise and was a bit confusing for volunteers, but it really shouldn't be used for too much more.
I'm not sure what you mean about making staff lists the go-to. I don't mean to imply elevating the importance of one list or the other... rather I'd like to give consistency to the naming pattern. For example, I assumed (incorrectly) that mdn-team was the staff list version of the mdn@list before I went digging.
I don't think the payoff is worth the hassle of changing the mailing list names.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.