Raindrop/Milestone Planning: Difference between revisions

Raindrop/Milestone Planning (view source)

475 bytes removed , 2 December 2009

109

edits

@@ Line 35: / Line 35: @@
 * Good defaults for triaging
 * Ability to do "Don't want this in my inflow".
-* Tracking people and relationships
+* Tracking people and relationships.
-* BE: Implement confidences to allow multiple extensions to override/cooperate on a specific schema. This is needed specifically to filter notifications.
-* BE: Provide a way to roll back extension changes that affect a common schema. For instance, if two schemas modify rd.msg.body, then have a way to roll back one of them and the subsequent schemas generated from rd.msg.body and re-run the dependent extensions based on the new version of rd.msg.body.
-* Use new confidence/aggregation work to properly filter out notifications.
 * New web-based account setup based on the security model, ideally something suitable for a hosted environment, but not required.
 * Security: investigate CouchDB OAuth to restrict access to the couch to only authorized users.
 * Complete the move to the server web API, remove old JS code.
+* run-raindrop.py to go away, controlled by front end.
 === Dog Food ===