Integration of DEP5 and SPDX into our packaging process for the generation of machine readable COPYING or LICENSE files for improved analysis of the licensing and copyright issues when releasing Ubuntu and derivative products.

PHP is about to make a new "minor" revision bump, from 5.3 to 5.4. This will remove some long standing security problems like register_globals, and add some advanced new features like Traits. The 5.3 series, meanwhile, will be coming to an end sometime sooner than the end of 12.04's 5 year supported cycle. In the interest of shipping an advanced but stable LTS, we should consider shipping 5.4.0 as the PHP version in 12.04 rather than 5.3.9.

Private Ops Review for ST-Ericsson LT

Private

Discuss the current HA cluster stack and its usage in OpenStack and finish with the merges of newest upstream changes. Additionally, discuss the adoption of Pacemaker Cloud [1]. "The Pacemaker Cloud project provides high levels of service availability for high scale cloud deployments. Our approach to high availability is to detect failures, isolate failures, followed by restart of the failed components. When repeated component failures occur the software escalates those failures into failures of higher level components." "" [1]: http://pacemaker-cloud.org/

jasper is a pile of hacks similar to casper. target of this spec is to re-implement the functions jasper fulfills in debian-installer modules. additionally the ac100-tarball-installer functionality should go into d-i as well.

Friday

Friday's security roundtable

Making our multi-monitor, dock and projector support better.

Translations roundtable discussion where to fit all other topics not covered in dedicated sessions

There are a few things we should cover for NetworkManager this cycle: mostly polish, but as general ideas: - reinstate daily builds for 0.9 to help with testing, knowing in advance about bugs, etc. - testing some of the new features likely to land and be useful for Precise: bonding, VLAN support, etc. - types of bugs or small enhancements that should be looked at in priority ?

Continuing cross-distribution meeting series, aimed at sharing ideas and problems that people may have related to ARM porting ARMv8 Standardization Multiarch Triplets

Profile guided optimisation is where you run a program, collect data on how it actually runs, then use that to make a further optimised build. We'd like to use PGO as a theme in a future quarter but need to investigate PGO and the potential gains first. Discuss.

Topics: - How to improve the relationship - Work on simliar features every cycle - Hardware support and LT - Ubuntu with Android image?

Representatives from Linaro SoC partners will gather to discuss the burgeoning topic of graphics power management. The issues around CPU power management for the CPU are fairly well understood and efforts are well under way, but for the GPU this is less so. We would like to cover: [1] Available measurements and controls for current generation GPUs. [2] What measurements and controls the software would ideally have access to. [3] What capabilities the next generation of GPUs might have.

Continuing cross-distribution meeting series, aimed at sharing ideas and problems that people may have related to ARM porting ARMv8 Standardization Multiarch Triplets

To more efficiently summarize and get an overview of the release, its important for tools to know which team to associate a specific package with for reporting, triage, etc. Ad hoc spreadsheets are being used at the moment, but it would be better if we had an open and flexible way to associate this property with the project in launchpad.

Private

A bit of work has been done late in the Oneiric cycle to improve friendly recovery to work better. Now with the LTS coming up, it's time to fix some of the bigger issues for good and make sure the recovery mode will be useful and working for everyone. Things to discuss include: - Dealing with udev so important devices are initialized in recovery mode - Properly initialize the network, either by using ifupdown or Network Manager - Update the plugins to work properly when network isn't available and give a clue to the user that they need to enable network

Discuss ideas to improve the community understanding of bug reporting and triage.

For USB-based mobile broadband modems it got common that the Windows driver is stored on the modem itself and as long as the driver is not installed the modem shows itself to the computer as a USB mass storage device. Therefore usb-modeswitch got introduced to switch these modems into modem modeunder Linux as there the driver is already available as a kernel module shipped with the OS. A similar problem occured now for USB printers, they also show themselves as mass storage devices by default to provide their Windows driver without need of a CD. So usb-modeswitch needs to be extended to printers Tests should be done whether the switching mechanisms are the same as for modems and only the printer's IDs need to be added or whether more work is needed.

