Revision 1 as of 2009-11-19 23:00:17

Clear message


This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.


This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

User stories



You can have subsections that better describe specific parts of the issue.


This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.



  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

== Rationale ==

Dell tends to purge most of the pool from the DVD before installing, to just what's needed by Ubiquity installs
Excessive DVD size causes extra factory burn time, because it's copied to the recovery partition
cdimage is pretty close to its tolerances (both in terms of physical disk space and in terms of platform QA capacity to validate ISOs around release time), and another matrix column is difficult

== Design ==

Maintain a tool to perform a required transformation, and pass the result through OEM Services?
Advantage of tool approach is that it provides more flexibility for different customer requirements, although it does involve more setup and less centralisation
Future work: (web?) front-end to permit arbitrary package selection (see also previous discussions around customisation tools, cf. Fedora's Reconstructor etc.)

Seed for additional contents, containing (in Dell's case):
 * language-pack-*
 * language-support-* (or equivalent)
 * fglrx
 * nvidia
 * wl
 * linux-generic-pae
 * oem-config-gtk

Dell need i386 only; will switch to amd64 once 64-bit Flash is stable

Depends on work in oem-config to install packages from pool
 * requires additional preseed to specify pool location (default: whatever sources.list says)
 * requires additional preseed for early command (mount recovery partition, where pool resides)
 * OEM Services has a `language-installer` tool for this, although we may prefer to use code from `ubiquity` to integrate with `python-apt`; requires further investigation to see what code can be reused
  * http://netbook-remix.archive.canonical.com/updates/pool/public/l/language-installer/