0.84/Reliability

Datastore rework

Owner: Tomeu Vizoso

Peers:

The datastore code needs to be rewritten, to simplify and improve maintainability. As a first step the API will not be changed at all (other than removing removable devices support, see next goal), so that the new implementation can be swapped in without changes to activities and Sugar. (tomeu)
Drop for now the management of removable devices inside the DS. Removable devices support in Sugar should happen without intervention from the DS. This will require that Sugar grows some kind of simple file manager that access the file system directly. (tomeu)
#8155 The datastore should hard link identical files, to handle repeated downloads of the same content without filling up NAND. (tomeu)
When an existing entry is modified, keep the old version and reference them with a version number. Compress versions with deltas. The journal needs to add a possibility to launch different versions of an activity from within the detail view. (tomeu)
Degrade gracefully if a database gets corrupted- Basic functionality should only depend on the filesystem being available. Any other data structures (full text index) should be rebuildable from the filesystem. (tomeu)

Tomeu is working on a prototype of the datastore rewrite.
If the journal is not going to display the contents of removable devices, we (Eben) need to design an alternative UI.
More work needed to define the goals.

Owner: Simon Schampijer

Peers

Complete Gadget implementation, which should hopefully fix our current scalabity issues and offer new features as activity and buddies search. (cassidy)
Integrate Gadget in glucose. It will require work on several modules, including sugar-presence-service, sugar-toolkit and sugar. (cassidy)
Integrate gadget in the Sugar UI. #7711 (erikos, eben)

Owner: ???