George Grey and Mark Shuttleworth

This session is for reviewing the state of Distributed Development, and planning for the next cycle.

Make image builds possible outside the data center and easily accessible and reproducible to developers, testers and end-users. The current setup is not easily installable on other computers and is not very well documented either. Evaluate what OEM/Linaro do in this area.

Private

Private

ITSM stands for IT service management. ITSM is a discipline for managing information technology (IT) systems, philosophically centered on the customer's perspective of IT's contribution to the business. ITSM stands in deliberate contrast to technology-centered approaches to IT management and business interaction. In order to differentiate ourselves from other orchestration products we should offer at least an Inventory Management system (ocsinventory) and a Request Tracker (rt).

Currently we are accessing the banshee database directly. This has the advantages of being very fast, and very flexible. It however is a bit evil. There are possibilities of crashing banshee, locking, etc. A better solution is a standalone daemon/dbus interface that reads the db, and that can shutdown when banshee starts up. This has a lot of other benefits such as using banshee's library code so that all our search align with the same searching that's already inside of banshee.

Tasks from daily community roundtable sessions

Monday's security roundtable

A training session about how the Linaro development process works with emphasis on how it fits in with the new roadmapping process.

(Probably informal) The toolchain is available in Ubuntu and Linaro Android, and as an community option in a range of other build systems. Discuss Yocto support.

There is no standard way to scale frequency and voltage for peripherals in Linux. Devfreq is a proposal meant to address that. Discuss how it works.

Define what levels of support to apply to boards and how they path that support levels can take Define how board support gets picked up (BOL) and phased out (End Of Life)

Many new laptop models come with two gfx chips, one with lower power consumption and other with more gfx processing power. What options exist to provide a better user experience to switch between the two, and what can be accomplished within the Precise timeframe.

