Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

For #3700 - Add Setting to Delete Data on "Quit" menu action #5098

Merged
merged 1 commit into from Sep 11, 2019

Conversation

ekager
Copy link
Contributor

@ekager ekager commented Sep 4, 2019

Pull Request checklist

  • Quality: This PR builds and passes detekt/ktlint checks (A pre-push hook is recommended)
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
  • Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features
    Screenshot_20190910-171217
    Screenshot_20190910-171221
    Screenshot_20190910-171237

@ekager ekager force-pushed the 3700-clear-data branch 6 times, most recently from 60988e7 to f7653f3 Compare September 5, 2019 21:13
@codecov-io
Copy link

codecov-io commented Sep 5, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@999d3cb). Click here to learn what that means.
The diff coverage is 31.53%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #5098   +/-   ##
=========================================
  Coverage          ?   11.72%           
  Complexity        ?      242           
=========================================
  Files             ?      246           
  Lines             ?    10145           
  Branches          ?     1496           
=========================================
  Hits              ?     1189           
  Misses            ?     8882           
  Partials          ?       74
Impacted Files Coverage Δ Complexity Δ
...va/org/mozilla/fenix/components/metrics/Metrics.kt 22.28% <ø> (ø) 0 <0> (?)
...fenix/settings/DeleteBrowsingDataOnQuitFragment.kt 0% <0%> (ø) 0 <0> (?)
...a/org/mozilla/fenix/browser/BaseBrowserFragment.kt 0% <0%> (ø) 0 <0> (?)
...lla/fenix/components/toolbar/DefaultToolbarMenu.kt 0% <0%> (ø) 0 <0> (?)
...ava/org/mozilla/fenix/settings/SettingsFragment.kt 0% <0%> (ø) 0 <0> (?)
.../mozilla/fenix/settings/SharedPreferenceUpdater.kt 0% <0%> (ø) 0 <0> (?)
...rg/mozilla/fenix/components/toolbar/ToolbarMenu.kt 94.44% <100%> (ø) 0 <0> (?)
...pp/src/main/java/org/mozilla/fenix/FeatureFlags.kt 90% <100%> (ø) 2 <0> (?)
...nix/components/toolbar/BrowserToolbarController.kt 92% <100%> (ø) 0 <0> (?)
...lla/fenix/settings/DeleteBrowsingDataController.kt 79.31% <71.42%> (ø) 0 <0> (?)
... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 999d3cb...0cf128b. Read the comment docs.

@ekager ekager force-pushed the 3700-clear-data branch 2 times, most recently from 07bb475 to f3504aa Compare September 9, 2019 20:39
@ekager
Copy link
Contributor Author

ekager commented Sep 9, 2019

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

  1. What questions will you answer with this data?
  • How often users tap "quit" from the browser toolbar menu
  1. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?
  • To measure how often users interact with the quit button in Fenix to measure feature success and visibility.
  1. What alternative methods did you consider to answer these questions? Why were they not sufficient?
  • N/A (These are baseline metrics)
  1. Can current instrumentation answer these questions?
  • Currently there are no events to track this button
  1. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the found on the Mozilla wiki.
  • All data is Category 2.
  1. How long will this data be collected?

Until 03/01/2020

  1. What populations will you measure?
  • All release, beta, and nightly users with telemetry enabled.
  1. Please provide a general description of how you will analyze this data.
  • Glean / Amplitude
  1. Where do you intend to share the results of your analysis?
  • Only on Glean, Amplitude and with mobile teams.

@ekager ekager requested a review from boek September 9, 2019 20:45
@ekager ekager marked this pull request as ready for review September 9, 2019 20:45
@ekager ekager requested review from a team as code owners September 9, 2019 20:45
@ekager
Copy link
Contributor Author

ekager commented Sep 9, 2019

Tagging @boek for data review and @colintheshots for the feature since it was similar to granular data options and I ended up using your categories and had to modify some of the functions to work with mine

@@ -252,7 +252,7 @@ sealed class Event {
enum class Item {
SETTINGS, LIBRARY, HELP, DESKTOP_VIEW_ON, DESKTOP_VIEW_OFF, FIND_IN_PAGE, NEW_TAB,
NEW_PRIVATE_TAB, SHARE, REPORT_SITE_ISSUE, BACK, FORWARD, RELOAD, STOP, OPEN_IN_FENIX,
SAVE_TO_COLLECTION, ADD_TO_HOMESCREEN
SAVE_TO_COLLECTION, ADD_TO_HOMESCREEN, QUIT
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@boek how do new events get into the metrics.md file? Do you have to change more files, or does the documentation automatically get added when you just add an event?

Should these be updated in the metrics.md file as part of the PR? At a quick glance I also didn't see save_to_collection or add_to_homescreen, so I'm wondering if I'm looking in the wrong place.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to manually add this to metrics.md for now. At least until the Glean auto-generate documentation PR is merged

@ekager

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added to metrics.md and metrics.yaml!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated, @boek does this mean open_in_fenix, save_to_collection, and add_to_homescreen did not get data review, or need to be updated?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@liuche that is correct
https://github.com/mozilla-mobile/fenix/pull/2131/files
and #4925 didn't get data reviews. In the short term I could put myself as a codeowner of metrics.kt until we get a better process

@ekager ekager force-pushed the 3700-clear-data branch 4 times, most recently from 2776901 to 70895b1 Compare September 11, 2019 18:45
@@ -78,7 +78,7 @@ events:
description: >
A string containing the name of the item the user tapped. These items include:
Settings, Library, Help, Desktop Site toggle on/off, Find in Page, New Tab,
Private Tab, Share, Report Site Issue, Back/Forward button, Reload Button
Private Tab, Share, Report Site Issue, Back/Forward button, Reload Button, Quit
bugs:
- 1024
data_reviews:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add a link to this PR for this data review?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just did!

@boek
Copy link
Contributor

boek commented Sep 11, 2019

  1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, updating existing probes w/ documentation

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

Yes, Fenix data controls

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

Fenix PM Vesta will monitor, and this has an expiry

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

Type 2

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

Default on

  1. 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

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

Yes

  1. Does there need to be a check-in in the future to determine whether to renew the data? (Yes/No) (If yes, set a todo reminder or file a bug if appropriate)**

Has expiry, 3/2020

  1. Does the data collection use a third-party collection tool? If yes, escalate to legal.

No

Copy link
Contributor

@boek boek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Data review

@boek boek removed the needs:data-review PR is awaiting a data review label Sep 11, 2019
Copy link
Contributor

@boek boek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one comment/question! 🚢

@ekager ekager merged commit e3209dc into mozilla-mobile:master Sep 11, 2019
@ekager ekager deleted the 3700-clear-data branch September 11, 2019 23:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants