Trying to improve ISO testing by running some automated testing before image publication.

Roundtable sessions of the Community team.

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

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

Discuss requirements with Desktop Team and others on how the existing Upstart user sessions need to be enhanced to provide suitable facilities to the desktop. = Key Questions = * What needs to be stored in a "session"? (list of entities and data types) * What interfaces are required to such sessions? * Is there a 1-to-1 mapping between users and sessions? * Can/should sessions persist? * Will users be able to manipulate their own session(s)? * What is the maximum amount of memory a session _could_ occupy? (Allowing an arbitrary large amount of data will impact the design). = References = * https://lists.ubuntu.com/archives/ubuntu-desktop/2012-October/003999.html * https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-upstart-session-requirements

The Canonical QA Cop is a cross company team that collaborates on improving the qa process and toolset inside Canonical.

Workshop session for the tools used to run the archive (not including Launchpad) - ubuntu-archive-tools, transition tracker, britney. https://blueprints.launchpad.net/ubuntu/+spec/foundations-r-upload-intermediary

Security Team roundtable discussion. Bring your questions and topics to discuss with the security team.

Query2 was introduced during 12.04 as a new feature for machine read-able format. While the new JSON format describes the images, it is rather unweildy. In light of that, it is proposed to deprecate the new format and introduce a simplified format which is based on request. The new format will return results based on URL, for example: data=cloud&distro=lucid&arch=amd64&stream=server&instance_type=ebs&region=ap-southeast-1 Will return: {     "request": {         "allactive": "1",         "arch": "amd64",         "bad_asks": [],         "cloud": "EC2",         "data": "cloud",         "distro": "lucid",         "instance_type": "ebs",         "region": "ap-southeast-1",         "release_tag": "release",         "stream": "server"     },     "response": [         {             "arch": "amd64",             "build_date": "2012-09-13",             "build_id": "D87316017B9FF4490EF14CB7119E8995",             "build_serial": "20120913",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": true,             "published_date": "2012-09-13",             "published_id": "ami-903575c2",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-903575c2",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-07-26",             "build_id": "9CF68D8D8D3F9B9D529A0BA3FDE64B94",             "build_serial": "20120724",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-07-26",             "published_id": "ami-786d2c2a",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-786d2c2a",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-04-03",             "build_id": "BB64C065F8912EAC3947D7407FCC3F68",             "build_serial": "20120403",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-04-03",             "published_id": "ami-6c6f283e",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-6c6f283e",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-02-21",             "build_id": "98BD8363A17C49562E89D52DF2F05097",             "build_serial": "20120221",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-02-21",             "published_id": "ami-7089cd22",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-7089cd22",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         }     ],     "vendor": {         "name": "Canonical Group, Ltd.",         "product": "Ubuntu Cloud Images",         "product_eula": "http://www.ubuntu.com/project/about-ubuntu/licensing",         "product_url": "http://www.ubuntu.com"     },     "version": {         "epoch": 1348259881,         "uuid": "7c057ef45e1543df8d538bd55d466733"     } } Rationale: Goal:

- Discuss questions for design track. - Go through the design sessions today.

Discuss the platform changes needed to support /opt/ installation for things like Unity .lens and .scope files, dbus .service files and application .desktop files

A discussion of best practices for measuring and reporting power consumption on low power devices. This will include software tools, lab testing environments, and tools for troubleshooting problems.

Audio of all forms (stereo, surround, 3D positional, etc.) must work extremely well in Ubuntu

= Rationale = As described in bug 972077, apt's on-disk format makes it difficult or impossible to update the archive without exposing a race condition to a client. While in theory potentially very small, in reality it makes 'apt' a very weak link in a automated install scenario. = Goal = Make apt hashsum mismatch errors go away permanently, and remove racey conditions when updating apt repositories.

Initially this came out as a discussion on #ubuntu-cloud (or was it #juju?) when swift CDN backed mirrors were announced for Amazon EC2 cloud. It is in a way related to servercloud-q-apt-improvements the hash based apt repositories. Debian has http://snapshot.debian.org/ repository. In essence it has every package, every version, every architecture, ever published in debian (more or less). Furthermore it also makes all of these packages available with standard apt-get, by storing and providing Releases/Packages files made by each publisher run (more or less). Currently in Ubuntu/Launchpad we do not have such facility. It is possible to retrieve individual source&binary packages from launchpadlibrarian, but the whole Ubuntu Archive is not available as of that point in time. Ideally if the Ubuntu Mirror is backed by immutable CDN, it should be relatively cheap to also store and server the repository files over the CDN to create equivalent service like snapshot.debian.org but only for the ubuntu archive. Another use case for this type of mirror would be the archive that currently holds automatically generated dbgsym packages. Currently dbgsym packages are not available for every single version of packages in the archive. And for launchpad/whoopsie/daisy retraces it has been requested to keep all versions of dbgsym packages and not remove them, otherwise retraces fail and we are loosing important information from submitted core dumps. Rationale: Goal:

This will cover 2 parts of the onramp: - Just knowing that you can help - Skill development

I suggested earlier in the Quantal cycle emabling connectivity checking by default; the suggestion brought up quite a lot of interesting discussion which we should bring back at UDS. There are some clear benefits such as being able to handle captive portals more gracefully, but there general idea of being able to know whether an "online" state means having actual Internet access or not brings some benefits, but introduces issues that we need to be prepared to tackle, such as how to reasonably know whether the Internet is reachable, what external servers to use, and how regular traffic generated from this would affect these servers. What needs to be done for connectivity checking to be working properly and efficiently for everyone? How can we make sure privacy and other concerns are taken into account? How can we use connectivity checking to improve the user experience on Ubuntu? Where does connectivity checking tie in to Ubuntu on different form factors? Where could this fail horribly? How can we best test such a feature?

Rationale: (from original description) It would be good to use the upstream "region" panel code and deprecate language-selector next cycle (better to have capplets integrated in system settings than have "launchers" for standalone apps there). Goal: The ubuntu-specific language-selector should be removed as GNOME upstream now provides a suitable alternative. We will maybe need some design input on the ui and to finish the coding part started this cycle. --- From original description: +1. The main missing bit here is integrating the ibus module chooser.

In the Community Roundtable some had a desire to talk about the introduction of the Shopping Lens.

Juju is subject to a rapid development pace, and will continue to do so. We should gate both trunks (python and go) on unit and functional tests passing. This should include some form of the official charm tests. This will require substantial infrastructure to test all providers such as MaaS.

Re-work packaging framework so its easier to work with and maintain. Rationale: Goal:

Ubuntu LoCo team leaders, members and interested parties share and discuss best practices for the creation and maintenance of Ubuntu teams.

The existing ReleaseManifest wiki page used for tracking the images including in a release is high-overhead and requires manual synchronization with the actual build infrastructure. Let's obsolete this with something simpler and auto-generated.

Community building and co-creation with consumers by Troels Lange Andersen, Director at LEGO New Business Group

In the Q cycle alternate CDs have been dropped for some flavours. But there is still one major feature missing from the ubiquity installer - RAID (mdadm) support. This spec will implement RAID support in ubiquity.

Enable various input drivers to provide sensor access on ARM devices (tablets and phones). This includes the following: - camera [PRIORITY] - wifi [PRIORITY] works - bluetooth [PRIORITY] works - touch [PRIORITY] works (single touch) - accelerometer - GPS - compass - NFC - Telephony

Hi! There have been many changes on PackageKit recently. The 0.8.x series broke API, so we are now able to do very clever cache handling in PackageKit backends, also we changed the DBus interaction to be a lot faster and did some improvements on the core, which will also result in increased speed due to less overhead. The new PackageKit also contains the possibility to run transactions in parallel, which provides another speed gain. The frontend API has been simplified, so it is now easier to use and more extendable. Also PackageKit now contains a few cool new features - like systemd-interaction. (inhibiting shutdown on upgrade & showing error messages) Also offline-upgrades are possible, if a recent enough Plymouth version is present. I don't know if these features are wanted in Ubuntu, but at least for the huge improvements made in PackageKit 0.8.x I suggest upgrading it to 0.8.x in the next cycle. Also, it would be very cool if the Aptcc backend of PackageKit (the current default backend) would receive the same improvements on Ubuntu-specific stuff like Aptdaemon did, so that most Ubuntu tools are usable with Aptdaemon and PackageKit. Most Aptd features are already present in PackageKit for a long time and just need implementation in the Aptcc backend. (which currently doesn't cover all features of PackageKit) The most recent PackageKit, including dependent packages, is available in Debian Experimental for testing. Aptd would need to be updated, because it's compatibility-layers will most likely not work with the changes done in PK. Kind regards, Matthias

Follow up on discussion from ubuntu-devel in September about how to improve the upload process for app developers to make it more scalable: https://lists.ubuntu.com/archives/ubuntu-devel/2012-September/035731.html Please note: this specification only focused on applications that are uploaded to the Extras extension repository. Thus, this process does not cover developer uploads of newer versions of software in the existing main archive (which includes the main, restricted, universe and multiverse components). We do want to explore and discuss the best way to provide updates for main archive apps, but those are out of scope for the current revision of the spec.

This session will be used to plan the features of the Xpresser desktop automation tool for the next cycle.

Review the current status of the project, adjusting the spec as necessary, and plan the future development and deployment of the website.

This piece of work is about reporting results from jenkins and utah in a consistent and helpful manner. The QA Team is creating a series of web reports that together will form a QA Dashboard for Ubuntu.

Graphics in general must work extremely well in Ubuntu (OpenGL specifically)

Now that we have the Nexus 7 as a reference device, it is becoming obvious that there would be certain system policies that might be applied to make Ubuntu Desktop behave better on a tablet. For example, it is common on tablet devices to press the power button and expect to instantly suspend the machine, instead of prompting the user for the desired action. We need to create a plan on how to identify and manage these potential policy differences.

Coding to do in Raring

Implement a widget mechanism in Unity. Provide the API for developing widgets. And provide the documentation on the API.

The Canonical hardware certification team will be hosting a session at UDS to plan and gather feedback about the certification programme for Ubuntu and how coverage will evolve during this cycle. As both hardware support in Ubuntu and available hardware continue to evolve, we need to review the elements we test, and the amount to which we test them, to ensure certification testing continues to be relevant for modern hardware while de-emphasizing elements whose usefulness decreases with age. Ubuntu end-users benefit from this effort by having information about which components are tested in Ubuntu-certified systems, which lets them know about the kind of experience they will have out-of-the-box with a Ubuntu-certified system. OEMs can also benefit from this to ensure that tested components work well with Ubuntu, thus ensuring that their systems can get certified and a good experience is provided for users. Canonical benefits from a well-defined and discussed certification coverage list to be able to tell OEMs that the hardware they include in their systems is tested to its full ability when certifying for Ubuntu. == Session overview == The UDS session will be a forum where we will discuss: * A quick overview of a test's lifecycle: blacklist, greylist and whitelist, and how a test moves between them. * A quick review of existing whitelist tests to determine their relevance and any need for improvement. * Quick overview of all tests mentioned in the 12.10 coverage document to see how they will change for 13.04, with review of greylist tests to see which ones will make it on the whitelits * Discussion on new tests to be added (they go in the greylist first) * Discussion on sleep/resume time thresholds for 13.04 == Current greylist == Hibernate/Resume (30 iterations) MMC data cards Hybrid Graphics: if UMA or discrete work out of the box: all ports working the certification will include a note specifying which device was certified. Multiple-Monitor (where supported, multi-head display (2 heads) are tested) Wi-fi Slider (hardware rfkill) Secondary function keys: Brightness Media Control Wireless Sleep Video switch Super key (Windows key) Bluetooth Audio Vertical edge scrolling Specific USB 3.0 devices Lid sensors Lid open HDMI audio Accelerometers Multitouch devices (basic functionality) Resuming from suspend in less than 3 seconds Overall suspend/resume time of less than 10 seconds == Possible new coverage ==  * Displayport audio  * Audio settings maintained after suspend. This means ensuring that user-visible settings don't change in ways that will be confusing, like the microphone (or even speakers) muting themselves for no reason, or changes in user-adjustable volume.  * LEDs  * Bluetooth file transfer  * Bluetooth browse file  * Horizontal scrolling

Servergy unveils new class of hyper-efficient Power Linux ™ Enterprise Server in a Microserver footprint. At under 9lbs, with the foot print of a legal pad of paper. The CTS-1000 is the next generation of high-density high-bandwidth Power Linux enterprise server that operates on up to 80% less power and space. Built on Power Architecture, and offering a variety of Linux distributions and software applications, the servers literally help pay for themselves.

Now that OpenStack has matured even more, High Availability is one of the components on which more concentration is required. HA support for certain components of the infrastructure have been provided in the form of Resource Agents, however, these do not address some of the uses cases. In this session we will discuss the following: HA for RabbitMQ  - Active/Active  - Active/Passive HA for MySQL  - Active/Passive - DRBD  - Active/Active - Galera Quamtum  - quamtum-l3-agent (Active/Passive)  - quamtum-dhcp-agent (Active/Passive)  - quamtum-server (HAProxy) Nova  - nova-api (HAProxy)  - nova-scheduler (HAProxy) Cinder (HAProxy) keystone (HAProxy) Glance (Ceph)  - glance-api  - glance-registry == Other == Ceph  - Pacemaker support Qpid == Resource agents == openstack-resource-agents: - cinder-api - cinder-schedule - cinder-volume - glance-api - glance-registry - keystone - nova-api - nova-cert - nova-consoleauth - nova-network - nova-novnc - nova-scheduler - nova-volume - quantum-agent-dhcp - quantum-agent-l3 - quantum-server ceph-resource-agents

This is a session to track progress of the Ubuntu Youth team throughout the Q cycle, and to plan activities for the R cycle.

Planning the Xubuntu R release.

A whirlwind tour of Ubuntu as used in organisations around the world. Chris Kenyon, Canonical's head of Sales will cover worldwide Ubuntu shipments, thin clients, Ubuntu's work with Openstack and how Canonical helps many of the world's largest companies get better value out of their Ubuntu deployments.

A whirlwind tour of Ubuntu as used in organisations around the world. Chris Kenyon, Canonical's head of Sales will cover worldwide Ubuntu shipments, thin clients, Ubuntu's work with Openstack and how Canonical helps many of the world's largest companies get better value out of their Ubuntu deployments.

HP Plenary

HP Plenary

Update on progress tracking for getting components together for aarch64 support in Ubuntu for the r cycle. Following on from https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-aarch64-porting Areas for development for 13.04: == toolchain == Progress of toolchain support for aarch64-linux-gnu, following on from https://blueprints.launchpad.net/linaro-ubuntu/+spec/aarch64-cross-bootstrap-debian-ubuntu == archive & package set == Progress of aarch64 archive:  * Archive opened for aarch64?  * Bootstrap progress  * Initial package builds   * dependencies of packages we care about, eg:     * apache2     * juju See also:  * https://blueprints.launchpad.net/linaro-ubuntu/+spec/aarch64-cross-bootstrap-debian-ubuntu == kernel == Selection of kernel(s) for aarch64   * assuming vexpress config   * any other ports required in the 13.04 timeframe?

Input devices (joysticks and gamepads), low-latency input and full button support for gaming mice and keyboards must work extremely well in Ubuntu

Decide on images to build for raring.

Review of the current Ubuntu Kernel patch delta from upstream. This session will look at the current delta comprised of both patches to the core and the ubuntu specific drivers. The aim is to record what we are carrying, review the reasons for that component(s) to be carried, and recommend replacements, updates, cleanups, upstreaming etc of those components.

At the Ubuntu Leadership Mini-Summit we want to to provide an opportunity to block off some time to discuss leadership topics and help empower our leadership and governance community to feel empowered to lead in our community.

Design and co-creation, by Frans Joziasse, Director and co-founder of PARK.

Roundtable with an open agenda to discuss any translations-related topics that might not be on the schedule

At the Ubuntu Leadership Mini-Summit we want to to provide an opportunity to block off some time to discuss leadership topics and help empower our leadership and governance community to feel empowered to lead in our community.

Intel to provide an update on UEFI for through 13.04 cycle

A roundtable discussion around MySQL in Ubuntu. Followup from UDS-Q and discussion of work items for this cycle. Rationale: Goal:

The Accomplishments clients consist of the Viewer, Daemon, and Trophy lens, These need to be setup for packaging and submitted to the Universe archive for Ubuntu 13.04.

Deploy and integrate the Ask Ubuntu plugin into the app developer site

GNOME's new Files app (Nautilus) has been a bit controversial. While the devs have admitted that they should have followed GNOME's feature proposal process and the UI had some obvious bugs in the 3.5 snapshots, I think Nautilus 3.6 is a clear improvement for most users. I believe that nautilus 3.8 is the best choice as default file manager for users and for Ubuntu developers for 13.04. I just don't see anything else that has the stability, shared maintenance, and integration with the default desktop that the latest nautilus has. We should come up with a list of specific requirements that we want from Nautilus which we can present to developers. Here's my start: - GtkMenuButton needs to export its menus to dbus for use by the HUD - While F10 opens the new gear menu, there is no keyboard accessible way to access the "view menu" - Traditional keyboard shortcuts like Alt+F, Alt+V, etc. have been dropped, which I'm thinking could cause trouble for accessibility.

We want to discuss and address considerations on obsolescence of libraries during a game's lifetime and how this works in Ubuntu when compared to other platforms

At the Ubuntu Leadership Mini-Summit we want to to provide an opportunity to block off some time to discuss leadership topics and help empower our leadership and governance community to feel empowered to lead in our community.

We now have cross-compilers in Ubuntu, and interesting cross-compilation targets in Ubuntu. It's time to step up the best practices around them and make sure we have a good working solution for the packages that are part of the image.

Define and identify requirements for participation and reporting of test results on a regular basis during the cycle.

Define the work that can be done by members of the Ubuntu community on the TV in the next cycle, set goals and milestones to measure progress along the way, and identify key people and resources within Canonical that will be available.

We need to address possible issues with process cleanup not handling some important actions (e.g. video mode restoration after app exit or crash)

Query2 was introduced during 12.04 as a new feature for machine read-able format. While the new JSON format describes the images, it is rather unweildy. In light of that, it is proposed to deprecate the new format and introduce a simplified format which is based on request. The new format will return results based on URL, for example: data=cloud&distro=lucid&arch=amd64&stream=server&instance_type=ebs&region=ap-southeast-1 Will return: {     "request": {         "allactive": "1",         "arch": "amd64",         "bad_asks": [],         "cloud": "EC2",         "data": "cloud",         "distro": "lucid",         "instance_type": "ebs",         "region": "ap-southeast-1",         "release_tag": "release",         "stream": "server"     },     "response": [         {             "arch": "amd64",             "build_date": "2012-09-13",             "build_id": "D87316017B9FF4490EF14CB7119E8995",             "build_serial": "20120913",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": true,             "published_date": "2012-09-13",             "published_id": "ami-903575c2",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-903575c2",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-07-26",             "build_id": "9CF68D8D8D3F9B9D529A0BA3FDE64B94",             "build_serial": "20120724",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-07-26",             "published_id": "ami-786d2c2a",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-786d2c2a",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-04-03",             "build_id": "BB64C065F8912EAC3947D7407FCC3F68",             "build_serial": "20120403",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-04-03",             "published_id": "ami-6c6f283e",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-6c6f283e",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         },         {             "arch": "amd64",             "build_date": "2012-02-21",             "build_id": "98BD8363A17C49562E89D52DF2F05097",             "build_serial": "20120221",             "build_type": "server",             "cloud_name": "EC2",             "distro_code_name": "lucid",             "distro_name": "Lucid Lynx",             "distro_version": "10.04",             "instance_type": "ebs",             "kernel_id": "aki-11d5aa43",             "latest_build": false,             "published_date": "2012-02-21",             "published_id": "ami-7089cd22",             "published_url": "https://console.aws.amazon.com/ec2/home?region=#launchAmi=ami-7089cd22",             "ramdisk_id": "None",             "region_name": "ap-southeast-1",             "release_tag": "release",             "response_type": "cloud"         }     ],     "vendor": {         "name": "Canonical Group, Ltd.",         "product": "Ubuntu Cloud Images",         "product_eula": "http://www.ubuntu.com/project/about-ubuntu/licensing",         "product_url": "http://www.ubuntu.com"     },     "version": {         "epoch": 1348259881,         "uuid": "7c057ef45e1543df8d538bd55d466733"     } } Rationale: Goal:

- Discuss questions for design track. - Go through design sessions for this day.

Ubiquity can be used on ARM devices either to install (e.g. Panda Boards) or to perform initial user configuration (oem-config mode). What changes are needed for ubiquity? * Lower memory footprint ? * Faster configuration ? * Design changes in steps ? * Fullscreen-mode ? The 12.10 slide decks of ubiquity and oem-config are available here: https://wiki.ubuntu.com/Ubiquity/SlideDecks

What conferences should we attend to run talks, workshops in support of other projects?