Based on feedback from the Ubuntu Community Survey (http://www.jonobacon.org/2011/10/24/ubuntu-community-survey-results/), the community get really motivated by seeing their contributions acknowledged and users thanking them because of them. This session is to discuss how we can improve this in the community.

Overview of Ubuntu Automated QA and high level plans going forward.

Complete the Unity Greeter design

First session of the week, meet the team Review Oneiric

Several ideas for improving debhelper support for Python: * python-multibuild for python3 w/ dh integration * dh_auto_test Others?

The Ubuntu Software Center version 5.0, introduced in Ubuntu 11.10, features a brand new user interface. For the Precise cycle, we will refine the new Software Center experience to speed things up considerably (in particular, to fix the regression in startup time), to make further improvements to the visual presentation, and to clean up all remaining inconsistencies and rough edges. The goal is a Software Center that is rock-solid, responsive, and a true pleasure to use. We will also consider new features to be added (particularly, Recommendations), as well as enhancements to existing features. The Recommendations feature is covered in a separate blueprint: https://blueprints.launchpad.net/ubuntu/+spec/consumer-p-software-center-recommendations

Planning to take glproxy from a proof of concept level to a library suitable for integration into a real-world application like glcompbench (for example).

Give an overview of what is currently being done for Android toolchain benchmarking in Linaro. Discuss future enhancements we should look into. Agenda: * explain what I currently do each month * discuss some of the short-comings * discuss some of the future ideas we have and get other ideas on what we should do to improve this Goals: * decide what areas we should focus on related to android toolchain benchmarking going forward * get an idea of the effort required * does Andy have the time to do this on his own

Joint session between kernel and toolchain working groups to discuss options to improve the kernel debugging experience.

An informational session to educate new UDD users that includes a short demo and informs more experienced users about new features.

At several points in the oneiric cycle, there were mismatched expectations regarding the handling of the toolchain. Despite discussions at last UDS that concluded with agreement that the kernel did not need to check the exact compiler version in use for building out of tree modules, the kernel team expected to use the same compiler version for building the kernel across all architectures for a given milestone, a requirement that the foundations team was not aware of. The outcome of this session is to be an understanding of any requirements for toolchain stabilization (gcc, binutils) from other parts of the team and a description of any freezes (timelines, scope, and rationale) that need to be applied to the toolchain for precise above and beyond the standard freezes.

Figure out how to get Firefox building with elfhack again. achiang brought this up here: https://wiki.ubuntu.com/ARM/PBlueprintIdeas

Private ops review for Samsung LT

The Hardware Certification team routinely performs certification testing of Kernel SRUs for recent releases. The objective is to run a small test suite on every system that has been certified with stock Ubuntu and ensure no regressions have occurred. This compliments the testing done by QA through the sheer range of hardware components and drivers exercised in the testing. The goal is to protect the Ubuntu user with a certified system from suddenly finding that something important doesn't work. Currently the test suite consists of just over 20 tests as defined at https://wiki.ubuntu.com/Kernel/kernel-sru-workflow/CertificationTestSuite. These tests are unlikely to fail unless there has been a major regression and due to the automated nature of the testing (which is essential due to the volume of systems which need to be covered in a short period of time) there are no manual tests. So far this has meant that even though there have been regressions encountered in SRU updates, the certification testing process has not picked them up. Some have been bugs that could only be discovered through manual testing and some have been fairly obscure corner cases that the test suite simply didn't address. The goal of this blueprint is to significantly increase the coverage of the SRU test suite within a few limits, the first being that all tests must be automated and the second being that there needs to be a sensible limit on the execution time of the test suite (to be discussed, but a guideline would be 30 minutes to 1 hour) so that SRUs can still be released in a timely manner. Each test should have as high a value as possible, so must focus on the most important hardware functionality first. Wireless testing is non-existent and testing of graphics and audio is not as good as it should be for such important pieces of functionality, so we intend to increase coverage in these areas at least. When considering new tests to add we will be looking to keep the SRU test suite synchronized with the test suite used to certify systems. This means that in the first instance new SRU tests should be sourced from the certification test suite and if a suitable test is not found then any new test created should also be included in the certification test suite. Initial thoughts on what needs to be tested are here: https://docs.google.com/document/d/1fHfOnnnVCXsSayz3XlaL9hgrl-uTBXHx7Ijbkc6aKTo/edit?hl=en_US == Agenda == * Introduction and overview * Wireless testing * Video testing * Audio testing * Q&A/Comments

The purpose of blueprint will keep track of the work needed to be done for integrating the Essex release into Precise.

Once http://plus.google.com becomes more than just invite-only, I would love to see Gwibber integration (in the form of an installable .deb of a plugin) for it... Hopefully when the Google+ API comes out, it would be much easier...

We want to start building a support community around application development topics and start promoting the resources we're going to use for that: - The ubuntu-app-devel mailing list - Askubuntu - ...

Discussion about how we build experiences in Ubuntu from the design to implementation level.

Currently Linaro uses a PPA for the package Overlay, and unless the source package requires a -dbg package, no dbg symbol package is provided for it. Discuss about possible ways to make dbg packages available for the Ubuntu LEB own packages/changes, covering the currently solution for Ubuntu and if it can be also applied for our ppa/derived distro.

Planning session for work needed to support UCM on Android for the Linaro development boards.

We're planning to support KVM on A15. This session is to discuss the QEMU parts of this. It's engineering-focused and QEMU-focused (the more general discussion and aspects which cut across different Linaro and external teams will be done in a different session).

Linaro's platforms allow the engineers of tomorrow to work on today's cutting edge SoCs with the leaders in the opensource community. This session will discuss this and come up with some concrete goals to enable outreach programs. Goals: Create a set of milestones and plans to test-run educational programs Select candidate programs Discuss interns and projects that may be interesting Agenda: Establish Linaro's educational outreach goals Have Dave Pigott give an overview of the school that would like to work with Linaro Discuss a possible program for the school Discuss adding other schools Talk about logistics Zach to talk about getting a program at UT off the ground, sister school? Interns, we now have some, talk about projects Other

Planning for a graphics benchmark dashboard that should be integrated with http://validation.linaro.org. There are to be 3 views into the data as described here: https://linaro-public.papyrs.com/public/4143/GWG2011-BENCHMARK-DASHBOARD

Introduction to the Week

Stefano Zacchiroli: Debian Project Leader

Brian Thomason and Juan Negron

Every cloud has an Aubergine lining... Cloud computing is becoming increasingly pervasive and important in the world today. Cloud computing is used in datacenters all over for resource utilization, hosting, storage, providing media content, on-demand computing power and many other applications. Competition is growing at a rapid pace in this new infrastructure race with public cloud space available from Google, Amazon, Canonical, Apple and others. For this and other reasons, we need to be sure that Ubuntu functions well in the cloud as both a host and guest OS. From a hardware certification point of view, we need to ensure that Ubuntu can function properly as a Virtual Machine on popular virtualization products: VMWare, XenServer and KVM. This means that we need to come up with a plan for extending infrastructure, tools and processes to allow for dedicated host machines for each of the respective virtualization products. However, we also need to keep this framed within the boundaries of Hardware Certification testing, not Software QA testing which is currently handled very well by the Ubuntu Server team and the Platform QA Team. To get this done, several things need to occur. First, we need to beef up the server testing, this means adding new tests to the server test suite if necessary. Infrastructure needs to be improved to provide the means to do multi-network device testing. This will most likely mean some significant expense in purchasing hardware and will also rely on assistance from IS in getting that infrastructure in place where applicable. Additionally, possible test development time and debugging time. We need dedicated hardware to serve as XenServer hosts (VMWare already exists, but we may wish to update to a newer version). We need automated means for doing SRU testing on VMs and the means to certify Ubuntu as a Virtual Machine on both VMWare (mostly existing already) and XenServer. Finally, we should start also testing KVM. This could mean a third dedicated server to run the current LTS and host KVM vms for cert purposes.

With GNOME moving to using more and more systemd and PackageKit in different places, instead of having to patch all the apps using them to use our services, it would be great to implement those in our stack (aptdaemon and ubuntu-system-service). Work has been started to implement PK system bus interface in aptdaemon, so part of this is in progress already. Also, systemd interfaces needed so far are just a couple easy ones AFAIR, so shouldn't be hard at all.

Instead of using hosts to front the EC2 mirrors, we should move our mirrors to being hosted on S3. There are numerous advantages to doing so -- most notably speed, lower costs, lower maintenance costs, access policies, etc. Using S3 also realizes some cost-savings for Canonical since all intra-zone transfers are free. Summary: 1. New mirrors would be setup in each region 2. Scripts would need to be updated to use regional mirrors 3. DNS names would need to be updated

Linaro ST-Ericsson

Linaro & Sky Meeting

Linaro & Bosch/ADIT meeting

We are seeing more and more people integrating on their laptop Unity and their preferred applications: - drag and drop support - custom quicklists - crazy integration patches It's proably time to get the most interesting one into the distro. Some effort were started to https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-o-default-apps-unity-integration, but due to lack of time, not anything was integrated in time. It's time to review the list and to push those forwards. If you have any idea on how to integrate better your preferred application with Unity, do not hesitate to suggest there! What is possible with current launcher is described in the Unity API page: https://wiki.ubuntu.com/Unity/LauncherAPI

Goals for the Ubuntu Women UDS-P cycle Add your ideas here for consideration in this formal blueprint: http://wiki.ubuntu-women.org/Roadmap-P

Libreoffice online has been demoed by Michael Meeks at the Libreoffice conference 2011 in Paris. Lets discuss what this technology could mean for Ubuntu.

Enable jack detection features in the "Sound Settings" page of GNOME Volume Control, and redesign the UI to be more user friendly (present "Port"/"Connector" as primary object, merge hardware tab into Input/Output tabs).

This meeting is to brainstorm on the current release process used Oneiric, what worked and what didn't, and ways they can be improved for Precise.

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

Ubuntu currently has a good first step implementation of CloudFoundry via Ubuntu Server and Juju that is stable and scalable. In this blueprint, we should discuss next steps as well as how to integrate CloudFoundry's current roadmap, features, best practices and experiences with Ubuntu Server and our Juju charms. Things to discuss: - build Cloudfoundry from source - use packages where possible. - ways of expanding our current charms - next step ideas.

Informational Sessions

The design team is planning to run design "theater" sessions at UDS. As a general rule, the design works on Canonical projects. It is our opportunity and pleasure during UDS to dedicate some time to help with other free open source software. What is Design Theater? During these sessions, we explore a design issue that you submit to us and take it through our design process. Why should you come? We hope to take you through the design process with real life examples, so we can share our design thinking and problem solving with you and propose any solution you might like. How can you participate? You have a choice: As an observer: come an look over our shoulders as we discuss applications design issues and join in the discussion. As a participant: bring us your free software application for which you need design guidance or user experience input. We'll try to fix it for you and show you how to approach this particular problem the design way. If you are thinking of joining us as a participant, please, send us your design question in advance, if you can, so we can get the ball rolling. Send it to: charline.poirier@canonical .com Who will be there from the Design team? At each session, you will find a user researcher, a brand designer, a user experience specialist, an interaction designer and a visual designer, Come find about our process and challenge us!

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Graphics and Multimedia Working Groups

Afternoon engineering and hacking session for Kernel and Power Management Working Groups For details of this session, see Power Mgmt Working Group: https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/Orlando Kernel Working Group:

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Android and Ubuntu Working Groups

Afternoon engineering and hacking session for Member Services

Afternoon of engineering and hacking for Member Services

Session for discussing progress on QA CoP topics and interests

Review of the current Ubuntu Kernel delta. 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.

For Oneiric we went the easy route of adding a way to run external applications for the stuff we wanted in the control center. But this looks quite bad (some panels are embedded, others run a separate application), so for P I'd like us to do a cleanup and avoid as much as possible having external windows. So, here's a list of what we have: * jockey: this could perfectly fit in the System Info panel * language-selector: we just need ability to install languages and input method support in the region panel to completely remove this * software sources: also maybe as part of the System Info panel, which does updates? the tricky one is Ubuntu One, so I guess we'd have to leave it as it is, or write a panel that just embeds the u1-panel window?

Linaro management meeting

In oneiric we updated Xen to a more recent version. In precise we need to do further work including testing to make Ubuntu a solid Host for Xen.

This will detail the plan for the Council for loco teams, approval, any new guidance pages to be written, goals to help get locoteams more involved in the community

* What can we expect from upstream this cycle? * Can we automate packaging more? * Worth using UDD branches? * Revise Ninja processes to be more efficient with macro upstream packages * Point releases as stable release updates?

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Graphics and Multimedia Working Groups

The session is driven by Linaro Release Team. The following topics will be discussed: * current release process - what's the current process? * release internals - how the release works? * the road to continuous integration - how the CI is going to transform the release?

Afternoon engineering and hacking session for Kernel and Power Mgt Working Groups For details of this session, see Power Mgmt Working Group: https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/Orlando Kernel Working Group:

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Platform Working Group

Afternoon of engineering and hacking for Member Services

Afternoon of engineering and hacking for Member Services

Need to ensure that 100% of the "Desktop" is translated into Chinese/Simplified for the LTS release

The usual. :)

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: - Reviewing the messages/prompts in PAM for appropriateness - Adding hints to PAM to allow GUIs to better display the prompts (i.e. if a prompt is for a password, key number, if prompting for a password change). - Improving the Unity Greeter prompts to interpret the hints - Improving PolicyKit to interpret the hints - Making it easier to enable non-password authentication (e.g. LDAP, two factor).

