Unit Tests

Development and Process

  • https://wiki.ubuntu.com/UbuntuEngineering/12.04/UpstreamDevelopment

  • clean up code structure to (among other important things) facilitate unit tests
  • make a chart for unit test coverage similar to our startup time
  • Improve developer documentation, common pitfalls (like usage of _()) how we expect patches, our development process
  • Overview of contributer docs (ie. architecture, writing tests etc.), as this is a source of the translation bugs.

Also because our code structure - having to follow through lots of files to debug something.

  • More code reviews - building a code-review culture.
  • The other thing we want to do is expand test-coverage. We're not doing too bad, but lots of room to improve.
  • We don't want to make it suck to contribute by being too restrictive (branch must do X and Y etc.), while at the same time building a helpful process.

Enhanced Unity Launcher Integration

Additional Tile Views for Subcategories and Exhibits

Installed View Improvements

OneConf Enhancements

  • optimize performance
  • add back search capability inside the oneconf view
  • there will be a oneconf session on Friday

Displaying multiple versions of a application (from e.g. the -backports branch)

Other Ideas and Miscellaneous Topics

  • python3, code style, tests, docstrings,
  • the store db tweaks & improvements,

  • bringing some of the synaptic actions to usc, reinstall, update, pin a version ... which would we want?
  • video clips
  • system capabilities (e.g. to know if a app needs full opengl or not)
  • plugin architecture
  • improve cdrom support
  • Seb24 :
    • "XX items in the list" in the list
    • New categories : ebook, Indicator, lens and scopes
    • update/upgrade directly in SC ?
  • dpm: Useful to report bugs in other languages.
  • mvo: Accessibility (ties into testing, as it'll help run ldtp)
  • Check with Mikail about whether Dash/Lenses should be something we're starting to focus on.
  • Update to Python 3? mvo is doubtful (dbus and xapian) - mvo will go to the python3 session.
  • kiwinote's new db-backend: we'll need to do a risk-assessment and see when we can ship it.
  • Supporting videos: hosting and streaming ourselves, or using a service (without breaking their terms), such as using webkit to render youtube flash/html5 player).
  • Supporting multiple screenshots (or localized screenshots?)
  • We need to develop plugin apis and docs. What type of plugins do we want to support? Eg. A plugin that we want to use to create a download bundle - a bundle of apps in a single download that you can take to a friend on your usb stick. The point is to foster creativity for this kind of thing. And once we have the api, we should refactor our own code to use it also.
  • New user interface for a help or support action, or even refund for for-pay apps. mpt drafted an interface design for it:

SoftwareCenter/UDSPreciseSessionNotes (last edited 2011-11-17 22:50:23 by gary-lasker)