Following on discussions the past few months on ubuntu-devel, review the current workflow for accepting new packages into Ubuntu, with an eye to refinements or improvements we could make this cycle. Includes submission to Debian, Backports, REVU (and potential for switching to DebExpo), and ARB.

Improve finger print authentication in Ubuntu

Open forum and discussion on how words and language are used in Launchpad, in the form of titles, labels, status and guides.

Charm authors will need first class documentation to write charms

There are several features in the Android kernel that are not acceptable in their current state. Linaro is interested in leading the process of developing upstream code that provides the same high-level functionality as found in the Android kernel and working on adapting the Android stack to use any new interfaces that result from this development. These features include: Wake locks https://linaro-public.papyrs.com/public/4571/KWG2011-ANDROID-WAKELOCK-UPSTREAMING Ashmem https://linaro-public.papyrs.com/public/4575/KWG2011-ANDROID-ASHMEM-UPSTREAMING Logger https://linaro-public.papyrs.com/public/4576/KWG2011-ANDROID-LOGGER-UPSTREAMING Extended OOM Killer https://linaro-public.papyrs.com/public/4577/KWG2011-ANDROID-OOM-KILLLER-UPSTREAMING Etherpad @ http://summit.linaro.org/uds-p/meeting/19254/linaro-kernel-android-upstreaming/

Currently for every kernel flavour we need the following packages: - kernel-headers-abi - kernel-headers-abi-flavour - kernel-image-abi-flavour - kernel-image-abi-flavour-dbgsym - linux-tools-abi-flavour - linux-tools-common Until we have one single kernel that could support different flavours, we need to support having different packages at our overlay. Common issues we have with the current solution: - DKMS depends on linux-headers/image-generic - How to depend on a common and single headers package - same dependency issue with the debug package This session is about discussin possible ways to fix this long standing issues at the Ubuntu LEB, and future planing on how to properly add new flavors in the future.

Most distributions build at a medium optimisation level but a fair bit of our work is enabled at -O3. Discuss the current status, benchmark results, arguments to justify, and areas that need work.

Placeholder for the second presentation for the NEON Optimization Forum. Michael Hope will give the presentation: What is the vectoriser, what does it do, and how do I write vectoriser friendly code?

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

There are a large number of existing .ubuntu.com sub-domains. Finding these is reliant on word-of-mouth or google. I propose we have a top-level URL or a well-advertised page on wiki.ubuntu.com that lists the available sub-domains such as: archive.ubuntu.com brainstorm.ubuntu.com cdimages.ubuntu.com changelogs.ubuntu.com ddebs.ubuntu.com fridge.ubuntu.com friendly.ubuntu.com harvest.ubuntu.com help.ubuntu.com irclogs.ubuntu.com isoserver.qa.ubuntu.com keyserver.ubuntu.com manpages.ubuntu.com merges.ubuntu.com one.ubuntu.com package-import.ubuntu.com paste.ubuntu.com planet.ubuntu.com reports.qa.ubuntu.com status.ubuntu.com testcases.qa.ubuntu.com unity.ubuntu.com wiki.ubuntu.com     :     : et cetera. Nice touches would be to: - Use friendly icons - Provide very brief description of each sub-domain. - Group the sites by categories such as:   - user type (user, developer, admin)   - product applicability (desktop, server, cloud)?

Private

Since Diablo, Openstack continues to grow at a rapid pace. As it will likely continue its pace throughout the Essex & P cycles, we need to determine which components, functionality and configurations matter most to us and how to test. With Juju driving automated complex deployment testing, we should drill down on specific areas of the stack that are critical to the success Ubuntu Cloud LTS. We should also consider how our testing can make use of upstream's existing QA infrastructure and how our efforts can benefit the Openstack community as a whole.

