Privacy/Features/Site-based data management UI: Difference between revisions
| Line 31: | Line 31: | ||
== Release Requirements == | == Release Requirements == | ||
Complete checklist of items that need to be satisfied before we can call this feature "done". | Complete checklist of items that need to be satisfied before we can call this feature "done". | ||
* {{new|user study?}} | |||
* {{new|design UX}} | |||
* {{new|document data sources and mappings to UX}} | |||
* {{new|security / privacy design discussion}} | |||
* {{new|write patch}} | |||
* {{new|test plan and tests}} | |||
== Next Steps == | == Next Steps == | ||
Revision as of 16:53, 20 April 2011
| Feature | Status | ETA | Owner |
| Site-based data management UI | on track | Q4 2011 | Sid Stamm |
Summary
It's helpful to be able to control what sites know and do on a site-by-site basis. Ideally, the site permissions dialog, cookie controls, and various other site-based preferences should be accessible via a single UI.
This feature will provide a UI in a content tab (much like the addons manager) that allows users to customize permissions and settings for sites on a site-by-site basis.
Team
Who's working on this?
- Lead Developer: Margaret Leibovic
- Product Manager:
- QA:
- UX: Jennifer Boriss
- Security:
- Privacy: Sid Stamm
Release Requirements
Complete checklist of items that need to be satisfied before we can call this feature "done".
- [NEW] user study?
- [NEW] design UX
- [NEW] document data sources and mappings to UX
- [NEW] security / privacy design discussion
- [NEW] write patch
- [NEW] test plan and tests
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
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
- There's a prototype patch in for site-specific privacy preferences in bug 573176
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
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.