Personal tools

Browse wiki

From MozillaWiki

Jump to: navigation, search
Platform/Features/Telemetry
Feature accessibility lead `  +
Feature accessibility notes `
Feature accessibility review `
Feature accessibility status `  +
Feature additional members Daniel Einspanjer (metrics), Graydon Hoare, Rob Sayre  +
Feature dependencies `
Feature engineering notes `
Feature engineering status `  +
Feature engineering team Automation and Tools  +
Feature feature manager Taras Glek  +
Feature functional spec `
Feature health OK  +
Feature implementation notes * [https://bugzilla.mozilla.org/show_bug.cgi?id=585196 telemetry infrastructure] * [https://bugzilla.mozilla.org/show_bug.cgi?id=652656 privacy policy update] '''Need''': Services plan, deployment plan, early items to measure.
Feature implementation plan `
Feature landing criteria `
Feature lead engineer Taras Glek  +
Feature list Platform  +
Feature localization lead `  +
Feature localization notes `
Feature localization review `
Feature localization status `  +
Feature name Telemetry  +
Feature non-goals This is not a system for gathering feedbacThis 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.t is distinct from the Test Pilot program.
Feature open issues and risks `
Feature operations lead `  +
Feature operations notes `
Feature operations review ` +
Feature operations status `  +
Feature overview Telemetry allows Engineering to receive agTelemetry 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. 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?ser based on what the Internet and Web do?
Feature priority P1  +
Feature privacy lead Sid Stamm, Asa Dotzler  +
Feature privacy notes `
Feature privacy review * [[Privacy/Reviews/Telemetry|Privacy Review]]
Feature privacy status `  +
Feature product manager Chris Blizzard  +
Feature product marketing lead `  +
Feature product marketing notes `
Feature product marketing status `  +
Feature products notes `
Feature products status `  +
Feature project `  +
Feature qa lead AndreiD  +
Feature qa notes `
Feature qa review `
Feature qa status Signed off for release  +
Feature rank 999  +
Feature requirements * Modify privacy policy(Asa) * Add UI (Mike Hommey) See https://bugzilla.mozilla.org/show_bug.cgi?id=659396 for ongoing telemetry enhancements.
Feature roadmap Platform  +
Feature secondary roadmap `  +
Feature security health OK  +
Feature security lead Curtis Koenig  +
Feature security notes [[Security/Reviews/Firefox6/ReviewNotes/telemetry|Notes]]
Feature security review * [https://wiki.mozilla.org/Security/Reviews/Firefox6/ReviewNotes/telemetry Security Discussion/Review]
Feature security status sec-review-complete  +
Feature stage Landed  +
Feature status `  +
Feature status note Deployed, see [http://arewesnappyyet.com arewesnappyyet.com]
Feature theme `  +
Feature users and use cases `
Feature ux design `
Feature ux lead Alex Limi  +
Feature ux notes `
Feature ux status `  +
Feature version Firefox 7  +
Categories Feature Page  +
Modification dateThis property is a special property in this wiki. 23 July 2012 21:18:16  +
hide properties that link here 
  No properties link to this page.
 

 

Enter the name of the page to start browsing from.