Closed
Bug 1390269
Opened 7 years ago
Closed 7 years ago
Convert TOUCH_ENABLED_DEVICE to opt-out
Categories
(Toolkit :: Telemetry, enhancement, P1)
Tracking
()
RESOLVED
FIXED
mozilla57
Tracking | Status | |
---|---|---|
firefox57 | --- | fixed |
People
(Reporter: jimm, Assigned: jimm)
References
Details
Attachments
(1 file, 1 obsolete file)
3.16 KB,
patch
|
jimm
:
review+
|
Details | Diff | Splinter Review |
Asa would like info about touch screen device support out on the release channel. This probe is currently opt-in and as such doesn't provide this data.
Assignee | ||
Comment 1•7 years ago
|
||
Data privacy wise I don't see this as an issue, we're just querying device info here, no different from say, cpu speed or screen dims.
Attachment #8897109 -
Flags: review?(gfritzsche)
Comment 2•7 years ago
|
||
Comment on attachment 8897109 [details] [diff] [review] patch Review of attachment 8897109 [details] [diff] [review]: ----------------------------------------------------------------- This looks fine to me technically. This still needs data review from a peer listed here: https://wiki.mozilla.org/Firefox/Data_Collection
Attachment #8897109 -
Flags: review?(gfritzsche) → review+
Assignee | ||
Comment 3•7 years ago
|
||
Comment on attachment 8897109 [details] [diff] [review] patch Requesting data review from rweiss
Attachment #8897109 -
Flags: review?(rweiss)
Comment 4•7 years ago
|
||
Comment on attachment 8897109 [details] [diff] [review] patch Review of attachment 8897109 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/components/telemetry/Histograms.json @@ +8163,5 @@ > + "expires_in_version": "never", > + "kind": "boolean", > + "releaseChannelCollection": "opt-out", > + "bug_numbers": [795307, 1390269], > + "alert_emails": ["jimm@mozilla.com"], I missed this before: you can now remove TOUCH_ENABLED_DEVICE from histogram-whitelists.json.
Comment 5•7 years ago
|
||
:jimm can you please provide answers to the questions in this doc: https://docs.google.com/document/d/1SSn5w8DfCSkHWJS8DNTd7ya82diWRxaDUFM5aL4UDDo/edit#heading=h.tdmbb3rtr1gg
Flags: needinfo?(jmathies)
Assignee | ||
Comment 6•7 years ago
|
||
(In reply to Rebecca Weiss from comment #5) > :jimm can you please provide answers to the questions in this doc: > > https://docs.google.com/document/d/ > 1SSn5w8DfCSkHWJS8DNTd7ya82diWRxaDUFM5aL4UDDo/edit#heading=h.tdmbb3rtr1gg https://docs.google.com/document/d/1K4zTgM127KTA-Ty14KnKSS19KsGSXL3t5UNohmuo7Qk/edit# Sure!
Flags: needinfo?(jmathies) → needinfo?(rweiss)
Comment 7•7 years ago
|
||
Comment on attachment 8897109 [details] [diff] [review] patch Review of attachment 8897109 [details] [diff] [review]: ----------------------------------------------------------------- Review is tentatively approved because this appears to be low risk, but please provide a person responsible WRT question (3) below. 1) Is there documentation that describes the schema for the ultimate data set available publicly, complete and accurate? (see here, here, and here for examples) Yes, the request is for a boolean Telemetry probe, which means that the standard Telemetry documentation applies here. 2) Is there a control mechanism that allows the user to turn the data collection on and off? (Note, for data collection not needed for security purposes, Mozilla provides such a control mechanism) Yes, standard opt-out for Telemetry applies. 3) If the request is for permanent data collection, is there someone who will monitor the data over time? The request is for permanent data collection, so a responsible individual needs to be named. 4) Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under? This appears to be a Type 1 data collection (determines whether the device is touch enabled, not whether they are using Touch). 5) Is the data collection default-on or default-off? Default-on. 6) Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)? No new identifiers. 7) Is the data collection covered by the existing Firefox privacy notice? If unsure: escalate to legal. Yes. 8) Does there need to be a check-in in the future to determine whether to renew the data? Current request is for permanent data collection, so no.
Attachment #8897109 -
Flags: review?(rweiss) → review+
Updated•7 years ago
|
Flags: needinfo?(rweiss)
Assignee | ||
Comment 8•7 years ago
|
||
thanks!
Attachment #8897109 -
Attachment is obsolete: true
Attachment #8903801 -
Flags: review+
Assignee | ||
Updated•7 years ago
|
Keywords: checkin-needed
Assignee | ||
Updated•7 years ago
|
Priority: P2 → P1
Pushed by mozilla@noorenberghe.ca: https://hg.mozilla.org/integration/mozilla-inbound/rev/53a7f7b59fbd Convert TOUCH_ENABLED_DEVICE to an opt-out probe. r=gfritzsche, data=rweiss
Keywords: checkin-needed
Comment 10•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/53a7f7b59fbd
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox57:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
You need to log in
before you can comment on or make changes to this bug.
Description
•