Platform/Features/Telemetry: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
m (clearing in prep for migration to new feature page format (will be done momentarily))
Line 1: Line 1:
{| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[Platform/Features/Telemetry|Telemetry]]
| {{StatusHealthy|status=Complete}}
| June 23
| Taras Glek
<section end="status" />
|-
|}


== Summary ==
Telemetry allows Engineering to receive aggregate data of browser health in the field.  Think cache hit rates, page load times across all browser instances or anything else we're interested in.
== Team ==
Who's working on this?
* '''Lead Developer''': Taras Glek
* '''Product Manager''': Chris Blizzard
* '''QA''': AndreiD
* '''UX''': Limi
* '''Security''': Curtis Koenig
* '''Services''': Unknown
* '''Metrics''': Daniel Einspanjer
* '''Privacy''': Asa Dotzler, [[User:Sidstamm|Sid Stamm]], Alex Fowler
Another person worth talking to is Graydon, who filed the original bug, and Sayer who has strong opinions on the matter.
== Release Requirements ==
Complete checklist of items that need to be satisfied before we can call this feature "done".
* Modify privacy policy(Asa)
* Add UI (Mike Hommey)
See https://bugzilla.mozilla.org/show_bug.cgi?id=659396 for ongoing telemetry enhancements.
== Next Steps ==
* Set up official server backend for receiving built-in telemetry.  Metrics team.  (May 6)
* Design & impl UI for opt-in. (limi & glandium)
* Land it with required privacy bits. (Asa)
* Move on to field trials. (A/B testing)
== Related Bugs & Dependencies ==
[https://bugzilla.mozilla.org/show_bug.cgi?id=585196 telemetry infrastructure]
[https://bugzilla.mozilla.org/show_bug.cgi?id=652656 privacy policy update]
[[Privacy/Reviews/Telemetry|Privacy Review]]
'''Need''': Services plan, deployment plan, early items to measure.
== Designs ==
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
== Goals/Use Cases ==
The goal for this feature is to give our developers the ability to know if changes they are making have wide-ranging positive and negative effects at scale.  Are users seeing better performance?
Another goal of this is to give us easy-to-use infrastructure to learn about the structure of the Internet as a whole.  That is, how do we tune our browser based on what the Internet and Web do?
== Non-Goals ==
This is not a system for gathering feedback from individual users.  It is a system for us to get aggregate health data about browsers in the field.  It's also a chance for us to run lightweight tests if we want to learn how certain settings will affect browser performance or user experience.  It is distinct from the Test Pilot program.
== Other Documentation ==
[http://codesearch.google.com/codesearch?q=UMA_histogram&vert=chromium Search List of macros used in Chrome]
[http://src.chromium.org/viewvc/chrome/trunk/src/base/metrics/ Metrics code in Chrome]
== Security ==
[https://wiki.mozilla.org/Security/Reviews/Firefox6/ReviewNotes/telemetry Security Discussion/Review]
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked, but not yet at risk of missing this release.
|-
| {{StatusAtRisk|status=&nbsp;}}
| At Risk: feature is at risk of missing this release.
|-
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}
__NOTOC__
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
[[Category:Features]]
[[Category:Firefox]]
[[Category:Performance]]
[[Category:Polish]]
[[Category:Priority 1]]
[[Category:Priority 2]]
[[Category:Priority 3]]
[[Category:Unprioritized]]

Revision as of 19:01, 11 July 2011