User:Mconnor/BIDSync(s): Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 65: Line 65:
* Hook key storage into BrowserID key wrapping/unwrapping
* Hook key storage into BrowserID key wrapping/unwrapping
* Implement support for revised UX based on BrowserID login/account creation/migration from existing Sync credentials.
* Implement support for revised UX based on BrowserID login/account creation/migration from existing Sync credentials.
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 83: Line 85:
* Define and document app-neutral data format for Apps metadata (shared with Android/HTML5 implementations)
* Define and document app-neutral data format for Apps metadata (shared with Android/HTML5 implementations)
* Write a Sync engine for Apps using the shared data format  
* Write a Sync engine for Apps using the shared data format  
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 99: Line 103:
* Hook key storage into BrowserID key wrapping/unwrapping
* Hook key storage into BrowserID key wrapping/unwrapping
* Implement support for revised UX based on BrowserID login/account creation/migration from existing Sync credentials.
* Implement support for revised UX based on BrowserID login/account creation/migration from existing Sync credentials.
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 118: Line 124:
* Create an Android content provider for access to Apps local store
* Create an Android content provider for access to Apps local store
* Write a Sync repository for Apps using the shared data format and the content provider
* Write a Sync repository for Apps using the shared data format and the content provider
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 133: Line 141:


<<not defined yet>>
<<not defined yet>>
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 152: Line 162:
* Provide an API for BrowserID consumers to have a key bundle wrapped/unwrapped using a master key
* Provide an API for BrowserID consumers to have a key bundle wrapped/unwrapped using a master key
* Store master key with BrowserID provider
* Store master key with BrowserID provider
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 168: Line 180:
==== Requirements ====
==== Requirements ====
* Provide a file that represents an entry point into a Sagrada system. Can be static.
* Provide a file that represents an entry point into a Sagrada system. Can be static.
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 184: Line 198:
* Implement HA, scalable server with entrypoint for each service
* Implement HA, scalable server with entrypoint for each service
* Do node-assignment to large-scale installations to distribute users across the instance
* Do node-assignment to large-scale installations to distribute users across the instance
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 201: Line 217:
* Document and implement changes to 2.0 API (almost all unused feature removal)
* Document and implement changes to 2.0 API (almost all unused feature removal)
* Take the clean-room opportunity to fix some long-standing database problems
* Take the clean-room opportunity to fix some long-standing database problems
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 217: Line 235:
* Process incoming logging data along entire pipeline to final storage location(s)
* Process incoming logging data along entire pipeline to final storage location(s)
* Some initial graph interpretations of incoming data
* Some initial graph interpretations of incoming data
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 231: Line 251:
==== Requirements ====
==== Requirements ====
* Abstract out the code that turns a Sagrada token into a userid and some additional metadata into a library that all Sagrada services can use.
* Abstract out the code that turns a Sagrada token into a userid and some additional metadata into a library that all Sagrada services can use.
==== Target Timeline ====


==== Risks ====
==== Risks ====
Line 246: Line 268:
* Operational deployment of v2.0 webheads, talking to a Replicated MySQL cluster with backups
* Operational deployment of v2.0 webheads, talking to a Replicated MySQL cluster with backups
* Durability of data is a requirement. HA requirement is similar to sync.
* Durability of data is a requirement. HA requirement is similar to sync.
==== Target Timeline ====


==== Risks ====
==== Risks ====
Confirmed users, Bureaucrats and Sysops emeriti
812

edits

Navigation menu