tpm-tools is an important feature in the enterprise from secure boot to 802.1x network authentication.

Discuss and decide on what should be tested on kernel SRUs, considering what is already available and what is missing.

Private

Apache Hadoop has gained widespread adoption; the various flavours of Hadoop appear to be consolidating and Cloudera have transferred a number of their Hadoop related projects to Apache including Bigtop (the Cloudera packaging for Redhat, Debian and SuSE). Packaging Hadoop for Ubuntu would help support developing a set of rock solid Juju charms for Hadoop by providing a well integrated version of the packaging for Ubuntu. Collaboration with Apache Bigtop would also potentially help support packaging the wider family of Hadoop related projects.

In Oneiric we have introduced color management. We have at least basic functionality now. You can take existing ICC profiles and assign them to devices (AFAIK monitors, printers, scanners, webcams) and then the devices are appropriately corrected. The profile assignments are done via the Color capplet of GNOME Control Center, the management and distribution of the profiles via colord, applications use liblcms1 and liblcms2 to apply the ICC profiles. In Precise we need to complete and improve the infrastructure: ArgyllCMS needs to be made distro-ready and added so that color calibration devices get supported, libcms1 needs to be replaced by libcms2, as the former is buggy and not maintained any more, and a color management UI must get added to the Common Print Dialog. We also need to determine who will maintain the color management stack in Ubuntu.

Wednesday

Wednesday's security roundtable

Defect Analysts have hundreds, if not thousands, of bug reports at which they could be looking. Their dashboard will be a collection of the highest priority bugs to review on a daily basis with links to reports of bugs matching specific criteria.

In order to consider Qt a recommended choice for Ubuntu app development, we need: - Better integration of the Qt development tools with Ubuntu-specific processes and tools, such as packaging, bzr, Launchpad... - Ability to access the Ubuntu platform APIs from Qt. - Ensure the packaged Qt development tools are in shape We'd like to discuss what needs to be done and a roadmap for this work.

Build a crash database for Ubuntu. Quoting Matthew: Microsoft, Apple, and Mozilla have dedicated crash tracking systems, separate from their bug trackers. This has multiple benefits, when compared with Launchpad and apport: - people don't need a sign-on account, of any sort, to report crashes - developers aren't spammed with e-mail notifications about duplicate crashes - non-developers aren't spammed with e-mail they don't understand after reporting crashes - the error message, explaining that a window just disappeared because the application crashed, appears in release versions of the software -- not just alphas and betas - contributors can easily see which are the most common causes of crashes - contributors can easily see how reliable their software is compared with previous versions. For these reasons, Ubuntu should have an error tracker too. Overview of crash reporters: http://en.wikipedia.org/wiki/Crash_reporter Public statistics from Mozilla: https://crash-stats.mozilla.com/products/Firefox Previous blueprint: https://blueprints.launchpad.net/ubuntu/+spec/crash-tracker Previous blueprint: https://launchpad.net/ubuntu/+spec/crash-reporting

Allowing people to sign in to an Ubuntu installation with their Ubuntu One credentials has a number of benefits: it makes sense on smaller or attached devices, your device is automatically paired with Ubuntu One, meaning that you have all your data without an additional "pairing" step, it means that you don't have to remember a different password per machine (not necessarily a benefit in everyone's eyes). This session is to discuss how, technically, signing in to an Ubuntu installation with Ubuntu One credentials might be done, what it would mean (does a new "local" user account get created? Should the "local" user account already exist and be matched somehow with the U1 account?), and which issues are generated by it (local caching of credentials, logging in while offline, etc).

The codecs targeted for optimization on ARM during the next quarter are libpng       needs NEON optimization, targets Linux and Android. Initial work there for Ubuntu LEB, but not for Android. libav related work       - realvideo - needs NEON optimization for rv30/rv40 to reach 720p - work to be done in libav       - ARM v6 optimizations for vp8.        There are initial patches for armv6 vp8 (article.gmane.org/gmane.comp.video.li...) and some realvideo neon (thread.gmane.org/gmane.comp.video.lib...). Both patches need to be examined, but this should be low-hanging fruit work.       - h264 10bit optimizations

