Collect fonts installed on Android devices in Nightly
Categories
(Core :: Layout: Text and Fonts, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox122 | --- | fixed |
People
(Reporter: tjr, Assigned: tjr)
References
Details
Attachments
(2 files)
3.66 KB,
text/plain
|
chutten
:
data-review+
|
Details |
59 bytes,
text/x-github-pull-request
|
Details | Review |
Because we are not succeeding in obtaining the number of submissions we want from volunteers to build a default font list on Android, we are considering collecting this data via Telemetry from the Nightly population.
We are filing this bug to put in a data review request to start the conversation about whether or not this is something we could do.
Assignee | ||
Comment 1•7 months ago
|
||
Comment 2•7 months ago
|
||
Comment on attachment 9357664 [details]
data-review.md
PRELIMINARY NOTES:
You may find it more comfortable next time to submit the data review request around the time you submit the implementation for code review. Then you can use the glean_parser data-review command to help generate the data review request form for you.
Be sure to remember to code your channel-specific collection code at point of instrumentation. Otherwise, refile a request for all-channel collection.
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 can be controlled through the product's preferences.
If the request is for permanent data collection, is there someone who will monitor the data over time?
No. This collection will expire within two months of landing.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, Technical.
Is the data collection request for default-on or default-off?
Default on for pre-release channels only.
Does the instrumentation include the addition of any new identifiers?
No.
Is the data collection covered by the existing Firefox privacy notice?
Yes.
Does the data collection use a third-party collection tool?
No.
Result: datareview+
Comment 3•7 months ago
|
||
Comment 4•6 months ago
|
||
(chutten is on PTO, so asking other data reviewers)
royang/travis, since we are changing the data sensitivity for technical constraints (our data blob only fits within a Text metric, will this need a new data review request?
Comment 5•6 months ago
|
||
The reason text metrics have this requirement is simply because they have a high potential to include sensitive information. In this case, I think that you are probably still just technical or interaction level, so I don't see a need to re-review this. One thing you might do is go to the Glean Dictionary and find this metric and you can add an "annotation" to it that explains this.
Comment 6•6 months ago
|
||
Agreed, take a look at this change I noted the actual data sensitivity category as a comment.
Comment 7•6 months ago
|
||
Thank you both for you feedback! I'll give the annotation a shot because I've never done that before, so I'm curious to try it out.
Comment 8•6 months ago
|
||
Authored by https://github.com/tomrittervg
https://github.com/mozilla-mobile/firefox-android/commit/3eb1972a4f61ceece755ea2454634c4456618894
[main] Bug 1858193: Add a OneTimeWorkRequest to collect Telemetry for Installed Fonts
Authored by https://github.com/tomrittervg
https://github.com/mozilla-mobile/firefox-android/commit/a592499f363af0f9c5c32050c579a55188959fe7
[main] Bug 1858193: Add a test for parsing font files
Updated•6 months ago
|
Description
•