Platform/Features/Telemetry
| Feature | Status | ETA | Owner |
| Telemetry | Scoping | Unknown | Taras Glek |
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: Unknown
- UX: Unknown
- Security: Unknown
- Services: Unknown
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".
Next Steps
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.
Related Bugs & Dependencies
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 high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
Non-Goals
Things we are specifically not doing or building as part of this feature.
Other Documentation
Can include things like:
- Competitive landscape
- Research & references
- Whatever else is useful to the project.
Legend (remove if you like)
| Healthy: feature is progressing as expected. | |
| Blocked: feature is currently blocked, but not yet at risk of missing this release. | |
| 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. |
Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.