What can we do to drive MOTU this cycle? What sprints should we aim for?

Ensure that a base set of packages is cross-compilable from an x86 host to an ARM target. The goal is to ensure the packaging of packages in Ubuntu Core, Ubuntu Server, and a base set of desktop system libraries/applications (qt, gtk, glib, freetype, firefox) supports cross-compilation of those packages..

A first set of metrics are to be put in place during Precise. This session is to discuss about code coverage and test escape analysis.

The Ubuntu Translations Portal was created at the end of the Natty cycle: https://blueprints.launchpad.net/ubuntu/+spec/ubuntutheproject-community-n-translations-portal On the Oneiric cycle work on other projects has put proomoting and using the portal on hold, but this cycle we'd like to relaunch it with more content useful to Ubuntu translators.

Learn how to write Juju Charms

Followup session for the ARB, to plan work items. See the etherpad page for the previous session: http://summit.ubuntu.com/uds-p/meeting/19549/community-p-app-review-board/

This session is to discuss how we plan work for an Ubuntu Accomplishments specification.

In this session we will consider Android Build System performance during last 6 months, what was good, what bad, what was done from LDS11.05 plans, what was not, how recent Android team workflow affects older plans. Then, we'll consider improvements to Android Build. This may include: tabbed build organization, commandline build launching, easier parameterization, test-result co-location, etc. Goals: Create a set of plans and milestones to improve how android-build looks and runs.

Delivering an ARM KVM product - Product definition - Technical project management / leadership - Involved parties - GNU/Linux platforms Kernel pieces - Linux as hypervisor - clocksource - SMP - virtual GIC - virtio? QEMU / qemu-kvm bits - Host ABI - Guest boot process -- boot ROM/kernel+initrd? - Virtio? Continuous integration using Fast Models

In order to bring the Validation Dashboard user experience one step forward the LAVA team will focus on a nice, comprehensive interface for the main use cases. Those were identified to be: * Platform Image Testing (example questions provided above.) * Kernel Continuous Integration ("Has Linus' kernel regressed on any of our boards over the last day?") * An individual jobs' click-flow: making it easy to follow a job from entering the scheduler to the actual result submission. * The validation.linaro.org frontpage, which should give an interesting overview of the most important tests being run. During this session, we would like to review the existing pages in LAVA to discuss whether they are useful, or should be modified or eliminated, and look for information that is missing or difficult to get at, and discuss how to improve that. Session notes: A few issues in the current proposal with width, layout, etc should need just a few fixes before we can roll it out Merge as-is, there is an issue with one of the reports we have on the front page being too wide, but that's really a bug in the report. Do we need the date? the date takes up a lot of space on there ACTION: make sure we have a bug on that report - it needs to be fixed regardless of whether we choose to have it on the front page Side bar - do we even need it? Some pages don't have enough information to warrant having a side bar - this can be dropped for those pages current side bar used has some visual issues, but in general people agreed that having a collapsable side bar would be useful. Screen width on some small screens is really bad, so we can't assume we have a lot of horizontal space to work with ACTION: Consider other sidebar widgets, ensure that other parts of the UI don't get hidden by the side bar Flow of submitting a job to seeing results through the lifecycle * having a "me" page - Should this be a global me page, or per app? - list of scheduler jobs that this user has scheduled - notification options - notify me by email or RSS feed for all my jobs? - ability to subscribe to subscribe to other events "actions on objects" would be subscribable from the context of the thing you want to be subscribed to - email notification could be jammed, could cause hangs if it doesn't timeout. We should put them in a message queue for the user, and those get processed by a job that runs frequently. We can mitigate with the RSS feed notification. -- I'm not sure this is totally needed, I think this could be set up so it doesn't have to block on the email. The mailer daemon should process the queue and we shouldn't have to care about it Front page: should load quickly - actual content is not easy to pick something that matters to everyone, so we could put just about anything here This is also a marketing page for lava, for linaro ACTION: Involve marketing in what should go here - get them to review what we do and make sure they agree theme/branding For lava as a project, we might want a generic lava logo rather than linaro branded (low prio) Menus: We need a top level menu that stats constant, apps can introduce 2nd level menus if needed example: dashboard currently changes the menu result view (/bundles/sha1) On the view that shows a list of test runs in a bundle it currently shows: test run - this links to the results and is fine test name - this links to some kind of confusing list of historic runs uploaded on - ok, some sense of time is good analyzed on - this is confusing, some people have said that they think this means that someone triaged this test result and filed bugs on it, etc. that's not what it means at all What we need here: some kind of pass/fail/totals - we should be able to see this at a glance, then drill down for details ***If we can determine context, then could we show the current results across the top, and below show historical results in comparison as a sort of waterfall view Could we build the context based on testing efforts? ACTION: Kiko is working on a set of mockups in basalmics to recommend to us - waterfall views - time based reports Should we have bundle streams? Should we name them something else? As a matter of fact, we explain what's a bundle stream at each sessions. Kernel waterfall is too busy, too many bricks Kiko has an idea to arrange this by trees - instead of having checkboxes for trees, have links for each kernel tree For boards where we can't run the test, we should have a red unsupported or broken block for the lava-test seciton

