Status
| Telemetry | |
| Stage | Landed |
| Status | ` |
| Release target | Firefox 7 |
| Health | OK |
| Status note | Deployed, see arewesnappyyet.com |
{{#set:Feature name=Telemetry
|Feature stage=Landed |Feature status=` |Feature version=Firefox 7 |Feature health=OK |Feature status note=Deployed, see arewesnappyyet.com }}
Team
| Product manager | Chris Blizzard |
| Directly Responsible Individual | Taras Glek |
| Lead engineer | Taras Glek |
| Security lead | Curtis Koenig |
| Privacy lead | Sid Stamm, Asa Dotzler |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | AndreiD |
| UX lead | Alex Limi |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | Daniel Einspanjer (metrics), Graydon Hoare, Rob Sayre |
{{#set:Feature product manager=Chris Blizzard
|Feature feature manager=Taras Glek |Feature lead engineer=Taras Glek |Feature security lead=Curtis Koenig |Feature privacy lead=Sid Stamm, Asa Dotzler |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=AndreiD |Feature ux lead=Alex Limi |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=Daniel Einspanjer (metrics), Graydon Hoare, Rob Sayre }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
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.
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?
2. Users & use cases
`
3. Dependencies
`
4. Requirements
- Modify privacy policy(Asa)
- Add UI (Mike Hommey)
See https://bugzilla.mozilla.org/show_bug.cgi?id=659396 for ongoing telemetry enhancements.
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.
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
Privacy review
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
Need: Services plan, deployment plan, early items to measure.
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=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.
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? |Feature users and use cases=` |Feature dependencies=` |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 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. |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=* Security Discussion/Review |Feature privacy review=* Privacy Review |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* telemetry infrastructure
Need: Services plan, deployment plan, early items to measure. |Feature landing criteria=` }}
Feature details
| Priority | P1 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Platform |
| Secondary roadmap | ` |
| Feature list | Platform |
| Project | ` |
| Engineering team | Automation and Tools |
{{#set:Feature priority=P1
|Feature rank=999 |Feature theme=` |Feature roadmap=Platform |Feature secondary roadmap=` |Feature list=Platform |Feature project=` |Feature engineering team=Automation and Tools }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | sec-review-complete | Notes |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | Signed off for release | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-complete |Feature security health=OK |Feature security notes=Notes |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=Signed off for release |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}