Alternative to sched_mc and hotplug

How do I take some script I have that tests something on my SoC and get it running with LAVA?

In this session we will talk about plans to more effectively parameterize Android builds across kernels, toolchains, compiler flags, etc.

This Summit will bring together the main players in ARM Set Top Box to describe their current plans and problems, to promote wider understanding and collaboration. The aim will be to propose initial solutions and with Linaro able to coordinate moving forward

This Summit will bring together the main players in ARM Set Top Box to describe their current plans and problems, to promote wider understanding and collaboration. The aim will be to propose initial solutions and with Linaro able to coordinate moving forward

This spec covers testing and usability of various server side management methods such as IPMI, and other management tools.

Adding the -lowlatency kernel into the universe repository will allow Ubuntu Studio users to have a tuned kernel for audio work installed by default. This kernel will be built and maintained by the Ubuntu Studio team, therefore it presumably would be in the universe repository. Responsibilities also include rebasing the kernel for security updates and working with -security to push updates.

Meeting between ARM, Linaro and Fujitsu

Review ARB activity, and plan for the next cycle. Introducing new members.

With the fast growing adoption of the Cloud, the lack of a consistent and efficient power management has become a major concern. A first set of features has been developed since UDS-O. The purpose of this blueprint is to discuss the remaining steps to complete Cloud power management for Precise.

With rapid release now a reality in Oneiric and presumably in Precise, we should discuss the potential impact of updates that can affect people that were just expecting security updates, but getting a whole lot more (new features and potentially breaking stuff that used to work). After this session, a clear path forward for supporting the existing LTS and Precise should be established and documented.

How to use Ask Ubuntu More effectively - show the experts in the field; the kind of people we want participating more often, how they can use the site to help answer everyday user questions

This is where we will track the progress of Kubuntu Docs for the 12.04 LTS release of Precise Pangolin.

= Summary = We have lots of ideas for changes we'd like to make to Upstart this cycle. This blueprint will outline those features at a relatively high level. Ideas (highly incomplete list currently): - Fully segregated SystemV / Upstart system shutdown - Introduce "setuid" and "setgid" stanzas to allow jobs to run as a different user/group. - Enable user jobs (a simple change to a dbus config file). = Desired Outcome = - A better understanding of those Upstart features you'd like us to work on - A feel for the relative importance of each feature which we'll factor into our plans to allow us to prioritise the work.

There are different services to print through the cloud, which means that you either print out of a cloud application, like Ubuntu One or Google Docs, or from a mobile device through the cloud to a printer at home, in the office, or at a print service. We should support this in Ubuntu One, allowing to print printable files from the cloud storage to services like Google Cloud Print and/or HP ePrint.

A session to go more in depth on Acceptance Criteria as it relates to Canonical upstreams, DX specifically.

Come and join us for a brainstorming workshop on the profile page in launchpad.