Discussion of Single Kernel binary topic. Etherpad @ http://summit.linaro.org/uds-p/meeting/19257/linaro-kernel-single-zimage/

Learn how to write Juju Charms

Delivering an ARM KVM product - Product definition - Technical project management / leadership - Involved parties - GNU/Linux platforms Kernel pieces - Linux as hypervisor - clocksource - SMP - virtual GIC - virtio? QEMU / qemu-kvm bits - Host ABI - Guest boot process -- boot ROM/kernel+initrd? - Virtio? Continuous integration using Fast Models

Discuss where to focus Ubuntu-specific AppArmor packaging and integration efforts.

On that topic something which comes often is when to lock screen, we should do a table listing the different cases where the screen might get locked (i.e on idle delay, suspend, lid close, user switching, etc) and the different credential scenarios (i.e autologin, password login, etc). We should also decide if the "lock screen on idle" option from the control center should affect, i.e user switching The topic comes quite often in bugs report and there is some conflicts there being "security" and "no password prompting", we currently force the screen locking on user switching or suspend but we should probably give an easy way to opt out for users who don't want it.

having a lot of thoughts on what can be OneConf (even it the scope of the post is more than a cycle I guess), I gathered them on this blog posts: http://blog.didrocks.fr/post/OneConf-in-Oneiric-and-the-way-forward%E2%80%A6

The QA tracker at http://iso.qa.ubuntu.com has been around for quite a while now. It's in desperate need of some small changes to better work with the amount of testing Ubuntu requires nowadays. This session is meant to discuss what are the most important changes we need to make the tracker work better for the LTS. These changes should ideally be implementable very quickly as the tracker starts being used for the first alpha.

It's expected this cycle that Multiarch will provide superior 32-bit compatibility for any packages that previously required ia32-libs, as well as a scalable way to add compatibility for other libraries going forward, removing one of the main pain points for running 64-bit by default. Adobe has just released a supported 64-bit version of flashplugin, removing one of the main causes for users to need 32-bit compatibility on Linux anyway. At the same time, the availability of UEFI only on our 64-bit images gives another compelling argument for running 64-bit instead of 32-bit, offering features like a fast UEFI boot instead of a slow BIOS POST and possibly secure boot capabilities (or possibly, the need to use UEFI to be bootable at all on certain secureboot-enabled hardware). Should we switch to promoting 64-bit ISOs by default for 12.04 (on the website, in pressings, etc)? What other blockers remain?

treach Darkwing how to package

