CloudServices/Sync/FxSync/Releases/0.3/PRD

From MozillaWiki
< CloudServices‎ | Sync‎ | FxSync‎ | Releases‎ | 0.3
Jump to: navigation, search


Please do not edit these pages without permission of the Mozilla Labs Weave project team. Your feedback and comments are welcomed on the discussion page.

Milestones

Milestone Date Description
M1 9/17/08 done 0.3m1 - Analysis & Prototyping of new Weave server & API
M2 9/30/08 0.3m2 - Alpha version of new Weave server
M3 11/26/08 0.3m3 - Weave client extension on Fennec
M4 TBD 0.3m4 - Weave client extension backported to desktop
A1 TBD 0.3a1 - Weave on Fennec - alpha 1
A2 TBD 0.3a2 - Weave on Fennec - alpha 2
B1 TBD 0.3b1 - Weave on Fennec - beta 1
B2 TBD 0.3b2 - Weave on Fennec - beta 2

Weekly Status & Open Issues

Note: Milestone targets are included in this document for initial planning purposes, authoritative landing targets will continue to be held per individual bug, and the latest tracking status for each feature area will be listed below.

Release Content

Content described here indicate planned features for this release of Project Weave. Feature status will be updated based on progress.

Weave 0.3 Features
User Experience

Users will continue their desktop sessions on the go by logging into their Weave accounts from Fennec. All saved bookmarks, cookies, and login information becomes available on the mobile browser.
User Experience Bugzilla Entries

Feature Id & Priority

Status

Description

Links

UE-001

[P1]

NS

Registration: User can choose to setup a Weave account to backup and synchronize their data. The task flow will be similar to the desktop but will be simpler given device limitations; select login, password, email, and encryption passphrase.

Bug Entries

UE-002

[P1]

NS

Login/Status: Login status will be displayed in a location consistent with Fennec UE guidelines(e.g. upper-right of Fennec title bar). Users will login (if not already) into their account and can choose to be remembered. Once logged in, user's login status will be displayed.

Bug Entries

UE-003

[P1]

NS

Accessing User Data: Bookmarks and history will be integrated into Fennec awesome bar/drop down with appropriate notations (e.g. star for bookmark). When users type in a few letters in the awesome bar a list of all matched URL's including sync'ed bookmarks are displayed. Tabs will appear in the Fennec tab list. Users can continue their desktop session by selecting the appropriate tab. Fennec's scrollable tab list will display thumbnails that the user can select using Fennec's navigation gestures. Note: Fennec team will determine the optimal user experience for these features.

Bug Entries

UE-004

[P1]

NS

Manage Preferences: Fennec preferences will provide users access and editing of Weave specific preferences. At a minimum, this will include account preferences (e.g. passwords, connection, sync frequency, last sync status) and data preferences (e.g. data types sync'ed).

Bug Entries

UE-005

[P2]

NS

Desktop Weave Client: Supporting Fennec with a new client extension also implies changes to the current desktop Weave client. In particular, the desktop client must now display the selected data sets for synchronization to be consistent with the mobile client. TBD: Support for remote wipe and data cleanup should the phone be lost by owner. See SEC001 below.

Bug Entries

Sharing and Sync

User data will be synchronized in both directions between desktop and Fennec. No sharing is offered in this release.

Feature Id & Priority

Status

Description

Links

SHR-001

[P1]

NS

Data Types: Rank ordered by priority, Places, Tabs, Passwords, and Forms data will be synchronized with the server and accessible from desktop and Fennec. Cookies will be supported time permitting but is currently not in scope. User can modify their preference to select which subset should be synchronized to the server. To prevent user confusion, the data set preference settings are also synchronized i.e. the sync'ed data sets are the same on the desktop and device. Modifying the settings on desktop will reflect on the device and vice-versa.

Sample Links

SHR-002

[P2]

NS

Sync Options: User may modify sync frequency, handling conflicts (e.g. desktop wins, device wins) and an option to sync immediately. These options will be available in preferences.

Sample Links

Security and Privacy

Users must login to their Weave accounts to continue their session and access user data. It is likely that most users will experience Weave initially through Fennec rather than the desktop. Thus users will be allowed to register and set up an account (messaged appropriately).

Feature Id & Priority

Status

Description

Links

SEC-001

[P2]

NS

Client extension of Weave on Fennec needs to protect the user's credentials since there is a distinct possibility of the phone being misplaced. Instead of requiring the user to enter a password each time they use Fennec (to continue their session) as this would be onerous, we will design a method allowing the user to lock-out and delete data on their mobile client if phone is lost/stolen. The exact method is TBD.

Sample Links

Performance

Sample overview

Feature Id

Status

Description

Links

PER-001

Status here

Sample description

Sample Links

Infrastructure

Sample description

Feature Id & Priority

Status

Description

Links

INF-001

[P1]

NS

Add GUID's to all data types when instantiated and stored on server

Sample Links

INF-002

[P1]

NS

Encrypt individual items (e.g. a bookmark) when communicating with server

Sample Links

INF-003

[P1]

NS

Refactor Weave desktop client to support Fennec features, and use new API.

Sample Links

Server Components

Summary description of features

Feature Id & Priority

Status

Description

Links

SVR-001

[P1]

NS

Robust Weave server with RESTful API that can support large volumes of clients (Fennec and desktop).

Sample Links

Key Dependencies

  • Weave server need to evolve to support a more robust API for client access. Revised server implementation is necessary before client extensions for Fennec and desktop can begin.
  • Fennec browser build (a working alpha) is necessary to test out integration.

Scoping & Resources

TBD-Dan

Document History

Version 0.1 --nkishore 19:07, 19 August 2008 (UTC)