Discuss AppArmor upstream test suite, and Ubuntu integration testing.

A "tablet test-drive" session to encourage Ubuntu-related tablet (and touch screen) development: multiple tablets will be on hand running the following UIs: - Ubuntu / Unity - Ubuntu / Gnome - Kubuntu Active (KDE Plasma Active UI) - WeTab (MeeGo base OS) - Android - Windows 8 We'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.

Discuss where to focus AppArmor development and integration efforts

A primer on what juju is for the common person.

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.

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.

All development work items for Lubuntu 12.10

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?

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.

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.

Pad - http://summit.ubuntu.com/uds-q/meeting/20344/ubuntu-manual-schedule-for-p-manual-and-beyond/

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

We want to increase the reporting ability of the test suites in the Indicators by switching to Google Test.

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.

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? ==== Note ==== As this session did not get enough traction (and I didn't go and drag people in...), no action items were decided upon. :-( // David

As ever

All the open issues that need to be fixed lo-menubar integration into main.

Our usual Edubuntu session to discuss the plans for the next 6 months. Please note that this time around a separate session has been booked for LTSP (foundations-q-ltsp)

General packaging blueprint for LibreOffice 3.6 on Ubuntu Q

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.

There's more work we can do to make Quickly better and keep pace with the platform. Specifically this cycle, a big focus will be porting to Python 3 for both managed projects and Quickly itself.

Discussing expanding the isotracker to perform testcase management and reporting for all kinds of testing, not just iso.

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.

Review of the Precise cycle and brainstorming on how to improve.

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. Explore how can Edubuntu and Zentyal developers can work together to provide an out of the box solution for school servers. Approved blueprints that would be implemented or related with this: https://blueprints.launchpad.net/ubuntu/+spec/student-control-panel-completion (zentyal desktop will integrate epoptes) https://blueprints.launchpad.net/ubuntu/+spec/edubuntu-profile-and-network-session-management (zentyal desktop will integrate Pessulus/Sabayon with LDAP backend) https://blueprints.launchpad.net/ubuntu/+spec/edubuntu-network-auth-client (zentyal desktop provides LDAP and Kerberos authentication) https://blueprints.launchpad.net/ubuntu/+spec/edubuntu-network-auth-server (zentyal provides LDAP and Kerberos server) https://blueprints.launchpad.net/ubuntu/+spec/edubuntu-user-management (zentyal has a LDAP users and groups management interface) https://blueprints.launchpad.net/ubuntu/+spec/edubuntu-ad-integration (zentyal provides ad-sync tool and samba4 integration) https://blueprints.launchpad.net/ubuntu/+spec/school-server-in-a-box (zentyal provides configuration of all needed services in one interface) https://blueprints.launchpad.net/ubuntu/+spec/zero-conf-server (zentyal is a simple interface to configure all services)