libjpeg-turbo has been worked on Linaro Evaluation Builds for some time now, and it has been shown to bring improvements vs Libjpeg62 on Android and Ubuntu builds (https://wiki.linaro.org/TomGall/LibJpegTurbo). There has been a comparison of libjpeg8 and libjpeg-turbo (with libjpeg8 compatibility turned on), https://wiki.linaro.org/TomGall/LibJpeg8 libjpeg-turbo is also available in Oneiric, using v62 emulation. Debian/Ubuntu P are going to move to libjpeg8 by default making current package obsolete in the future. So we should discuss - should we package libjpeg-turbo with v8 compatibility mode enabled? Why would that be advantageous? - should we test v8 emulation mode - what needs to be taken care of there? - is there a real advantage of using v8 instead of ljt? Discuss with Ubuntu to see if they should really continue with v8. - as part of the testing - we should probably run tjbench as part of LAVA tests to get comparisons (plain libjpeg vs ljt) - any benchmarking needed for the Android platform?

In this session we will talk about automated Android testing. Description ------------------ Before each change is accepted it undergoes premerge testing. The tester, LAVA, runs a set of tests on a test build that contains the change. To get the most out of the test loop, we would like to identify areas of improvement so that faults found in this loop can be efficiently analysed and fixed. Agenda ------------ 1. Introduce what we have and what's happened recently with reviewing, building and testing. 2. Open a discussion on improvements/new features  * What improvements can we make in LAVA  * What improvements can we make in Gerrit  * Speed ups/efficiencies. Goals -------- 1. Discuss new tests 2. Plan for keeping a unit alive in a failed state 3. Plan for bootloader testing (JTAG) 4. Discuss the best way to capture and present test results for developers

As usual the Canonical hardware certification team will be hosting a session at UDS to plan and gather feedback about the general run of the certification programme for Ubuntu. For 12.04 LTS these are the goals of the improvements of the hardware certification team: == Blocked systems follow-up == When a system fails certification for a particular system the hardware certification team is doing a good job opening bugs, helping developers to debug the error and testing candidate fixes and packages. This is a great start, but for 12.04 LTS we need to improve the way we follow up those blocked system. How do we know when a system has been unblocked? When do we recertify? We need a proper policy for this, plus the needed integration between the certification site and Launchpad to be able to do this in an automated fashion. Also, we need to have good reports to help us following up for bugs waiting verification on -proposed. == Improve the efficiency of regular testing == Right now, the hardware certification team performs two types of regular testing: weekly testing on the development release and SRU testing on the kernels in -proposed. The weekly testing is currently run against all the systems scheduled to be certified in the next Ubuntu release and the SRU against all systems certified for the Ubuntu release that the SRU is being released for. We want to improve the efficiency of this type of regular testing by reducing the number of systems tested. The idea is to maintain a list of the minimum set of systems required for each of the testing. == Functional and stress testing coverage == Every 6 months the hardware certification team revisits the list of components that are covered in the certification programme and the list of tests that are part of the certification site. We will revisit the list and come up with a list of things that we will need to include (or remove) to the list for 12.04 LTS certification. Some ideas:  * USB 3.0  * 30 cycles suspend and hibernate  * Multitouch  * Battery  * Wifi slider (FCC requirement?) * BIOS modes: uEFI vs Compatibility vs Legacy

Ensure the ability to fully use Ubuntu Medium in Ubuntu 12.04 This is needed for the typographic review of the user interface. It will be necessary to be able to ship and use Ubuntu Medium and Ubuntu Medium Italic without advise effects on the rest of the interface. Currently a metadata loss occurs in FontConfig, the font matching framework used on Linux. Data that is (incorrectly) presumed to be duplicated is discarded, later causing the substitution of Ubuntu Medium with Ubuntu Bold or vice-versa at higher up levels of the stack in Qt and Gtk+. Similar issues occur with the Linux Libertine typeface, another advanced font with multiple weights within the same family. To implement, this will require upstream fixing of FontConfig and associated libraries to fix the model. To encourage completion or this, Ubuntu Medium will be once again re-uploaded to the 12.04 archives at an early stage.   LP bug #744812. There's a data-loss (discarding additional meta-data on the assumption that it's duplication, when it's not) in FontConfig, which is perpetuated by anything that follows FC's data-model and presumptions (Qt, Gtk+).   I keep not getting far enough stuck to work out a decent solution. But two guesses at the moment are either to duplicate entries (give two slightly different entries) within the current model, or to extend the data-model to cope with the meta-data in the fonts themselves.   I believe that other OSs have two basic API entries; a "dumb" mode that just matches on string:name + bool:bold + bool:italic, and an advanced selection mode that selects based on string:name + integer:weight + integer:slant + string:style + etc.   The two advanced open fonts it affects are Ubuntu (shows up particular with Medium) and with Linux Libertine.

There are two big topics to discuss in this session: - Fixing the way we handle /etc/resolv.conf to be consistent across the whole distro - Integrate a DNS resolver daemon in the default Ubuntu desktop installation == The notes below are about including a local resolver in the default Ubuntu Desktop installation == The idea is to have a local resolver like dnsmasq or unbound running on all Ubuntu desktop installations and controlled by Network Manager. All machines would then use "nameserver 127.0.0.1" in their /etc/resolv.conf search path/domain may be retained in resolv.conf or moved into dnsmasq/unbound's configuration too. The main benefit of doing this is to increase overall responsiveness of the desktop by having a local DNS cache and allow for better dispatching of DNS queries. For example in the following scenario: - Wired connection with DNS 1.1.1.1 and domain blah.com - Wireless connection with DNS 2001::2 and domain example.com - VPN connection with DNS 2.2.2.2 and domain ubuntu.com With current Network Manager, all DNS queries would be going to 2.2.2.2, making everything slow if the latency on that link is high. Also, any request to blah.com or example.com will be sent to 2.2.2.2 which doesn't necessarily know these domains (if they are internal domains for example). The resolver will fix all that by sending DNS queries to the right server depending on the domain, will cache the results and will properly handle timeouts and detection of broken server, thereby reducing delays and reliability of DNS on Ubuntu.

Google Cloud Print allows printing on your local printers from whereever you can send jobs to the Google Cloud Print service, especially from mobile devices, like smartphones, tablets, and computers running Google Chrome OS. Google itself only offers to either use HP ePrint printers (network printers which can receive print jobs by e-mail) or to use the Chromium browser as server to share the local printers to Cloud Print. The latter is officially only supported under Windows and Mac OS X, but under Linux it can be enabled through a secret "Cheat Mode", entering the URL "about:Flags" and enabling the “Cloud Print Proxy” entry, then clicking the wrench at the upper right and selecting "Preferences" -> "Under The Hood" and there will be a "Google Cloud Print" section near the end of the list. So these methods are awkward, running a full-featured browser only to make available ones printers or to have to use a printer out of small choice of models. There is also a "cloudprint" package in Universe which is a small lightweight command line tool to replace the Cloud Print functionality of Chromium, but usual desktop users are not aware of that. What we would need is something like a capplet in GNOME Control Center to (de)activate and configure Google Cloud Print. This GUI needs to be designed and it also needs to be decided which user daemon will be used to enable Cloud Print, the one of Chromium or the "cloudprint" package.

Private Ops Review for TI LT

ARM & Fujitsu Business Meeting

Community testing of accessibility during the development cycle. During most cycles, testing can not be started until the last month or later of the cycle. Testing needs to start as close to the cycle start as possible, with Alpha2 as the latest date to be able to test it.

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

Discussion and action items coming from UDS-P for the direction and development of the LoCo Team Portal during the "P" Cycle This to discuss: Bug #878593

kvm plans:    * 1.0    * spice    * robust caps-lock handling    * vde (needs MIR) Community requests?

With our switch to tb this cycle we let the default installation without a calendering solution. We should decide if we need one by default. We might not need a full client ui but we should probably at least have a way to subscribe to a remote calendar to have desktop integration and notifications working

We will present Developers.com, a site for developers to find the tools they need to create apps.

David Brash of ARM will discuss the ARMv7 architecture with an emphasis on new features.

In this session we'll talk about the future of Linaro Android and brainstorm ways we can make things better for the platform. Agenda: ICS Android's Pandaboard Build Community unification Phone builds/components RT Linux Android LTS (long-term-support) Single Android image Getting to 48 hour monkey Goals: Have a lively discussion about Linaro's future Android plans Generate ideas for future topics

Session remotely led by Vincent Guittot We will discuss the results of investigations into sched_mc - how to make it save power on dual core, single cluster - results for quad-core experiements

This Summit will bring together the main players in ARM Set Top Box to describe their current plans and problems, to promote wider understanding and collaboration. The aim will be to propose initial solutions and with Linaro able to coordinate moving forward

Discuss where to focus AppArmor development and integration efforts, part 1 of 2.

The Kernel SRU cadence continues to march along. It has been tweaked a bit now and then as needed. It is time once again to see if it needs further refinement or is it the thing of beauty we believe it to be.

Using 1.5GB DVD Image by default

Review LTS release schedule, coordinate across teams, plan delivery across milestones.

An opportunity to meet the community and discuss initiatives for the next cycle. Topics: - content in design blog - creative community initiatives (wallpaper, music)

P-cycle discussion of the master git tree maintenance

Discussion during UDS-P on the further plans and development for summit.ubuntu.com Discussion Items:  * Header links and navigation, currently too many links in the header  * Setting up summit to run concurrent summits allowing for the removal of the Linaro hard coding All items which were not completed last cycle have been added to this list.

Despite current efforts Ubuntu still receives lots of bug reports without a package. These bugs are may be about serious issues in Ubuntu and are unlikely to be triaged. Using launchpadlib and text processing is it possible to determine what packages these bugs may be about? Are there other ways to determine the right package for them?

We'd like the tutorials section of the app developer site to grow with interesting content for Ubuntu app developers. In this session we'll discuss and come up with a plan to do that. Ideas: - Brainstorming of topics where we need tutorials - Structure the list of topics in a shortlist of essential ones - Reach out to the community to assign at least one person to a tutorial - Set up editorial permissions and process in place on the app developer site

kde filesharing improvements/fixes

LTS Thunderbird Enhancements

Agenda of "Android Porting" session at Connect. ============================== This will be a "How-To" session on "Porting Android on New Platforms", including but not limited to following sub-topics:    * Android Software Stack overview    * AOSP Code structure    * Vendor/Device specific settings and HAL implementations/hooks.    * AOSP Build process.    * Android Boot process. * Android Debugging

Placeholder for the first presentation for the NEON Optimization Forum. Mans Rullgard will give a presentation on NEON optimization best practices.

Discussion of of overall Linaro kernel process, including CI loop and bug tracking, Android trees, Landing Team trees, upstream coordination, etc. Etherpad @ http://summit.linaro.org/uds-p/meeting/19260/linaro-kernel-ci-loop/

Select a GL tracing and debugging tool and add EGL/GLES2.0 support to it.

David Brash

David Brash

Keith Bergelt from OIN

Ubuntu certification is entirely performed by Canonical engineers, who receive systems to be certified and test them on a Canonical facility. It would be desirable to allow partners to perform a pre-test themselves on-site, so they can have a clear idea of whether a system is likely to be certified, and take any action they deem necessary. This eases the logistics and increases the amount of systems that can be tested by allowing partners to anticipate work that needs to be done. However, since a certification program implies a strong validation component, the process needs to be improved and formalized to better respond to the special requirements of this new arrangement. A third-party testing environment introduces the following challenges (note possible solutions in parentheses): - non-Canonical engineers won't be as familiar with the Ubuntu certification suite (make the tests less prone to failure and clearer in their instructions, have clear, unambiguous documentation on how to run tests and what to do when they fail, improve the tests and redesign the testing tool's user interface to make the process friendlier and more "foolproof"). - A certain motivation for "cheating" appears (automate as much as possible, so as to reduce reliance on a human's judgement at test runtime. do not show the results during the testing process. Instead, results are sent to Canonical for assessment.). - Partner testing labs may not have internet connectivity (ensure that the tools can reliably collect all needed data offline, and submit on a connected system). Particular suggestions include: - A complete redesign of the Checkbox UI to address usability concerns that have been raised both in the past and as part of the large amount of feedback gathered from Ubuntu Friendly. This is particularly important as the tool gets wider exposure and is compared to other, more polished applications present in Ubuntu. - Splitting the tests into categories:   1 - Tests that can be executed and verified automatically (no human interaction required - testing CPU frequency governors)   2 - Tests where the system can perform the required action and only confirmation is required from a human. (Changing display resolution)   3 - Tests where a human has to perform an action and then the system can test and decide whether the test passes (insert USB stick and automatically test read/write behavior, wiggling the mouse and checking that things work as expected) - For category 2, collecting the information for later review, possibly by Canonical engineers, so the partners will mainly collect information and won't necessarily receive feedback as to which tests passed and which failed. - An "academic exam" approach, where, as mentioned, the testing tools just collect raw data and send to Canonical for analysis. To avoid all possible forms of cheating, some form of video surveillance has been suggested. - Signing and/or encryption of test data, to identify and/or avoid tampering. This needs more thought as, being free software, the source code for the tools is widely available. - Looking at the way Checkbox is used currently and adding functionality that's needed (keeping old submissions, something that at the moment is done ad hoc, but whose frequent need indicates it should be doable through the UI). - Leveraging information gathered from the Ubuntu Friendly program. Since this will have widespread use, a lot can be learned about which tests are important to people, how people are running them, how to make them easier or automate them, and how to redesign the user interface for the testing tools to make the process as streamlined as possible. Ubuntu Friendly constitutes an external user running the test suite without prior knowledge and no help, so the usability and automation improvements that will derive from that program will prove valuable to enhance the partner self-performed pretesting experience. Partners will be benefited by faster certification times, since they can get faster local feedback on how their systems perform prior to sending them in for actual certification. Canonical hardware certification engineers will profit from a more-automated set of tests and tools, enabling them to certify more systems. End-users will benefit from a wider selection of Ubuntu-certified systems, with the confidence that results are trustworthy due to the verification processes in place to prevent faulty systems from gaining certified status. All three will also benefit from the widespread on-the-field experience, knowledge, user interface redesign and test improvements stemming from the Ubuntu Friendly program and results.

discuss what GNOME version we will track for the LTS.

Based on the results of the Ubuntu Community Survey (http://www.jonobacon.org/2011/10/24/ubuntu-community-survey-results/) a common area of de-motivation is with community members often bickering about Ubuntu and it's focus and direction. Many felt like this was frustrating because many of those who bicker contribute little.

For some derivative products based on Ubuntu, it is key to be able to offer some customization of Unity. For example, business and government entities running Ubuntu would prefer to have other applications on the home lens than photo viewers and music players. It is also important for localized images for regions like China.

* Whither Kubuntu Mobile? * Plasma Active for the win?

Present current state of OpenJDK on ARM for the p-series

CEPH has become a first class object and block storage mechanism, and has integration hooks for key pieces of Ubuntu Cloud Infrastructure. Especially interesting is CEPH-RBD for storing kvm block devices on the scalable CEPH block store, and the Hadoop HDFS shim to replace HDFS with CEPH in hadoop clusters.

Jay's plenary, but as a session

General improvement of power consumption

The Ubuntu online brand guidelines will make it easier to access the guidelines, download assets, look at examples of design work; it will be an important tool for Canonical and the entire Ubuntu community, and useful in communicating the brand clearly and in the right way. We'd like to present the first version of the site, get feedback, hear comments, suggestions, etc., so that it can as useful and easy to use as possible.

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking sessions for Graphics and Multimedia Working Groups

Discussion with David Brash of ARM

Afternoon engineering and hacking session for Kernel and Power Mgt Working Groups

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Platform Working Group

The Ubuntu Cloud images are built by a loose confederation of scripts. There is no documentation on how to setup an image build server, nor is there any documentation on the dependencies of the scripts. This blue print seeks to consolidate the information and consolidate the tools to make reproduction of a build server and maintenance of the scripts easier.

Afternoon of engineering and hacking for Member Services

Afternoon of engineering and hacking for Member Services

Linaro Roadmap Review - Agenda TBD

We currently have a couple of problems with the Firefox and Thunderbird upgrade experience, which users of Mozilla's update service don't experience (ie, everybody on Windows, Mac, or anyone using mozilla.org binaries on Linux). 1) A long standing issue we have is that upgrades totally break all currently running instances of Firefox or Thunderbird until they are restarted. This is made worse because we move the install location around between updates, but pulling the rug from underneath any running instance is probably never going to work reliably, even if the install location doesn't change. Note, this isn't just an issue with Mozilla applications - we just notice it more because we update them a lot more frequently than anything else in the archive. As another example, there was a glade -> GtkBuilder transition a few cycles ago, where upgrades between distro-versions broke things such as the currently running instance of gnome-panel [2] due to the glade files being replaced with gtkbuilder ui files. I just wanted to point this out before people start blaming Firefox that this is really a problem with how our package manager works... Upstream are currently planning work around silent updates, and they have a wiki page documenting how their update process will probably work [3]. We might be able to learn some things from this. 2) We have no way of warning people if any of their addons might stop working when we offer them an upgrade. People using upstream builds are notified before an upgrade if any of their ddons aren't compatible with the update, and if there are no addon updates available to fix this. Do we want to provide such functionality, bearing in mind: - We haven't had that many bug reports yet from users complaining of addons being incompatible after an upgrade, although there have been 1 or 2. - As of the time of writing, 92% of addons on AMO are compatible with the current Firefox beta (due to be released on November 8th). However, approximately 75% of addons in use are not hosted on AMO [4]. - From Firefox 10 (Jan 31st, 2012), addons are going to default to being compatible, with some exceptions (addons with binary components) [4]. [1] - https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-mozilla-upgrade-experience [2] - https://launchpad.net/bugs/422568 [3] - https://wiki.mozilla.org/Background_Updates [4] - https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible

