Firefox/SHIELD: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 68: Line 68:


== History ==
== History ==
* June 2014 - mconner files [https://bugzilla.mozilla.org/show_bug.cgi?id=1031506 a tracker bug] for enhancing FHR to proactively detect and solve problems for users.
* '''June 2014''' - mconner files [https://bugzilla.mozilla.org/show_bug.cgi?id=1031506 a tracker bug] for enhancing FHR to proactively detect and solve problems for users.
* December 2014 - bsmedberg files [https://bugzilla.mozilla.org/show_bug.cgi?id=1111016 bug 1111016] for implementing the smallest-possible set of changes necessary to support [https://support.mozilla.org/en-US/kb/rate-your-firefox-experience-heartbeat Heartbeat] (a prompt shown to users asking them to rate Firefox) and Self-Repair (a minimal version of the problem-solving functionality, described in detail in dependent bugs).
* '''December 2014''' - bsmedberg files [https://bugzilla.mozilla.org/show_bug.cgi?id=1111016 bug 1111016] for implementing the smallest-possible set of changes necessary to support [https://support.mozilla.org/en-US/kb/rate-your-firefox-experience-heartbeat Heartbeat] (a prompt shown to users asking them to rate Firefox) and Self-Repair (a minimal version of the problem-solving functionality, described in detail in dependent bugs).
* Early 2015
* '''Early 2015'''
** UITour is enhanced to support Heartbeat prompts, sending user responses to input.mozilla.org.
** UITour is enhanced to support Heartbeat prompts, sending user responses to input.mozilla.org.
** Self-Repair is implemented as a set of static files hosted on AWS that Firefox retrieves.
** Self-Repair is implemented as a set of static files hosted on AWS that Firefox retrieves.
* Late 2015 - Self Repair is renamed to Shield since the project covers more than just repairing Firefox. The name covers the server that deploys configuration files (recipes) and the in-product component that executes the recipe.  
* '''Late 2015''' - Self Repair is renamed to SHIELD since the project covers more than just repairing Firefox. The name covers the server that deploys configuration files (recipes) and the in-product component that executes the recipe.  
** Example 1: The Shield server deploys a recipe to a client indicating that the user should be included in the daily Heartbeat sample. The in-product component responds by offering the Heartbeat prompt.
** Example 1: The Shield server deploys a recipe to a client indicating that the user should be included in the daily Heartbeat sample. The in-product component responds by offering the Heartbeat prompt.
** Example 2:  The Shield server matches a “preference repair recipe” to the user configuration, and returns it.  Firefox runs the recipe steps to fix the broken preference.
** Example 2:  The SHIELD server matches a “preference repair recipe” to the user configuration, and returns it.  Firefox runs the recipe steps to fix the broken preference.
* February 2016 - Work begins on the SHIELD backend service, [https://github.com/mozilla/normandy Normandy]. Work on the system add-on begins as well.
* '''February 2016''' - Development begins on the SHIELD backend service, [https://github.com/mozilla/normandy Normandy]. Work on the system add-on begins as well.
* April 2016 - Normandy replaces the self-repair server at the domain [https://self-repair.mozilla.org self-repair.mozilla.org]. Development on the system add-on continues.
* '''April 2016''' - Normandy replaces the self-repair server at the domain [https://self-repair.mozilla.org self-repair.mozilla.org]. Development on the system add-on continues.
Confirmed users
950

edits

Navigation menu