The accessibility instantiator telemetry (A11Y_INSTANTIATORS) expires in Firefox 61. It's important for us to have ongoing data about accessibility client usage in order to best focus our investments and track how changes impact usage.
Hi Francois. Am I supposed to get review on the actual patch from you as well as the form? The documentation doesn't explicitly say so: > ◾ Add a file to the bug that contains the measurement code to be landed in Firefox > ◾ Flag a data steward peer for review with r? on the file that contains your completed form However, getting review from a data peer for the patch would seem to make sense.
Comment on attachment 8976427 [details] Bug 1462238: Extend/clarify expiry of accessibility instantiator/consumers telemetry. data-review=francois https://reviewboard.mozilla.org/r/244574/#review250622
Attachment #8976427 - Flags: review?(mzehe) → review+
Comment on attachment 8976428 [details] Request for data collection review form. 1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate? Yes, in Histograms.json and Scalars.yaml. 2) Is there a control mechanism that allows the user to turn the data collection on and off? Yes, telemetry setting. 3) If the request is for permanent data collection, is there someone who will monitor the data over time?** Yes, James Teh. 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. 5) Is the data collection request for default-on or default-off? Default on, all channels. 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? No, permanent.
Attachment #8976428 - Flags: review?(francois) → review+
(In reply to James Teh [:Jamie] from comment #4) > However, getting review from a data peer for the patch would seem to make > sense. I usually take a look at the same time to see if anything is missing from Histograms.json or Scalars.yaml, but you're welcome to explicitly flag me as a second reviewer too. The one thing to note is that you also need a first reviewer to look at the actual code which adds the telemetry probes (in the case where you're not just renewing an existing one). Data stewards only review the documentation, it's the first reviewer's job to make sure that the code matches the documentation.
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/cb4152d2175e Extend/clarify expiry of accessibility instantiator/consumers telemetry. r=MarcoZ data-review=francois
You need to log in before you can comment on or make changes to this bug.