Ubuntu Wiki

• Launchpad Entry: kubuntu-lucid-netbook-packaging

• Created: November 20, 2010

• Contributors: ScottKitterman

• Packages affected: kdebase-workspace, plasma-netbook, kubuntu-meta, kubuntu-netbook-default-settings, and others (potentially)

Summary

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.

Rationale

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

User stories

Assumptions

Design

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

Implementation

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.

Migration

Include:

• 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

two questions: 1) Moving the plasma netbook binary now that it is part of workspace 2) what do we want to do with any netbook specific applications

• In general, decide which default apps we want later (last alpha?)
• Lighter weight alternative to amarok
  • - Needs to have internet audio support (daap would be nice) - Needs to have ability to subscribe to feeds (Podcasts)
• not everyone has 2gb of RAM with x86 (think ARM)
• Think about smaller screen interactions.

* Different install process (arm vs x86)

Packaging: * How to package multiple frontend shells

• - Always want the primary plasma installed as fallback - Put alternate plasmas in separate binaries - Package separately and have an ability to select which shell to start

Actions

Roman: look into describing how to setup qemu for people to QA test

• - Testdrive rocks! You don't have to do a darn thing just for this - Also help.ubuntu.com has the info needed to setup Qemu

• - test latest upstream kde - try KNE - Look at (Auto Login) being ticked by default in a netbook install

Riddell: rename KNE to KNR (remix) Why? UNR to become UNE

* Create page on website to introduce KNR, what it is, who it is for * Look at predefined gestures for arora (for touchscreen)

* All the kde packages should build on arm (be mindful of build failures)

Investigate: * Trunk kde has a way to switch which shell gets started (in systemsettings, http://tinyurl.com/ycc6h3h)

CategorySpec