The goals for the Accessibility Team community for the Precise cycle. Please add items for discussion to the whiteboard!

The Papercuts project failed to reach its target of fixing 100 papercut bugs in both the Natty and the Oneiric cycles. The initiative needs a new life.

Continuation of sessions of day 1 and day 2.

Private

Today you can buy a computer preloaded with Ubuntu from many different vendors. The OS image used at the factory is often modified to provide better hardware support. It may also contain customizations such as additional bookmarks or applications. As a result of these customizations, the upgrade path to the next version of Ubuntu is not as clean as it could be.

Arkose has been entirely rewritten over the past 6 months and a lot of new features have been implemented. During this session, I'd like to talk about the next set of improvements for Arkose and where it can and should be integrated with the distro. Amongst changes I think are worth discussing in this session are:  - Supporting two different "backends", apparmor and LXC  - Offering a better run time experience for users of the wrapper  - Discussing how we want to ship the profiles  - Extend the profile format to include more fine grained options: cgroup options, firewalling rules, ...  - Use Arkose to start GUI packages from older version of Ubuntu - Allow spawning commands in an existing container, allowing to save some resources in some cases Other planned upstream changes:  - Improve the CLI tool to match the features supported by the python module  - Split the python module into plugins helping reduce the number of dependencies of arkose itself

