0.84/Reliability

From Sugar Labs
< 0.84
Revision as of 04:45, 7 October 2008 by Marcopg (talk | contribs)
Jump to navigation Jump to search

Datastore rework

People

Owner: Tomeu Vizoso

Peers:

  • Marco Pesenti Gritti

Actions

  • 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) #6269
  • Support arbitrary metadata properties that activities wish to add #4662. (tomeu)

Status

  • 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.

Solid clipboard

People

Owner: Eben Eliason

Peers:

  • Tomeu Vizoso
  • Marco Pesenti Gritti

Actions

  • The Sugar clipboard supports multiple clippings at once, which is fantastically useful, assuming you can tell them apart. Right now, you cannot. A primary goal of the next major update to the clipboard is to expose the identities of clippings, including support for activity supplied titles, colors, icons, and previews. The first order goal is to define an API to make this possible.
  • In some cases, clippings won't have titles at all (or activities won't cooperate to supply them). We need to improve the default behaviors for generating titles, colors, and previews so that the clipboard is still usable.
  • We really need to support a direct "paste" action on clipping items, which poses an implementation challenge. It's important, however, to make this action work in our "object oriented" environment.
  • We should have secondary option for paste-and-remove (option-ctrl-v) on the paste button.
  • We should have secondary option for copy-and-erase (ctrl-x) on the copy button, to handle the action usually known as "cut".
  • The clipboard should support drag'n'drop reordering of clippings, both to make a series of paste-and-removes occur in a desired order, and to allow one to move clippings back to the top, so they don't fall off the bottom as more are made.

Tickets

This list is a subset which focuses on the key areas I would like to address. For a more complete list, which invcludes some less noteworthy yet attention deserving bugs, please view the full trac query.

Status

Memory bloat

People

Owner: Marco Pesenti Gritti

Peers

  • Riccardo Lucchese
  • Tomeu Vizoso

Actions

  • Improve base memory usage of the sugar shell and related services. (tomeu)
  • Improve base memory usage of the Activity class. (marco)
  • Write a clear check list about things you need to do to ensure you are not leaking pygtk widgets. (tomeu)
  • The reference cycle between Widget, Palette and Invoker is causing a lot of leaks. The Palette should not know about the invoker at all. The Invoker should control the Palette instead, pop it up and down, set his position etc. (marco)
  • BuddyModel is referenced by sugar.presence.buddy.Buddy which is cached, so it doesn't get released as soon as we would like. (tomeu)

Ideas

  • We need some way to constantly monitor memory usage.

Status

  • Several heavy shell dependency has been dropped.
  • Merge of the journal and of the shell service into the shell is in progress.

Quality assurance

People

Owner: Marco Pesenti Gritti

Peers:

  • Simon Schampijer
  • Joel Stanley

Ideas

  • Get a buildbot running on at least Fedora and Ubuntu.
  • Pylint the core codebase, check regressions in the buildbot, make it a requirement to be pylint clean to submit patches.
  • Add basic checks on the buildbot about shell and activity startup.
  • Integrate sugarbot into sugar-jhbuild and buildbot. Write tests for it and encourage the activity authors to do so too.
  • Start writing unit tests and use nose to run them into the buildbot. We will have to figure out how to unit test UI code.
  • Form a community driven bug squad to help with testing and bug triaging, both on the XO version of Sugar and on other distributions. It's important that we get testing well before OLPC is trying to close down it's releases.
  • Developers should start using Sugar daily, either on the XO or on a normal laptop.

Status

  • Defined the general goals.
  • Work on the buildbot is in progress, but it's already useful.
  • Zach working on sugarbot integration.
  • sugar shell and module are pylint clean and checked by the buildbot.
Retrieved from "https://wiki.sugarlabs.org/index.php?title=0.84/Reliability&oldid=9480"