While Ubuntu runs fine on low spec hardware, the minimal system requirements are still pretty high. Ubuntu will not run on truly embedded hardware, the smallest Ubuntu root filesystem in the form of ubuntu-core still uses more than 100MB diskspace when unpacked. A tool to create even smaller footprint filesystems already exists in the form of initramfs-tools which has hooks and scripts to allow the addition of any binary from the underlying Ubuntu filesystem (or chroot) it gets executed from. Scope of this spec is to research, plan and implement the creation of a truly embedded rootfs builder which creates an absolute minimal filesystem that can also run on hardware with extremely limited diskspace by using parts of the existing infrastructure from initramfs-tools (i.e. copy_exec and friends).

Feedback session on what went well and what needs to be tweaked from our experiences in precise. Goal is to keep the experiments that did work, and adjust those parts that were still causing problems.

A discussion of the use of GStreamer in Ubuntu TV taking into account any existing third-party GStreamer sources and sinks.

This specification is to plan the work of the Ubuntu Accomplishments releases over the coming release cycle. Goals discussed so far include: * Maturing our API. you can see a list of these goals at https://wiki.ubuntu.com/Accomplishments/NewAPI * Getting Local Accomplishments support to a level of quality that matches Global Accomplishments. * Expanding our help and guidance for how to get started using the system. Please join the session, particularly if you are interested in contributing to the project.

Hands on help with Launchpad bugs and getting involved in contributing to Launchpad

Discussing options for improving manual testing, metrics, and user feedback for those running the development version of ubuntu

Discussing ways to integrate the ubuntu friendly database for testing needs. -Creating a testing hardware database for targeted testing -Identifying and communicating with people with specific hardware for iso testing, feature testing, and hardware enablement and/or bug fixing -Make available the testing pool/results to developers (upstreams?)

(maintaining and reviewing charms)

Port indicators to GMenu

Giving an entirely new version of any widely used software program to our entire user base all at once is unnecessarily fraught with peril. Instead, let's employ a phased update strategy wherein we provide the updated software to an ever-expanding set of random users. This pool of users will be grown as our confidence of that software update grows, fed by realtime information from the crash database and other potential sources. We should discuss the tradeoffs of doing this just post-release or during development, when we're also trying to land large changes to the operating system. We should build this at a level that still affords power users the ability to forcibly install all updates. Update-manager is one such option. It might be worth also discussing the possibility of using feature flags.

Things to package for Q

Review of Quantal schedule and Interlock schedule to 12.04.1 needs. Primary page is:     https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule Need to synch with:     https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule (for 12.04.1)    https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock

The third Open Compute Project (OCP) Summit is the week before UDS, in San Antonio. This bluerprint/session is to serve to inform others about the current and future hardware specifications for the OCP (v2 and v3) as well as; List any known software components of the OCPv1 and v2 spec, Document future up-and-coming requirements , Classify any pieces that would need to be solved by an OEM/ODM (such as providing a bios flash tool / sensors module), Take note of any pieces that could be solved in Ubuntu such as using standard ipmi calls, etc, or tools to convery "OCP config files" that might be written for a CentOS SNMP server, to ones that would work on Ubuntu, hardware enablement, BMC, etc).

This session is designed to discuss which accomplishments we want to focus on for the forthcoming cycle to expand the Ubuntu Community Accomplishments collection.

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.

Discussing how to better organize the diverse set of teams within ubuntu and it's flavors dealing with QA.

How are people using charms? What kind of things should we recommend to people? How can we collect these best practices?

We receive a multitude of package installation failure bug reports because people have misconfigured their /etc/default/grub file. These are often due to simple syntax errors which we should guide users into fixing for themselves.

Mono has the ability to generate code ahead of time and store this alongside the CIL image. This can significantly reduce startup time, allow sharing the in-memory code, and allow for more extensive optimisations to be performed.

Discuss ideas for cloud-init or cloud-utils. Request for Features? Request for Participation in developing Features?

Catch all session (should be scheduled in a big slot if possible) for networking in Quantal. Discussing with Mathieu Trudel, we don't think there's enough to discuss this time around to warrant the usual 2-3 networking related sessions. If we're wrong, then we'll schedule another one.

Session to discuss how the virtual team working on the 12.04.1 point release will organize their work

Discussing the state of testcases and there use inside of ubuntu flavors. Testcases are generic and ubuntu-centric, causing confusion and poor results when utilizing them for testing flavors

Discuss what demand there is to make a GNOME flavor of Ubuntu, what it would contain and if it would have patches over upstream GNOME and what work needs to be done to make it happen.

Have a comprehensive smoke testing suite that is reliable by the end of the cycle

a new approach to users?

Etherpad Lite is the future of etherpad, it has a neat integration API, lets look at how tightly we can integrate it wiht summit for single sign on, pad creation and pad content management