You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
For any intrusive maintenance please send a notification to email@example.com as this will also reach interested parties outside the SRE org.
Please use firstname.lastname@example.org for team-wide communications, plus the subteam ones for subteam-specific communication. Looking at ops-private's archive, it seems like its uses can be replaced by sre@ for the most part, and thus and unless there are objections, we will be filing a task for its closure. Given subscription to these groups is limited by design to the team members, the intention is for these to be used seldomly for async private communications ("agenda for our meeting next week", "OKRs due N/N", "follow up from our meeting the other day", "out sick", etc.) and not for siloing teams into their own spaces. More public mediums like Phabricator are more appropriate for anything that anyone else that could be helpful or interesting to folks across SRE, Tech, the org or the community.
All teams in SRE have a dedicated Google Group, with a working email address. This means the following can be used for emails, calendar invites, Google Docs permissions etc.
- email@example.com - all engineers, managers and directors in SRE
- firstname.lastname@example.org - managers and directors in SRE.
- email@example.com - Infrastructure Foundations
- firstname.lastname@example.org - Observability
- email@example.com - Datacenter Operations
- firstname.lastname@example.org - Service Operations
- email@example.com - Traffic
- firstname.lastname@example.org - Data Persistence
Problems that we are trying to solve:
- There is no easy way (without enumerating every team member) for someone in a subteam to address their peers, for a manager to address their subteam, or folks from another team to email or Cc a subteam.
- Similarly, there is no easy way to invite a team into e.g. a recurring calendar invite and make sure that it will be kept consistent as team members come and go. We see that e.g. with the introduction of new team members and recurring team meetings. Sometimes these are even maintained by outside of SRE, e.g. Linh's invites for team meetings with the CTO.
- ops-private@ is a legacy name from years ago when this team was called TechOps. "Operations" is gradually taking on a different meaning across the org: business operations, i.e. the COO's department. ops-private@ is another place to maintain membership, with membership criteria not even being well defined or consistently applied. Another way to phrase this is that we lack a source of truth :)
- ops@ (aka ops-l) suffers from a lot of these problems as well, but with 130+ members it's a beast of its own, so keeping it out of scope for now.
- Open question to the group, especially those of you outside of SRE: do we need another group that is the union of SRE + folks with an SRE title across Tech? sreish, sre-wmf, sre-at-large, sre-wide are suggestions.
PS: Adapted from an an e-mail by Faidon Liambotis to ops-private and sre on 2020-05-15 Subject: [sre] Google Groups & mailing lists changes for SRE