Ship Email Quality Report MVP

[katia-sentry]

I finally got numbers from the Sentry side of things, they see click through rates of the weekly quality report in the .25-.5% range, which is not great with industry average being much higher usually (at least 3% and a "good" rate being more like 20% based on some google sleuthing). I'm not sure it makes a lot of sense for us to do this given that data and us inherently having even less data to put into a weekly report that might be helpful.
Source: https://redash.getsentry.net/queries/6534?p_Invoice%20Channel=%5B%22Self-Serve%22%2C%22Touch%22%2C%22Partner%22%2C%22Other%22%5D&p_org_edition=%5B%22Team%22%2C%22Business%22%5D

[Adal3n3]

8/14 Meeting note with @aj-codecov:

• Business Goal: What is the business objective of sending a weekly summary email?
• Target Audience: We know that IC developers care only about changes they made at the commit and PR level, which they currently receive through Codecov PR comments. Why should we send them an email? Will they read it or create noise? What actionable information do they need from a weekly summary?
• Recipients: Who will receive this email?
• Problem Statement: What problem are we trying to solve with this email?
• Next Step: @aj-codecov will follow up with Sarah to understand the success metrics, feedback, and customer engagement related to Sentry’s weekly email.

[katia-sentry]

We've deprioritized this work for Q3'24