Closed Bug 1703307 Opened 1 year ago Closed 1 year ago

Include `app.update.background.enabled` in Telemetry Environment

Categories

(Toolkit :: Application Update, task)

task

Tracking

()

RESOLVED FIXED
90 Branch
Tracking Status
firefox90 --- fixed

People

(Reporter: nalexander, Assigned: bytesized)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

This is just like the existing app.update.auto setting, which requires special handling in the Telemetry Environment.

Assignee: nobody → ksteuber
Attachment #9215859 - Flags: data-review?(chutten)

Comment on attachment 9215859 [details]
background_update_data_review.md

DATA COLLECTION REVIEW RESPONSE:

Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes.

Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

If the request is for permanent data collection, is there someone who will monitor the data over time?

Yes, Kirk Steuber is responsible.

Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, Interaction.

Is the data collection request for default-on or default-off?

Default on for all channels.

Does the instrumentation include the addition of any new identifiers?

No.

Is the data collection covered by the existing Firefox privacy notice?

Yes.

Does there need to be a check-in in the future to determine whether to renew the data?

No. This collection is permanent.


Result: datareview+

Attachment #9215859 - Flags: data-review?(chutten) → data-review+
Pushed by ksteuber@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/eb40719c0827
Include `app.update.background.enabled` in Telemetry Environment r=chutten,nalexander
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in before you can comment on or make changes to this bug.