The Nokia Qt team wants to reach out to designers to showcase the QtQuick software and the power of QML to design UIs sharing the same toolset with developers.

We have detected a need for DSL integration in Juju, this would mean that any of the current configuration management applications available. Advantages * Faster implementation of juju on running platforms * Faster testing of juju on individual nodes * Complements the amazing capabilities of juju with some node specific templating For all this we need to talk about: * Ways to export through a RESTful interface metadata from Juju * Ways to implement this so Juju can action on this without problem * Finding ways around the SPOFs Juju roadmap right now has priority on colocation Colocation can be used in colocation mode as well Colocated service has access to filesystem services (whichever they are) and can establish master/slave relationships with the master unit Juju charms can trigger an update of the facter information since it's always stateful, it can be a "trigger" on the update hook So far the best action would be to query the CLI (juju status) and its a very effective way to recover information from juju in a quick (albeit slightly dirty) way ACTIONS [lynxman] write puppet external node classifier for juju status -> puppet: TODO [clint-fewbar] Start project for recovering useful information out of juju status: TODO [juju] after colocation investigate cli interface for local / arbitrary unit / relation info: TODO

CouchDB replication through U1 makes Ubuntu a unique and attractive platform for forward-looking apps. However, reliability problems have made it difficult to actually use. So how do we improve the situation? And what can app devs expect from CouchDB sync in Precise? * What current upstream CouchDB work might improve the situation for P? * What version of CouchDB will ship in P, what will the U1 infrastructure run? * Although an understandable move because of load/reliability issues, syncing only once an hour makes the platform far less interesting from an app developer perspective... are we stuck with this? * From a user experience perspective, what we really want is continuous replication... and that's also where the platform gets *really* interesting [insert awesome Novacut demos]. * Jason would like to see a U1 sync testbed available in parallel to the production infrastructure... uses usual SSO, but runs on newest Ubuntu release and newest CouchDB... has *no* data-safety guarantee! I want to help improved U1 CouchDB reliability, but can't do much if the production infrastructure isn't usable for my apps.

