Privacy/Reviews/Test Pilot in Thunderbird
Contents
Document Overview
| Feature/Product: | Test Pilot in Thunderbird |
| Projected Feature Freeze Date: | (tbd) |
| Product Champions: | Rafael Ebron, Mark Banner |
| Privacy Champions: | Sid Stamm |
| Security Contact: | tbd |
| Document State: | [NEW] |
Timeline:
| Architectural Overview: | (date TBD) |
| Recommendation Meeting: | (date TBD) |
| Wrap-up Meeting: | (if necessary) |
Architecture
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described.
The main objective of this feature/product is: The goal of Test Pilot in Thunderbird is to launch Test Pilot studies to learn how users use Thunderbird to make improvements to the products. For example, we would like to launch studies such as the Menu and Toolbar and usage study to learn what menu items and buttons users use the most to improve the UI of the product. Another study is a "Day in the Life of a Thunderbird User" to learn about usage patterns. These studies will help us make improvements to Thunderbird and tell us where to focus.
Design Documents: Link to any design or architectural documents here.
Components
Describe any major components in the system and how they interact. Also include any third-party APIs (those Mozilla does not control) and what type of data is sent or received via those APIs.
Component X
This component does A, B and C and interacts with component Y to do D.
The tables below simply summarize the data encountered by this component.
Stored Data:
| What | Where |
|---|---|
| data type | where stored |
Communication with Component Y
| Direction | Message | Data | Notes |
|---|---|---|---|
| In: | message 1 | types of data received from component Y with the message | |
| Out: | message 2 | types of data sent to component Y with the message |
User Data Risk Minimization
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.
Alignment with Privacy Operating Principles
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.
See Also: Privacy/Roadmap_2011#Operating_Principles:
Principle: Transparency / No Surprises
(How the feature addresses this)
Recommendations: (what can be improved)
Principle: Real Choice
Recommendations:
Principle: Sensible Defaults
Recommendations:
Principle: Limited Data
Recommendations:
Follow-up Tasks and tracking
| What | Who | Bug | Details |
|---|---|---|---|
| [NEW] Initial Overview Discussion | ? | Meeting time TBD |
