Page MenuHomePhabricator

Make quarterly and yearly Phabricator statistics / metrics emails have a second recipient
Closed, ResolvedPublic

Description

Followup to T337387, T337388. Because single humans of failure aren't good.

In the scripts in the puppet repo we now have your personal email address (as sender and/or recipient) in multiple places. How about this: We move it to a single location at the start of the puppet class.. and use a variable in all other places.. you get a mailman list .. we replace your personal address with the list address in that one central puppet location.. later you just follow-up with "add people to the list".

Thanks for the thoughts! Thing is that I don't expect all those (currently five) automated emails to be interesting for the very same audience but rather different individuals (co-)handling different automated emails. So if I understand correctly, that's probably not the best solution when it comes to signal vs noise ratio in people's inboxes. :-/

For the time being, I'd propose to stick with the current format in the file modules/profile/manifests/phabricator/main.pp in the repository operations/puppet and add additional recipients per automated email. (Not sure what the proper array syntax is, though.)

Event Timeline

Change 929714 had a related patch set uploaded (by Aklapper; author: Aklapper):

[operations/puppet@production] phabricator: Add second recipient for quarterly/yearly metrics emails

https://gerrit.wikimedia.org/r/929714

Change 929714 merged by Dzahn:

[operations/puppet@production] phabricator: Add second recipient for quarterly/yearly metrics emails

https://gerrit.wikimedia.org/r/929714

Is this a duplicate of T334628 or different?

I think this task obsoletes T334628.

Change 929714 merged by Dzahn:

[operations/puppet@production] phabricator: Add second recipient for quarterly/yearly metrics emails

https://gerrit.wikimedia.org/r/929714

Heads-up to @Maryann-Onyinye: Hi, from now on you should automatically receive the Phabricator data for the "Technical Community Newsletter" (next one in T334115) via email, on the first day of a quarter, because T337387 is resolved and T338955 has been merged. This obsoletes the "manual" subtask T334121.

Yes. Thanks a lot!