Text-Free Boot

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Graphics and Multimedia Working Group

A training session guiding users through common use-case scenarios for BZR users.

Afternoon engineering and hacking session for Kernel and Power Mgt Working Groups

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Platform Working Group

Afternoon of engineering and hacking for Member Services

Afternoon of engineering and hacking for Member Services

Linaro Roadmap Review - Agenda TBD

Linaro Roadmap Review - Agenda TBD

Discussion about Ubuntu on phones.

That's another "classic" for UDS, we should probably not change a lot but we said we would revisit having pitivi on the CD, we should also have a look to GNOME new stuff like the sushi previewer for nautilus

The FreeIPA team (https://launchpad.net/~freeipa) has been working with the goal to get the packages included in Debian and Ubuntu. Running an instance of FreeIPA provides an easy to maintain kerberos realm for users and machines, 'AD for Linux'. This is something that has been requested by administrators for years, so it's about time to provide it in Ubuntu as well, even if just as a technology preview and not something fully supported (=in universe). Even though the focus for the LTS is on stability, it shouldn't raise the bar for providing new funtionality in universe too high. The current state of the packaging effort: IPA client - dependencies packaged * certmonger * python-krbv * python-nss - client packaged, testing ongoing [ref 1] IPA server - dependencies mostly packaged * 389-ds * dogtag missing - server packaging shared with the client, currently disabled from building due to concentrating on getting the client running Dogtag cert server - dependencies packaged * tomcatjss - consists of several small components, some of them completed, more or less simple to package the rest, just not got that far yet Ideally, the packages would flow from Debian, though it would mean getting someone to sponsor the uploads. [1] https://www.redhat.com/archives/freeipa-devel/2011-September/msg00408.html

Goals for the UDS-P cycle to help the Ubuntu Leadership Team establish relationships with formal Ubuntu Leadership Councils, Boards, and leaders throughout the community in a effort to provide resources for mentoring new leadership and encourage and motivate current leadership to become even more effective and efficient.

A review of past activity and future plans for the Ubuntu-Hams team. Open to all amateur radio operators and anyone else who is interested.

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.

We currently test Ubuntu Server ec2 AMI's at key milestones during the current development cycle; we should expand this todo daily testing of both the current development release and existing supported releases as well to provide assurance that Ubuntu Server cloud images are validated on ec2 and OpenStack.

Followup on https://blueprints.launchpad.net/launchpad/+spec/other-o-bug-lifecycle, reviewing results of developer survey, and discussing proposed changes to bug states and workflows.

Grow the contributions of community submitted charms for juju

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Graphics and Multimedia Working Group

Private

Afternoon engineering and hacking session for Kernel and Power Mgt Working Groups

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Platform Working Group

Afternoon of engineering and hacking for Member Services

Afternoon of engineering and hacking for Member Services