George, David and Kiko make a roadmap

Harvest hasn't seen much development recently, but we still need a good place to summarise all the needed work in the distribution. Problems both in representation and data should be discussed.

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.

Mike Sweet intends to remove the filters which are not used by Mac OS X from the CUPS upstream package: http://www.cups.org/str.php?L3930 We have agreed on this on the last OpenPrinting Summit and the filters will be continued and hosted by OpenPrinting. In addition, the filters for the PDF printing workflow will not be adopted by CUPS but joined with the CUPS filters we overtake. All Linux distributions would have to include this new CUPS filters package then to get CUPS continuing to work and have the same feature set as before. Due to the fact that this package will use the PDF workflow by default and that all major desktop applications send their print jobs already in PDF, this will complete the implementation of PDF as standard print job format in all distros (if they do not patch against the PDF workflow). See also my updated web page: https://www.linuxfoundation.org/collaborate/workgroups/openprinting/pdfasstandardprintjobformat This will also clean our heavily patched CUPS package somewhat. We need a name for this new upstream package. Should we call it simply "cups-filters"? Or "op-cups-filters"? Or do we rename Foomatic to openprinting and have the packages - openprinting-db - openprinting-db-nonfree - openprinting-db-engine - openprinting-rip - openprinting-cups-filters Note that we keep foomatic-rip/openprinting-rip separate from the CUPS filters as this filter is a universal filter which also works with many other printing systems. Another decision to make is whether we really should maintain all the filters which get over to us from CUPS or whether we should discontinue some. The filter set will contain "imageto..." and "textto..." filters which are not made use of by the usual desktop applications, they send all PDF (and some send PostScript). Alternatively, these filters could be made optional. Usually these are decisions to be made by upstream, in this case OpenPrinting, but in this session I want to have some pre-discussion from the distribution point of view, so that when this new upstream project gets created it will be created with the distro's needs in mind.

Informational Session

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking sessions for Graphics and Multimedia Working Groups

Afternoon engineering and hacking session for Kernel and Power Mgt Working Groups For details of this session, see Power Mgmt Working Group: https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/Orlando Kernel Working Group:

Afternoon engineering and hacking session for Validation and Infrastructure Working Groups

Afternoon engineering and hacking session for Platform Working Group

Afternoon of engineering and hacking for Member Services

Afternoon of engineering and hacking for Member Services