How can we get better at celebrating contributions to Ubuntu development? There is massive amounts of great work going into Ubuntu, some of this is under the radar because it is less visible. Celebrating this more publicly would be both inspiring for those who did the good work, and others who didn't know about the great work before.

The current set of Ubuntu Cloud Infrastructure charms to deploy openstack are the best we could do given the constraints provided by the current version of juju. Given that juju has an aggressive roadmap for 12.04LTS that will address it's production tagged bugs (https://bugs.launchpad.net/juju/+bugs?field.tag=production), we should define precisely what the charms should deliver.

Come and talk to us about any usability issues you have, ideas for changes and find out how the Launchpad team looks at usability and how we make changes.

We'd like to use Firefox as a toolchain testsuite and a benchmark. Discuss approach, existing testsuites, and the parts to benchmark. I would like to check if these workloads are the interesting ones? Load and rendering of a good set of web pages JavaScript Start up of browser Shutdown of browser Imaging - or are we covered by EEMBC DENBench, ConsumerBench Input data that can be redistributed? I would like to hear the views on this and understand how to proceed. Can Mozilla share the tp5 pages? Is it necessary that the content is redistributed, or can it be internal to the tcwg? How to proceed with cross-compiling? I would like to use a multistrap/xdeb approach, but it seems hard. Is it OK to create a chroot with everything installed, zip it up and reuse it for some months? Configuring the build for different flags and features Should we use .mozconfig, myRules.mk, and myConfig? If debian package is used for building, can myrules and myconfig still be used? Which benchmark(s) to choose for browsing? ARMBBench EEMBC BrowsingBench Talos with a set of pages Would it be possible to integrate ARMBBench or EEMBC BrowsingBench in the Talos framework? System level testing What are the plans for system level? Is there an overlap? Can we benfit, work together... When done, should the toolchain browsing benchmark tests be run in LAVA?

On Tue, Sep 20, 2011 at 9:05 PM, Zach Pfeffer <email address hidden> wrote: > Ha! > > Yeah sounds cool. > > Happy to meet up. We could probably pull it into our builds - create > an ecryptfs partition for people to play with. Thanks for the intro, Andy! Zach, the cool thing about eCryptfs is that it doesn't require a partition. It's a layered filesystem, so you just mount one directory on top of another. The top one has a cleartext view of files/folders. The lower one (which is the one that's actually written to the lower filesystem -- any filesystem you like -- contains the encrypted data, which gets written to disk). If you want to play with it, just install ecryptfs-utils, and assuming ecryptfs is built into your kernel (it is by default in Ubuntu), just run "ecryptfs-setup-private". Logout, and then back in. Your $HOME/Private directory is where you'd save your sensitive data (like a ~/.firefox cache, for instance, which you can symlink back into place). The actual encrypted data is stored in $HOME/.Private. Play with it a bit and you'll get the idea. Alternatively, you can encrypt *all* of $HOME. Anyway, seems like it might be kinda cool, from a security and privacy PoV for Linaro builds. I'm in Austin this week, and then traveling to Boston for the next 2. Grab a beer some time after that, and before UDS? Cheers, -- :-Dustin Dustin Kirkland Manager, Systems Integration Corporate Services Canonical, LTD

The archive needs a rich set of modern packages for "WebScale" operations, review the list of unpackaged technologies and target popular new technologies which need packaging. Whiteboard will contain a list of low hanging fruit with a positive impact.

In this sessions we will talk about how to integrate proprietary binary overlays onto LEBs. Description ------------------ The Linaro Platform unit recognizes that at least some of the binary drivers and firmware needed to deliver an accelerated LEB experience will be provided under a restricted license. To unblock full enablement while maintaining our open development approach (which makes available all open-source components as well as the build service), the Linaro Android LEB program needs to grow support to supplement LEB builds through an overlay mechanism, containing acceleration binaries. The situations targeted are: Binaries available on a login protected vendor or third party site Binaries provided for download behind a click through form Binaries available for download freely, but requiring user to accept a click-through license upon install This work will include tools and LAVA improvements that will allow users and the validation lab to deal with the new binary components. It will also deliver proof of concept refactoring of Android Platform code to build without the binaries to support our pure upstream builds. Acceptance Criteria ------------------------------- 1. Linaro Android Overlay package format defined and published supporting shipping an overlay file tree alongside with a license text 2. Linaro Android Overlay packages support including binaries requiring user acceptance or acknowledgement of included license text 3. Tools supporting the installation of Linaro Android Overlay packages by humans is available 4. Tools supporting the automated installation of Linaro Android Overlay packages, for LAVA, is available 5. LAVA supports managing LEBs with Linaro Android Overlays: one or more LEBs with overlays are automatically tested in LAVA See https://blueprints.launchpad.net/linaro-android/+spec/linaro-platform-android-device-tree for the original description. Agenda ------------ Explain the present status of Proprietary binaries in our builds. Discuss the Blocking issues in the present distribution of binaries with linaro android. Discuss a solution for end users to access the proprietary binaries. Discuss a solution for LAVA to have access to the proprietary binaries. Goal of this Session ----------------------------- To brainstorm and generate concrete work items for integrating proprietary binaries with Linaro LEBs.

We would like to package metadata with the Linaro (Ubuntu and Android) images. The purpose is to pass information about the image to linaro-(android-)media-create such as information related to live builds or capabilities to be matched with hwpacks.

5 minute talks, first come first serve, show up early to reserve a place in line!

As opposed to having fully-fledged 1-on-1 mentoring, we might want to think of a much more light-weight approach and coordinate efforts such as: 1) reach out to new contributors, thank them for their work and get feedback, 2) reach out to people who might be ready to apply for upload rights and help them, 3) reach out to contributors that went inactive and get feedback from them and offer help. This should be easily manageable by a small team and would make the developer world a much more social experience.

