Make image builds possible outside the data center and easily accessible and reproducible to developers, testers and end-users. The current setup is not easily installable on other computers and is not very well documented either. Evaluate what OEM/Linaro do in this area.

Figure out how to get Firefox building with elfhack again. achiang brought this up here: https://wiki.ubuntu.com/ARM/PBlueprintIdeas

currently every ubuntu install requires an initrd, this is caused by the fact that we: a) use UUID for finding the rootfs b) some packages have a requirement to process bits before the rootfs is mounted this spec is supposed to span across multiple releases, we first need make the kernel recognize UUIDs for partitions and second there needs to be something like a database that knows when a package is installed that needs an initrd. This spec is considered implemented if initrds are only generated once a package is installed that require them or the user explicitly choose to use an initrd.

In ubuntu ARM mostly developer boards are supported. Target of this programme is to: a) involve more community across the board in the ubuntu arm world b) have the community select a device for adoption in the next cycle c) help the community with the implementation for this device (image building etc) d) have the community take over the maintenance of the resulting image

As we enter the second cycle of Ubuntu Server on ARM, we must work towards addition tuning and performance options that make sense on ARM including comparing against the x86 server kernel, and changing any relevant confirmation options.

Discussion and handling of various virtualization solutions on the ARM platform including Codezero Embedded Hypervisor and KVM

today ubuntu-core is actually the most minimal OS you need to run apt-get, there is no root password, no user or any other configuration in place on the core images ... this confuses users that want to use -core as a minimal development environment. target of this spec is to give users something in hand to easier make use of ubuntu-core, collect certain typical usecases and document what needs to be done to turn -core into a proper rootfs for these cases.

As actual ARM server hardware begins to enter the marketplace, a standardized way to test and benchmark performance must be developed and run on all active platforms we support for ARM server.

jasper is a pile of hacks similar to casper. target of this spec is to re-implement the functions jasper fulfills in debian-installer modules. additionally the ac100-tarball-installer functionality should go into d-i as well.

Ensure that a base set of packages is cross-compilable from an x86 host to an ARM target. The goal is to ensure the packaging of packages in Ubuntu Core, Ubuntu Server, and a base set of desktop system libraries/applications (qt, gtk, glib, freetype, firefox) supports cross-compilation of those packages..

For ARM targets we currently have semi-preinstalled images - an already extracted rootfs on SD card which is expanded to fit the media on first boot and run oem-config. We should investigate the feasibility of having an installer more in line with Ubuntu desktop, that is installing from a squashfs based live-image. There are performance issues to consider - such an image proved very slow a couple of cycles before - and the fact that most of our target hardware only has one storage media by default, making the source and the target of the install necessarily the same. We could have such a live-installer made initially only for the particular case of installing from SD card to an external USB drive.