Hi all,
This is the start of regular ( weekly?) progress report for Sync.next
engineering and coordination. The goal is to provide more external visibility
into our development process. If this doesn't work for you, let me know what
does. These updates cover the last two weeks.
-chris
- Did failure analysis of existing Sync product to identify weaknesses of
previous approach and big wins going forward:
https://mobile.etherpad.mozilla.org/sync-failures
- Continuing to iterate, design, and prototype on Sync.next storage and data
protocols.
- https://wiki.mozilla.org/Identity/CryptoIdeas/06-Queue-Sync-CouchDB
(warner, ckarlof)
- Prototype implementation in Jetpack:
https://github.com/ckarlof/syncable-service-poc
- Note: Readme is outdated
- https://wiki.mozilla.org/User:Rnewman/TreeSync (rnewman)
- Revisited the idea of using Sync 2.0 as an object backing store
- Dev deployment at: http://web.sync2.profileinthecloud.net
- Developed PouchDB component for Firefox chrome code (vlad)
- https://github.com/vladikoff/pouchdb/tree/firefox_component
- This implements a local CouchDB interface over IndexedDB and provides a
client API for remote CouchDB instances
- Created new Sync wiki: https://wiki.mozilla.org/User_Services/Sync
- Migrated user stories to new wiki:
https://wiki.mozilla.org/User_Services/Sync/v1
- Developed a migration plan for current Sync users to Sync.next:
https://wiki.mozilla.org/User_Services/Sync/v1#Migration_strategy
- Requested "Elm" twig to be reset for Sync.next hacking
https://bugzilla.mozilla.org/show_bug.cgi?id=900212
Next week:
- Start prototyping TreeSync (rnewman)
- Integrate and evaluate Sync 2.0 server with QueueSync prototype (ckarlof)
- Re-review existing Desktop Sync codebase (ckarlof, lloyd)_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
