Places:Fx3FeaturePlan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 55: Line 55:


== Schedule ==
== Schedule ==
''Describe the rough schedule here, linking back to relevant product release milestones, as well as linking to any build/release notes.''
 
Only P1s are currently listed here.
 
{|border=1px solid black
|-
|Target Milestone
|Feature
|Notes
|-
|?
|Platform support for annotations
|
|-
|A4
|Places Bookmarks on by default
|Needs to be on by 3/31 - 4/6 in order to get a reasonable number of weeks of nightly testing before A4 code freeze.
|-
|?
|Platform support for sync
|
|-
|?
|Platform API for extensibility
|
|-
|?
|Unified Places Organizer
|
|-
|?
|UI Parity with Fx2
|
|-
|?
|Protection and safeguarding against data loss
|
|-
|?
|Bookmark date is never lost
|
|-
|?
|Backup and restore for all Places data
|
|-
|?
|Improve performance
|
|}


= Design & Implementation =
= Design & Implementation =

Revision as of 20:52, 19 March 2007

DRAFT **** DRAFT **** DRAFT **** DRAFT ****

Status

Feature tracking bug
  • bug 355737 - meta bug: re-implement all the existing bookmarks UI on top of the Places backend
  • bug 370099 - places-based bookmarks blockers

Overview

Describe the goals and objectives of the feature here.

Motivation

Describe the motivation behind the feature here.

Use Cases

Describe the primary use cases for the feature here.

Requirements

List functional and non-functional requirements for the feature here, with links back to any relevant product PRD. These requirements should be prioritized.

PLCS-001a Provide platform support to enable syncing of Places datamodel objects to a remote server P1 FR This is just an event model and not the network infrastructure/sync layer, just the platform hooks.
PLCS-001b Build a sync client on this new infrastructure P2 FR
PLCS-001c Provide platform support to support generic annotations P1 FR New area for extension authors to explore. We aren't going to be able to implement everything for Places ourselves.
PLCS-001d Ensure that Places includes a usable and robust API for extensibility P1 NFR
PLCS-002a Unified user interface that improves the usability and discoverability of features P1 NFR details
PLCS-002b Parity with Firefox 2 Bookmarks/History UI P1 FR
PLCS-002c Provide some UI that allows users to mark a URI as "interesting" P2 FR
PLCS-002d Provide some UI that allows users to annotate a URI with tags P2 FR
PLCS-002e Provide some UI that allows users to annotate a URI with free-form notes P3 FR
PLCS-003a Protection and safeguarding against data loss P1 FR
PLCS-003b Bookmark data is never lost between browsing sessions P1 NFR
PLCS-003c Provide backup and restore functionality for bookmarks P1 FR
PLCS-003d Make it easy for users to export their bookmarks for use in another application P2 FR
PLCS-004a Index web page content into a DB that can be queried P2 FR See Bug 342913
PLCS-004b Allows users to search on all available URI metadata P2 FR
PLCS-004c Support SQL queries of the bookmarks database in the Error Console P3 FR
PLCS-005a Improve performance (as measured by memory use, transactional speed and Ts) of bookmark and history storage and retrieval operations P1 NFR

Schedule

Only P1s are currently listed here.

Target Milestone Feature Notes
? Platform support for annotations
A4 Places Bookmarks on by default Needs to be on by 3/31 - 4/6 in order to get a reasonable number of weeks of nightly testing before A4 code freeze.
? Platform support for sync
? Platform API for extensibility
? Unified Places Organizer
? UI Parity with Fx2
? Protection and safeguarding against data loss
? Bookmark date is never lost
? Backup and restore for all Places data
? Improve performance

Design & Implementation

Documentation
Repository
Indicate where the code for the feature lives (in branch or as extension).

API Changes

list any API changes made by this feature.

Extensibility

list work done to make feature extensible by add-ons & any impact to extensibility of Firefox

Customization

list changes to preferences and customization controls for the feature

Performance

list effects on performance, tests used, metrics targeted

Reliability/Stability

list effects on reliability/stability, tests used, metrics targeted

Security

list security impact and link to results of security reviews

Privacy

list privacy impacts and any tie-ins to user privacy features

Global Audience

list l10n requirements and a11y efforts

Web Compatibility

list any known effects on compatibility with websites

Other

any other implementation or design related documentation

Discussion & Implications

Caveats / What We've Tried Before

links to previous design documents, discussions, etc.

References

links to external documents that could inform the design of the feature