Since we have been a bit sloppy on that topic since lucid (or busy with new features) we should aim back at better performances for the lts, that include cpu and memory usage and login time. See https://bugs.launchpad.net/ubuntu-boot-speed https://wiki.ubuntu.com/DesktopTeam/11.10/BootSpeedAnalysis has boot charts for various releases and comparative charts for lucid vs. oneiric and Dell Mini 10 (reference platform, slow Atom + SSD) vs. ThinkPad X201 (fast quad core + SSD, for identifying unnecessary dependencies) https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ApM3WkUQgY4WdGtnMFFnelU2ZlpMSnUxMmhFZGhWZ0E&authkey=CL-LzIQL&hl=en_US#gid=0 has more comparisons of two machines between 9.10 and 11.10.

Open Week, Developer Week, Application Developer Week, User Days

During the Oneiric cycle a set of tools to create localized ISOs were developed. We'd like to expand on those tools, get some community feedback and a wider adoption of those tools to create ISOs adapted to a particular region. This will be a community-based effort, and to kick it off we'll need to: - Create a policy for these images: -- What can be changed and what cannot -- Where should the images be published -- How can the images be tested - Create documentation on how to build these images - Create documentation on how to test them In this session we'll discuss and elaborate on this topics to come up with a clear plan on how the community can create localized ISO images

Discuss cloud new utilities that can be added to cloud-utils or new packages that Ubuntu should bring in.

For ARM targets we currently have semi-preinstalled images - an already extracted rootfs on SD card which is expanded to fit the media on first boot and run oem-config. We should investigate the feasibility of having an installer more in line with Ubuntu desktop, that is installing from a squashfs based live-image. There are performance issues to consider - such an image proved very slow a couple of cycles before - and the fact that most of our target hardware only has one storage media by default, making the source and the target of the install necessarily the same. We could have such a live-installer made initially only for the particular case of installing from SD card to an external USB drive.

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.

