Skip to content
This repository was archived by the owner on Oct 14, 2020. It is now read-only.
This repository was archived by the owner on Oct 14, 2020. It is now read-only.

DECISIONS: Provide guidelines on how all Shield add-on studies should behave in general cases #252

@motin

Description

@motin

Moved here from mozilla/shield-studies-addon-template#68

From Krupa:

would it be possible to have general guidelines on how all SHIELD add-on studies behave when it comes to uninstall/remove actions by users?
i see a long email thread about what the expected behavior should be for jonathanKingston/http-dns#13

My thoughts:
The v4 Shield Utils API takes care of uninstalling the add-on if the user opts out of the study via an API method; however the study Krupa linked does not use the Shield Utils API, which explains the discrepancy. I agree that it would be:

  • good to have this documented somewhere, and possibly
  • require that all devs use the Shield Utils API for Shield studies.

Either way, we have been discussing whether or not to uninstall the add-on when the study ends, and those kinds of decisions and rationales should be documented somewhere. Establishing these guidelines may require some collaboration with UX, data, legal, etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions