There are some newer technologies floating around that we may want to consider adding to the supported seed. These include: * Nginx - Has become de-facto scalable web server, and grown up as an OSS project now * Node.js - Gaining popularity fast, and *SHOULD* be a build-dep of OpenStack Horizon    - Also a direct dependency of the new Juju GUI * MongoDB (also headed for main as part of juju) -- Others? - seed prunin. Anything that can be dropped? Rationale: Goal:

Roundtable sessions of the Community team.

An initial roundtable to help kick off this UDS.

Morning sync to discuss sessions to attend during the day and review any sessions attended the day prior.

Discuss and outline the work required to fully enable Unity 3D for accessibility and LDTP/at-spi based automated testing.

Open roundtable to discuss any Ubuntu App Development topics that might or might not be in the schedule.

Ubuntu Online Accounts was added in 12.10, with initial support for Empathy, Shotwell, Gwibber and the Google Drive scope. The goal is to bring support for Online Accounts to more desktop applications, by demonstrating the available documentation and resources, and giving some examples.

Walk though the process of installing the Nexus7 image on your device and how to report bugs.

This session is about providing tooling which would allow the flavors to have total control over their release schedule and image creation.

It's time to update the Ubuntu development videos. In the sessions we want to discuss - which topics to pick (Essentials: Intro to Ubuntu Development, Getting Set Up, Discussion of a Debian package, Fixing a small bug) - solutions to recording/editing videos/screencasts

- We need something like debian/watch for charms. - Upstream source repos - charms using old formats

We present a proposed redesign of the Wubi installer, for the benefit of anyone who would like to work on it.

Openstack QA workplan for Ubuntu. -- Add the following to the lab - quantum, ceph - james-page Add different deployment options on a less frequent basis - james-page Rationale: Goal:

Enhance Dash to support searching online music.

This session is to review the Raring Release Schedule and discuss removing the 3 Alpha & one of the two Beta milestones.

The last two parts of the onramp: - Knowing what to work on. - Rewarding people who contribute to charm stuff, raise the visibility

The XCP Toolstack is an open source, server and cloud virtualization platform which provides a rich management API on top of the Xen hypervisor. The purpose of this blueprint is to discuss improvements to the Ubuntu XCP Toolstack that we wish to make during the Q-series development cycle. We would also like to discuss ideas for improving the interaction between the XCP Toolstack and other Cloud and Server managment interfaces, such as OpenStack, CloudStack, and Juju. Rationale: As a type-1 hypervisor, Xen provides various architectural benefits over KVM which make it well suited for the cloud. The XCP Toolstack is a Xen management platform which makes Xen easy to use, and integrates well with OpenStack and CloudStack. Goals: 1) To bring the XCP Toolstack in Ubuntu 13.10 on-par with XCP 1.6 and XenServer 6.1 in terms of feature parity and performance. 2) To build a development community around the XCP Toolstack and Ubuntu.

SRU process and schedule for Essex and Folsom. Rationale: Goal:

In order for the Hundred Paper Cuts project to stay healthy, it needs a constant flow of new bugs, several hundred each cycle, for people to work on. Making it easier to report paper cuts will help keep the reports flowing, and a desktop utility bundled with ubuntu-dev-tools could help with this.

Review of the kernel configuration for 13.04. This will concentrate on confirming the policy for various option types as well as new options. For major new options, we will discuss and confirm the selection of each.

Review deferred items and decide what to pick up for raring.

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

Often times a driver from a specific linux-backport-modules package is made available which is required for enablement (eg: a new driver from compat-wireless). It would be of great benefit to expand ubuntu-drivers-common to be aware of these updates where appropriate == TODO == This applies to Precise and Raring * [rtg] to deal with modaliases in the control files * [tseliot] Code to handle the logic when multiple driver versions are available * [tseliot] Add an entry for the default drivers so that users can go back to the default drivers once they've tried lbm * Recommend the default driver when multiple versions are available * How do we notify users that new drivers are available and what updates do we show * Input drivers : config files to pass module parameters * Should we pop up a notification even when the driver already works? We don't want to break things that work * Modify the description of the packages in the driver manager * Consider backporting this work to quantal

Cover community needs, ideas and plans for outreach and recruitment

Xen is a mature, enterprise-grade, open-source type I hypervisor. This session we will give a brief project update about our recent 4.2 release and the roadmap for our upcoming 4.3 release. We will then discuss various topics about Xen integration in Ubuntu. A detailed feature list for 4.2 can be found here: http://wiki.xen.org/wiki/Xen_4.2_Feature_List There are two related features that are probably the most important from a user / integration perspective: * libxl has gone from being a "tech preview" to having an officially-supported stable interface. libxl is a library designed to allow all the basic hypervisor functionality in a consistent, stable interface which will be backwards-compatible. There are already libvirt bindings available for libxl (not sure which release this will be in). * xl is now the default toolstack, rather than xend. xl is built on top of libxl, and is meant to be a drop-in replacement for xm. It is entirely written in C (xend and xm are written in python). The main difference users see (other than performance improvements) should only be that they type "xl" instead of "xm" for their basic commands. Rationale: Goal: 1. To update other Ubuntu developers on the progress of the Xen project 2. To define what it would look like to have Xen be easy-to-use, robust, and reliable in Raring 3. To identify any changes which need to happen for #2 to take place.

A discussion of how to measure boot & resume time for ARM devices, tools for measurement, and what things can be done to improve the performance of each.

Presentation session to introduce and gather input about the new Ubuntu App Developer upload process [1], its scope for 13.04 and the work ahead. [1] https://wiki.ubuntu.com/AppDevUploadProcess

Secure your Ubuntu SSO account with 2-factor authentication! Get help setting up and using your *new* YubiKey (or Android/iOS smartphone!) to add an extra layer of security to your Ubuntu SSO account. Come to the workshop sessions and help us out making Ubuntu SSO more secure for you and everybody else.

NUX now is lacking the flexibility of input method support, only ibus can be used, we need make nux support XIM or native immodule support, then users who use NUX based application can choose whichever input method based on their decision.

Meeting for Ubuntu IRC ops, to meet and discuss various topics.

Application server technologies such as Django, JavaEE or Ruby on Rails work in a similar way: an application server provides a runtime and services to a number of applications it hosts, such as access to data sources, configuration options, etc in a way that shields the applications from the underlying topology. This blueprint aims to extend the Juju subordinate service concept, provide support for a number of application server technologies in two ways: charms for some of the most common application servers and tools to enable users to create charms for their own application to be deployed on top of any compatible application server. Rationale: Goal:

With the need of doing UI testing in UE, we are looking for a set of existing test cases that can be used for that, unity test suite is an ideal candidate as a starting point.

Shortly after the UDS there is the Color Management Hackfest in Brno, where I am invited to participate. I am there to work on color management obn the printing part, but I can also forward any ideas, wishes, and requirements for Ubuntu. In this session we can discuss what is important for Ubuntu and needs to be talked about on the hackfest. http://www.freedesktop.org/wiki/OpenIcc/Events/Hackfest/2012

Currently, virtualization infrastructure from qemu to openstack, does not fully comprehend architectures that are non-x86. While qemu has finally been built on powerpc in precise to enable a KVM enabled VM, things like libvirt and openstack do not entirely know about the existence and difference for non-x86 hosts and VMs. Enablement is needed so that these differences are apparent and so that jobs/VMs can be created as "generic" or specific to a certain architecture. == Comment == Hi Ben, Currently the session shortname (virt-powerpc) doesn't fit the convention for the tracks. Would you be able to determine where you think this best fits? -- Daviey Change to servercloud. -- BenC

We've learned a lot since the creation of charm helper. Debian packagers took 7 iterations before boiling all of debhelper's goodness into a declarative system. We can learn from them, and get there in our second iteration.

- Finishing the Java6 to Java7 transition - Obsoleting Java6 for 13.04 - OpenJDK plans for new architectures - Brainstorming about OpenJDK 8 for 14.04

We've talked about reverting uploads as a tool for correcting regressions in the development release. This practice has not been adopted as widely as it probably should be. Discuss the reasons and come up with clear policies on when reverting is the right answer (as well as when it isn't), so we can act on these policies quickly and with confidence, minimizing development velocity lost across the team.

How do I know my code is not consuming too much memory

While the 13.04 cycle focus will not be on tooling for an Ubuntu SDK for app developers, we do want to kick off a discussion and ultimately define the criteria we will use to assess each one of the contending technologies and libraries we will include in a future Ubuntu SDK. Also we want to discuss what a future SDK should include in terms of tools, libraries, etc.

All development work items and discussions for Lubuntu 13.04. Some topics for discussions : * Specific testcases * Dropping alternate ISO in favor of netboot install * Discuss release schedule * ...

Openstack grizzly in Ubuntu Its big - who in the team knows which bits and where do we have gaps? -- james-page Rationale: Openstack has been in Ubuntu for 4 releases now and is established and stable. Folsom is the next release of Openstack and Ubuntu should have this release as well. Goal: Include the grizzly release in Ubuntu 13.04 and 12.04

Discuss packaging changes/work for raring.

Checkbox is too complicated. It has a plugable architecture that is flexible in some ways at the cost of being difficult to maintain. We want to simplify the architecture so that it is flexible in ways that matter to users while coping more easily changes. First, we should move the flow of the application from the prompt plugins to the frontend process. This change would make the user interface extensible independently from the backend. As a result, this would make it trivial to run a single test after completing a test run. Second, we should move the responsibility of the remaining plugins to standalone scripts. The command to call the scripts would be configurable to remain flexible. For example, this could be the command to run tests in random order:     checkbox-runner $CHECKBOX_SHARE/jobs/local.txt \     | checkbox-transform --blacklist='plugin=local' \     | checkbox-random Last, we should introduce the concept of a test plan to invalidate forking Checkbox with custom tests. A test plan would have the sorted jobs from a whitelist with their scripts, so any version of checkbox with this support would run the same tests the same way.

As part of this session we should talk about these topics: - Find a way to deal with updating the wiki page in the most painless way. - Investigate how we could get things into Harvest automatically. - Encourage engineers to tag bugs as 'bitesize'."

I have three accessibility items. First, I'd like to drop the HighContrastInverse & LowContrast themes. GNOME dropped support for these two themes late this cycle and they can no longer be set in an unpatched gnome-control-center. The idea is that this one theme will be significantly better than trying to support three mediocre themes. I hacked in support for these themes for 3.6.0 in Ubuntu 12.10 but gnome-themes-standard 3.6.1 isn't building for me yet with the hack. The two dropped themes aren't really terribly usable anyway, and unless someone steps up to maintain them, it's not worth the headache to try to keep them building. My second item is a requested feature. It would be really great if Unity would support the zoom and color effects built in to GNOME 3.6. By setting inverse or adjusting the brightness/contrast this way, all apps (even web pages in your web browser) will respect your color setting. http://bicha.net/img/gnome-zoom1.png http://bicha.net/img/gnome-zoom2.png http://bicha.net/img/gnome-zoom3.png And finally, Unity includes a mostly hidden accessibility status menu. It's probably a good thing it's hidden as it's almost useless at the moment. I filed bug http://pad.lv/1067166 requesting that a replacement be designed and included in 13.04.

A chance for IT managers to share ideas and experiences.

During the Precise cycle, we had a living translation coordinator community with active members who did things done. This has deteriorated during the Quantal cycle because of life, but it would be useful for the ubuntu-translations effort to resurrect the initiative. Possible tasks that need volunteers: - Language pack update management - Translation import management - Bug management - Reviewing the wiki content at https://wiki.ubuntu.com/Translations/ - ?