1406425 - Properly deal with release data in the aggregator

Status: RESOLVED WONTFIX

(Data Platform and Tools :: General, enhancement, P4)

Description

[Chris H-C :chutten]

With bug 1406391 we'll be going from having some release channel users opting in to data sharing to 0% of release users opting in to data sharing.

We should have a plan for what to do about this before it happens (likely when 58 hits release in January).

I'm thinking we should aggregate some sample of opt-out data.

Comment 1

[Georg Fritzsche [:gfritzsche]]

The two main options i see are:
1) Having some kind of release/opt-out data show up.
   Is that a lot of effort? Do we have partial solutions for this already?
2) Not showing any data for release channels.
   Do we know if anyone relies on the release channel data right now?
   Maybe it is enough in the short-term to communicate that release data on TMO is going away.

Comment 2

[Frank Bertsch [:frank]]

I think we should focus on the latter. Sampling is hard because not everyone is reporting everything; and to get enough samples that we can say "yes, this is representative" for every metric would substantially increase the size of the aggregates job.

I'll send out an email to let everyone know. I think this is for the better anyways, because most people look at release data and assume it includes everyone, which is a major footgun.

Comment 3

[Chris H-C :chutten]

Just so long as we keep it in our minds that we're doing this because of technical reasons, not because we have anything against showing release data to the public. I can easily see this turning into lore that "we publish release data in public" within, say, 4 years.

Not sure how to do this, though.