Page MenuHomePhabricator

Split up the tech-mgt mailing lists to cover different use cases
Closed, ResolvedPublic

Description

Several people don't belong on tech-mgt in general but should see certain messages. Kevin and Joel and Victoria discussed solutions; Victoria selected on separate, overlapping mailing lists. Joel to implement.

possible approach: “Extended staff”, “Strategic staff” and “Leadership”

Event Timeline

Will there be some secret decoder ring to tell me which of the 3 to post which message to?

JAufrecht added a subscriber: ksmith.

@ksmith Do you have more details on the composition of the lists? I think that a public discussion of list definitions and names might be helpful even if exactly who is on which list might not be public.

Will there be some secret decoder ring to tell me which of the 3 to post which message to?

The one ring that rules them all… "soz for cross posting"

From my perspective, the most urgent need is for: Tech Programs. That's pretty easy: if you own (or co-own) a program (or, I would argue, a sub-program), you would be on the list. Plus presumably me, Joel, and Victoria. Not sure if any eng-admin folks would need to be on that one. There are a couple tech manager who would not be on that list by that criterion, so maybe it should be tech-mgt PLUS non-manager program owners. The "co-own" part would be to include our Product Managers, in cases where the eng lead is listed as the primary owner.

I'm not sure what an "extended"/"leadership" list would be used for. I believe there was at least one "sub-team" manager, but maybe they are already on tech-mgt. @JAufrecht : Maybe you could check with Victoria to see if she still feels an extended list would be necessary, if we already have tech-mgt and tech-program-owners. The original thought was something like managers + product managers.

Decided at tech-mgt meeting:
Create a new list named tech-hr@wikimedia.org, reserved exclusively HR-related information sent to people managers. The current tech-mgt@wikimedia.org list becomes inclusive, used for most communications, and joinable by anyone in Tech (or Audiences) that wants to know what’s going on.

Work breakdown:

  • Create new tech-hr (Google list, so ask techsupport@)
  • Expand current list (ask tech-mgt who should be on the list)?
  • Email to all of tech-all for self-invite/request