Closed Bug 1528078 Opened 9 months ago Closed 6 months ago
Add telemetry for get
User Media/get Display Media/enumerate Devices secure vs insecure vs legacy
Comment on attachment 9061937 [details] Bug-1528078-data-collection-review.md This was a duplicate post, obsoleting.
Attachment #9061937 - Attachment is obsolete: true
Comment on attachment 9061936 [details] Bug-1528078-data-collection-review.md Sharing the load with Tim.
Attachment #9061936 - Flags: data-review?(chutten) → data-review?(tdsmith)
Comment on attachment 9061936 [details] Bug-1528078-data-collection-review.md data-review+; thank you! -- 1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate? Yes, in UseCounters.conf. 2) Is there a control mechanism that allows the user to turn the data collection on and off? Yes, the Firefox telemetry opt-out. 3) If the request is for permanent data collection, is there someone who will monitor the data over time?** Yes, Jan-Ivar Bruaroey. 4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under? Category 1, technical data. 5) Is the data collection request for 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. 7) Is the data collection covered by the existing Firefox privacy notice? Yes. 8) Does there need to be a check-in in the future to determine whether to renew the data? (Yes/No) No, this is a permanent collection. 9) Does the data collection use a third-party collection tool? No.
Attachment #9061936 - Flags: data-review?(tdsmith) → data-review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/25bc2e11f12f Adding WebRTC device access and deprecated interface telemetry r=jib,smaug
You need to log in before you can comment on or make changes to this bug.