BEGIN:VCALENDAR PRODID:-//summit.ubuntu.com//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-TIMEZONE:UTC X-WR-CALNAME:uds-q X-WR-CALDESC:uds-q BEGIN:VEVENT UID:20633 DTSTART:20120507T160000Z DTEND:20120507T165500Z CATEGORIES: SUMMARY:Introduction and Keynote LOCATION:Hall East DESCRIPTION:Mark Shuttleworth and Jono Bacon URL:http://summit.ubuntu.com/uds-q/meeting/20633/introduction-and-keynote/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20590 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES:Foundations SUMMARY:Foundations Roundtable Monday LOCATION:G. Ballroom A DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20590/foundations-roundtable-monday/ X-TYPE:roundtable X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20423 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES:Desktop SUMMARY:Deprecate Language Selector LOCATION:G. Ballroom B DESCRIPTION:That's a leftover from precise but 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 that those "launchers" for standalone apps there).\N\NWe will maybe need some design input on the ui and to finish the coding part started this cycle.\N\N+1. The main missing bit here is integrating the ibus module chooser.\N URL:http://summit.ubuntu.com/uds-q/meeting/20423/desktop-q-deprecate-language-selector/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20369 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES:Cloud & Server SUMMARY:Apt Improvements LOCATION:G. Ballroom C DESCRIPTION:As Ubuntu Server depends more and more heavily on automated usage of apt, we're seeing more and more failures of tests, installs, Juju, MaaS that result from apt mirror or proxy issues or general issues in apt's behavior.\NHere we will address ways we can make Apt more reliable. URL:http://summit.ubuntu.com/uds-q/meeting/20369/servercloud-q-apt-improvements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20491 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES:Other SUMMARY:Qt 5 LOCATION:Jr. Ballroom 1 DESCRIPTION:Technology update, QML2, architecture changes, Ubuntu needs.. URL:http://summit.ubuntu.com/uds-q/meeting/20491/other-q-qt-5/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20456 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES:Hardware SUMMARY:Kernel Team Round Table - Monday LOCATION:Jr. Ballroom 2 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20456/kernel-team-round-table-monday/ X-TYPE:roundtable X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20723 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES:Community SUMMARY:Community Roundtable Monday LOCATION:Room 201 DESCRIPTION:Tasks from daily community roundtable sessions URL:http://summit.ubuntu.com/uds-q/meeting/20723/community-roundtable-monday/ X-TYPE:roundtable X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20609 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES:Security SUMMARY:security-q-roundtable LOCATION:Room 208 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20609/security-q-roundtable/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20655 DTSTART:20120507T170000Z DTEND:20120507T174500Z CATEGORIES: SUMMARY:Sound Theme LOCATION:Room 210-211 DESCRIPTION:In this session we will go through the process we are following to choose a great sound theme for Ubuntu. URL:http://summit.ubuntu.com/uds-q/meeting/20655/sound-theme/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20451 DTSTART:20120507T180000Z DTEND:20120507T185500Z CATEGORIES: SUMMARY:Server Vendor Enhancements for Apport LOCATION:G. Ballroom A DESCRIPTION:Server vendors provide additional tooling for analysis of system crashes. This session is to discuss how these vendors can best integrate their tools into apport. URL:http://summit.ubuntu.com/uds-q/meeting/20451/server-q-apport-enhancements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20289 DTSTART:20120507T180000Z DTEND:20120507T185500Z CATEGORIES:Other SUMMARY:Maintenance and Enhancement of the Arsenal Reports used for tracking bugs LOCATION:G. Ballroom B DESCRIPTION:Rationale:\NScripts are a key part of the quality we want to achieve. So, we need to organize how we develop and use arsenal, to avoid people being bottlenecks in the process or only one person or another to be responsible for all the structure, which doesn't scale.\N\NDefine maintenance schema for reports being used to track bugs that the teams are working on (including but not limited to: http://status.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html).\N\NGoal:\NHave a defined process on how to contribute to arsenal (code reviews, mailing list discussions prior to implementation). Communication improved among people involved with arsenal. Not having scripts failing for days or unexpectedly due to changes known to a few. URL:http://summit.ubuntu.com/uds-q/meeting/20289/other-q-arsenal-report-enhancements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20416 DTSTART:20120507T180000Z DTEND:20120507T185500Z CATEGORIES:Foundations SUMMARY:Plans for Python 3.3 (and 3.4) availability LOCATION:G. Ballroom C DESCRIPTION:Python 3.3 will be released by August 2012, theoretically in time for 12.10. Should we make it available in Quantal, and if so, do we keep Python 3.2 or only support Python 3.3.\N\NLong term, if history is any guide, Python 3.4 could be released by February 2014, which is probably too late for 14.04 LTS, although we make the alphas/betas available early in that cycle and switch to the final release by 14.04 final.\N\NSome arguments for supporting 3.3 in 12.10 include proper support for namespace packages (likely, PEP 420) and built-in virtualenv, among lots of other improvements. Arguments against supporting 3.3 include not being sure that all our packages build against it (especially since it's still in alpha as we speak). Arguments against supporting both 3.2 and 3.3 include the additional disk image space necessary to support both. Arguments for supporting both include a longer and better transition period to a presumably 14.04 LTS world where only Python 3.3 is supported.\N\NWe also need to consider how this will work with Debian, with their planned freeze in June, after which we can't switch the default Python 3 version. URL:http://summit.ubuntu.com/uds-q/meeting/20416/foundations-q-python33/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20498 DTSTART:20120507T180000Z DTEND:20120507T185500Z CATEGORIES:Foundations SUMMARY:Create filesystems for embedded devices LOCATION:G. Ballroom G DESCRIPTION: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.\N\NScope 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). URL:http://summit.ubuntu.com/uds-q/meeting/20498/foundations-q-embedded-rootfs/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20674 DTSTART:20120507T180000Z DTEND:20120507T185500Z CATEGORIES:Cloud & Server SUMMARY:OpenStack HA LOCATION:Jr. Ballroom 1 DESCRIPTION:Discuss HA for OpenStack components (RabbitMQ, MySQL, Keystone, Glance) based on the discussion at the OpenStack Design Summit. URL:http://summit.ubuntu.com/uds-q/meeting/20674/servercloud-q-openstack-ha/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20509 DTSTART:20120507T180000Z DTEND:20120507T185500Z CATEGORIES:Cloud & Server SUMMARY:Juju resource map LOCATION:Room 201 DESCRIPTION:Provider-agnostic descriptions of what a given cloud provides, intersects with constraints URL:http://summit.ubuntu.com/uds-q/meeting/20509/servercloud-q-juju-resource-map/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20584 DTSTART:20120507T180000Z DTEND:20120507T185500Z CATEGORIES:Security SUMMARY:Supporting OpenJDK in stable releases LOCATION:Room 210-211 DESCRIPTION:Discuss transitioning stable releases to latest OpenJDK for security reasons and for successful Panda buildds. Also discuss strategy once OpenJDK 6 goes End of Life in November 2012. URL:http://summit.ubuntu.com/uds-q/meeting/20584/security-q-openjdk/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20231 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Cloud & Server SUMMARY:Eucalyptus updates in 12.10 LOCATION:G. Ballroom A DESCRIPTION:Discussions on euca2ools, the new features in Eucalyptus 3.0, and the soon to be released Open Source Eucalyptus 3.1. URL:http://summit.ubuntu.com/uds-q/meeting/20231/servercloud-q-eucalyptus/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20548 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Community SUMMARY:LoCo Portal Content Review LOCATION:G. Ballroom B DESCRIPTION:As part of the work on the LoCo portal this cycle, we'd like to review the current content in terms of the information we present to newcomers to the site, and ensure the core message of the site and all relevant documentation is up to date.\N\NIn short, we want to ensure that the LoCo portal has prominent additional sections with brief and visually rich information on:\N- What a LoCo team is\N- How to join a LoCo team\N- ... URL:http://summit.ubuntu.com/uds-q/meeting/20548/community-p-loco-portal-content-review/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20385 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Hardware SUMMARY:Certification coverage for 12.10 LOCATION:G. Ballroom C DESCRIPTION:This blueprint is for scheduling purporses only. Please read the full description at:\N\Nhttps://blueprints.launchpad.net/certify-planning/+spec/cert-q-12.10testing\N URL:http://summit.ubuntu.com/uds-q/meeting/20385/cert-q-12.10coverage/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20431 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Desktop SUMMARY:Awareness of existing user configurations in software feature upgrades LOCATION:G. Ballroom F DESCRIPTION:Back when everyone had an xorg.conf and a lot of the X bugs were due to\Nmalformed config files, we would collect the files and run them through\Ncheckers. Brian Murray ran a bot that'd test xorg.confs in bugs posted\Nto launchpad for instance. Found quite a few issues that way. These\Ndays xorg.conf's are rare and hardly anyone hand-edits them so we don't\Ndo this anymore (although maybe we should...)\N\NBut the concept could be applied more generally for config files of all\Nsorts.\N\NThe most effective thing you can do (IMHO) is create apport hooks for\Nevery application that installs a config file, that looks for and\Nattaches that file when a user files a bug via 'ubuntu-bug package'.\NThe hooks are trivial python scripts, basically just:\N\N from apport.hookutils import *\N from os import path\N\N def add_info(report):\N if ui.yesno("Would you like to include your ~/.myconf?"):\N attach_file_if_exists(report, path.expanduser('~/.myconf'), 'MyConf')\N\N[You can omit the yesno prompt if you're absolutely certain there's no\Nchance of sensitive info in the config file, or if you programmatically\Nstrip out or hide that info.]\N\NCopy your hook to /usr/share/apport/package-hooks locally, and test it\Nout yourself. Once you have it working the way you think it should,\Npost it to the package's bug tracker (ubuntu-bug ), and make\Nsure to mark it as a patch. A package maintainer will review and\Nincorporate it into the package.\N\NNext, wait, and let a nice database of config files accumulate in\Nlaunchpad.\N\NThen, run a launchpadlib script to download all the configs. Weed out\Nall the dupes. Keep track of the package version.\N\NNow make a test that iterates through all the config files, launching\Nthe program, and testing if it successfully loads or exits/crashes.\NIf the app has a test suite, bonus, run that too.\N\NFinally, go file bug reports (both in launchpad and upstream) for the\Nfailures that occur.\N URL:http://summit.ubuntu.com/uds-q/meeting/20431/desktop-q-awareness-of-userconfigs-in-upgrade/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20298 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Other SUMMARY:Feedback on Precise Release and Improvements LOCATION:G. Ballroom G DESCRIPTION: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. URL:http://summit.ubuntu.com/uds-q/meeting/20298/other-q-prior-release-feedback/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20579 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Security SUMMARY:AppArmor testing LOCATION:G. Ballroom H DESCRIPTION:Discuss AppArmor upstream test suite, and Ubuntu integration testing. URL:http://summit.ubuntu.com/uds-q/meeting/20579/security-q-apparmor-testing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20715 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Community SUMMARY:Qt Birds of a Feather and Question and Answer LOCATION:Room 202 DESCRIPTION:Q&A / BoF on Qt Project governance, community, contributions, state of the project, etc. URL:http://summit.ubuntu.com/uds-q/meeting/20715/community-q-qt-bof/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20399 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Community SUMMARY:Juju World Tour 2k12 LOCATION:Room 208 DESCRIPTION:Shows we're hitting up. URL:http://summit.ubuntu.com/uds-q/meeting/20399/community-q-juju-conferences/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20407 DTSTART:20120507T190000Z DTEND:20120507T200000Z CATEGORIES:Foundations SUMMARY:Test that migrations are being assisted by m-a LOCATION:Room 210-211 DESCRIPTION:There are multiple bug reports indicating problems with migration-assistant and it being unsuccessful in migrating items for people. There doesn't seem to be much manual testing done of migration-assistant so it would be helpful if we were to setup automated testing somehow.\N\NProblem Bugs\NBug 986161 - imported bookmarks from ubuntu not found\NBug 986730 - nothing transferred from Windows 7\NBug 980676 - migration-assistant encountering multiple users cause ubiquity to crash\NBug 987902 - nothing imported URL:http://summit.ubuntu.com/uds-q/meeting/20407/foundations-q-testing-migration-assistant/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20527 DTSTART:20120507T210000Z DTEND:20120507T211500Z CATEGORIES: SUMMARY:How Ubuntu and Canonical work with OEMs LOCATION:Hall East DESCRIPTION:Chris Kenyon URL:http://summit.ubuntu.com/uds-q/meeting/20527/how-ubuntu-and-canonical-work-with-oems/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20528 DTSTART:20120507T211500Z DTEND:20120507T213000Z CATEGORIES: SUMMARY:HP with Bdale Garbee LOCATION:Hall East DESCRIPTION:HP URL:http://summit.ubuntu.com/uds-q/meeting/20528/hp-part-i/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20529 DTSTART:20120507T213000Z DTEND:20120507T214500Z CATEGORIES: SUMMARY:HP with Bdale Garbee LOCATION:Hall East DESCRIPTION:HP URL:http://summit.ubuntu.com/uds-q/meeting/20529/hp-part-2/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20535 DTSTART:20120507T214500Z DTEND:20120507T220000Z CATEGORIES: SUMMARY:juju Charm Store LOCATION:Hall East DESCRIPTION:Marco Ceppi URL:http://summit.ubuntu.com/uds-q/meeting/20535/juju-charm-store/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20355 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Other SUMMARY:Zentyal power management LOCATION:G. Ballroom B DESCRIPTION:A previously proposed task within the power-management blueprint that was postponed, implement a NUT module for Zentyal to manage UPS on standalone servers.\N\Nhttps://lists.ubuntu.com/archives/ubuntu-server-bugs/2011-July/058794.html URL:http://summit.ubuntu.com/uds-q/meeting/20355/other-zentyal-ups-management/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20383 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Hardware SUMMARY:New Toolkit for Distributed Testing LOCATION:G. Ballroom C DESCRIPTION:Planning the design of a distributed testing toolkit for Desktop and Laptop hardware. This new toolkit will allow users to access both local and remote resources. Tests can be executed across networks, providing both SUT status and test result reporting.\N\NReasoning:\NThe current tools available for hardware testing are complex and difficult to maintain. This makes feature enhancement slow. There is a need to replace existing tools with a more powerful suite. The largest change to the current set of suites required by the teams involved is remote execution and reporting. The flexibility to execute tests on systems from a centralized location is valuable in both time and resources. In addition, the support for differing workflows is desirable. By making the new suite a library, any number of interfaces can be written to exercise those options. This provides the teams using the library to easily build an interface that exactly meets their needs and process.\N\NWork so far:\NA team of engineers from Canonical has begun work on a python library with the capabilites to execute tests across private networks just as easily as you would on a local system. Prototyping of the basic features is complete and a demo of this prototype will be presented in this session. URL:http://summit.ubuntu.com/uds-q/meeting/20383/hardware-q-distributed-testing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20741 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Foundations SUMMARY:Identify impact of the switch to pure live images for ARM platforms LOCATION:G. Ballroom F DESCRIPTION:For 12.10 we will switch the ARM images from preinstalled to be normal live images.\NThis session is not for discussing technical bits of this change but to get all stakeholders\Nusing the preinstalled images together to discuss the possible impact of this move. URL:http://summit.ubuntu.com/uds-q/meeting/20741/foundations-q-drop-preinst-images/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20450 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Hardware SUMMARY:Test Drive Different Tablet UIs - User Experiences LOCATION:G. Ballroom H DESCRIPTION:A "tablet test-drive" session to encourage Ubuntu-related tablet (and touch screen) development: multiple tablets will be on hand running the following UIs:\N\N- Ubuntu / Unity\N- Ubuntu / Gnome\N- Kubuntu Active (KDE Plasma Active UI)\N- WeTab (MeeGo base OS)\N- Android\N- Windows 8\N\NWe'll set tablets side-by-side and let developers try them: the idea would be to compare and contrast the various tablet UIs to spur (and, hopefully, accelerate) innovation in Ubuntu's tablet OS. URL:http://summit.ubuntu.com/uds-q/meeting/20450/hardware-q-tablet-test-drive/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20627 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Cloud & Server SUMMARY:Xen work for Q-series LOCATION:Jr. Ballroom 2 DESCRIPTION:We would like to have a discussion about providing better integration between Xen and Ubuntu. URL:http://summit.ubuntu.com/uds-q/meeting/20627/servercloud-q-xen/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20745 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Design SUMMARY:Design Theatre LOCATION:Room 201 DESCRIPTION:Discussion of design issues you may have in your software. URL:http://summit.ubuntu.com/uds-q/meeting/20745/design-theatre/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20709 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Desktop SUMMARY:Control of TV from a local network LOCATION:Room 202 DESCRIPTION:A session to discuss the options surround control of an Ubuntu TV from a local network. Example: a remote control app on another device and an EPG guide on another device. URL:http://summit.ubuntu.com/uds-q/meeting/20709/desktop-q-tv-control/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20342 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Foundations SUMMARY:What can or must we do for UDD in the Q cycle? LOCATION:Room 208 DESCRIPTION:Ubuntu Distributed Development (UDD) is a great way to develop packages for Ubuntu using the Bazaar dVCS. While great progress has been made in previous cycles, there are still some warts around quilt packages and the importer. There may also be other issues we'd like to address for the Q cycle. This session will identify the top needs for Ubuntu developers and attempt to round up resources (both inside and outside Canonical) to tackle the biggest blockers. URL:http://summit.ubuntu.com/uds-q/meeting/20342/foundations-q-udd/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20322 DTSTART:20120507T220000Z DTEND:20120507T230000Z CATEGORIES:Other SUMMARY:Dell Devops Community Feedback LOCATION:Room 210-211 DESCRIPTION:BoF/Discussion on things community developers would want in a devops machine that came with Ubuntu. URL:http://summit.ubuntu.com/uds-q/meeting/20322/other-dell-devops-community-feedback/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20236 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:Hardware SUMMARY:Kernel Version and Flavors LOCATION:G. Ballroom A DESCRIPTION:Discussions on the likely mainline kernel version and appropriate kernel flavors for Q.\N\NThe current list of arch's and flavor's for Precise are listed below.\N\NDistro - Precise 12.04\N\NArch: Flavour -- Description\N\Ni386: generic -- kernel for desktop machines with less than 4GB of ram\Ni386: generic-pae -- kernel for desktop machines with more than 4GB of ram\Ni386: virtual -- kernel for virtual machine use (KVM/EC2)\N\Namd64: generic -- kernel for desktop/server machines\Namd64: virtual -- kernel for virtual machine use (KVM/EC2)\N\Narmel/armhf: omap -- kernel for ARM OMAP-3 hardware\Narmel/armhf: omap4 -- kernel for ARM OMAP-4 hardware\N\NPorts - Precise 12.04\N\NArch: Flavour -- Description\N\Npowerpc: powerpc-smp -- PowerPC with SMP support\Npowerpc: powerpc64-smp -- PowerPC64 with SMP support URL:http://summit.ubuntu.com/uds-q/meeting/20236/hardware-q-kernel-version-and-flavors/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20331 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:Foundations SUMMARY:A better publishing mechanism for Wubi LOCATION:G. Ballroom B DESCRIPTION:Right now, Wubi is built locally, then uploaded by Evan to http://people.canonical.com/~evand/wubi . This has meant that, on occasion, changes to grub that affect Wubi users, as well as milestone CD builds block on Evan.\N\NWe should fix this bottleneck by making publishing of new Wubi binaries an automated process. This should, if possible, also sign the Wubi binary. URL:http://summit.ubuntu.com/uds-q/meeting/20331/foundations-q-wubi-publishing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20408 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:Community SUMMARY:Upstream App Developer Documentation LOCATION:G. Ballroom C DESCRIPTION:Identify tutorials and documentation needed by upstream developers to port and integrate their applications with Ubuntu and Unity URL:http://summit.ubuntu.com/uds-q/meeting/20408/community-q-upstream-appdev-docs/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20464 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:QA SUMMARY:QA community structuring and needs LOCATION:G. Ballroom F DESCRIPTION:Discussing communication strategies, interactions with sister communities and team organization, recruitment and recognition URL:http://summit.ubuntu.com/uds-q/meeting/20464/qa-q-community/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20578 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:Security SUMMARY:AppArmor development LOCATION:G. Ballroom H DESCRIPTION:Discuss where to focus AppArmor development and integration efforts URL:http://summit.ubuntu.com/uds-q/meeting/20578/security-q-apparmor-dev/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20673 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:Cloud & Server SUMMARY:Openstack Juju Charms Next Steps LOCATION:Jr. Ballroom 1 DESCRIPTION:Discuss current state of the Juju charms for deploying Openstack on Ubuntu and define what is needed to cover new Openstack components being added during Folsom/Quantal.\N URL:http://summit.ubuntu.com/uds-q/meeting/20673/servercloud-q-openstack-charms/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20493 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:Foundations SUMMARY:Secure distribution of third-party .debs LOCATION:Jr. Ballroom 2 DESCRIPTION:Care has been taken over the years to ensure that clicking a link to an executable on a website doesn't cause untrusted code to be run, and that all package downloads from the Ubuntu archive and from PPAs can be done securely. But lots of community and third-party documentation directs users to download unsigned .debs from websites and install them, and software center facilitates this. We need to examine the security around third-party packages. URL:http://summit.ubuntu.com/uds-q/meeting/20493/foundations-q-security-of-third-party-debs/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20593 DTSTART:20120507T231500Z DTEND:20120508T000000Z CATEGORIES:Desktop SUMMARY:Kubuntu Quantal Development LOCATION:Room 201 DESCRIPTION:Coding to do in Quantal URL:http://summit.ubuntu.com/uds-q/meeting/20593/kubuntu-q-development/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20474 DTSTART:20120508T000500Z DTEND:20120508T010000Z CATEGORIES:Cloud & Server SUMMARY:OpenStack Deployment on ARM Server LOCATION:G. Ballroom A DESCRIPTION:The goal of this blueprint is to ensure OpenStack is able to be deployed on ARM server hardware. URL:http://summit.ubuntu.com/uds-q/meeting/20474/servercloud-q-openstack-deployment-on-arm/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20354 DTSTART:20120508T000500Z DTEND:20120508T010000Z CATEGORIES:Other SUMMARY:Making Zentyal more Ubuntu ecosystem friendly LOCATION:G. Ballroom B DESCRIPTION:Is not an easy task for packages that provide integration between other packages in the archive to be policy compliant. According to the Ubuntu policy a package cannot modify other package's configuration files. Some\Ntechniques has been introduced to help on this task, from dotdee [0] to augeas [1], discuss with other developers how to deal with this situation that also affects other configuration management software like\Npuppet, juju, etc.\N\N[0] http://blog.dustinkirkland.com/2011_04_01_archive.html\N[1] http://augeas.net/ URL:http://summit.ubuntu.com/uds-q/meeting/20354/other-zentyal-ubuntu-conf-management/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20234 DTSTART:20120508T000500Z DTEND:20120508T010000Z CATEGORIES:Foundations SUMMARY:Improvements to the ISO tracker and some build related scripts LOCATION:G. Ballroom C DESCRIPTION:Discussion of changes that would help:\N - release team with managing and publishing images, understanding \N the quality/shipability\N - qa teams (ubuntu and flavors) for understanding quality of images and issues for\N developers\N - testers ease of using system, logging results, automated logging, knowing bugs URL:http://summit.ubuntu.com/uds-q/meeting/20234/foundations-q-iso-tracker/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20754 DTSTART:20120508T000500Z DTEND:20120508T010000Z CATEGORIES: SUMMARY:What exactly is juju anyway? LOCATION:G. Ballroom H DESCRIPTION:A primer on what juju is for the common person. URL:http://summit.ubuntu.com/uds-q/meeting/20754/what-exactly-is-juju-anyway/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20545 DTSTART:20120508T000500Z DTEND:20120508T010000Z CATEGORIES:Community SUMMARY:App Developer events LOCATION:Jr. Ballroom 1 DESCRIPTION:Promote and run a successful series of online app developer events, including at least:\N- The Ubuntu App Developer Week\N- The Ubuntu App Developer Contest URL:http://summit.ubuntu.com/uds-q/meeting/20545/community-p-appdevelopers-events/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20297 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Foundations SUMMARY:Requirements for implementation of $XDG_RUNTIME_DIR on the desktop LOCATION:G. Ballroom A DESCRIPTION:The $XDG_RUNTIME_DIR fd.o spec has received criticism on the FHS mailing list due to implementation bugs that allow non-root users to DoS the /run directory. Discuss what's required for a solution in Ubuntu. URL:http://summit.ubuntu.com/uds-q/meeting/20297/foundations-q-xdg-runtime-dir/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20742 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:QA SUMMARY:Testing strategies for the user space networking stack LOCATION:G. Ballroom B DESCRIPTION:Testing strategies for user-space testing of the network stack (network manager, etc). URL:http://summit.ubuntu.com/uds-q/meeting/20742/testing-strategies-for-the-user-space-networking-stack/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20586 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES: SUMMARY:software-center-q-client LOCATION:G. Ballroom C DESCRIPTION:Plans for the software-center client URL:http://summit.ubuntu.com/uds-q/meeting/20586/software-center-q-client/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20719 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Other SUMMARY:Backports BoF LOCATION:G. Ballroom F DESCRIPTION:Talk about backports, including joining the backports team. URL:http://summit.ubuntu.com/uds-q/meeting/20719/other-q-backports-bof/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20710 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Desktop SUMMARY:Discussion of GStreamer in Ubuntu TV LOCATION:G. Ballroom G DESCRIPTION:A discussion of the use of GStreamer in Ubuntu TV taking into account any existing third-party GStreamer sources and sinks. URL:http://summit.ubuntu.com/uds-q/meeting/20710/desktop-q-tv-gstreamer/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20330 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Foundations SUMMARY:Detail and begin the arm64/aarch64 port in Ubuntu LOCATION:G. Ballroom H DESCRIPTION:We need to start thinking about (and working on) the aarch64/arm64 port in Debian and Ubuntu, this spec should ultimately list what we know, what we need to know, what we need to be working on, how, and when. URL:http://summit.ubuntu.com/uds-q/meeting/20330/foundations-q-aarch64-porting/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20323 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Cloud & Server SUMMARY:MySQL RoundTable LOCATION:Jr. Ballroom 1 DESCRIPTION:A round table discussion around MySQL in Ubuntu.\N URL:http://summit.ubuntu.com/uds-q/meeting/20323/servercloud-q-mysql-roundtable/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20457 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Hardware SUMMARY:Kernel Team Round Table - Tuesday LOCATION:Jr. Ballroom 2 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20457/kernel-team-round-table-tuesday/ X-TYPE:roundtable X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20608 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Other SUMMARY:Bug Report Shadow Database Planning LOCATION:Room 201 DESCRIPTION:Rationale:\NMultiple teams are working on reports using .json files obtained from Arsenal. We're looking for a better way to maintain a stateful, historical bug database without stressing the launchpad server.\N\NGoal:\NAgree in a way of persisting launchpad data "locally", being that the source of data for reports. Implement that. URL:http://summit.ubuntu.com/uds-q/meeting/20608/other-q-bug-report-shadow-database/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20724 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Community SUMMARY:Community Roundtable Tuesday LOCATION:Room 202 DESCRIPTION:Tasks from daily community roundtable sessions URL:http://summit.ubuntu.com/uds-q/meeting/20724/community-roundtable-tuesday/ X-TYPE:roundtable X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20610 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Security SUMMARY:security-q-roundtable LOCATION:Room 208 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20610/security-q-roundtable/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20595 DTSTART:20120508T160000Z DTEND:20120508T165500Z CATEGORIES:Desktop SUMMARY:Kubuntu Quantal Future LOCATION:Room 210-211 DESCRIPTION:Things needing changed to keep everyone happy and friendly in the future for kubuntu\N URL:http://summit.ubuntu.com/uds-q/meeting/20595/kubuntu-q-future/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20512 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Hardware SUMMARY:Firmware Test Suite Improvements for 12.10 LOCATION:G. Ballroom A DESCRIPTION:List of features and improvements for the Firmware Test Suite for Ubuntu 12.10 URL:http://summit.ubuntu.com/uds-q/meeting/20512/hardware-q-fwts-improvements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20389 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Cloud & Server SUMMARY:Ceph Object Integration with OpenStack LOCATION:G. Ballroom B DESCRIPTION:This session is to discuss providing object storage in OpenStack deployments with ceph. The blueprint is used for tracking work needed to be done in order to accomplish this. This includes charms, relevant packaging, and testing needed. URL:http://summit.ubuntu.com/uds-q/meeting/20389/servercloud-q-ceph-object-integration/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20425 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Desktop SUMMARY:GNOME Plans Review LOCATION:G. Ballroom F DESCRIPTION:Hey,\N\NNot sure how much we need to discuss but it's always good to have a GNOME checkpoint session.\N\NIt's likely that this cycle we will not "hold back" on things we kept behind until now, which means we need to bring clutter on the CD and see how we do that and what it means (do we need extra testing on some platforms during the cycle, how will it work for people not having 3d working, etc).\N\NSome other desktopish topics I would like to discuss, not sure if that's the right session but since we will probably have time in that one:\N\N- our delta with upstream and Debian and how we could lower it? mpt suggested that "launchpad-integration" items are quite "geeky", they also create most of our diff over Debian and extra work and don't really "scale" since they require sources patching, maybe it's time to discussion dropping that?\N\N- tools, though UDD didn't change a lot so I don't think the consensus will be any different from what it was other cycles\N\N- whatever other topics you guys come with ;-) URL:http://summit.ubuntu.com/uds-q/meeting/20425/desktop-q-gnome-plans-review/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20716 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Community SUMMARY:Ubuntu Accomplishments Development Planning LOCATION:G. Ballroom G DESCRIPTION:This specification is to plan the work of the Ubuntu Accomplishments releases over the coming release cycle.\N\NGoals discussed so far include:\N\N * Maturing our API. you can see a list of these goals at https://wiki.ubuntu.com/Accomplishments/NewAPI\N * Getting Local Accomplishments support to a level of quality that matches Global Accomplishments.\N * Expanding our help and guidance for how to get started using the system.\N\NPlease join the session, particularly if you are interested in contributing to the project. URL:http://summit.ubuntu.com/uds-q/meeting/20716/community-q-ubuntu-accomplishments-development-planning/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20682 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Community SUMMARY:Continuing Packaging Guide Improvements LOCATION:G. Ballroom H DESCRIPTION:The Packaging Guide has seen a lot of changes and improvements of the past few cycles. Let's keep this momentum going and discuss next steps. URL:http://summit.ubuntu.com/uds-q/meeting/20682/community-q-packaging-guide/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20626 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Foundations SUMMARY:Refine our SRU process to be more agile while avoiding too many pitfalls LOCATION:Jr. Ballroom 2 DESCRIPTION:Our current SRU process is perhaps slightly over-engineered as a reaction to the fact that out previous SRU process was almost certainly far too lightweight. While there's (I hope obvious to all) value in documentation, audit trails, regression testing, and "bake-in" periods, our current process makes it somewhat difficult to get urgent fixes out quickly, while also discouraging the casual observer with an "obviously-correct" 2-character patch from making contributions to stable releases.\N\NWe don't want to throw the babies out with the bathwater here, but we need to discuss ways we can make the process more agile while still keeping it robust enough to avoid making serious mistakes along the way. URL:http://summit.ubuntu.com/uds-q/meeting/20626/foundations-q-more-agile-sru-process/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20568 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Desktop SUMMARY:Running LibreOffice testsuites for Ubuntu q-series LOCATION:Room 201 DESCRIPTION:Running LibreOffice 3.6 testsuites on Ubuntu Q for continuous integration. URL:http://summit.ubuntu.com/uds-q/meeting/20568/desktop-q-libreoffice-qa-testsuites/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20546 DTSTART:20120508T170000Z DTEND:20120508T174500Z CATEGORIES:Community SUMMARY:App Developer external outreach LOCATION:Room 203 DESCRIPTION:We want to increase the visibility and awareness of Ubuntu app development outside of the regular Ubuntu channels.\N\NThis blueprint will serve to discuss initiatives and plan an external outreach campaign. One of the first initiatives will be a series of articles published to a set of targetted media sites or print publications not directly associated with Ubuntu. URL:http://summit.ubuntu.com/uds-q/meeting/20546/community-p-appdevelopers-external-outreach/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20530 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES: SUMMARY:State of the Server LOCATION:G. Ballroom A DESCRIPTION:Robbie Williamson URL:http://summit.ubuntu.com/uds-q/meeting/20530/state-of-the-server/ X-TYPE:plenary X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20378 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Hardware SUMMARY:Improve certification testsuite, tools and processes for external testing LOCATION:G. Ballroom B DESCRIPTION:External testing, that is, the testing performed outside of Canonical\Ncertification labs, is a significant part of all the testing\Nactivities around Ubuntu that is growing on every cycle.\N\NIt is becoming more common that people outside the certification team\Nwant to run our certification tools and tests, to either submit\Nresults to Friendly, test their systems, or check if a system would\Npass certification.\N\NAs part of the continuous improvement practices currently in place,\Nthe certification team will focus on enhancing the user experience for\Nexternal testers for both desktop and server, so that they can run\Ntest cases with the maximum coverage (both for hardware and software)\Nand report problems effectively.\N\NThe areas that have been identified to work on during the next cycle\Nare the following ones:\N\N== Test case usability improvement ==\N\NSome test cases executed internally in the laboratory assume the\Npresence of devices and configurations needed to run them\Nsmoothly. Unfortunately, when these test cases are executed in a\Ndifferent environment, they fail and cannot be used unless all the\Nprerequisites are properly fulfilled.\N\N* We need to take into account that for the external whitelist is\N going to be run outside the lab, so we cannot make assumptions on\N configuration\N\N* Automate as much as possible to get rid of any assumption and also\N run the test cases on any system that matches a minimal set of\N requirements.\N\N* Provide guidelines either in the documentation or the test case\N description to configure the environment properly when full\N automation isn't attainable.\N\N* Improve general usability of the testcases, to allow people less\N familiar with the tools, to run the test suite without having to ask\N questions.\N\N== Documentation ==\N\NDocumentation is intended to solve any doubt that could prevent a\Ntesting session from finishing properly with the submission of results\Nand the reporting of the problems found.\N\N* Create a document that describes the procedure to run test cases\N using the external whitelist in a desktop.\N\N* Update the document for the server that was created in the previous\N cycle. This includes, for example, adding a section about how to\N troubleshoot problems. For instance, what to do if a test case\N doesn't work as expected, the test results cannot be submitted, etc.\N\N* Create training material for TAMs and customers, so that they can\N get some hands-on experience before certifying a device for a given\N release for the first time.\N\N* Provide guidelines either in the documentation or the test case\N description to configure the environment properly when full\N automation isn't attainable.\N\N== Whitelist coverage ==\N\NThe different set of test cases between the internal and the external\Nwhitelist, causes that the coverage achieved depends on the whitelist\Nexecuted when it shouldn't be the case.\N\N* Review both whitelists and make sure that they provide the same\N amount of coverage.\N\N* When the improvements on test case automation aren't enough to get\N the desired coverage, create alternative and easy to configure test\N cases that can be used to test the same capability/feature in a\N different environment.\N\N== User interface usability ==\N\NThe new Qt interface is a step forward in terms of having a modern\Ninterface that looks appealing to users. However, we have to make sure\Nthat it lives up to the expectations of testers.\N\N* Review the interactions required to run test cases and solve any\N issue that prevents the tester from having a good experience that\N encourages collaboration and makes reporting problems easy. For\N example, look at the consistency of buttons when marking a test\N cases as passed/failed/skipped.\N URL:http://summit.ubuntu.com/uds-q/meeting/20378/cert-q-external-testing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20658 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Foundations SUMMARY:Evidence-based development through metrics collection LOCATION:G. Ballroom F DESCRIPTION:How often does the installation fail? How do we know which language packs to include on the CDs? What hardware is suspend and resume still not working on? URL:http://summit.ubuntu.com/uds-q/meeting/20658/foundations-q-metrics/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20484 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Other SUMMARY:Launchpad Clinic LOCATION:G. Ballroom G DESCRIPTION:Hands on help with Launchpad bugs and getting involved in contributing to Launchpad URL:http://summit.ubuntu.com/uds-q/meeting/20484/launchpad-clinic/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20575 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES: SUMMARY:Lubuntu work items for Q LOCATION:G. Ballroom H DESCRIPTION:All development work items for Lubuntu 12.10 URL:http://summit.ubuntu.com/uds-q/meeting/20575/lubuntu-q-work-items/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20794 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES: SUMMARY:ubuntu-based openstack distro with integrated glusterfs LOCATION:Jr. Ballroom 1 DESCRIPTION:GlusterFS 3.3 brings significant improvements in the cloud area, with better support for VM image storage, as well as object storage and an HDFS compatibility library. We think this release will be useful for OpenStack deployments, and we'd like to create an integrated stack that utilizes GlusterFS - both for object storage (Swift interface) and VM image storage. URL:http://summit.ubuntu.com/uds-q/meeting/20794/gluster-cloud/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20573 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Desktop SUMMARY:General X.org plans for Quetzal LOCATION:Jr. Ballroom 2 DESCRIPTION:The biannual catch-all X discussion session. If you are involved in a project that directly depends on the X stack, or needs a particular feature from the stack, come along. URL:http://summit.ubuntu.com/uds-q/meeting/20573/desktop-q-xorg-general/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20432 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Desktop SUMMARY:Keybindings Health Check LOCATION:Room 202 DESCRIPTION:We had tried to get some shortcut changes during the Precise cycle. Some successfully, some were not (like changing the "change worspace " keybindings).\N\NI propose a healthy check session/discussion with the design team to see what changes will be done for 12.10, what we need to expose on gnome-control-center, reviewing what we already expose there. Also, what changes are needed on the window manager side to propose more than one (configurable) keybinding to not break past conventions with new proposed ones. URL:http://summit.ubuntu.com/uds-q/meeting/20432/desktop-q-keybindings-health-check/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20628 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Foundations SUMMARY:Session Management & Multiseat LOCATION:Room 203 DESCRIPTION:= Summary =\N\NThe Desktop Team have a requirement for Multiseat support. Currently, ConsoleKit is used to handle sessions but has issues:\N\N- it's apparently unmaintained\N- requires $XDG_SESSION_COOKIE.\N\NFedora now uses a facility called 'logind' which replaces ConsoleKit and uses cgroups and PAM to provide X session and terminal session and seat management.\N\NThis session is to:\N\N(1) Discuss the plan regarding either making use of logind, updating ConsoleKit or writing our own tool.\N(2) Identify a list of requirements on a ConsoleKit successor.\N\N= References =\N\N- http://www.x.org/wiki/Development/Documentation/Multiseat\N- http://www.freedesktop.org/wiki/Software/ConsoleKit URL:http://summit.ubuntu.com/uds-q/meeting/20628/foundations-q-session-management/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20337 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Cloud & Server SUMMARY:Juju Formal Release Process LOCATION:Room 204 DESCRIPTION:This thread proposes a release process for Juju:\N\Nhttps://lists.ubuntu.com/archives/juju/2012-April/001431.html\N\NThe basics:\N\N* Keep it simple\N* 6 weeks of open trunk\N* 1 week of stabilization\N* 1 week of testing/critical fixing reserved\N* Aim to drop releases before FeatureFreeze in Ubuntu\N* Release series minor version bumped if backward incompatible changes are made\N* Semantic versions adopted (starting at 0.5.0 which is the version of juju in lp:juju when release process starts) URL:http://summit.ubuntu.com/uds-q/meeting/20337/servercloud-q-juju-release-process/ X-TYPE:discussion X-ROOMNAME:room-204 END:VEVENT BEGIN:VEVENT UID:20411 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES:Community SUMMARY:Ubuntu platform API documentation LOCATION:Room 208 DESCRIPTION:Identify which APIs need to be documented for application developers and ways in which we can provide these APIs in a developer friendly way URL:http://summit.ubuntu.com/uds-q/meeting/20411/community-q-platform-docs/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20654 DTSTART:20120508T180000Z DTEND:20120508T185500Z CATEGORIES: SUMMARY:Password selection LOCATION:Room 210-211 DESCRIPTION:There are currently some issues changing password in Ubuntu using a simple one. On the other end, we are introducing devices with a different type of security and input.\N\NThe purpose of this session is to discuss the current issue in Ubuntu Desktop and brainstorm solution for new form factors and if and how these can be linked. URL:http://summit.ubuntu.com/uds-q/meeting/20654/password-selection/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20325 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:Cloud & Server SUMMARY:Utilities to work with MySQL. LOCATION:G. Ballroom B DESCRIPTION:This blueprint is to discuss the work need to add MySQL Utilities package to Debian and Ubuntu. URL:http://summit.ubuntu.com/uds-q/meeting/20325/servercloud-q-mysql-utilities/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20718 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:Other SUMMARY:Installer Slideshow checkup and planning LOCATION:G. Ballroom C DESCRIPTION:The installer slideshows for *buntu 12.04 worked out great, and with an LTS behind us now is a great opportunity to take a breath and look around. It's time to think back to what has gone well over the last few releases, and what we can improve.\N\NThere are lots of different slideshow projects built in to one, so it would be great if we can all put our heads together and get a feel for the effort as a whole — where this is working and where it isn't. So, if you happen to be reponsible for one of the many installer slideshows, please drop by!\N\NWith this session, we're going to plan for the next few releases and, hopefully, we can build a sturdier project structure than we have had for the past few releases. This is also an opportunity to think about more elaborate, project-wide features such as screenshot localization, and better localization in general. URL:http://summit.ubuntu.com/uds-q/meeting/20718/installer-slideshow-checkup-and-planning/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20587 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES: SUMMARY:software-center-q-server LOCATION:G. Ballroom F DESCRIPTION:Plans for the software-center server URL:http://summit.ubuntu.com/uds-q/meeting/20587/software-center-q-server/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20463 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:QA SUMMARY:Expanding and Refining Manual Application Testing LOCATION:G. Ballroom G DESCRIPTION:Discussing options for improving manual testing, metrics, and user feedback for those running the development version of ubuntu URL:http://summit.ubuntu.com/uds-q/meeting/20463/qa-q-manual-app-testing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20574 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:Desktop SUMMARY:Supporting USB video devices LOCATION:G. Ballroom H DESCRIPTION:USB video devices (DisplayLink, among others) are technically supported by the Ubuntu X stack, but in practice are difficult to set up and finicky. What are the important use-cases for USB video, and can we make them less painful? URL:http://summit.ubuntu.com/uds-q/meeting/20574/desktop-q-xorg-usb-video-support/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20557 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:Community SUMMARY:Transition help.ubuntu.com to SUMO LOCATION:Jr. Ballroom 1 DESCRIPTION:Mozilla SUMO is the product that powers support.mozilla.org and we are aiming to transition help.ubuntu.com in its entirety to SUMO in the Q-Cycle or at the very least get excellent work done towards that goal. URL:http://summit.ubuntu.com/uds-q/meeting/20557/community-q-docteam/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20550 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:Desktop SUMMARY:Backup 12.10 Enhancements LOCATION:Room 201 DESCRIPTION:Déjà Dup Backup Tool has some ambitious long-term changes. This is a discussion of what we can do this cycle, what people can do to help, and feedback about both the current state and planned changes. URL:http://summit.ubuntu.com/uds-q/meeting/20550/desktop-q-deja-dup/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20659 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:Foundations SUMMARY:LXC containers introduction, demo and q&a session LOCATION:Room 208 DESCRIPTION:It was originally planned to have a plenary session at UDS to show some of the improvements that happened to LXC and containers in general over the past cycle. Unfortunately, the schedule being already full, this plenary won't happen.\N\NI'd appreciate if this session could be scheduled early in the week and before the actual LXC session.\N\NHere's the agenda for this session:\N - Quick introduction to LXC and containers\N - Presentation of the current features and what was added during the 12.04 cycle\N - Some use cases for containers for developers and in a production environment\N - A demo of Ubuntu 12.04's LXC\N - Q&A and open discussion\N\NThis session is aimed at anyone with an interest in LXC and containers. During the session you should learn enough to start using LXC in your everyday work.\NIdeas resulting from the Q&A and open discussion part of this session will be added to the other LXC session later in the week where we'll define the final roadmap for 12.10. URL:http://summit.ubuntu.com/uds-q/meeting/20659/foundations-q-containers-demo/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20453 DTSTART:20120508T190000Z DTEND:20120508T200000Z CATEGORIES:Community SUMMARY:Juju Charm Workflow Improvements LOCATION:Room 210-211 DESCRIPTION:We should review all our charm processes and make sure they are low-barrier. We also need to figure out github integration. URL:http://summit.ubuntu.com/uds-q/meeting/20453/community-q-juju-charm-workflow/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20531 DTSTART:20120508T210000Z DTEND:20120508T211500Z CATEGORIES: SUMMARY:Ubuntu at Google LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20531/google-part-1/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20532 DTSTART:20120508T211500Z DTEND:20120508T213000Z CATEGORIES: SUMMARY:ubuntu at google LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20532/google-part-2/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20539 DTSTART:20120508T213000Z DTEND:20120508T214500Z CATEGORIES: SUMMARY:Ubuntu Derivatives LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20539/ubuntu-derivatives/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20538 DTSTART:20120508T214500Z DTEND:20120508T220000Z CATEGORIES: SUMMARY:Ubuntu Community LOCATION:Hall East DESCRIPTION:Accomplishing an awesome app developer community URL:http://summit.ubuntu.com/uds-q/meeting/20538/ubuntu-community/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20492 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Other SUMMARY:Qt Media Hub LOCATION:G. Ballroom A DESCRIPTION:QML/Qt5 in use, example discussion, graphical effects, etc. URL:http://summit.ubuntu.com/uds-q/meeting/20492/other-q-qt-media-hub/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20320 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Community SUMMARY:Leadership Summit LOCATION:G. Ballroom B DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20320/leadership-summit/ X-TYPE:workshop X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20360 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Cloud & Server SUMMARY:Clarifying Charm Store policy around Ubuntu Releases LOCATION:G. Ballroom C DESCRIPTION:The charm store has only been around for one release, so we're still learning how it relates to releases of Ubuntu. Also the LTS is likely a desired target for the next 2 years for conservative users. Topics:\N\N* When do we advance the charms dev focus to each new release of Ubuntu\N* Should we auto backport and forward port charms, if so, how? URL:http://summit.ubuntu.com/uds-q/meeting/20360/servercloud-q-juju-charms-release-policy/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20728 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Cloud & Server SUMMARY:OpenLDAP MDB: Life after BerkeleyDB LOCATION:G. Ballroom F DESCRIPTION:OpenLDAP's new MDB library provides basically unlimited scaling for reads, high speed writes, and extremely efficient memory use. It has already been ported into a full OpenLDAP backend, a Cyrus SASL sasldb backend, a Heimdal hdb backend, and an SQLite backend with dramatic resource savings and performance gains yielded in each case. Work is also underway to provide a perl DB module, and other projects such as OpenDKIM are now adopting it. With the prevalence of apps dependent on SQLite in Android and other mobile platforms, and the order of magnitude efficiency gains from MDB, the potential for battery savings and extended runtimes on mobile devices is significant. What other apps/tools should we explore for MDB adoption? URL:http://summit.ubuntu.com/uds-q/meeting/20728/openldap-mdb-life-after-berkeleydb/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20781 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:QA SUMMARY:Utilizing ubuntu friendly for testing LOCATION:G. Ballroom G DESCRIPTION:Discussing ways to integrate the ubuntu friendly database for testing needs. \N-Creating a testing hardware database for targeted testing\N-Identifying and communicating with people with specific hardware for iso testing, feature testing, and hardware enablement and/or bug fixing\N-Make available the testing pool/results to developers (upstreams?) URL:http://summit.ubuntu.com/uds-q/meeting/20781/qa-q-friendly-integration/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20341 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Hardware SUMMARY:Ubuntu Kernel Delta Review LOCATION:G. Ballroom H DESCRIPTION: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. URL:http://summit.ubuntu.com/uds-q/meeting/20341/hardware-q-kernel-delta-review/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20800 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Design SUMMARY:Design Theatre LOCATION:Jr. Ballroom 1 DESCRIPTION:Continuation of Monday's session. Solving design problems together. URL:http://summit.ubuntu.com/uds-q/meeting/20800/design-theatre/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20288 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Foundations SUMMARY:Replace archive admin shell access with API clients LOCATION:Jr. Ballroom 2 DESCRIPTION:The Ubuntu archive administration team has always required direct privileged shell access to the ftpmaster system in order to perform many of its routine tasks. This is a security problem, it prevents us from opening some tasks up to those who are not Canonical employees, and it makes it hard for us to improve our own tools. Improve the Launchpad API to handle all our requirements and write suitable API clients.\N\NWe will know we have succeeded when archive admins no longer require shell access to do their jobs. URL:http://summit.ubuntu.com/uds-q/meeting/20288/foundations-q-replace-archive-admin-shell-access/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20556 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Community SUMMARY:Developer Advisory Team Plans for Q LOCATION:Room 201 DESCRIPTION:Started during the P cycle, the Developer Advisory Team has been reaching to development contributors and while things have worked out quite well, there are surely things we can improve. https://wiki.ubuntu.com/DeveloperAdvisoryTeam\N\NAgenda:\N - team meetings\N - outreach\N - improve feedback collection process\N - get notified about contributor status changes (active→inactive, new→experienced)\N - following up with contributors who don't reply\N - avoiding trello craziness\N\N URL:http://summit.ubuntu.com/uds-q/meeting/20556/community-q-developer-advisory-team/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20630 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Foundations SUMMARY:Upstart roadmap LOCATION:Room 202 DESCRIPTION:= Summary =\N\NGeneral discussion on the direction Upstart is heading in.\N\N= Ideas =\N\N- interactive boot.\N- full Upstart and SysV segregation (+ Upstart controlled shutdown).\N- event log for problem determination.\N- 'initctl kill '\N- enabling user jobs.\N- introducing user job logging.\N- mountall plans.\N- custom actions.\N- cron replacement.\N- conditional start/stop on condition, based on whether a particular job is available for. Examples being:\N  - dovecot+postfix\N  - nis+autofs\N- ...?\N\N= References =\N\N- https://wiki.ubuntu.com/Upstart/Ideas\N- https://lists.ubuntu.com/archives/ubuntu-devel/2011-June/033402.html\N- https://lists.ubuntu.com/archives/upstart-devel/2011-August/001707.html\N\N= Blueprints =\N\N- https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-upstart-service-readiness\N- https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-upstart-overcome-ptrace-limitations\N\N- https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-upstart-for-admins\N- https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-upstart-convert-main-initd-to-jobs\N- https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-upstart-roadmap URL:http://summit.ubuntu.com/uds-q/meeting/20630/foundations-q-upstart-roadmap/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20247 DTSTART:20120508T220000Z DTEND:20120508T230000Z CATEGORIES:Other SUMMARY:Open Input Framework Gestures in Chromium LOCATION:Room 204 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20247/touch-gestures-in-chromium/ X-TYPE:discussion X-ROOMNAME:room-204 END:VEVENT BEGIN:VEVENT UID:20753 DTSTART:20120508T231500Z DTEND:20120509T000000Z CATEGORIES: SUMMARY:Sound settings redesign review LOCATION:G. Ballroom A DESCRIPTION:Sound settings redesign review and discussion around further improvements and limitations of current implementation. URL:http://summit.ubuntu.com/uds-q/meeting/20753/sound-settings/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20415 DTSTART:20120508T231500Z DTEND:20120509T000000Z CATEGORIES:Community SUMMARY:Promote and encourage upstream delivery in Ubuntu LOCATION:G. Ballroom C DESCRIPTION:Get more app developers talking about Ubuntu and targeting Ubuntu. Promote Ubuntu as a platform in the places independent app developers socialize. URL:http://summit.ubuntu.com/uds-q/meeting/20415/community-q-upstream-evangelism/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20607 DTSTART:20120508T231500Z DTEND:20120509T000000Z CATEGORIES:Foundations SUMMARY:Upstart service readiness LOCATION:G. Ballroom F DESCRIPTION:Upstart currently considers a service "ready" (fully initialised) once:\N\N- [Services] The process has forked the expected number of times (0-2)\N- [Tasks] The process has been exec'd successfully\N\NFor daemons therefore, "service readiness" is inextricably linked to the\Noverloaded 'expect' stanza which is also used for PID tracking.\N\NThe problem is that some services (such as cups) are _not_ ready once they have forked 'n' times.\N\NThe proposal is to introduce a new 'ready on' stanza coupled with a 'ready' event that would allow explicit control over when Upstart deems a service to be in a usable state:\N\Nhttp://people.canonical.com/~jhunt/blueprints/upstart-service-readiness-table.html\N\NSummary:\N\N- No change to existing 'expect' behaviour.\N- If no 'ready on' condition specified, 'ready' event emitted immediately\N  after 'started'.\N- If 'ready on' condition specified, 'ready' event emitted if and when\N  condition becomes true.\N- 'ready' event can optionally be used by other services as a more\N  reliable way to know when a service is fully initialized and thus usable.\N\NObservations:\N\N- possible to specify multiple values in 'ready on' condition such as:\N  "ready on (dbus NAME=org.bar.foo and file FPATH=/var/log/myapp.log and socket PROTO=inet PORT=80"\N  "ready on stopped myjob and started myjob2"\N- upstart-socket-bridge will be retained but with advent of (C), no\N  longer necessary to modify any daemons as is required by systemd for\N  "socket activation".\N\NAdvantages:\N\N- No change to existing 'expect' behaviour.\N- Solves the readiness problem since .conf files would have a rich\N  palette of sources of readiness to choose from which should cover 99%\N  of all cases (udev, dbus, file, socket).\N- More reliable behaviour.\N- Would allow for simplification for jobs that currently fail to work\N  solely via ptrace (for example, see gross hacks in /etc/init/cups.conf).\N\NWork required:\N\N- Finish (C).\N- Implement (D) and (E).\N- Modify upstart-udev-bridge to look at "ready on" job stanzas to allow\N  "ready on ".\N\NConcerns:\N\N- (D) would need to be accepted into the upstream kernel.\N- (D) would not currently work in LXC containers since netlink is effectively disabled (as it is not namespace-aware). Correct fix would presumably be to make netlink ns-aware?\N- (D) ties this feature to Linux rather heavily\N  (*could* provide a very crude /proc/net/{tcp,udp} implementation but\N  performance would be poor as file must be continually re-read!)\N- (C) would need to use inotify (or fsnotify to avoid complexities to overcome racy behaviour for inotify recursive watches) but could be ported to other architectures\N  (such as FreeBSD using kqueue).\N\N----------------------------------\N\NAlternative idea (from apw): put the onus on the daemons to inform Upstart when they are ready.\N\NThis is in fact already possible using 'expect stop' where Upstart waits for the application to send SIGSTOP before considering it ready. It could be extended to obtain the PID directly via sigaction(2) to avoid the need to obtain it via ptrace(2). Could go a stage further and provide some sort of formal API rather than a signal to allow a daemon to indicate readiness (coupled with a utility command to do the same).\N\NAdvantages:\N\N+ simple.\N+ puts onus on daemons rather than Upstart.\N+ potentially removes the need to use ptrace for PID tracking.\N+ if the API idea were selected, this could be used with SysV jobs too (by providing a NOP implementation for the traditional SysV init).\N+ no kernel support required (so would map across to other systems (BSD/Hurd if desirable).\N+ could be standardized as part of the LSB since it would be init-system-agnostic.\N\NDisadvantages:\N\N- daemons may ignore the standard behaviour.\N- we would need to modify every daemon in the archive to work with this model.\N- highly unlikely that commercial vendors would modify their products unless it were an approved standard.\N- putting control in the hands of the daemons is not necessarily desirable: consider if they go haywire - Upstart would not be able to control the problem as it may not yet know the PID.\N URL:http://summit.ubuntu.com/uds-q/meeting/20607/foundations-q-upstart-service-readiness/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20508 DTSTART:20120508T231500Z DTEND:20120509T000000Z CATEGORIES:Cloud & Server SUMMARY:Juju Charm Store Maintenance LOCATION:G. Ballroom G DESCRIPTION:(maintaining and reviewing charms) URL:http://summit.ubuntu.com/uds-q/meeting/20508/servercloud-q-juju-charmstore-maintenance/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20377 DTSTART:20120508T231500Z DTEND:20120509T000000Z CATEGORIES:Desktop,Hardware,QA SUMMARY:Improvements to the Checkbox Qt interface LOCATION:Jr. Ballroom 1 DESCRIPTION:This blueprint is just a placeholder for scheduling purporses. For the description please go to:\N\N https://blueprints.launchpad.net/certify-planning/+spec/cert-q-external-testing\N URL:http://summit.ubuntu.com/uds-q/meeting/20377/cert-q-checkbox-qt/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20704 DTSTART:20120508T231500Z DTEND:20120509T000000Z CATEGORIES:Other SUMMARY:Create "agents" to deal with bugs and alert people about them LOCATION:Jr. Ballroom 2 DESCRIPTION:Rationale:\NWe have lots and lots of bugs filed on a daily basis, bugs that could, given a set of heuristics, be automatically triaged. By triaged we mean flagged as important/unimportant. We want to do that with some level of certainty, to avoid missing important reports but removing the need of manually triaging every single bug filed against Ubuntu packages.\N\NGoal:\NHave a script or a set of scripts that automatically do the first round of triage, removing useless or not likely to be useful bug reports, and raising the priority of the potential issues whenever they happen. Remove the need of worrying about triaging all bugs and let us focus on fixing the important ones. URL:http://summit.ubuntu.com/uds-q/meeting/20704/other-q-bug-agents/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20792 DTSTART:20120508T231500Z DTEND:20120509T000000Z CATEGORIES:Desktop SUMMARY:Requirements for desktop Upstart LOCATION:Room 208 DESCRIPTION:Figure out the most important use-cases for using Upstart in the desktop session and what requirements this puts on Upstart to verify whether it can start to be used for the desktop session in 12.10. URL:http://summit.ubuntu.com/uds-q/meeting/20792/desktop-q-upstart-session-requirements/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20499 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Foundations SUMMARY:Integrate Linaro hwpacks for arm with the Ubuntu image build infrastructure LOCATION:G. Ballroom C DESCRIPTION:To use their evaluation builds on different ARM architectures Linaro creates\Nso called hardware packs which contain board specific bits like kernel, bootloader \Nand drivers.\N\NThe Ubuntu infrastructure currently uses debian-cd in the backend to make images\Nbootable on ARM boards. In 12.10 we want to remove this duplicated effort and teach\Ndebian-cd about hwpacks from linaro so that it can make use of them for certain \N(if not all) ARM targeted images in the future.\N\NIn the session going along with this spec we will have to discuss the necessary\Nchanges to debian-cd but also possibly required changes to the hwpacks (we might\Nwant to use a long term supported kernel for example or can not distribute drivers\Nlegally in a community distro which linaro includes in their builds with approval from \Nthe vendor etc.) URL:http://summit.ubuntu.com/uds-q/meeting/20499/foundations-q-hwpack-integration/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20421 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Desktop SUMMARY:Application Startup Time LOCATION:G. Ballroom F DESCRIPTION:Application startup time is unnecessarily slow in a large number of\Ninstances. Can we see some improvement in that area in the Q cycle? The\Nprice of RAM has dropped dramatically, and usage has not increased all\Nthat much. Can't we use it for something when it's available?\N\NWe now have Zeitgeist. This means we can know what users will do after\Nlogin. It's possible to tell not only what applications will be started,\Nbut also what files will be used. In many cases, there's only a single\Nhuman user in the system. I would really like it if I could set my work\Ndesktop to boot automatically in the morning, and it'd load my stuff\Ninto RAM while waiting for me to log in. There's also a few websites I\Nalways check first thing while I have my first cup of coffee. Load them\Ntoo so I don't have to wait for it. I'm the only human user on my\Ndesktop, so why not log me in automatically, but in the background,\Nkeeping the login screen as it is?\N\NTo my mind, these are all attainable goals:\N\N* Sub-second login\N* Instant loading of frequently used applications\N* Zero-delay access to most frequently used websites.\N\NEveryone is telling me to go buy a fast SSD. But that's expensive and in\Nmy case, it doesn't provide any benefits that can't be achieved by\Nsoftware. RAM is extremely cheap, and much faster than any SSD on the\Nmarket. What currently happens is that the login screen sits there\Nidling, waiting for me to pay attention to the computer before it starts\Ndoing work it knows I'm going to want it to do. That's rude, isn't it?\N\NIn networked environments of diskless desktops, such as schools and\Noffices, the effects can be even greater. It might not be possible to do\Nbackground logins for the user, but a lot of things can still be loaded\Nin advance, providing a significantly improved experience. And of\Ncourse, the older the computers are, the greater the effect will be. URL:http://summit.ubuntu.com/uds-q/meeting/20421/desktop-q-application-startup-time/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20795 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Desktop SUMMARY:Port indicators to GMenu LOCATION:G. Ballroom G DESCRIPTION:Port indicators to GMenu URL:http://summit.ubuntu.com/uds-q/meeting/20795/desktop-q-indicator-gmenu-port/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20591 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Foundations SUMMARY:Improving Reliability of Software RAID LOCATION:Jr. Ballroom 1 DESCRIPTION:mdadm currently has a gaggle of open bugs, and every cycle the RAID ISO tests produce new and interesting bugs. It seems like we're doing something a bit wrong with Software RAID. There are some valid solutions here: https://wiki.ubuntu.com/ReliableRaid which should be discussed and either refuted or implemented. URL:http://summit.ubuntu.com/uds-q/meeting/20591/foundations-q-software-raid/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20398 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Community SUMMARY:Juju Charm Growth LOCATION:Jr. Ballroom 2 DESCRIPTION:Growing the amount of charms in the charm store URL:http://summit.ubuntu.com/uds-q/meeting/20398/community-q-juju-charm-growth/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20551 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Community SUMMARY:Packaging requirements for Apps in Ubuntu LOCATION:Room 201 DESCRIPTION:The App Review Board and its processes were put in place 1.5 years ago. It's time to review how policies and requirements have been working out for us.\N\NDaniel H put together some discussion about a key point of these policise, the /opt requirement, at https://wiki.ubuntu.com/OptRequirement which can provide a basis for the discussion URL:http://summit.ubuntu.com/uds-q/meeting/20551/community-q-app-packaging-requirements/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20743 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Hardware SUMMARY:LTS backport testing in 12.04 LOCATION:Room 202 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20743/lts-backport-testing-in-1204/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20796 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Desktop SUMMARY:Synchronizing settings among multiple computers using Ubuntu One LOCATION:Room 203 DESCRIPTION:Using more than one computer, often it would be useful to have a way to synchronize settings among multiple computers. For example you change the desktop wallpaper on your office PC and you want to find the same wallpaper when you go back home on your personal PC or on your laptop. Language settings, online accounts, privacy settings ecc... are only few examples of settings you could want to have synchronized.\N\NMore specs in my blog page: http://www.andreagrandi.it/2012/02/21/ubuntu-syncronizing-settings-among-multiple-pc-using-ubuntu-one/ URL:http://summit.ubuntu.com/uds-q/meeting/20796/synchronizing-settings-among-multiple-computers-using-ubuntu-one/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20592 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES:Desktop SUMMARY:Kubuntu Quantal Active LOCATION:Room 204 DESCRIPTION:Kubuntu Active in Quantal URL:http://summit.ubuntu.com/uds-q/meeting/20592/kubuntu-q-active/ X-TYPE:discussion X-ROOMNAME:room-204 END:VEVENT BEGIN:VEVENT UID:20653 DTSTART:20120509T000500Z DTEND:20120509T010000Z CATEGORIES: SUMMARY:Feedback on Notifications LOCATION:Room 210-211 DESCRIPTION:Notify OSD has been around for a while. In the main time our competitors introduced solutions using quite different approaches.\N\NCome to this session to discuss current issues and brainstorm eventual improvements. URL:http://summit.ubuntu.com/uds-q/meeting/20653/feedback-on-notifications/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20691 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Desktop SUMMARY:Hybrid graphics support strategy planning for Q LOCATION:G. Ballroom A DESCRIPTION:Review the current state of hybrid graphics and what's feasible for 12.10.\N\N- base prime/dma_buf -support is now in 3.4rc\N- prime sharing support for ttm/nouveau/i915 is queued for 3.5\N- preliminary work towards a new driver api in the xserver has been submitted for review on 2012-05-05 (scrn->screen), 'drvmodelv3' staged in git\N- randr api still being worked out, preliminary work in git\N\Nhttp://airlied.livejournal.com/75555.html\N\Nold blueprint for reference: https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-hybrid-graphics URL:http://summit.ubuntu.com/uds-q/meeting/20691/desktop-q-hybrid-graphics/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20809 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Other SUMMARY:Improving infrastructure for Ubuntu Flavors LOCATION:G. Ballroom B DESCRIPTION:Are there any infrastructure changes would help the Ubuntu Flavors and their communities with development and test? URL:http://summit.ubuntu.com/uds-q/meeting/20809/other-q-ubuntu-flavors/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20520 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:QA SUMMARY:Platform QA Metrics LOCATION:G. Ballroom C DESCRIPTION:Track progress and be able to determine how long will take us to get to 100% coverage and help us prioritize the work URL:http://summit.ubuntu.com/uds-q/meeting/20520/qa-q-metrics/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20496 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Foundations SUMMARY:Phased updates of software packages LOCATION:G. Ballroom G DESCRIPTION:Giving an entirely new version of any widely used software program to our entire user base all at once is unnecessarily fraught with peril.\N\NInstead, 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.\N\NWe 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.\N\NWe should build this at a level that still affords power users the ability to forcibly install all updates. Update-manager is one such option.\N\NIt might be worth also discussing the possibility of using feature flags. URL:http://summit.ubuntu.com/uds-q/meeting/20496/foundations-q-phased-updates/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20296 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Foundations SUMMARY:Merging / onto /usr LOCATION:Jr. Ballroom 1 DESCRIPTION:Fedora has decided that they are going to merge {/bin,/lib,/sbin} into /usr. https://fedoraproject.org/wiki/Features/UsrMove This means that upstream support for distinguishing between / and /usr for early boot services will atrophy more than it already has, and there will be extra work involved for Ubuntu to maintain this capability. Furthermore, if we can rely on /usr to be mounted when upstart starts, we can simplify a number of system jobs. Explore whether we should change initramfs-tools in Ubuntu as well for 12.10 to provide this guarantee. URL:http://summit.ubuntu.com/uds-q/meeting/20296/foundations-q-usr-merge/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20458 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Hardware SUMMARY:Kernel Team Round Table - Wednesday LOCATION:Jr. Ballroom 2 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20458/kernel-team-round-table-wednesday/ X-TYPE:roundtable X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20725 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Community SUMMARY:Community Roundtable Wednesday LOCATION:Room 202 DESCRIPTION:Tasks from daily community roundtable sessions URL:http://summit.ubuntu.com/uds-q/meeting/20725/community-roundtable-wednesday/ X-TYPE:roundtable X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20394 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Cloud & Server SUMMARY:MAAS Next Steps LOCATION:Room 203 DESCRIPTION:Outline the next steps we need to take with the maas project for 12.10. URL:http://summit.ubuntu.com/uds-q/meeting/20394/servercloud-q-maas-next-steps/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20611 DTSTART:20120509T160000Z DTEND:20120509T165500Z CATEGORIES:Security SUMMARY:security-q-roundtable LOCATION:Room 208 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20611/security-q-roundtable/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20452 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:Cloud & Server SUMMARY:Server Vendor Enhancements for Apport LOCATION:G. Ballroom A DESCRIPTION:Server vendors, like HP, provide additional tooling for analysis of system crashes. This session is to discuss how these vendors can best integrate their tools into apport. URL:http://summit.ubuntu.com/uds-q/meeting/20452/servercloud-q-apport-enhancements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20747 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:Desktop SUMMARY:Desktop configuration lockdown LOCATION:G. Ballroom B DESCRIPTION:Specification for a set of policies and settings important for desktop lockdown. URL:http://summit.ubuntu.com/uds-q/meeting/20747/desktop-q-configuration-lockdown/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20373 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:Cloud & Server SUMMARY:Package (more) AWS tools for Ubuntu LOCATION:G. Ballroom C DESCRIPTION:Add Ubuntu packages for more AWS tool sets like Auto Scaling, ELB, EMR, CloudSearch, ElastiCache, etc..\N\NMake sure that the ec2-api-tools and ec2-ami-tools packages are kept up to date with new releases from Amazon so that they support the latest EC2 features. URL:http://summit.ubuntu.com/uds-q/meeting/20373/servercloud-q-awstools/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20769 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:Other SUMMARY:U1DB workshop LOCATION:G. Ballroom F DESCRIPTION:U1DB is in beta as of today, and we want to show and tell and guide you through how to use it in your apps. URL:http://summit.ubuntu.com/uds-q/meeting/20769/u1db-workshop/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20597 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:Desktop SUMMARY:Kubuntu Quantal Packaging LOCATION:G. Ballroom G DESCRIPTION:Things to package for Q URL:http://summit.ubuntu.com/uds-q/meeting/20597/kubuntu-q-packaging/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20290 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:Other SUMMARY:Discussions of what should get uploaded to -proposed and when LOCATION:G. Ballroom H DESCRIPTION:In Precise Beta 2, we were able to use -proposed as a staging archive for the first time. This blue print is to gather examples and use cases, as they occur during the remainder of the cycle, of what worked well, and what caused problems. Thinking is we can then get together at UDS, review the use cases, and figure out some polices to use it effecively going forward. URL:http://summit.ubuntu.com/uds-q/meeting/20290/other-q-freeze-use-of-proposed/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20523 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:QA SUMMARY:ubuntu-qa-tools: Improvements and Packaging LOCATION:Room 201 DESCRIPTION:This session is intended to gather feedback from current users of the ubuntu-qa-tools code, including vm-tools and dl-ubuntu-test-iso. We would like to get the tools packaged for wider use, and ensure their continued maintenance. URL:http://summit.ubuntu.com/uds-q/meeting/20523/qa-q-ubuntu-qa-tools/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20799 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES: SUMMARY:Multi-Monitor Improvements LOCATION:Room 202 DESCRIPTION:In this session we will be discussing the improvements planned for the Ubuntu multi-monitor user experience.\N\NThe design specification can be found here:\Nhttps://docs.google.com/a/canonical.com/document/d/1aHvJ-iIw-59bXTYBmIhQqEx0za2h9jpFE_RhZ2VOvJc/edit\N\NCome along to share your feedback and ideas. URL:http://summit.ubuntu.com/uds-q/meeting/20799/multi-monitor-improvements/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20429 DTSTART:20120509T170000Z DTEND:20120509T174500Z CATEGORIES:Desktop SUMMARY:System Compositor LOCATION:Room 203 DESCRIPTION:A change I'd like to make for 12.10 is to use a compositor to control video from boot to shutdown.\N\NThis gives us the following benefits:\N- We can have smooth transitions from the splash screen to the greeter to the session and back again\N- We don't use VT switching anymore which has been shown to be problematic\N- We use one consistent monitor layout for all stages of the boot\N- We can use the greeter as the lock screen (couldn't get it to work this cycle for the above reasons)\N- We can ensure that you can never accidentally switch to a locked session\N- We can show the greeter while the session loads\N\NThe technology used will probably be Wayland, and in some ways this change is to implement the Wayland Tech Preview that was proposed for Precise [1].\N\NNote that not all video drivers will support this, and we will continue to support the current system for those that do not support it (primarily the nvidia driver).\N\N[1] https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-wayland-tech-preview URL:http://summit.ubuntu.com/uds-q/meeting/20429/desktop-q-system-compositor/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20657 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Foundations SUMMARY:btrfs requirements for Quantal LOCATION:G. Ballroom A DESCRIPTION:Catch up with significant btrfs consumers (particularly the server team) on their requirements for btrfs in Quantal, in light of upstream activity. Figure out areas where we might be able to help. URL:http://summit.ubuntu.com/uds-q/meeting/20657/foundations-q-btrfs-requirements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20368 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Cloud & Server SUMMARY:Graphical interface for Domain Directory management LOCATION:G. Ballroom B DESCRIPTION:With the inclusion of Samba4, Ubuntu still lacks of a graphical interface to manage a domain directory, including LDAP, Samba, DHCP, DNS, etc. For administrators coming from the Windows world a graphical interface is a must. In the past some tools like SWAT did this job but they have become obsolete with the release of Samba4 that needs a more complex setup. Zentyal is currently the only interface on Ubuntu that can manage and maintain synchronised Samba4 and OpenLDAP. We will discuss further improvements on this and integration with Ubuntu default components. URL:http://summit.ubuntu.com/uds-q/meeting/20368/servercloud-q-samba4-interface/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20468 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Hardware SUMMARY:Automated testing for HDA sound cards LOCATION:G. Ballroom F DESCRIPTION:Hda-emu is a way to test kernel code for Intel HDA sound cards, without having the hardware at hand. Discuss how to evolve this code into a regression test suite, that we could run before e g releasing proposed kernels, and how to integrate it into existing QA efforts (jenkins etc). URL:http://summit.ubuntu.com/uds-q/meeting/20468/hardware-q-hda-automated-qa/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20616 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Other SUMMARY:Quantal Release Schedule Review and Interlocks LOCATION:G. Ballroom G DESCRIPTION:Review of Quantal schedule and Interlock schedule to 12.04.1 needs.\N\NPrimary page is:\N    https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule\N\NNeed to synch with:\N    https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule (for 12.04.1)\N   https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock URL:http://summit.ubuntu.com/uds-q/meeting/20616/other-q-release-schedule-review/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20570 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Desktop SUMMARY:Ubuntu Manual schedule for Precise manual and beyond LOCATION:G. Ballroom H DESCRIPTION:Pad -\N\Nhttp://summit.ubuntu.com/uds-q/meeting/20344/ubuntu-manual-schedule-for-p-manual-and-beyond/ URL:http://summit.ubuntu.com/uds-q/meeting/20570/desktop-q-ubuntu-manual/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20744 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Foundations SUMMARY:Distro buildd usage LOCATION:Jr. Ballroom 1 DESCRIPTION:Review the buildd resources available for the distro builds and various test builds, discuss buildd uses outside the core distro team (like daily Go builds, and unity test builds). URL:http://summit.ubuntu.com/uds-q/meeting/20744/foundations-q-buildds-usage/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20233 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Community SUMMARY:Summit development plans from UDS-Q LOCATION:Jr. Ballroom 2 DESCRIPTION:Discussion during UDS-Q on the further plans and development for summit.ubuntu.com URL:http://summit.ubuntu.com/uds-q/meeting/20233/community-q-summit/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20762 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Desktop SUMMARY:Ubuntu Desktop in an Enterprise Setup LOCATION:Room 202 DESCRIPTION:Corporations deploying Ubuntu Desktop instances face a number of issues in adopting it in their environment. The major pain is Microsoft tools that mostly dominated the backend infrastructure - Active Directory, Exchange, LiveMeeting, Office and other. URL:http://summit.ubuntu.com/uds-q/meeting/20762/desktop-q-desktop-in-enterprise/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20526 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:QA SUMMARY:Lab administrative tasks Q LOCATION:Room 203 DESCRIPTION:This blueprint is created to as a way of tracking the work the Platform QA team is doing on the lab during the Q cycle. URL:http://summit.ubuntu.com/uds-q/meeting/20526/qa-q-labsetup/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20596 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Desktop SUMMARY:Kubuntu Quantal Images LOCATION:Room 204 DESCRIPTION:What ISO images to release with Quantal? URL:http://summit.ubuntu.com/uds-q/meeting/20596/kubuntu-q-images/ X-TYPE:discussion X-ROOMNAME:room-204 END:VEVENT BEGIN:VEVENT UID:20461 DTSTART:20120509T180000Z DTEND:20120509T185500Z CATEGORIES:Cloud & Server SUMMARY:Review of Server Bug Triage Process LOCATION:Room 208 DESCRIPTION:The ubuntu server team have been using the current bug triage process for a full release now.\N\NWe should review the current process and reports to ensure that the current process is working and to identify any improvements that can/should be made during the quantal release cycle. URL:http://summit.ubuntu.com/uds-q/meeting/20461/servercloud-q-bug-triage-review/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20487 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Desktop SUMMARY:Monitor Calibration LOCATION:G. Ballroom A DESCRIPTION:Come and calibrate your monitor using the Colorhug open source hardware and Ubuntu 12.04 URL:http://summit.ubuntu.com/uds-q/meeting/20487/monitor-calibration/ X-TYPE:workshop X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20379 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Hardware SUMMARY:Improving automated certification testing of Kernel SRUs LOCATION:G. Ballroom B DESCRIPTION:Kernel Stable Release Updates (SRUs) are tested by the certification team in search of possible regressions or bugs that may affect certified systems.\N\NThese tests have to be performed in sync with the SRU release cadence, and in order not to hold up the SRU's release, they need to be done within a tight schedule, so they entirely consist of automated tests, to provide the response times and scalability the SRU process requires.\N\NDue to its nature, SRU testing would benefit from as many tests as possible, but always with the constraint that they be automated or, at most, require a human to review collected data in bulk. Tests that require interactive verification or human action are to be avoided.\N\NTo enhance the value provided by SRU testing, we need to both add new tests, and improve the existing ones, based on input from the Kernel team about the areas that traditionally give the most trouble, and possible ways to test for bugs or regressions.\N\N== Improving the test development process ==\NFrom inception to actual implementation in real SRU runs, tests may take up to 4 months to actually start being run. This diminishes the value and means that the number of tests that can be implemented per cycle is very small.\N\NThe test development process needs to be described, analyzed and reengineered with the goal of reducing the turnaround time for new tests as much as possible.\N\N== Improving coverage in existing areas ==\NCoverage has been improved in e.g. wireless testing, but some other areas, such as graphics and audio, can still use some improvement. Consulting with experts on these areas as to which tests would be useful to have, and implementing them (ideally with the new process so we can start seeing results as soon as possible).\N\N== Automating plugging/unplugging of devices ==\NComing up with a solution that can automate traditionally manual actions (such as USB, memory card, external video and FireWire insertion or removal). This would enable automation of these high-interest tests, and open up new areas for SRU testing.\N\N== Benefits from this blueprint ==\N\NThe certification team will benefit from an ability to develop reliable tests more quickly, by being able to respond to requests from other teams, as well as having techniques for automating physical interaction which will allow fully automatic and more comprehensive testing while maintaining scalability.\N\NThe kernel team will benefit from wider testing, able to catch more bugs and regressions in sync with the SRU cadence, and an increase in the number of test results the certification team will provide.\N\NList of possible tests:\Nhttps://docs.google.com/spreadsheet/pub?key=0AhMEQ8F2hKQOdC1Vd0RGWllLa3R1ZXNkbldsaDJvaWc&output=html URL:http://summit.ubuntu.com/uds-q/meeting/20379/cert-q-sru-coverage/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20410 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Cloud & Server SUMMARY:ARM Server general enhancements (for ARMv7 and perhaps v8) LOCATION:G. Ballroom C DESCRIPTION:This is a starting point for discussion of ARM Server topics. We will need at least one session at UDS for this area. We should probably get more specific, like systems management, network fabric, etc. URL:http://summit.ubuntu.com/uds-q/meeting/20410/servercloud-q-arm-server/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20362 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Cloud & Server SUMMARY:Libvirt work for Q LOCATION:G. Ballroom F DESCRIPTION:Items include:\N  finishing MIR of netcf, and linking libvirt against netcf\NGet community input URL:http://summit.ubuntu.com/uds-q/meeting/20362/servercloud-q-libvirt/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20486 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Hardware SUMMARY:Open Compute Project Roundtable LOCATION:G. Ballroom G DESCRIPTION:The third Open Compute Project (OCP) Summit is the week before UDS, in San Antonio.\N\NThis 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\N, 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).\N URL:http://summit.ubuntu.com/uds-q/meeting/20486/hardware-q-ocp-roundtable/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20580 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Security SUMMARY:AppArmor Ubuntu packaging and integration LOCATION:G. Ballroom H DESCRIPTION:Discuss where to focus Ubuntu-specific AppArmor packaging and integration efforts. URL:http://summit.ubuntu.com/uds-q/meeting/20580/security-q-apparmor-ubuntu/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20413 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Community SUMMARY:Upstream App Developer Outreach LOCATION:Jr. Ballroom 1 DESCRIPTION:Identify and engage targetted upstreams to submit their apps to the Ubuntu Software Centre URL:http://summit.ubuntu.com/uds-q/meeting/20413/community-q-upstream-outreach/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20761 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:Other SUMMARY:Developer membership board approval LOCATION:Jr. Ballroom 2 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20761/developer-membership-board-approval/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20521 DTSTART:20120509T190000Z DTEND:20120509T200000Z CATEGORIES:QA SUMMARY:QA & Release, building bridges LOCATION:Room 202 DESCRIPTION:Discuss what went well and what didn't go so well in terms of QA - Release team communication during P and try to put in place the actions for smoother milestones during Q. URL:http://summit.ubuntu.com/uds-q/meeting/20521/qa-q-release-communication-improvements/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20649 DTSTART:20120509T210000Z DTEND:20120509T211500Z CATEGORIES: SUMMARY:Electronic Arts LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20649/electronic-arts/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20536 DTSTART:20120509T213000Z DTEND:20120509T214500Z CATEGORIES: SUMMARY:Intel (part 1) LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20536/intel-part-1/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20537 DTSTART:20120509T214500Z DTEND:20120509T220000Z CATEGORIES: SUMMARY:Intel (part 2) LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20537/intel-part-2/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20295 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Foundations SUMMARY:Integration testing for the bootloader LOCATION:G. Ballroom A DESCRIPTION:We would like automated integration testing of our bootloader for 12.10. Foundations will probably need to write these tests, with QA team providing guidance on the kind of tests to run. URL:http://summit.ubuntu.com/uds-q/meeting/20295/foundations-q-grub-integration-testing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20366 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Cloud & Server SUMMARY:User namespace (update) LOCATION:G. Ballroom B DESCRIPTION:Present current design of user namespace, and discuss likely upstreaming dates and possible early inclusion in our kernel. URL:http://summit.ubuntu.com/uds-q/meeting/20366/servercloud-q-userns/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20560 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Community SUMMARY:Review of the ARB process using MyApps LOCATION:G. Ballroom C DESCRIPTION:With lots of work put into https://myapps.developer.ubuntu.com/ it should be interesting to review MyApps from the ARB perspective and see if there are small tweaks which would speed up the review of free apps. URL:http://summit.ubuntu.com/uds-q/meeting/20560/community-q-myapps-review/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20569 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Desktop SUMMARY:LibreOffice package split collateral damage analysis LOCATION:G. Ballroom F DESCRIPTION:This blueprint is about analysing the damage that is done by the spliting of LibreOffice into separate packages, which never was a goal at the upstream project. Because of that, in some cornercases LibreOffice crashes or fails to perform because of missing parts, when not installed completely. This is more severe than in other distros because we ship only a partial installaltion with the default install.\NExamples include:\N- document wizards not working in the default install (need java components)\N- mailmerge not working in writer in the default install (needs libreoffice-base)\N- some HTML-imports not working in writer in the default install (needs libreoffice-base)\N- formfields/checkboxes not working in writer in the default install (needs libreoffice-base)\N\NFixing all these upstream is an uphill battle as new dependencies might be added under the radar by new features. So while a full libreoffice install on Ubuntu is doing fine, the default installation on Ubuntu is casting a shadow on both Ubuntu and LibreOffice. URL:http://summit.ubuntu.com/uds-q/meeting/20569/desktop-q-libreoffice-split/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20714 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Community SUMMARY:Growing Ubuntu Community Accomplishments Collection LOCATION:G. Ballroom G DESCRIPTION:This session is designed to discuss which accomplishments we want to focus on for the forthcoming cycle to expand the Ubuntu Community Accomplishments collection. URL:http://summit.ubuntu.com/uds-q/meeting/20714/community-q-growing-ubuntu-community-accomplishments/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20768 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Desktop SUMMARY:Switching to Google Test for Indicators LOCATION:G. Ballroom H DESCRIPTION:We want to increase the reporting ability of the test suites in the Indicators by switching to Google Test. URL:http://summit.ubuntu.com/uds-q/meeting/20768/desktop-q-indicator-gtest/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20386 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Hardware SUMMARY:12.10 certification testing LOCATION:Jr. Ballroom 2 DESCRIPTION:During the Q cycle, the certification team will have a number of routine duties to perform\N\N- Weekly testing to check that tools are working correctly (while also aiming to discover some hardware related bugs in Ubuntu)\N- Milestone testing, which should be more thorough than weekly testing, in order to catch more bugs and raise them with the appropriate parties as soon as possible.\N- Certification testing, at the end of the cycle to determine whether systems can be certified or not.\N\NThe purpose of this blueprint is to think about what changes can be made to these processes, in order to do better certification.\N\N= Functional coverage =\N\NSome new hardware is becoming commonplace and we should be including it in our certification coverage, at least to the extent that we test it and if it fails we report that about the system:\N\NFunctional coverage usually takes a good hour, so this will be discussed in a separate session.\N\N- Accelerometers should be included as a greylist item\N- USB 3.0 should be included as a greylist item (meaning that USB 3.0 devices need to be tested against the USB 3.0 port)\N- 3G/WWAN modems should be included as a greylist item\N- Touchscreens multitouch should be considered for inclusion as a greylist item\N- HDMI audio should be included as a greylist item\N- Considering adding Super-key testing (i.e. launcher shortcut) to spec and backport to 12.04.1\N\N= Process =\N\N== 12.10 kernel in 12.04 LTS testing ==\N\NFrom 12.10 onwards, changes to the kernel and some other closely linked packages such as X will be tested to work on the LTS (12.04) during the development cycle. This means that systems scheduled to be certified with 12.10 will be also tested on 12.04 LTS with the 12.10 backport, to ensure that nothing breaks.\N\NAlso, this means that we will need to make changes to the certification site (both public and internal) to be able to distinguish a system certified with 12.04 kernel, or with 12.04 with a backported kernel.\N\NStrictly speaking this would double the testing effort required by the certification team, since each system would have to be tested with each kernel in combination with the 12.04 userspace and 12.10 userspace.\N\NOne method of doing this would be to change the test infrastructure so that a 12.04 test run is done immediately after the 12.10 one is completed.\N\N== Weekly testing ==\N\NAt the moment weekly testing is performed on a subset of about 25 systems available in the certification labs. A tool is used to try and get the best hardware coverage possible on this small set of systems (by not including multiple systems with the same GPU or Wireless card for example). The main purpose is to identify when the testing tools break, but issues with Ubuntu itself may be uncovered as well. For this reason an automated run is done (no manual testing), which means that some issues may not be detected. This mostly works well, but improvements may be made to better detect regressions in the tools (there were one or two cases in the last cycle where problems went unnoticed for some time). For example, the status of some tests changed from passing, to being skipped due to changes in the internal working of Checkbox. Since they weren't appearing as failures this wasn't picked up.\N\NThis could be achieved by having a method that compares two subsequent week results, and reports on things that might have changed.\N\NTesting of the 12.10 kernel in 12.04 will also have to be included in the weekly testing process. It might be necessary to test them bi-weekly if a good method for integrating them with the normal test run cannot be found.\N\N== Milestone testing ==\N\NTesting at release milestones is performed on the same systems as weekly testing, but instead of only doing a fully automated run, manual testing is performed as well. This means that any issues which would block certification will be detected, assuming they exist on the systems in the test pool. Last cycle it was found that some systems which weren't included in the test pool had very critical failures caused by a driver for a component not covered by certification (IR reciever). We would not like to have to test on every system at every milestone, but at the same time we'd like to be able to detect issues like this earlier, which can only really be achieved by a full test run. Some sort of comprimise may be possible.\N\NBecause systems will need to be tested manually at milestones, the technique described above for handling the 12.10 kernel in 12.04 LTS described above will probably not be suitable.\N\N== ARM Certification ==\N\NIt is already known that the Certification testing tools (mainly Checkbox) are mostly not working on ARM devices. Since some ARM certification testing may be necessary during the Q cycle we need to achieve a baseline of usability so that Checkbox can be adapted to testing a specific ARM based product. This will be defined as the ability for Checkbox to submit hardware information and a basic set of test results. URL:http://summit.ubuntu.com/uds-q/meeting/20386/cert-q-12.10testing/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20525 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:QA SUMMARY:QA Team Backlog LOCATION:Room 201 DESCRIPTION:This blueprint captures all the ongoing tasks that the Platform QA team is going to be doing during Q, set the focus for the coming 6 months in terms of QA ongoing activities, such as keep running test cases, triaging problems, etc. URL:http://summit.ubuntu.com/uds-q/meeting/20525/qa-q-backlog/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20372 DTSTART:20120509T220000Z DTEND:20120509T230000Z CATEGORIES:Cloud & Server SUMMARY:OpenStack SRUs LOCATION:Room 202 DESCRIPTION:With the release of Essex on Precise we wish to regularily provide timely updates to our users who are still using Essex. The purpose of this blueprint is to figure out the process and track work that needs to be done.\N URL:http://summit.ubuntu.com/uds-q/meeting/20372/servercloud-q-openstack-stable/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20466 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:QA SUMMARY:Improving iso testing process and results LOCATION:G. Ballroom A DESCRIPTION:Discussing improvements as to how, when, and why we iso test. Additionally defining and understanding the communities enhanced role in iso testing URL:http://summit.ubuntu.com/uds-q/meeting/20466/qa-q-iso-testing-process/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20713 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES: SUMMARY:Unity Greeter updates for 12.10 LOCATION:G. Ballroom B DESCRIPTION:Planned updates including Greeter as the Lock Screen, flicker free transitions, confirmation dialogue, morphing login box, drop-down menus and back button. URL:http://summit.ubuntu.com/uds-q/meeting/20713/unity-greeter-q/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20677 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:Hardware SUMMARY:Defensive software for OEM installs LOCATION:G. Ballroom C DESCRIPTION:We’re aiming to make Ubuntu more resilient against hardware failures, with a focus on OEM-preinstalled Ubuntu. For example, an invalid CMOS time/date value can cause the system to fail in various unexpected ways.\N\NThe purpose of this session is to define which problems may arise due to:\N\N * "Sitting on the shelf" problems, eg RTC battery going flat\N * General mass-production issues\N * Missing drivers due to subtle SKU alterations\N * Low-memory situations\N * Corruption during factory pre-load\N\N- or any other areas that we can identify during the session. We'll be aiming to outline potential solutions to these issues, and carry out that development work in the Q timeframe. URL:http://summit.ubuntu.com/uds-q/meeting/20677/hardware-q-defensive-software/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20449 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:Cloud & Server SUMMARY:Ubuntu Cloud Images Roundtable LOCATION:G. Ballroom F DESCRIPTION:Discussion of improvmenet and enhancements to the Cloud Images and Cloud-Init\N\N\N* Addition of an SSH recovery Shell: Depending on the virtualization solution (i.e. EC2 EBS versus EC2 Instance-store versus OpenStack), the ability to recover from file system corruption is limited or non-existent. In order to support users across different virtualization solutions, it is proposed to introduce a SSH recovery method to assist users in recovering from file-system corruption or missing disks.\N\N Proposal:\N 1. On failure of mount-all or on cloud-init failure to mount all disks, SSH would be \N launched\N 2. Users would be forced into a screen session with an error message.\N 3. Users would need to reboot.\N\N* Dynamic multiple LOCALE support: While English is the language of Ubuntu development, the use of Ubuntu is global. Further many Ubuntu users have default locale settings that are different. When SSH'ing into a Ubuntu Cloud Image, some software may fail to work properly with invalid locale settings set by SSH.\N\N Proposal: Develop a method of compiling new locales based on SSH LC_* and LANG \N settings sent by SSH client.\N\N* Improving methods for users to find official EC2 AMI ids: Over the last couple of months we have made significant progress in developing new ways for users to discover the official EC2 AMI ids. Between the AWS Quickstart, AWS Marketplace (free tier and paid support), cloud-utils (which provides ubuntu-cloudimg-query), cloud-images.ubuntu.com (/query and /query2) and cloud.ubuntu.com/ami, there are several official ways to find the images.\N\N Discussion: What are the deficiencies in the current methods of finding images and \N how could we make finding the official AMI's easier? URL:http://summit.ubuntu.com/uds-q/meeting/20449/servercloud-q-cloud-images/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20524 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:Cloud & Server SUMMARY:ARM Server Benchmarking and Performance LOCATION:G. Ballroom G DESCRIPTION: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. URL:http://summit.ubuntu.com/uds-q/meeting/20524/servercloud-q-server-benchmark-and-performance/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20291 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:Other SUMMARY:Standardizing ways of understanding which bugs development teams are fixing and which ones they aren LOCATION:G. Ballroom H DESCRIPTION:Bugs should be assigned to the teams in order to get them considered for fixing as part of a release (stable,development). However our current infrastructure gives us no effective way of telling the difference between bugs that the development team is not committing to fix, and ones they haven't looked at yet. This causes inefficiencies, and doesn't scale well for teams (release, support, etc.) that have to look at wide range of bugs and issues across multiple development teams. This session is to discuss and agree on some conventions/policies/and possibly additional tooling to make this effective for all the stakeholder, for q development release, and p lts supported release. URL:http://summit.ubuntu.com/uds-q/meeting/20291/other-q-release-bug-list-workflows/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20549 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:Community SUMMARY:LoCo Portal Design Iteration LOCATION:Jr. Ballroom 2 DESCRIPTION:We want to make the Ubuntu LoCo portal a hub for social LoCo activities.\N\NThis blueprint proposes the redesign of the portal's homepage to more effectively showcase LoCo team activity and to inspire community members. URL:http://summit.ubuntu.com/uds-q/meeting/20549/community-p-loco-portal-design-iteration/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20552 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:Community SUMMARY:Application Review Board LOCATION:Room 201 DESCRIPTION:Review the processes & how the ARB team is doing. URL:http://summit.ubuntu.com/uds-q/meeting/20552/community-q-app-review-board/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20785 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES: SUMMARY:DX Packaging Training LOCATION:Room 203 DESCRIPTION:Training session for the DX team. URL:http://summit.ubuntu.com/uds-q/meeting/20785/dx-packaging-training/ X-TYPE:workshop X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20583 DTSTART:20120509T231500Z DTEND:20120510T000000Z CATEGORIES:Security SUMMARY:Kernel Backports security upgrade path LOCATION:Room 210-211 DESCRIPTION:Discuss how to get users with the kernel backports transitioned into the latest backport so they remain secure with proper security updates. URL:http://summit.ubuntu.com/uds-q/meeting/20583/security-q-kernel-backports/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20684 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Community SUMMARY:Translations roundtable LOCATION:G. Ballroom A DESCRIPTION:A roundtable to discuss any issues, improvements, ideas around the Ubuntu Translations community URL:http://summit.ubuntu.com/uds-q/meeting/20684/community-q-translations-roundtable/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20364 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Cloud & Server SUMMARY:Openstack Next Steps LOCATION:G. Ballroom B DESCRIPTION:The purpose of blueprint will keep track of the work needed to be done for integrating the Folsom release into Quantal. URL:http://summit.ubuntu.com/uds-q/meeting/20364/servercloud-q-openstack-folsom/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20806 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Desktop SUMMARY:Compiz GLES2 Handover LOCATION:G. Ballroom C DESCRIPTION:Hand over and implement the Linaro GLES 2 branches. URL:http://summit.ubuntu.com/uds-q/meeting/20806/desktop-compiz-gles2-handover/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20605 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Other SUMMARY:Future Release Infrastructure LOCATION:G. Ballroom F DESCRIPTION:As we move towards new markets and challenges to satisfy those markets, its time to re-examine how we've been doing things, and start planning for the longer term infrastructure goals we want to have in place for the next LTS and beyond. The build infrastructure has evolved since it was started 8 years ago, and several things work very well, while others could benefit from some brainstorming about what we'd do if we had a clean slate. URL:http://summit.ubuntu.com/uds-q/meeting/20605/other-q-future-release-infrastructure/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20783 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:QA SUMMARY:QA Team Organization LOCATION:G. Ballroom G DESCRIPTION:Discussing how to better organize the diverse set of teams within ubuntu and it's flavors dealing with QA. URL:http://summit.ubuntu.com/uds-q/meeting/20783/qa-q-team-organization/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20791 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Desktop SUMMARY:Regional/national application outreach LOCATION:G. Ballroom H DESCRIPTION:Several countries have "special apps", that are very useful to that country. E g applications needed to log in to government sites, for declaring taxes etc. Could we get these apps into the Software Center, the partner archive, debian...so that it is extremely easy for users to install them?\N\N==== Note ====\N\NAs this session did not get enough traction (and I didn't go and drag people in...), no action items were decided upon. :-( // David URL:http://summit.ubuntu.com/uds-q/meeting/20791/desktop-q-regional-application-outreach/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20340 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Hardware SUMMARY:Kernel Configuration Review LOCATION:Room 201 DESCRIPTION:Review of the kernel configuration for Q 12.10. 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. URL:http://summit.ubuntu.com/uds-q/meeting/20340/hardware-q-kernel-config-review/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20396 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Community SUMMARY:Ask Ubuntu tasks for 12.10 LOCATION:Room 202 DESCRIPTION:Things to accomplish for this cycle URL:http://summit.ubuntu.com/uds-q/meeting/20396/community-q-askubuntu/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20790 DTSTART:20120510T000500Z DTEND:20120510T010000Z CATEGORIES:Desktop SUMMARY:Indicator Redesign LOCATION:Room 203 DESCRIPTION:http://design.canonical.com/2012/04/status-menus/\N\NDiscussion and tasks for changes in the indicators. URL:http://summit.ubuntu.com/uds-q/meeting/20790/desktop-q-indicator-redesign/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20318 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Foundations SUMMARY:Python 3 only on the 12.10 desktop CD LOCATION:G. Ballroom A DESCRIPTION:It is a release goal to have only Python 3 on the desktop CD image for 12.10. URL:http://summit.ubuntu.com/uds-q/meeting/20318/foundations-q-python-versions/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20365 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Cloud & Server SUMMARY:Openstack QA LOCATION:G. Ballroom B DESCRIPTION:The purpose of this blueprint is to keep track of work that needs to be done in order to improve our Openstack QA lab. URL:http://summit.ubuntu.com/uds-q/meeting/20365/servercloud-q-openstack-qa/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20469 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:QA SUMMARY:Canonical QA CoP meetup at UDS LOCATION:G. Ballroom F DESCRIPTION:This meeting is held at each UDS for the Canonical QA CoP to discuss topics of quality within Canonical. This is an open session, however, so community topics and repesentation is appreciated. URL:http://summit.ubuntu.com/uds-q/meeting/20469/qa-q-community-of-practice/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20506 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Cloud & Server SUMMARY:Juju Charm Best practices LOCATION:G. Ballroom G DESCRIPTION:How are people using charms? What kind of things should we recommend to people? How can we collect these best practices? URL:http://summit.ubuntu.com/uds-q/meeting/20506/servercloud-q-juju-charm-best-practices/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20767 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Community SUMMARY:Debian Health Check LOCATION:G. Ballroom H DESCRIPTION:As ever URL:http://summit.ubuntu.com/uds-q/meeting/20767/community-q-debian/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20661 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Foundations SUMMARY:Continued development of the Ubuntu error tracker (part two) LOCATION:Jr. Ballroom 1 DESCRIPTION:Part two of: https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-crash-database URL:http://summit.ubuntu.com/uds-q/meeting/20661/foundations-q-crash-database-2/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20459 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Hardware SUMMARY:Kernel Team Round Table - Thursday LOCATION:Jr. Ballroom 2 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20459/kernel-team-round-table-thursday/ X-TYPE:roundtable X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20726 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Community SUMMARY:Community Roundtable Thursday LOCATION:Room 202 DESCRIPTION:Tasks from daily community roundtable sessions URL:http://summit.ubuntu.com/uds-q/meeting/20726/community-roundtable-thursday/ X-TYPE:roundtable X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20789 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Desktop SUMMARY:Foundations Upstart Sync LOCATION:Room 203 DESCRIPTION:Take the results of:\N\Nhttps://blueprints.launchpad.net/ubuntu/+spec/desktop-q-upstart-session-requirements\N\NAnd connect them with the foundations folks working on Upstart. URL:http://summit.ubuntu.com/uds-q/meeting/20789/desktop-q-foundations-upstart-sync/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20612 DTSTART:20120510T160000Z DTEND:20120510T165500Z CATEGORIES:Security SUMMARY:security-q-roundtable LOCATION:Room 208 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20612/security-q-roundtable/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20326 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Cloud & Server SUMMARY:Server ISO Tests Review LOCATION:G. Ballroom A DESCRIPTION:Review the current set of Mandatory, Run Once, and Optional tests for Ubuntu Server on http://iso.qa.ubuntu.com/, and make changes as needed to fit the current Ubuntu Server product. URL:http://summit.ubuntu.com/uds-q/meeting/20326/servercloud-q-server-iso-tests-review/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20336 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Other SUMMARY:Extra large application performance testing LOCATION:G. Ballroom B DESCRIPTION:Today, whether you are developing a web service, website or a web application, a vast majority of these are required to sustain a satisfactory level of service and/or user experience to a large capacity of users/clients. There is a wide range of performance challenges that today's developer needs to meet and overcome. \N\NWhat will be covered:\N* In this workshop we will explore the various performance challenges and solutions available today for developers to overcome these challenges and build failure resilient applications by using open source tools (e.g. Apache JMeter) running on Ubuntu servers.\N* This 1 hour workshop will cover end-to-end the process of building a test scenario and successfully running an extra large capacity load test. A user attending this workshop can expect to gain the knowledge of how to easily run a load test using open source tools on Ubuntu. \N\NTopics that will be covered include:\N* Today's performance challenges - what to look for\N* Available tools for super easy performance testing\N* "Hello World" in Performance Testing - creating a test script in 10 minutes using Apache JMeter\N* Run an extra large capacity test\N* Answering performance and JMeter related questions. User can ask any level of question and get answered. URL:http://summit.ubuntu.com/uds-q/meeting/20336/other-extra-large-application-testing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20382 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Hardware SUMMARY:Checkbox Core Architecture LOCATION:G. Ballroom C DESCRIPTION:Determine the various technologies to be applied in the design of Checkbox Core. Checkbox Core is a distributed testing toolkit. It will allow users to execute tests and receive status and results across private networks. Strategies must be developed to handle the complexities of this type of transaction across unsecurred networks.\N\NReasoning:\NThe current Checkbox framework is complex and difficult to enhance. There is also the added difficulty of split usage. Hardware Certification requires one type of suite, Ubuntu Friendly another, and QA a third. Checkbox Core is being designed to resolve these issues in a few ways. The first is by simplifying the design. The core is a Python library that supports the existing features of the Checkbox application, but as simple calls rather than integrated actions. Teams adopting the core can use as much or as little of this library as they need. Secondly, the core supported remote execution and results reporting, including the ability to execute across private networks. Security is, therefore, paramount to this effort. Lastly, Checkbox Core has no GUI. As a library is allows the users to determine what features they need and provides an easy SDK for developing an interface most useful to that team.\N\NStatus:\NThe Checkbox Core team is in the process of identifying the technology required to fully implement the spec as it is currently written. Some details require further discussion. Security is a major area not fully defined. A prototype is available to guide future discussions and planning. URL:http://summit.ubuntu.com/uds-q/meeting/20382/hardware-q-checkbox-core/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20706 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Community SUMMARY:IRC team meeting and IRCC review LOCATION:G. Ballroom F DESCRIPTION:a discussion of where we are at and what the major work items are for the Q cycle including\Noperator recruitment\NIRCC council member election URL:http://summit.ubuntu.com/uds-q/meeting/20706/community-q-ircc/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20514 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Foundations SUMMARY:Guided fixing of grub configuration errors LOCATION:G. Ballroom G DESCRIPTION: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. URL:http://summit.ubuntu.com/uds-q/meeting/20514/foundations-q-fix-grub-config-errors/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20564 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Desktop SUMMARY:Global menubar for Libreoffice - final polish LOCATION:G. Ballroom H DESCRIPTION:All the open issues that need to be fixed lo-menubar integration into main. URL:http://summit.ubuntu.com/uds-q/meeting/20564/desktop-p-libreoffice-lo-menubar-polish/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20485 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Other SUMMARY:Launchpad Clinic LOCATION:Jr. Ballroom 1 DESCRIPTION:Hands on help with Launchpad bugs and getting involved in contributing to Launchpad URL:http://summit.ubuntu.com/uds-q/meeting/20485/launchpad-clinic/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20293 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Foundations SUMMARY:Create /etc/pristine/ containing unmodified copies of conffiles LOCATION:Jr. Ballroom 2 DESCRIPTION:Currently, dpkg is aware of which files in a package are conffiles, the conffiles checksums and where those conffiles live on the system once the package is installed.\N\NHowever, there are problems:\N\N(1) What if the user modifies a conffile incorrectly such that the service no longer starts or behaves erratically?\N(2) What if the user modifies an Upstart job conffile such that the system no longer boots?\N      (This is the same problem as (1) but results in a significantly worse outcome!)\N(3) What if the user cannot remember what changes they made to invalidate the conffile (and forgot to backup the unmodified conffile)?\N\NThere are many facilities available to help with (3) including version-control systems and configuration management systems. However, the default Ubuntu system should have a *simple* way to mitigate some of the problem scenarios.\N\NThe proposal is to modify dpkg either directly or by way of triggers such that every conffile is installed as normal but an additional copy of the conffile is placed in /etc/pristine/ (or some sub-directory). The files will all be given the same owner+group as the corresponding original conffile but permissions will be set to 0440 to discourage inadvertent modification.\N\NThis gives the following benefits:\N\N(a) Problem (1) can be solved easily since the user can use diff(1) to compare their modified conffile with the pristine version\N     in /etc/pristine/.\N\N(b) Problem (2) can be solved in the same way as Problem (1), but there is some extra magic available to help the user:\N\NIf they have modified /etc/init/*.conf directly, or even created /etc/init/*.override files to modify the .conf file indirectly, we could add a new boot option that would invoke Upstart like this:\N\Ninit --confdir /etc/pristine/init/ --startup-event=emergency-boot --no-log --no-sessions --debug\N\NDoing this would ensure that the system will boot *using the pristine conffiles* installed in /etc/pristine/init/ rather than the\Npotentially corrupted /etc/init/*.conf files. We could then start a job based on the 'emergency-boot' event that would guide the user to restoring their system to a normally booting one. We could just show the user which job files/override files they have changed by date and offer to revert the changes but there are a few possibilities. We could even warn the user if they leave /etc/init/ in a condition different from /etc/pristine/init/ but the expectation is that at the end of the recovery process, all future boots will behave as expected.\N\N(c) By having a pristine copy of each conffile of the system, it would also be possible to provide 3-way merge facilities in the future when dpkg could show the user the following on package upgrade:\N\N- the locally modified conffile\N- the local pristine version of the conffile\N- the new about-to-be-installed pristine conffile\N\NThe costs of creating /etc/pristine/:\N\N- Extra disk space consumed\N\NTaking two 12.04 systems as examples:\N\Npackage count: 1751\Nsize of conffiles: 11M\N\Npackage count: 4041\Nsize of conffiles: 16M\N\NA basic desktop install would show slightly lower figures, but these numbers are significant enough that we might want to audit the conffiles in a default install to consider a strategy.\N\NFor example, for the first system above, of the top 15 largest conffiles, 8 come from the 'brltty' package and those 8 files account for 20% of the total conffile size (2.2M).\N\NAdditional information/thoughts:\N\N- FreeBSD already retains pristine copies of key system configuration files in /etc/defaults/. Using this name though could be confusing to Ubuntu users where /etc/default/ is used to store files that are *intended* to be modified.\N\N- What about the 'ucf' ("Update Configuration File") and 'etckeeper' packages?\N- Might be helpful to create /etc/pristine/README with a couple of lines of description? URL:http://summit.ubuntu.com/uds-q/meeting/20293/foundations-q-dpkg-pristine-conffiles/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20418 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Community SUMMARY:Unity Developer Documentation LOCATION:Room 201 DESCRIPTION:Review the existing Unity developer documentation, identify areas for improvement URL:http://summit.ubuntu.com/uds-q/meeting/20418/community-q-unity-docs/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20370 DTSTART:20120510T170000Z DTEND:20120510T174500Z CATEGORIES:Cloud & Server SUMMARY:Juju Integration LOCATION:Room 202 DESCRIPTION:Playing nicely with others, adoption/migration URL:http://summit.ubuntu.com/uds-q/meeting/20370/servercloud-q-juju-integration/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20338 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Community SUMMARY:Getting involved with Ubuntu TV LOCATION:G. Ballroom A DESCRIPTION:Identify ways to involve community in the design and implementation of the Ubuntu TV project URL:http://summit.ubuntu.com/uds-q/meeting/20338/community-q-ubuntu-tv-involvement/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20748 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:QA SUMMARY:Applying Ubuntu QA tools and practices to upstream LOCATION:G. Ballroom B DESCRIPTION:It would be useful to discuss where the Ubuntu QA team is moving with its focus on tools and practices and how it applies to upstream projects. It would be especially interesting to see how these tools can benefit upstream projects with regard to cross-platform Linux distributions support. URL:http://summit.ubuntu.com/uds-q/meeting/20748/applying-ubuntu-qa-tools-and-practiced-to-upstream/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20757 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Cloud & Server SUMMARY:Byobu LOCATION:G. Ballroom C DESCRIPTION:In 12.04, Byobu moved to Tmux as its default backend. Thoughts? What's working well? What's not?\N - on tty, tmux is a little wonky\N - on smaller sized terminals, tmux status is blanked out\N - anyone still using screen backend? maintain support for screen?\N - issues with byobu/tmux causing too much load?\N - issues on micro machines?\N - new byobu.co website -- looking for a volunteer web developer to create the site and content... URL:http://summit.ubuntu.com/uds-q/meeting/20757/servercloud-q-byobu/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20356 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Cloud & Server SUMMARY:Ubuntu Cloud Archive LOCATION:G. Ballroom F DESCRIPTION:Recently it was announced (at http://wiki.ubuntu.com/ServerTeam/CloudArchive) that we will be backporting newer releases of Openstack to precise in order to offer users a chance to use newer features of Openstack when it becomes available. The purpose of this blueprint is to figure out the process and track work that needs to be done. URL:http://summit.ubuntu.com/uds-q/meeting/20356/servercloud-q-cloud-archive/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20708 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Desktop SUMMARY:AOT compile mono libraries at install time LOCATION:G. Ballroom G DESCRIPTION: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. URL:http://summit.ubuntu.com/uds-q/meeting/20708/desktop-q-mono-aot/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20517 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Community SUMMARY:Edubuntu plans for 12.10 LOCATION:G. Ballroom H DESCRIPTION:Our usual Edubuntu session to discuss the plans for the next 6 months.\NPlease note that this time around a separate session has been booked for LTSP (foundations-q-ltsp) URL:http://summit.ubuntu.com/uds-q/meeting/20517/community-q-edubuntu/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20424 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Desktop SUMMARY:Quality, Testability of Desktop Components LOCATION:Jr. Ballroom 2 DESCRIPTION:The Canonical upstream teams did some good progresses on testing and quality this cycle, that's a good step for the Ubuntu Desktop quality, we still rely on quite some components from other upstreams though that didn't engage into a such process yet though (those who looked at gnome-settings-daemon, nautilus, gvfs, etc bugs on launchpad probably know what I mean there). I would like to see if we can work on our side and with upstream to get those automated tested in some ways.\N\NIt would be also nice to see regular run and report of the testsuits for other components which already have one (i.e glib, gtk) and some testing of their rdepends before upload. URL:http://summit.ubuntu.com/uds-q/meeting/20424/desktop-q-desktop-quality/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20617 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Foundations SUMMARY:Event-based initramfs LOCATION:Room 201 DESCRIPTION:Initramfs is used for getting the root filesystem mounted and passing control the real init on the real root fs. Once the kernel boots, it passes control to the init in the initramfs. This init then runs scripts that are responsible for checking if the root device is configured properly and capable of mounting the root fs on it. In parallel, behind the scenes, udev runs and uses the help of blkid to run "admin" scripts like "mdadm", "lvm", "cryptsetup" to configure the root device. This is all event based, i.e the devices are configured as and when they become available. However the exception to this is configuring the LUKS devices, which are configured using cryptsetup. The script that runs cryptsetup, first checks up if the device which is to be configured as an encrypted device, is available. If not then it waits for some time and then it checks again if the device is available or not. If not then it will simply give up and get the user to a busybox prompt. If the device is available, then cryptsetup is called and the device is configured as a LUKS device. Once the device is available a udev event is generated and again, udev runs blkid and calls whatever admin script needs to be called if any other subsystem is stacked on top of this LUKS device. While all this is good, there are two observations to be made here:\N\Na. The invocation of cryptsetup is procedural and not completely event based.\N\Nb. There is a repeatition of code for mounting, checking filesystems, crypt devices, LVM devices and so on - one code path is found in upstart jobs and the other in initramfs.\N\NSo one idea that lets you remove this duplication and at the same time enables the LUKS devices in an event based fashion, is to make the initramfs event based in the true sense, by bringing in upstart in initramfs. This means that we copy the jobs in /etc/init/ in initramfs and run them at boot time. This brings in the simplicity, elegance and robustness of upstart in initramfs and also gives you more flexibility to handle the events in a way that you want URL:http://summit.ubuntu.com/uds-q/meeting/20617/foundations-q-event-based-initramfs/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20662 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Community SUMMARY:Community Council - Code of Conduct Review LOCATION:Room 202 DESCRIPTION:Reviewing and discussing all the feedback we've received on the CoC V 2 URL:http://summit.ubuntu.com/uds-q/meeting/20662/community-council-code-of-conduct-review/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20401 DTSTART:20120510T180000Z DTEND:20120510T185500Z CATEGORIES:Community SUMMARY:Juju Training Events LOCATION:Room 210-211 DESCRIPTION:Charms Schools, webinars, and IRC, oh my! URL:http://summit.ubuntu.com/uds-q/meeting/20401/community-q-juju-training-events/ X-TYPE:discussion X-ROOMNAME:room-210-211 END:VEVENT BEGIN:VEVENT UID:20553 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Community SUMMARY:Stack overflow Ask Ubuntu service integration and monitoring LOCATION:G. Ballroom B DESCRIPTION:The Stack Overflow affiliated website Askubuntu.com has yielded volumes of user information and valuable direct community involvement. It's likely worth the effort to pay special attention to this resource particularly with upcoming future challanges requiring informing of users confused by Unity, trying out Ubuntu TV or server cloud features, or installing Ubuntu on a tablet device, for example. Discussion will likely involve new concepts to better serve question askers and answer providers alike. Automation of question keyword filtering and responsible person notification, search machine optimization, topic separation according to UX, application development, and API enrichment are subtopic candidates. URL:http://summit.ubuntu.com/uds-q/meeting/20553/community-q-askubuntu-integration/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20766 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Other SUMMARY:Defects Dashboard LOCATION:G. Ballroom C DESCRIPTION:Rationale:\NThis is a revival of https://blueprints.launchpad.net/ubuntu/+spec/other-p-bug-dashboard. \NWe have lots of sources of information about our packages and bugs, and issues potentially unreported (with whoopsie-daisy). We need to consolidate this information and make it available in a palatable way, so we can worry about what to do to fix and avoid bugs, instead of worrying about how to figure out where to look to check for issues.\N\NGoal:\NHave a centralized place to do a health check of Ubuntu. We want, in a glance, to be able to know packages that have spikes in bugs, bugs that should be fixed but aren't getting the proper attention, problems that are happening but no bugs were reported yet, and the like. URL:http://summit.ubuntu.com/uds-q/meeting/20766/other-q-defects-dashboard/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20787 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Community SUMMARY:Ubuntu LoCo Council Items for the Quantal cycle LOCATION:G. Ballroom F DESCRIPTION:This will detail the plan for the Loco Council for loco teams, approval, any new guidance pages to be written, goals to help get locoteams more involved in the community URL:http://summit.ubuntu.com/uds-q/meeting/20787/community-q-lococouncil/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20513 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Cloud & Server SUMMARY:cloud-init and cloud-utils discussion LOCATION:G. Ballroom G DESCRIPTION:Discuss ideas for cloud-init or cloud-utils.\NRequest for Features?\NRequest for Participation in developing Features?\N URL:http://summit.ubuntu.com/uds-q/meeting/20513/servercloud-q-cloud-init-utils/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20414 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Community SUMMARY:Upstream App Developer Support LOCATION:Jr. Ballroom 1 DESCRIPTION:Provide support and mentoring resources for upstream app developers who want to port or integrate their application with Ubuntu and Unity URL:http://summit.ubuntu.com/uds-q/meeting/20414/community-q-upstream-support/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20476 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Other SUMMARY:Developer Membership Board Discussion LOCATION:Jr. Ballroom 2 DESCRIPTION:This is not the DMB Meeting (that'll be a private meeting).\N\NTopics:\N* Setting reasonable expectations to applicants\N  - Some sort of self test?\N  - Documentation on our requirements from endorsers?\N* Disentangling membership from PPU.\N* Expiring PPU rights.\N* Periodic upload rights review?\N* Meeting length. How can we get through applicants faster. URL:http://summit.ubuntu.com/uds-q/meeting/20476/other-q-dmb-discussion/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20631 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Foundations SUMMARY:Upstart stateful re-exec LOCATION:Room 202 DESCRIPTION:= Summary =\N\NUpstart is not currently able to retain state across a re-exec. Re-exec is useful in the following scenarios:\N\N(1) The version of Upstart is upgraded.\N\N(2) An Upstart dependency (eglibc, libnih) is upgraded.\N\N(3) Upstart is run from the initramfs.\N\NWithout full re-exec support, upgrades are complicated significantly. An example:\N\Nhttps://bugs.launchpad.net/ubuntu/+source/upstart/+bug/985755\N\NProblem here is that upgrading from lucid to precise causes errors since the version of Upstart *running* is older than the version of Upstart *installed*. Full re-exec handling would resolve the problem as that would allow the post-inst script to re-exec upstart such that the running version == the installed version.\N\N= Details =\N\NThe problem is no so much the re-exec - that's easy to do, but that on re-exec, the new instance of Upstart needs to retain the state of the old instance (difficult). This state-passing would be critical to having Upstart run in the initramfs for example since without it, the main system instance of Upstart would have no knowledge of existing jobs started by Upstart in the initramfs (for example plymouthd).\N\N= Plan =\N\N- create a pipe.\N- fork.\N- child creates socket and listens on it.\N- child passes details of socket back to parent via pipe\N (or could just use well-known location).\N- child closes pipe.\N- parent re-execs itself (closing pipe), passing a cmdline option to notify\N init to read from the socket.\N- child sends meta-data on existing jobs through pipe.\N- parent parses meta-data and initializes data structures based on this info.\N\N Plan is to use JSON for structured representation of meta-data.\N\N= Perceived issues =\N\N- Cannot restore D-Bus connections. This might not be an issue for the initramfs scenario since there shouldn't be any, but is an issue for Upstart upgrades.\N- New version of init being exec'ed must understand all historical JSON syntax quirks if we ever change how we represent objects.\N- Child must send its version to the re-exec'ed parent and if that parent detects the child is newer than it, state passing would\N be usafe since this scenario is indicative of downgrading the Upstart version. In such instances, the best course of action may be to:\N - generate a warning\N - log the childs state to a file\N - re-exec with no state-passing.\N- adding an extra library dependency to /sbin/init is a concern.\N- existing JSON libraries may be unsuitable for boot\N - would need to select a library with very clean code and\N comprehensive tests.\N - should we implement a JSON subset parser in NIH for safety?\N - time cost (code+tests) may be prohibitive?\N\N= References =\N\N- https://bugs.launchpad.net/upstart/+bug/348455\N- https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-event-based-initramfs\N- https://lists.ubuntu.com/archives/upstart-devel/2011-August/001707.html\N URL:http://summit.ubuntu.com/uds-q/meeting/20631/foundations-q-upstart-stateful-re-exec/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20562 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Community SUMMARY:Ubuntu Women UDS-Q Goals LOCATION:Room 203 DESCRIPTION:Goals for the Ubuntu Women UDS-Q cycle\N\NAdd your ideas here for consideration in this formal blueprint: http://wiki.ubuntu-women.org/Roadmap-Q URL:http://summit.ubuntu.com/uds-q/meeting/20562/community-q-ubuntu-women-project-goals/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20702 DTSTART:20120510T190000Z DTEND:20120510T200000Z CATEGORIES:Other SUMMARY:Staffing the +1 maintenance team for Quantal LOCATION:Room 204 DESCRIPTION:Discuss staffing of the +1 maintenance team for Q, to make sure we have a full roster. URL:http://summit.ubuntu.com/uds-q/meeting/20702/other-q-plus-one-maintenance-staffing/ X-TYPE:discussion X-ROOMNAME:room-204 END:VEVENT BEGIN:VEVENT UID:20636 DTSTART:20120510T210000Z DTEND:20120510T211500Z CATEGORIES: SUMMARY:Ubuntu Automation Test Harness LOCATION:Hall East DESCRIPTION:Gema Gomez URL:http://summit.ubuntu.com/uds-q/meeting/20636/ubuntu-automation-test-harness/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20540 DTSTART:20120510T211500Z DTEND:20120510T213000Z CATEGORIES: SUMMARY:Calxeda LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20540/calxeda/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20635 DTSTART:20120510T213000Z DTEND:20120510T214500Z CATEGORIES: SUMMARY:State of the OpenStack Union LOCATION:Hall East DESCRIPTION:Thierry Carrez URL:http://summit.ubuntu.com/uds-q/meeting/20635/state-of-the-openstack-union/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20541 DTSTART:20120510T214500Z DTEND:20120510T220000Z CATEGORIES: SUMMARY:MAAS Demo LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20541/maas-demo/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20327 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Foundations SUMMARY:Improvements to the bucketing system in the crash database LOCATION:G. Ballroom A DESCRIPTION:In 12.04 we have a fairly simple bucketing algorithm. Taken from apport, it merely concatenates the top of the stack trace with the signal and binary path [1]. It does not make use of apport's bug patterns [2] or hooks [3].\N\NIn 12.10, we should provide server-side hooks that in some cases provide additional information to diagnose the issue and in other cases provide part of the unique identifier for the aforementioned set of instances that form a bucket.\N\NDevelopers will be able to set flags in the crash database service that require clients reporting future instances of a crash that matches a pattern to attach specified additional information.\N\NCare will have to be taken to notify the user that additional information may be collected, while still ensuring that in the absence of an Internet connection, crashes can be processed by the user immediately but uploaded later.\N\NThe process of attaching additional information cannot provide an interactive UI.\N\N1: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/report.py#L1142\N2: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/report.py#L793\N3: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/doc/package-hooks.txt URL:http://summit.ubuntu.com/uds-q/meeting/20327/foundations-q-bucketing-improvements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20321 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Community SUMMARY:Leadership Summit LOCATION:G. Ballroom B DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20321/leadership-summit/ X-TYPE:workshop X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20426 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Desktop SUMMARY:Holistic Approach to Ubuntu Documentation LOCATION:G. Ballroom C DESCRIPTION:I think it's necessary for Ubuntu to take documentation to another level.\N\NWhen I first started with Ubuntu, I really wanted to learn how it all\Nfit together. I have used computers most of my life so I'm accustomed to\Nreading documentation and I was perfectly willing to dive right in. But\Nit just wasn't that easy, not necessarily because of the information\Nitself, but because of how it was organized and presented. There were no\Nclear starting point and no trails to follow. There were broken links on\Nwikis, and outdated information lying around. Much of the documentation\Nwould only use version numbers, and have no easy way to see when it was\Nlast updated, or if it had been superseeded. Confusion reduces peoples\Nability to learn.\N\NTo me, this is The Issue with Ubuntu. If we're really going to succeed\Nin taking Ubuntu «across the chasm», then we must make it easy for the\Ncurious to become users and for the enthusiasts to become power-users.\NFor this to happen, we need to do something drastic about the way\Ndocumentation is presented. I think Ubuntu Documentation must:\N\N* Have an obvious starting point\N* Lead to the next step\N* Be instantly recognizable as valid or invalid\N* Be grouped when applicable\N* Primarily focused on LTS\N* Reviewed for each release (hence the point above)\N* Easy to contribute to by reporting issues\N* Be not only API docs, but contain readable text.\N\Ndeveloper.u-c and help.u-c has improved a lot in this regard, but not\Nenough. Look at this page first:\Nhttp://developer.ubuntu.com/resources/platform/api/12-04/. As a reader,\NI can come across issues that I'm not able to read, but will help\Nimprove the documentation. I should have a very easy way to report it.\NThere's no way at all on that site, though at the very bottom, I can\Nsubmit a tutorial.\N\NAnother example, look at this page:\Nhttp://developer.ubuntu.com/api/ubuntu-12.04/python/Unity-5.0.html.\NRight, but that's Ubuntu 5.0. I was looking for 5.10. Is this still\Nvalid? There's no way to know. We shouldn't rely on people to trust that\Nif not stated otherwise, it is valid. This is the web. There are\Nmillions of old and unmaintained documents out there. It must be obvious\Nthat it is valid. This also helps anyone recognize invalid\Ndocumentation, enabling them to report it or fix it.\N\NAnd what if my primary focus is developing an application for LXDE and I\Nwant to use only an indicator? In this specific case, I'd use a separate\Nversion for the API docs and call it Unity Specification 1.0 for 12.04.\NThen if there are any changes between now and 14.04, I'd call that 2.0.\NFor versions in between I'd add 1, 2 or 3. So, if there are API changes\Ni 13.04, I'd expect to find a Unity Specification 1.2 and that it would\Nclearly show the differences between 1.2 and 1.0, considering the newest\NLTS the\N\NIn the case of Unity-5.0 for Python above, I'm not sure I'd call that\NDocumentation. That is the convention, but I'm not sure that's what\Npeople expects. I'd call that document a Specification. For\NDocumentation, I would expect more readable text, explaining what it's\Nfor and how it is used.\N\NEnum: Unity.FilterRenderer\NCHECK_OPTIONS_COMPACT 4\N\NRight. How do I use it? .)\N URL:http://summit.ubuntu.com/uds-q/meeting/20426/desktop-q-holistic-documentation/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20367 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Cloud & Server SUMMARY:XCP Toolstack Improvements LOCATION:G. Ballroom F DESCRIPTION: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.\N[edit] URL:http://summit.ubuntu.com/uds-q/meeting/20367/servercloud-q-xcp/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20516 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Foundations SUMMARY:Networking improvements for Quantal (IPv6, DNS, Network Manager) LOCATION:G. Ballroom G DESCRIPTION:Catch all session (should be scheduled in a big slot if possible) for networking in Quantal.\NDiscussing 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. URL:http://summit.ubuntu.com/uds-q/meeting/20516/foundations-q-networking/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20567 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Desktop SUMMARY:LibreOffice packaging for Ubuntu q-series LOCATION:G. Ballroom H DESCRIPTION:General packaging blueprint for LibreOffice 3.6 on Ubuntu Q URL:http://summit.ubuntu.com/uds-q/meeting/20567/desktop-q-libreoffice-packaging/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20352 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Cloud & Server SUMMARY:Push to the Clouds LOCATION:Jr. Ballroom 1 DESCRIPTION:Continuation of Push to the Clouds\N\N1. Publishing image meta-data via Glance Servers: Hardware is till pending on the production servers. Glance.ubuntu.com has been provisioned with a staging host.\N\N Discussion: \N 1. What images do we want to publish? \N 2. Do we need to produce -disk1.img (KVM compataible boot images) for \N pre-Precise images?\N 3. Are the disk image formats provided on cloud-images.ubuntu.com \N adiquate? Do we need to produce other disk image types?\N \N2. Publishing of official Ubuntu images on other cloud vendors\N\N\N\N\N\N\N\N\N. URL:http://summit.ubuntu.com/uds-q/meeting/20352/servercloud-q-push-to-the-clouds/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20561 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Community SUMMARY:Ubuntu Hams - current status and future plans LOCATION:Jr. Ballroom 2 DESCRIPTION:We'll talk about amateur radio, and promoting Ubuntu-hams. In particular, there is interest in using gnuradio with some of the TV receiver USB dongles which are supported. URL:http://summit.ubuntu.com/uds-q/meeting/20561/community-q-ubuntu-hams/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20808 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Foundations SUMMARY:DEX (and debian-derivatives) discussion LOCATION:Room 201 DESCRIPTION:Session to discuss where DEX -- making sure patches from Ubuntu and other derivatives are getting back upstream, and reducing Ubuntu/Debian divergence -- should be focusing work. See here for some discussion:\N\Nhttp://thread.gmane.org/gmane.linux.debian.derivatives/866 URL:http://summit.ubuntu.com/uds-q/meeting/20808/dex-and-debian-derivatives-discussion/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20813 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Design SUMMARY:Ubuntu Mobile Use Cases LOCATION:Room 202 DESCRIPTION:Since Mark Shuttleworth's writings of Ubuntu on mobile devices [1] there will be more and more interest expressed in what hardware is most useful and which software components lead to wh at user experience. This blueprint serves to measure the progress of Ubuntu development toward mobile use cases. Anything concrete can be included in a test plan, otherwise discussion likely involves sharing of knowlege and new ideas. For example, regarding the 'magick rotation' software, just how stable is it and relevant will it continue to be? What are the most important features of Ubuntu on Android and how is this part of the larger goal towards mobility? Being that UDS includes 'Desktop' and 'Server' tracks but nothing relating to mobility, this blueprint best fits between 'Design' and 'Other.'\N\N[1] http://www.markshuttleworth.com/archives/820 URL:http://summit.ubuntu.com/uds-q/meeting/20813/design-q-mobility-factors/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20825 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Desktop SUMMARY:Improved Authentication Experience LOCATION:Room 203 DESCRIPTION:It would be nice to improve the authentication mechanisms in Ubuntu to be more user friendly and make it easier to enable modern authentication schemes. This will probably involve:\N- Reviewing the messages/prompts in PAM for appropriateness\N- Adding hints to PAM to allow GUIs to better display the prompts (i.e.\Nif a prompt is for a password, key number, if prompting for a password\Nchange).\N- Improving the Unity Greeter prompts to interpret the hints\N- Improving PolicyKit to interpret the hints\N- Making it easier to enable non-password authentication (e.g. LDAP, two\Nfactor). URL:http://summit.ubuntu.com/uds-q/meeting/20825/desktop-p-improved-authentication/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20821 DTSTART:20120510T220000Z DTEND:20120510T230000Z CATEGORIES:Desktop SUMMARY:LTS point release backports of X/kernel/etc. stack LOCATION:Room 204 DESCRIPTION:Pockets vs. renames vs. PPAs for deployment of update stacks to LTS point releases. URL:http://summit.ubuntu.com/uds-q/meeting/20821/desktop-q-xorg-lts-backport-2/ X-TYPE:discussion X-ROOMNAME:room-204 END:VEVENT BEGIN:VEVENT UID:20824 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Desktop SUMMARY:Zeitgeist in Q LOCATION:G. Ballroom A DESCRIPTION:- zeitgeist 1.0?\N- libzeitgeist 2.0?\N- what applications are still missing zg integration?\N- changes needed for "activity-log-manager" aka "Privacy" panel?\N\NItems postponed from P:\N- unity quicklists\N- contacts lens\N- disabling reading from DB (while still logging) URL:http://summit.ubuntu.com/uds-q/meeting/20824/desktop-q-zeitgeist/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20683 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Cloud & Server SUMMARY:Getting Chef Back Into Ubuntu LOCATION:G. Ballroom C DESCRIPTION:In 12.04 chef and ohai were removed from the Ubuntu archives at the request of the maintainer due to being outdated and unsupported. This session is about how we can get both chef and ohai back into the Ubuntu archives at supported levels. URL:http://summit.ubuntu.com/uds-q/meeting/20683/servercloud-q-chef/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20490 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Foundations SUMMARY:Continuous scan of the archive for ISA (in)compatibility LOCATION:G. Ballroom F DESCRIPTION:Every architecture we ship has instruction supersets that cause incompatibilities with our baseline targets, for example:\NNEON on armhf\Naltivec on powerpc\Ncmov on i386\Nsse, 3dnow, etc on amd64\N\NWe need to both define a base ISA for each architecture, and sort out ways to continually scan for violations of same. URL:http://summit.ubuntu.com/uds-q/meeting/20490/foundations-q-isa-scanning/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20703 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Other SUMMARY:Planning session for the 12.04.1 point release LOCATION:G. Ballroom G DESCRIPTION:Session to discuss how the virtual team working on the 12.04.1 point release will organize their work URL:http://summit.ubuntu.com/uds-q/meeting/20703/other-q-12.04.1-team/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20400 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Community SUMMARY:juju portal LOCATION:Jr. Ballroom 1 DESCRIPTION:Easy docs and stuff for people URL:http://summit.ubuntu.com/uds-q/meeting/20400/community-q-juju-portal/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20652 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Design SUMMARY:Course of Unity Bindings Frameworks (Qt, Gtk+) LOCATION:Jr. Ballroom 2 DESCRIPTION:Mark Shuttleworth announced (a while ago for 11.04) that Canonical would leverage Qt more, and subs\Nequently Qt is found in important parts of Ubuntu like Ubuntu One.\N\NBeing a relatively new kid on the block, Unity has its work cut out for outreach to existing developers of both Qt and Gnome/Gtk+ interfaces. Without coordination and documentation the advantages of this delicate balance of legacy interface development and ermerging Unity technology are lost.\N\NIn simple terms, this blueprint serves to consider and unify developers' goals and ideas concerning Unity and legacy Qt and Gnome/Gtk+ bindings. Deliverables could include a wiki page for easy to understand development information applicable to both APIs. URL:http://summit.ubuntu.com/uds-q/meeting/20652/design-q-unity-bindings/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20675 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Cloud & Server SUMMARY:PowerNap integration into OpenCompute LOCATION:Room 201 DESCRIPTION:Discuss the integration of PowerNap into OpenCompute, and gather ideas for its roadmap. URL:http://summit.ubuntu.com/uds-q/meeting/20675/servercloud-q-powernap-opencompute-integration/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20676 DTSTART:20120510T231500Z DTEND:20120511T000000Z CATEGORIES:Other SUMMARY:MOTU BOF Session LOCATION:Room 202 DESCRIPTION:MOTU's current mission has been defined as:\N\N* Maintaining packages that do not belong in any package-sets.\N* Providing guidance and training for new generalist developers.\N* Extended Quality Assurance functions.\N\NAre we living up to this mission? What plans do we want to make for the Quantal cycle? URL:http://summit.ubuntu.com/uds-q/meeting/20676/other-q-motu-bof/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20699 DTSTART:20120511T000500Z DTEND:20120511T010000Z CATEGORIES:Other SUMMARY:Release Team Members meeting LOCATION:G. Ballroom F DESCRIPTION:Meeting of release team members to discuss release process improvements. URL:http://summit.ubuntu.com/uds-q/meeting/20699/other-q-release-team-meeting/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20815 DTSTART:20120511T000500Z DTEND:20120511T010000Z CATEGORIES:QA SUMMARY:Drafting testcases for ubuntu flavors LOCATION:G. Ballroom G DESCRIPTION: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 URL:http://summit.ubuntu.com/uds-q/meeting/20815/qa-q-testcases-for-flavors/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20488 DTSTART:20120511T000500Z DTEND:20120511T010000Z CATEGORIES:Foundations SUMMARY:Continued development of the Ubuntu error tracker LOCATION:Jr. Ballroom 1 DESCRIPTION:Integration with a hardware database.\NPig or Hive (Hadoop) support.\NBackporting the reporting client (whoopsie) to previous Ubuntu versions.\NDiscuss the state of Upstart's inotify event support.\NFurther changes to the statistics website.\NAPI requirements.\NSort out our story on mean time between failures (http://paste.ubuntu.com/957235/, http://instagr.am/p/KDe4WPhRxl).\NAdditional problem types (desktop application hangs, package installation failures, debconf dialogs during package installation, ...)\NProviding an apport API for applications handling recoverable errors.\NSurfacing architecture (and other data points) only when relevant\NShould we continue to process and retrace crashes from derivatives?\NCan we set /proc/sys/fs/suid/dumpable to 2? (programs not normally dumped are dumped, but only readable by root). We need some way of ensuring we never ever send cores from ssh-agent, among others.\N...\N\NOther crash database blueprints:\Nhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-q-crash-database-2\Nhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-q-metrics\Nhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-q-updates-from-crash-reports\Nhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-q-fix-ddebs\Nhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-q-bucketing-improvements\Nhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-q-phased-updates\N\NAdditional background information:\Nhttp://paste.ubuntu.com/958213/\N\NSpecification (read this first):\Nhttp://wiki.ubuntu.com/ErrorTracker URL:http://summit.ubuntu.com/uds-q/meeting/20488/foundations-q-crash-database/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20507 DTSTART:20120511T000500Z DTEND:20120511T010000Z CATEGORIES:Cloud & Server SUMMARY:Juju Charm Unit Tests LOCATION:Jr. Ballroom 2 DESCRIPTION:Including tests within each charm URL:http://summit.ubuntu.com/uds-q/meeting/20507/servercloud-q-juju-charm-unit-tests/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20814 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Other SUMMARY:extending juju to the hud LOCATION:G. Ballroom A DESCRIPTION:taking the successes on juju to use the hud to search and find computing tasks.\N\Nusers could open the hub, and using natural language, type a question or describe a problem and an appropriate juju "charmling" will help the user solve the problem without the need for appreciable computer knowledge.\N\Nthis would use heuristics to determine possible solutions, choose the most likely correct "charmling", and assist the user.\N\Nuse cases could extend to any desktop usage, including very complex tasks requiring multiple steps and settings. examples might include:\N * fix a broken wireless connection\N * install packages\N * add a printer\N * connect to a print server\N\Nfor example, a user needs to add a printer. the user would open the hud and type, "how do i add a printer?". heuristics would determine the most probably answer, and start the "charmling" which would open an informational dialogue box telling the user, "The printer dialogue box is being opened. You probably want to select the "+ Add" button" and then opens the printer dialogue box.\N\Nanother example might be a user wanting to create a pdf. user opens the hud, types the question, heuristics are employed, and "charmling" is deployed which opens up a sane tutorial with examples.\N\N URL:http://summit.ubuntu.com/uds-q/meeting/20814/other-q-juju-and-the-hud/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20720 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Cloud & Server SUMMARY:Choosing an OpenFlow Controller for Ubuntu LOCATION:G. Ballroom B DESCRIPTION:OpenFlow enables networks to evolve, by giving a remote controller the power to modify the behavior of network devices, through a well-defined "forwarding instruction set". -http://www.openflow.org/\N\NThere are several FOSS implementations of openflow controllers. This session is intended to review the list and choose one for packaging in universe. Our criteria will be based on language choice, quality, development community health, and OpenStack Quantum support.\N\NThe current list for review are:\N\N1) NOX[1] - Created by Nicira, supporting C++. No quantum plugin. Not\Nto be confused with "NOX classic" an older implementation supporting\Nboth C++/Python. \N\N2) POX[2] - Same as NOX, but younger of the two projects and supports\NPython. No quantum plugin. \N\N3) Beacon[3] - Research project written in Java by David Erickson, a PhD\Ncandidate at Stanford. No quantum plugin.\N\N4) Floodlight[5] - Written in Java and recently opensourced by Big\NSwitch Networks as "the foundation of a commercial controller product". In terms of Quantum plugins, Big Switch Networks stated on the project mailing list[6] that it wasn't in *their* roadmap,\Nbut encouraged the community to do it, e.g.:\N "...Big Switch also has a quantum plugin but its based on\N functionality not present in Floodlight on this point."\N\N5) Trema[7] - Supports Ruby and C. Developed out of Japan according to their twitter\Nfeed[8]. NEC has created a Quantum plugin[9] that works with Trema, as well as their commercial OpenFlow controller.\N\N6) RYU[10] - Written in Python by NTT, who have also directly contributed a Quantum plugin[11].\N\N\N [1] http://www.noxrepo.org/nox/about-nox/\N [2] http://www.noxrepo.org/pox/about-pox/\N [3] https://openflow.stanford.edu/display/Beacon/Home\N [4] http://www.linkedin.com/pub/david-erickson/3/89b/166\N [5] http://floodlight.openflowhub.org/\N [6] http://bit.ly/K1w69p\N [7] http://trema.github.com/trema/\N [8] http://twitter.com/#!/trema_news\N [9] https://github.com/nec-openstack/quantum-openflow-plugin\N [10] http://www.osrg.net/ryu/\N [11] https://github.com/openstack/quantum/tree/master/quantum/plugins/ryu URL:http://summit.ubuntu.com/uds-q/meeting/20720/servercloud-q-openflow-controller/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20707 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Desktop SUMMARY:Finger print authentication LOCATION:G. Ballroom C DESCRIPTION:Improve finger print authentication in Ubuntu URL:http://summit.ubuntu.com/uds-q/meeting/20707/desktop-p-fingerprintauthentication/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20495 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Foundations SUMMARY:Transition the archive to Java 7 LOCATION:G. Ballroom F DESCRIPTION:Java 7 was released last year and is now the primary development/support focus for both OpenJDK and Oracle.\N\NJava 6 has limited support lifetime left.\N\NWe should transition all Java packages in the archive to OpenJDK 7 and endeavour to drop OpenJDK 6 from the archive. URL:http://summit.ubuntu.com/uds-q/meeting/20495/foundations-q-java7/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20518 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:QA SUMMARY:Adding test coverage to Ubuntu LOCATION:G. Ballroom H DESCRIPTION:Start building a comprehensive regression testing suite, this blueprint is a discussion to decide where to start adding test cases, so basically choose the most important missing tests and have a clear list of priorities. URL:http://summit.ubuntu.com/uds-q/meeting/20518/qa-q-add-test-coverage/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20448 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Cloud & Server SUMMARY:ARM Server Deployment LOCATION:Jr. Ballroom 1 DESCRIPTION:System management and service orchestration for ARM Server, including MAAS and juju enablement. URL:http://summit.ubuntu.com/uds-q/meeting/20448/servercloud-q-arm-deployment/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20460 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Hardware SUMMARY:Kernel Team Round Table - Friday LOCATION:Jr. Ballroom 2 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20460/kernel-team-round-table-friday/ X-TYPE:roundtable X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20727 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Community SUMMARY:Community Roundtable Friday LOCATION:Room 201 DESCRIPTION:Tasks from daily community roundtable sessions URL:http://summit.ubuntu.com/uds-q/meeting/20727/community-roundtable-friday/ X-TYPE:roundtable X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20565 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Desktop SUMMARY:Gwibber Service improvements LOCATION:Room 202 DESCRIPTION:Discussion of plans for improvements to the Gwibber service in 12.10\N\NThe Gwibber backend needs some re-factoring to make it more testable, robust and faster. URL:http://summit.ubuntu.com/uds-q/meeting/20565/desktop-q-gwibber/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20807 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Other SUMMARY:SPDX and DEP5 Generation LOCATION:Room 203 DESCRIPTION:SPDX and DEP5 Generation URL:http://summit.ubuntu.com/uds-q/meeting/20807/other-q-spdx-gen/ X-TYPE:discussion X-ROOMNAME:room-203 END:VEVENT BEGIN:VEVENT UID:20294 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Foundations SUMMARY:Finish the archive reorg LOCATION:Room 204 DESCRIPTION:Archive reorganization has been stalled in a halfway state. Discuss what needs to happen for 12.10 to make the main/universe distinction obsolete for community and Canonical stakeholders. URL:http://summit.ubuntu.com/uds-q/meeting/20294/foundations-q-finish-archive-reorg/ X-TYPE:discussion X-ROOMNAME:room-204 END:VEVENT BEGIN:VEVENT UID:20613 DTSTART:20120511T160000Z DTEND:20120511T165500Z CATEGORIES:Security SUMMARY:security-q-roundtable LOCATION:Room 208 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20613/security-q-roundtable/ X-TYPE:discussion X-ROOMNAME:room-208 END:VEVENT BEGIN:VEVENT UID:20430 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Desktop SUMMARY:The future of third-party driver installation LOCATION:G. Ballroom B DESCRIPTION:We have had Jockey for quite a while now to perform the installation\Nof proprietary (e. g. NVidia), alternative (e. g. fglrx vs.\Nfglrx-updates), third-party (e. g. from openprinting.org) drivers.\N\NHowever, I feel that this needs some refreshing:\N\N * The code base of Jockey is quite complex, it was meant for a lot\N more stuff than we are actually using it for. We also came up with\N simpler ways of mapping hardware to packages, mostly with\N additional tags in the apt package lists. We also have a more\N upstream friendly API in PackageKit/aptdaemon now to do this kind\N of thing.\N\N We can simplify the jockey code base and backend logic a lot (up\N to the extend of completely dropping it) by making full use of\N above new technologies and dropping the extra features we don't\N use. The exception is the openprinting.org detection, but that\N could go into system-config-printer or python-cups directly.\N\N * We install some drivers (like Broadcom wifi) straight from Ubiquity\N now, which certainly makes sense for devices where there is no free\N alternative. For the others (e. g. NVidia) we pop up a notification\N and offer to install them. I'd like to walk through the current UI\N and discuss how this could be made more steamlined and less\N confusing (e. g. for NVidia it can potentially offer 6 different\N drivers for you!)\N\N * We might consider merging the jockey UI functionality, which is\N mostly a shallow GUI around "install that package" now) into\N software-center, control-center, or something similar to the codec\N installer. I'd again appreciate if someone from the design team\N could participate in that (hello Matthew!).\N URL:http://summit.ubuntu.com/uds-q/meeting/20430/desktop-q-third-party-driver-installation/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20417 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Community SUMMARY:Advertise new apps in the Software Center LOCATION:G. Ballroom C DESCRIPTION:Promote the availability of new apps in the Software Center, both in USC itself and through other channels, to raise awareness of apps targeting Ubuntu URL:http://summit.ubuntu.com/uds-q/meeting/20417/community-q-app-promotion/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20760 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Cloud & Server SUMMARY:working session result of apt-improvements LOCATION:G. Ballroom F DESCRIPTION:https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-apt-improvements\N URL:http://summit.ubuntu.com/uds-q/meeting/20760/servercloud-q-apt-improvements-working-session/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20832 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Desktop SUMMARY:GNOME Flavor LOCATION:G. Ballroom G DESCRIPTION: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. URL:http://summit.ubuntu.com/uds-q/meeting/20832/desktop-q-gnome-flavor/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20544 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Desktop SUMMARY:Quickly 12.10 Enhancements LOCATION:G. Ballroom H DESCRIPTION:There's more work we can do to make Quickly better and keep pace with the platform.\N\NSpecifically this cycle, a big focus will be porting to Python 3 for both managed projects and Quickly itself. URL:http://summit.ubuntu.com/uds-q/meeting/20544/desktop-q-quickly/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20335 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Foundations SUMMARY:Plan for future x32 ABI support LOCATION:Jr. Ballroom 1 DESCRIPTION:The x32 ABI (http://sites.google.com/site/x32abi/) provides a compromise between IA32 and x86-64: it has a 32-bit pointer size, which is more memory-efficient and may often be faster, but has 64-bit registers and a larger register file. Support for it is gradually trickling into various relevant upstreams (kernel, glibc, gcc, etc.). Although the pieces are unlikely to be in place in time for 12.10, we should think ahead for how we might deploy this in Ubuntu. URL:http://summit.ubuntu.com/uds-q/meeting/20335/foundations-q-x32-planning/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20582 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Security SUMMARY:eCryptfs in Ubuntu 12.10 LOCATION:Jr. Ballroom 2 DESCRIPTION:In this session, we'll discuss eCryptfs in Ubuntu 12.10. Both of the upstream eCryptfs maintainers will be present to discuss the future of eCryptfs, upstream and in Ubuntu.\N\NTopics include:\N - Stabilization and testing with the new unit test framework\N - AES-NI acceleration improvements\N - Longstanding issues or bugs that need to be revisited\N - Steps to removing the "experimental" label in the upstream Linux kernel tree\N - Remote key retrieval in the ecryptfs-utils userspace packages\N - Introduction of ecryptfs.org\N - Migration of questions/answers from Launchpad Answers to StackExchange sites\N - Problems around the ecryptfs-utils prerm check of if ecryptfs is in use\N - ... URL:http://summit.ubuntu.com/uds-q/meeting/20582/security-q-ecryptfs/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20334 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Other SUMMARY:Improving release notes and technical overview content LOCATION:Room 201 DESCRIPTION:Our release notes and technical overview could use a bit of tuning. Part of this is to be clear on the goals they are serving. Session is for discussion of the goals, and ways we can approach better, more automated generation of the content for them.\N(Leveraging blueprints completion notes, etc.) URL:http://summit.ubuntu.com/uds-q/meeting/20334/other-q-release-notes/ X-TYPE:discussion X-ROOMNAME:room-201 END:VEVENT BEGIN:VEVENT UID:20820 DTSTART:20120511T170000Z DTEND:20120511T174500Z CATEGORIES:Foundations SUMMARY:Discuss how to allow Ubuntu-based devices to receive full-image updates LOCATION:Room 202 DESCRIPTION:Some devices that it's interesting to run Ubuntu on cannot do package-by-package updates for various reasons. Discuss what a solution looks like for implementing this with updating by way of swapping full OS images, various pitfalls associated with not running package maintainer scripts on upgrade, etc. URL:http://summit.ubuntu.com/uds-q/meeting/20820/foundations-q-image-based-updates/ X-TYPE:discussion X-ROOMNAME:room-202 END:VEVENT BEGIN:VEVENT UID:20830 DTSTART:20120511T180000Z DTEND:20120511T185500Z CATEGORIES:Desktop SUMMARY:Desktop Roundtable LOCATION:G. Ballroom A DESCRIPTION:UDS Q Desktop Recap URL:http://summit.ubuntu.com/uds-q/meeting/20830/desktop-q-desktop-roundtable/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20371 DTSTART:20120511T180000Z DTEND:20120511T185500Z CATEGORIES:Cloud & Server SUMMARY:Kvm work for Q LOCATION:G. Ballroom B DESCRIPTION:Session to discuss and collect community wishlist for kvm and related packages URL:http://summit.ubuntu.com/uds-q/meeting/20371/servercloud-q-kvm/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20489 DTSTART:20120511T180000Z DTEND:20120511T185500Z CATEGORIES:Foundations SUMMARY:Get LiveFS building happening on Soyuz buildds LOCATION:G. Ballroom F DESCRIPTION:In the interest of better parallelization, as well as better use of idle machine time, we'd like to move livefs building from an out-of-band affair to a launchpad-buildd-driven build job type. This has been architected a couple of times in the past and repeatedly not made it to implementation due to lack of time, but it really should be done soon, even if the work spans a couple of cycles. URL:http://summit.ubuntu.com/uds-q/meeting/20489/foundations-q-livefs-in-soyuz/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20462 DTSTART:20120511T180000Z DTEND:20120511T185500Z CATEGORIES:QA SUMMARY:Expanding the isotracker testcase management capabilities LOCATION:G. Ballroom H DESCRIPTION:Discussing expanding the isotracker to perform testcase management and reporting for all kinds of testing, not just iso. URL:http://summit.ubuntu.com/uds-q/meeting/20462/qa-q-isotracker-testcases/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20412 DTSTART:20120511T180000Z DTEND:20120511T185500Z CATEGORIES:Community SUMMARY:MyApps submission experience and expectations for upstreams LOCATION:Jr. Ballroom 1 DESCRIPTION:Review the current process and identify which parts of the documentation need to be improved. Also figure out what specifically we expect from upstreams and which help the ARB can provide. URL:http://summit.ubuntu.com/uds-q/meeting/20412/community-q-upstream-myapps/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20440 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:Cloud & Server SUMMARY:Next steps for Hadoop on Ubuntu LOCATION:G. Ballroom A DESCRIPTION:During Ubuntu precise, packages for hadoop, hbase, hive, zookeeper and pig where delivered via PPA for use in associated charms which are now avaliable in the charm store for Ubuntu 12.04.\N\NThe packaging is based on Apache Bigtop with relevant patches to support building on Ubuntu precise and for ARM.\N\NThis session will discuss where we take this work next. URL:http://summit.ubuntu.com/uds-q/meeting/20440/servercloud-q-bigdata-hadoop/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20397 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:Community SUMMARY:IRC Workshops LOCATION:G. Ballroom B DESCRIPTION:Here we go again! URL:http://summit.ubuntu.com/uds-q/meeting/20397/community-q-irc-workshops/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20328 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:Foundations SUMMARY:Generate debug symbols for all package versions LOCATION:G. Ballroom C DESCRIPTION:We currently only generate ddebs for the most recent versions of packages in the archive. With the new crash database, we receive a lot of core dumps which we cannot completely retrace because of this issue (https://errors.ubuntu.com/api/retracer/results). For the Launchpad-reporting side of things, this results in an ugly "cannot report this problem" dialog.\N\NIS is also not happy with the manner in which this is currently implemented.\N\NLet's get ddebs support into soyuz. URL:http://summit.ubuntu.com/uds-q/meeting/20328/foundations-q-fix-ddebs/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20729 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:Community SUMMARY:Ubuntu App Developer Site incremental improvements LOCATION:G. Ballroom F DESCRIPTION:Building upon the foundations of the initial Ubuntu App Developer site, we'd like to expand it on a second design phase.\N\NDepending on the resource allocation from design, the scope might be reduced, so this blueprint is also to discuss the incremental improvements that can make a substantial impact and that we can work on next cycle. URL:http://summit.ubuntu.com/uds-q/meeting/20729/community-p-appdevelopers-site-incremental-improvements/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20519 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:QA SUMMARY:Improving Smoke Testing Coverage LOCATION:G. Ballroom G DESCRIPTION:Have a comprehensive smoke testing suite that is reliable by the end of the cycle URL:http://summit.ubuntu.com/uds-q/meeting/20519/qa-q-builds-smoke-testing/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20555 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:Community SUMMARY:Reaching out to future Ubuntu developers LOCATION:G. Ballroom H DESCRIPTION:We reach out to potential new Ubuntu Developers in a number of ways. We have the weekly Developer update, public Hangouts, Ubuntu Developer Week, announcement of initiatives, interviews and other bits. Let's plan how we approach new contributors this cycle. URL:http://summit.ubuntu.com/uds-q/meeting/20555/community-q-dev-outreach/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20497 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:Foundations SUMMARY:Degraded Hardware Notifications aka 'things you rather not see' LOCATION:Jr. Ballroom 1 DESCRIPTION:== Degraded Hardware Notifications ==\N\NThere are multiple ways hardware can degrade on the machine you are\Nusing.\N\N* degraded RAID\N* 100% disk space usage\N* 100% inode usage\N* S.M.A.R.T. - failing hardware\N* etc (?!)\N\N== Current notifications ==\N\N* are sometimes annoying (endless popups on desktop for SMART)\N* non-existent AFAIK (inodes)\N* not configured out the box (degraded RAID http://pad.lv/535417)\N\N== Proposed notifications ==\N\NSometimes a user may not have the permissions to rectify the problem.\NThe notification should stay persistent, until fixed.\NThese notifications are important across all installation types.\NThis notifications should not replicate Nagios/Check_Mk monitoring.\N\N* system indicators (Ubuntu Desktop)\N* byobu plugin (Ubuntu Server)\N* MOTD (Ubuntu Core)\N* landscape notifications\N* others ?! (Virtual Machines, cloud instance, etc)\N\N== UDS session ==\N\N* Discuss what notifications we would like to implement\N* How/where/who will implement them URL:http://summit.ubuntu.com/uds-q/meeting/20497/foundations-q-degraded-hw-notification/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20363 DTSTART:20120511T190000Z DTEND:20120511T200000Z CATEGORIES:Cloud & Server SUMMARY:Lxc work for Q LOCATION:Jr. Ballroom 2 DESCRIPTION:Our usual LXC discussion at UDS so we get back home with plenty of container related action items. URL:http://summit.ubuntu.com/uds-q/meeting/20363/servercloud-q-lxc/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20542 DTSTART:20120511T210000Z DTEND:20120511T220000Z CATEGORIES: SUMMARY:Lightning Talks LOCATION:Hall East DESCRIPTION:Come break stuff! URL:http://summit.ubuntu.com/uds-q/meeting/20542/lightning-talks/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT BEGIN:VEVENT UID:20563 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Community SUMMARY:Unblocking Developers LOCATION:G. Ballroom A DESCRIPTION:A lot of our development processes involve a review or approval step. Let's review how we've done in the P release and see what we can improve for Q. URL:http://summit.ubuntu.com/uds-q/meeting/20563/community-q-unblocking-developers/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20705 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Community SUMMARY:Accessibility Community Team Plans LOCATION:G. Ballroom B DESCRIPTION:Planning what the Accessibility Community Team is going to do for the next cycle. We were over ambitious last cycle, so it's time to pare down and look at what's realistic for this next cycle. URL:http://summit.ubuntu.com/uds-q/meeting/20705/community-q-accessibility-community-team-plans/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20475 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Foundations SUMMARY:LTSP improvements for quantal LOCATION:G. Ballroom C DESCRIPTION:General discussion on improving LTSP's integration in Ubuntu and our overall thin client experience.\NIdeas that have been mentioned and should be discussed:\N - How to deal with chroot upgrades (currently not supported)\N - Making maintenance easier\N - Split ltsp-live out of the main ltsp package\N - Rebase on Debian's packaging for ltsp itself (only package we don't simply sync at the moment)\N - Generating a .img image from an LTSP chroot that can be used to make a standalone thin client image URL:http://summit.ubuntu.com/uds-q/meeting/20475/foundations-q-ltsp/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20511 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Cloud & Server SUMMARY:Juju upstart integration LOCATION:G. Ballroom F DESCRIPTION:Tooling to promote/encourage upstart usage in charms URL:http://summit.ubuntu.com/uds-q/meeting/20511/servercloud-q-juju-upstart-integration/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20594 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Desktop SUMMARY:Kubuntu Quantal Docs LOCATION:G. Ballroom G DESCRIPTION:a new approach to users? URL:http://summit.ubuntu.com/uds-q/meeting/20594/kubuntu-q-docs/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20770 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Community SUMMARY:Localized ISO community growth, Quantal plans LOCATION:G. Ballroom H DESCRIPTION:Review of the Precise cycle and brainstorming on how to improve. URL:http://summit.ubuntu.com/uds-q/meeting/20770/community-q-localized-iso-community-growth/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20717 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Community SUMMARY:Ubuntu Youth Team LOCATION:Jr. Ballroom 1 DESCRIPTION:The Ubuntu Youth team has been dead for a few years. It was a place where youth people can find others from their ages, and discuss about Ubuntu and what can they do about it. My intention with this session would be to find ways to revive this group, and also to define this group purpose and main vision for now on. Also, discussing how to promote it, how its leadership is going to be taken (Point for Philip Ballew, current Team leader) and how to give it an useful position in the community are points that are important to be taken care of during this session. URL:http://summit.ubuntu.com/uds-q/meeting/20717/community-q-ubuntu-youth/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20827 DTSTART:20120511T220000Z DTEND:20120511T230000Z CATEGORIES:Community SUMMARY:CC Instrumentation LOCATION:Jr. Ballroom 2 DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20827/cc-instrumentation/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20711 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES: SUMMARY:Make Ubuntu fully proxy compatible LOCATION:G. Ballroom A DESCRIPTION:Ubuntu 12.10 should be fully proxy compatible, what means that every app should work with proxies for http, https, ftp, etc.\N\N\NSo please add proxy support for:\N\Nadd-apt-repository, see bug #994569\N\Ngpg, see bug #443404\N\Nbzr, still searching for bug report URL:http://summit.ubuntu.com/uds-q/meeting/20711/full-proxy-support/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-a END:VEVENT BEGIN:VEVENT UID:20420 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES:Desktop SUMMARY:Clean Old Kernels LOCATION:G. Ballroom B DESCRIPTION:Discuss cleaning old kernels for the user URL:http://summit.ubuntu.com/uds-q/meeting/20420/desktop-q-clean-old-kernels/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-b END:VEVENT BEGIN:VEVENT UID:20554 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES:Community SUMMARY:Planning Developer/Bug fixing initiatives LOCATION:G. Ballroom C DESCRIPTION:In the past we have had great interest from new contributors in getting involved through organised initiatives. Both clarity in instructions and a clear set of targets have helped a lot here.\N\NIn the session we should discuss possible targets for bug fixing initiatives, who can help and set up an initial schedule. URL:http://summit.ubuntu.com/uds-q/meeting/20554/community-q-dev-initiatives/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-c END:VEVENT BEGIN:VEVENT UID:20522 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES:QA SUMMARY:Ubuntu Automation Test Harness LOCATION:G. Ballroom F DESCRIPTION:This blueprint is to keep track of the roadmap of UATH and the features that will land on it during Q. URL:http://summit.ubuntu.com/uds-q/meeting/20522/qa-q-ubuntu-automation-test-harness/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-f END:VEVENT BEGIN:VEVENT UID:20746 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES:Community SUMMARY:Etherpad Lite Summit integration LOCATION:G. Ballroom G DESCRIPTION: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 URL:http://summit.ubuntu.com/uds-q/meeting/20746/etherpad-lite-summit-integration/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-g END:VEVENT BEGIN:VEVENT UID:20353 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES:Other SUMMARY:Zentyal integration on Edubuntu LOCATION:G. Ballroom H DESCRIPTION:Zentyal Server is able to provide configuration deployment and management for typical services on a Edubuntu server: HTTP proxy with content-filtering, LDAP and Kerberos or LTSP thin clients. Zentyal Desktop allows to configure these services on the terminals including authentication and session profiles.\N\NExplore how can Edubuntu and Zentyal developers can work together to provide an out of the box solution for school servers.\N\NApproved blueprints that would be implemented or related with this:\N\Nhttps://blueprints.launchpad.net/ubuntu/+spec/student-control-panel-completion (zentyal desktop will integrate epoptes)\Nhttps://blueprints.launchpad.net/ubuntu/+spec/edubuntu-profile-and-network-session-management (zentyal desktop will integrate Pessulus/Sabayon with LDAP backend)\Nhttps://blueprints.launchpad.net/ubuntu/+spec/edubuntu-network-auth-client (zentyal desktop provides LDAP and Kerberos authentication)\Nhttps://blueprints.launchpad.net/ubuntu/+spec/edubuntu-network-auth-server (zentyal provides LDAP and Kerberos server)\Nhttps://blueprints.launchpad.net/ubuntu/+spec/edubuntu-user-management (zentyal has a LDAP users and groups management interface)\Nhttps://blueprints.launchpad.net/ubuntu/+spec/edubuntu-ad-integration (zentyal provides ad-sync tool and samba4 integration)\Nhttps://blueprints.launchpad.net/ubuntu/+spec/school-server-in-a-box (zentyal provides configuration of all needed services in one interface)\Nhttps://blueprints.launchpad.net/ubuntu/+spec/zero-conf-server (zentyal is a simple interface to configure all services) URL:http://summit.ubuntu.com/uds-q/meeting/20353/other-edubuntu-zentyal-integration/ X-TYPE:discussion X-ROOMNAME:grand-ballroom-h END:VEVENT BEGIN:VEVENT UID:20329 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES:Foundations SUMMARY:If a crash is already fixed by an update, prompt to install it LOCATION:Jr. Ballroom 1 DESCRIPTION:From the specification (https://wiki.ubuntu.com/ErrorTracker):\N"If a software update is known to fix the problem, replace the primary alert with the software update alert (or progress window, depending on the update policy), with customized primary text. Or point them at a web page (not a wiki page!) with details if a workaround exists, but no fix is available yet."\N\NShould we show the crashes the user has received that are now fixed by a software update in the description of that update?\NShould we provide a flag to automatically install updates that fix problems which left the system in an unusable state? URL:http://summit.ubuntu.com/uds-q/meeting/20329/foundations-q-updates-from-crash-reports/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-1 END:VEVENT BEGIN:VEVENT UID:20235 DTSTART:20120511T231500Z DTEND:20120512T000000Z CATEGORIES:Other SUMMARY:Improving weekly release meeting and other communication channels LOCATION:Jr. Ballroom 2 DESCRIPTION:Feedback on the results of the experiments we tried in precise. What worked, didn't, what we want to keep going forward. URL:http://summit.ubuntu.com/uds-q/meeting/20235/other-q-release-communication/ X-TYPE:discussion X-ROOMNAME:junior-ballroom-2 END:VEVENT BEGIN:VEVENT UID:20831 DTSTART:20120512T000500Z DTEND:20120512T010000Z CATEGORIES: SUMMARY:Closing Summary LOCATION:Hall East DESCRIPTION: URL:http://summit.ubuntu.com/uds-q/meeting/20831/closing-summary/ X-TYPE:plenary X-ROOMNAME:hall-east END:VEVENT END:VCALENDAR