In what ways can we improve Upstart from an administrators perspective? What would make sysadmin's lives easier? - custom actions [e.g. status, force-reload, try-restart] - programmatic enabling/disabling of services - improved logging - serialized/interactive boot - suggested new common events? (see `man upstart-events` for current examples) - ability to list "services which will start on boot" - fixing LP bug: 406397 would make writing/testing new jobs easier See last cycle's blueprint for reference: https://blueprints.launchpad.net/ubuntu/+spec/foundations-o-upstart-for-admins

Complete and publish https://juju.ubuntu.com/AppArmor. (currently in draft)

If we are to grow Ubuntu's user base by a factor of 10, we need to look at ways to scale the community. Community growth is a key to taking Ubuntu to people who have never seen it or heard of it. Here's one powerful way to scale: Build local communities at a town/city level. Make Ubuntu more of an in-person phenomenon, and less of a virtual one. We should gather and discuss how to make this happen, as well as any other thoughts for scaling.

Every LTS we're confronted with the Python upgrade story. This is made difficult because there is usually no overlap in Python versions from LTS to LTS. Not that we've ever come up with a very satisfactory solution before, but let's at least discuss it again since if there is anything we can do, 12.04 is probably a good time to do it. Just to remind us: since there will never be a 2.8, we only have to worry about Python 3. (Doubtful we'd remove Python 2.7 from main any time soon.) Python 3.3 is slated for after 12.04, and it will only be in alpha during this cycle, which is probably in too much flux to put it in this LTS. Extrapolating out, I think it's possible we'd see a Python 3.4 just before 14.04.

Discussion on Live CD/USB integration with Secure Boot. Will we need to create signed images? How will we maintain user-modifiability? Can we avoiding signed images?

Topics: - Go over the current test cases and show what is currently tested - How to hook Offspring builds into LAVA as soon they are completed? - Supporting different test bundles across images and platforms - Extending test support: - Hardware support, such as wifi, bluetooth, sound - Regression/smoke test for LEB images

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Graphics and Multimedia Working Group

This will be a presentation talking about how to get involved and participate in the Linaro community. The primary audience is: * people who are transitioning from propriety to open source * community members interested in getting involved in Linaro Topics included:   * working in open source - differences from properietary   * working with Linaro   * leasons learned from a community member's success story

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

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Platform Working Group

Afternoon engineering and hacking sessions for Member Services

Afternoon of engineering and hacking for Member Services

Meetup for folks interested in the hard-float ABI work, discussing status to date and what's still remaining.

We built a great tool, let's tell the world!

What metrics should the defect analysts be gathering for their engineering teams? What visualizations of this data would be useful and what tool(s) should be used to create the visualizations?

Similar to the IPv6 session we had in Budapest. Discuss what changed in Oneiric and what we want to focus on for Precise. Things to discuss at least include: - New ifupdown supporting dhcpv6 - Testing our most important server and client packages for IPv6 support - Status of IPv6 support for Ubuntu core services like archive.ubuntu.com, archive.canonical.com, ntp.ubuntu.com, geoip.ubuntu.com, ... so we can have a perfectly working install in an IPv6 only environment - Privacy extensions - Dual-stack DHCP server support

Current status of UEFI support in Ubuntu. Discussion of pre-UDS testing, discussion of new areas we'd like to support, and bugs that need fixing.

Goals for improving the News Team over all, clean up documentation for UWN and Fridge, as well as update Front Page for Fridge and Branding efforts.

Say cheese

Hacking on summit.ubuntu.com while everyone is together.

Cloud-live project delivers usable and bootable cloud infrastructure. Purpose of this blueprint is to set and define goals for the future of the project.

Dealing with Ubuntu and governments

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Graphics and Multimedia Working Group

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

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Platform Working Group

Afternoon engineering and hacking sessions for Member Services

Afternoon engineering and hacking sessions for Member Services