Launchpad.net

Blueprints

14 blueprint(s) matching “foundations-1305”

Since the initial plan of cross building the android container on a livefs buildd did not work out, we have roughly redefined the build process for these touch image parts to build from source packages instead. Nothing of this process has been detailed yet nor have work items for the defined bits been assigned, we s...
Ubuntu Kernel session to discuss misc kernel topics related to the upcoming 13.10 Saucy release. Discussion to include the following: * Upstream kernel version to target for 13.10 * Supported 13.10 Ubuntu kernel flavors * Kernel config review? (we are not yet rebased off of v3.9 so there is little to review) * Ubu...
Bring up the new arm64 architecture for saucy, starting with a cross build.
Image based updates for Ubuntu
With Ubuntu getting ported to more and more mobile devices, the standard update mechanism through apt and dpkg is starting to show some limitations. As a result, Ubuntu is now looking at supporting an additional way of updating devices that are based on read-only images. For those devices, we're looking at doing im...
Chromium has matured to being as good or better than Firefox. It will be the foundation of a lot of Ubuntu Touch code and webapps code. We should consider using Chromium as the default browser in Ubuntu.
Upstart Work Items for Ubuntu
Summary of Upstart work items for this cycle.
Launching applications needs to be done in a consistent and controlled manner so that various hooks can be included for security and consistent tracking of applications. This looks at using Upstart for that, based on the prototype here: https://code.launchpad.net/~ted/+junk/upstart-app-launch In this session we n...
Although the "rolling release" discussions from last cycle didn't actually result in a plan to institute a rolling release, they did leave several questions outstanding. As well as implementing an easy way to perpetually stay on the development release (by way of a symlink or similar), it would be helpful to discus...
On Phones and Tablets we do not want any user interaction (fsck, full system encryption etc) on boot. Plymouth does not have any onscreen keyboard capabilities so it will be impossible to interact with it this way. This spec is to define either ways to avoid user interaction at all, or make plymouth usable with touc...
We want to use Checkbox to certify ARM based servers. Previous investigation has shown that Checkbox requires some fixes to make it work well on ARM. The goal of this blueprint is to define the work that needs to be done to achieve this. Being a tool for testing hardware, many of the tests used in Checkbox have suc...
We have made good progress in the last six months on delivering well tested and stable releases of Checkbox to our PPAs. The aim of this blueprint is to continue down that road and reduce the amount of time this process takes so that we can do even more frequent releases while remaining rock solid. Right now the re...
UEFI, Secure Boot and hardware enablement backports work for Kubuntu
Automating the Language Pack refresh process to ensure quality translations, enabling upstream and Ubuntu to easily push fixes, especially for LTS releases. Right now delta language pack updates are automatically uploaded to either a PPA for stable releases or directly into the archive. That  works well for those, b...
Checkpoint for the current state of Ubuntu Touch Power Management policy and development.