<schedule>
    <conference>
    <title>Desktop Summit 2011</title>
    <subtitle>Guadec/Akademy</subtitle>
    <venue>...</venue>
    <city>Berlin</city>
    <start>2011-08-06</start>
    <end>2011-08-12</end>
    <days>7</days>
    <day_change>00:00</day_change>
    <timeslot_duration>00:40</timeslot_duration>
    </conference>
    
<day index="1" date="2011-08-06">
<room name="Audimax">
<event id="registration">
	<start>08:30</start>
	<duration>1:30</duration>
	<room>Audimax</room>
	<slug>registration</slug>
	<title>Registration</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="opening">
	<start>10:00</start>
	<duration>0:20</duration>
	<room>Audimax</room>
	<slug>opening</slug>
	<title>Opening</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="degrees-playing-nice-large-companies-open-source">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>degrees-playing-nice-large-companies-open-source</slug>
	<title>Degrees of Playing Nice: Large Companies in Open Source</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>People inside companies associated with open source need to act in ways that are compatible with the community. It often takes an explicit effort for companies to be positive members and contributors in the open source environment. At the same time, it's important that the community understands what companies are doing and where they are going.</abstract>
	<description/>
	<persons><person id="0">Dirk Hohndel</person></persons>
	<links></links>
	</event>
	
<event id="coffee-break-4">
	<start>10:50</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>coffee-break-4</slug>
	<title>Coffee Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="get-new-contributors-and-diversity-through-outreach">
	<start>11:20</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>get-new-contributors-and-diversity-through-outreach</slug>
	<title>Get new contributors (and diversity) through outreach</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Programs like Google Summer of Code often provide excited students who disappear after a summer's work. Meanwhile, request for help emails on development lists are frequently met with silence. Hackathons create a flurry of commits, but then we never hear from the participants again. Expanding your team is possible, and it requires care in terms of outreach, expectation management, and mentorship.In the past two years, projects have been experimenting with new strategies for gaining and retaining participants. Their lessons can be applied to your communities. We will cover:* How the Fedora Design Team brings in new contributors who stay involved* How changing the culture of the Debian-Mentors mailing list led to more package review* How the San Francisco Ruby meetup grew in in numbers as well as in diversity, moving from 2% women to 18% in one yearBy focusing on unusual, effective outreach strategies, the talk will leave you with practical tips you can use withinyourproject. We will conclude with group questions and answers.Target audience: anyone involved in an free software project who wants to find more contributors</abstract>
	<description/>
	<persons><person id="0">Asheesh Laroia</person></persons>
	<links></links>
	</event>
	
<event id="conflict-management-teams-and-communities">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>conflict-management-teams-and-communities</slug>
	<title>Conflict management in teams and communities</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Must successful communities are based on healthy, friendly and collaborative cultures. However it happens that constructive discussions (with only good intentions from all parties) end up in non positive conflicts. This talk outlines the backgrounds of selected conflict-solving methods and provides opportunities for communities and teams to use them. Audience: Everyone :-)</abstract>
	<description/>
	<persons><person id="0">Thomas Thym</person></persons>
	<links></links>
	</event>
	
<event id="lunch-break-1">
	<start>12:30</start>
	<duration>1:30</duration>
	<room>Audimax</room>
	<slug>lunch-break-1</slug>
	<title>Lunch Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="cost-going-it-alone">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>cost-going-it-alone</slug>
	<title>The Cost of Going it Alone</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>When working with community software, which costs more, working a private branch, based off a stable version, or developing the features upstream? Many companies choose to take stable software and adapt it to their needs, rather than building their projects near the tip of the upstream projects.In the first case, you are taking on board the maintenance cost of your code, plus the cost of periodically merging code from the upstream project back into your branch, with all of the integration issues that brings. In the second, you lose time with community processes, rewriting code to the satisfaction of the community, and you risk maintaining features for months on personal branches before they finally meet the approval of the project maintainers, if they ever do.The answer will be obvious to most people – but depending on who you are, the “obvious” answer might change.People who are accustomed to working with community projects, who have perhaps gone through painful merges in the past, will recognise the value of getting changes upstream. Others, who have seem many hours wasted waiting for patch review, or facing Yet Another Patch Rejection, may point to the obvious advantage of self determination that a private branch gives.By looking at the past, we hope to give a clear quantitative answer to the question: Does maintaining code out-of-tree cost more than getting it upstream, in the long run? Are there situations when maintaining a feature out of tree makes more sense?</abstract>
	<description/>
	<persons><person id="0">Dave Neary</person></persons>
	<links></links>
	</event>
	
<event id="navigators-and-explorers-leadership-model-open-source-teams">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>navigators-and-explorers-leadership-model-open-source-teams</slug>
	<title>Navigators and Explorers: A Leadership Model for Open Source Teams</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Setting direction, organizing resources, charting a course through (or avoiding) moments of crises and attracting new and retaining existing participants and are all ways that effective leadership can help increase the stability and quality of your open source project. However, many of our teams still lack visible, effective leadership, putting these projects at risk of not achieving what their participants hope to.There are many leadership models that have been devised and documented over time. Choosing a model that works for a given community and context is critical to leadership that produces the desired results. Navigators and Explorers is a model that does not rely on top-down dictation or charismatic leaders but which instead emphasizes organizing and drawing out the creativity in your teammates through light-weight processes built around consensus building, mapping and community support systems.Absolutely anyone can learn to employ the principles of this model with a few key principles in hand. This presentation will describe these principles and give concrete examples of how to practice and employ them in your own project. If you feel your open source project(s) could benefit from improved leadership and/or you wish to develop your own leadership skills, this presentation may help you realize those goals.</abstract>
	<description/>
	<persons><person id="0">Aaron Seigo</person></persons>
	<links></links>
	</event>
	
<event id="sponsor-lightning-talks">
	<start>15:20</start>
	<duration>0:45</duration>
	<room>Audimax</room>
	<slug>sponsor-lightning-talks</slug>
	<title>Sponsor Lightning Talks</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="coffee-break-3">
	<start>16:05</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>coffee-break-3</slug>
	<title>Coffee Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="why-are-we-here">
	<start>16:35</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>why-are-we-here</slug>
	<title>Why are we here?</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>What is the why of KDE? Why do we do what we do?Those are questions that KDE contributors may answer in many different ways, but common answers include the words "freedom" and "fun". We know, individually, why we do what we do. What we sometimes lack is a coherent story that we can present to the outside world and use as a guide for our own efforts.In the talk, I will ask what it means to be part of KDE and when software qualifies as KDE software. We used to know what KDE was, but that definition has been blurred. KDE is changing and we now have KDE software that does not use the KDE Frameworks and ambitions for greater use of the KDE Frameworks beyond KDE software.As we become bigger and more diverse, how do we maintain the common purpose that is essential to our individual sense of belonging to a larger whole? How do we explain that to people in the outside world and persuade them to use our software and join our community?</abstract>
	<description/>
	<persons><person id="0">Stuart Jarvis</person></persons>
	<links></links>
	</event>
	
<event id="gnome-and-kde-interns-showcase">
	<start>17:15</start>
	<duration>0:45</duration>
	<room>Audimax</room>
	<slug>gnome-and-kde-interns-showcase</slug>
	<title>GNOME and KDE Interns Showcase</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>This session is all about the GNOME and KDE Google Summer of Code, Season of KDE and GNOME Outreach Program for Women interns. In a fast-paced lightning talk session, each participant has the chance to show what he/she is working on.Interested in what our interns are building? Can’t wait to meet our next rockstars? This is where you can find them and see what they’re up to!</abstract>
	<description/>
	<persons><person id="0">Ruben Vermeersch and Lydia Pintscher</person></persons>
	<links></links>
	</event>
	
<event id="panel-copyright-assignment">
	<start>18:10</start>
	<duration>0:50</duration>
	<room>Audimax</room>
	<slug>panel-copyright-assignment</slug>
	<title>Panel on Copyright Assignment</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	</room>
<room name="Kinosaal">
<event id="heart-blingness-clutter-and-gnome">
	<start>11:20</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>heart-blingness-clutter-and-gnome</slug>
	<title>Heart of Blingness: Clutter and GNOME</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Clutter is a toolkit for creating fast, dynamic, compelling and portable user interfaces; it feels at home on the desktop as well as on mobile devices. Clutter is part of the GNOME 3.0 platform, and sits right at the heart of the GNOME 3.0 user experience, by powering the Shell.This talk will show the progress made by Clutter in the last year, with new layout management options, new animation features, and performance improvements. This talk will also show what the Clutter development team wants to improve and make available for the GNOME 3.2 release, and the future of Clutter and GTK development for a better GNOME application developer experience.</abstract>
	<description/>
	<persons><person id="0">Emmanuele Bassi</person></persons>
	<links></links>
	</event>
	
<event id="clutter-everywhere">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>clutter-everywhere</slug>
	<title>Clutter Everywhere</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The year of the Linux desktop has come and gone. Now is the year for Linux in your mobile, your tablet, your TV and your fridge. But how can you make your blingy iFart app without tying yourself to one platform whilst still taking advantage of the 3D hardware in your phone? Clutter to the rescue!This talk targets developers needing a lightweight platform abstraction layer to build all sorts of graphical, slick-looking, accelerated applications. We will demonstrate a range of exiting(!) applications running on GNU/Linux, Windows, Android, WebOS and a very specialized System On Chip: the Intel CE 4100, a TV/Set Top Box platform</abstract>
	<description/>
	<persons><person id="0">Chris Lord, Damien Lespiau, Neil Roberts</person></persons>
	<links></links>
	</event>
	
<event id="webkit-clutter-port-present-and-future-webkitgtk-status-and-roadmap-webkit2">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>webkit-clutter-port-present-and-future-webkitgtk-status-and-roadmap-webkit2</slug>
	<title>WebKit Clutter Port Present and Future; WebKitGtk Status and Roadmap to WebKit2</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>On WebKit Clutter:The Clutter port of WebKit has been recently announced and the branch has been uploaded to a public repository where its development continues. It shares most of the GObject-based public API with the current WebKitGTK+ port, and also shares all the backends that provide platform-dependant services to WebCore: cairo for drawing, soup for HTTP and GStreamer for multimedia.During the talk we'll explore how the clutter port manages to share code with WebKitGTK+ and the challenges there are to sharing even more. Given clutter doesn't have a single widgets toolkit, we'll talk about how the port acknowledges that fact and allows supporting the various clutter-based toolkits. We will also look at web compatibility, and explore the features that have been implemented.Looking forward, and most importantly, we'll discuss what work could be done in the future to make it rock even more, in particular by leveraging clutter functionality and its ability to use the GPU. We'll raise questions about pushing it upstream to live inside webkit.org, and how it could be better integrated or even merged with WebKitGTK+ in the future.On WebKitGTK+:This talk for WebKitGTK+ embedders and those interested in integrating the web with the free desktop will summarize the various WebKitGTK+ improvements from the last year in rendering, GTK+ 3 support, accessibility, networking, etc. Also, we will cover WebKit2 architecture and the roadmap for WebKit2 support for WebKitGTK+, including API design, plans for GNOME integration and demos.</abstract>
	<description/>
	<persons><person id="0">Gustavo Noronha Silva, Martin Robinson, Alejandro G. Castro</person></persons>
	<links></links>
	</event>
	
<event id="kde-contributions-qt">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>kde-contributions-qt</slug>
	<title>KDE contributions to Qt</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>KDE has contributed to Qt in many ways since the humble beginning back in 1996. This spans from bug reports, ideas and suggestions, to marketing effects where developers first learn about Qt through KDE. Nokia opened for external contributions back in 2009. Knut Yrvin, Aron Seigo and Robin Burchell has studied contribution statistics and technology contributions to Qt. Knut is giving an overview of the results. He will focus on the share volume of contributions from different parties external to Nokia, including technology contributions as Xquery/XPath and Phonon.  Knut will include some comments on work done supporting open standards as the Open Document Format too, explaining the importance of this. The presentation can be viewed by all, both persons who are new to free software, and those who are more experienced users and developers.</abstract>
	<description/>
	<persons><person id="0">Knut Yrvin</person></persons>
	<links></links>
	</event>
	
<event id="gnome-shell-version-%CF%80">
	<start>17:15</start>
	<duration>0:45</duration>
	<room>Kinosaal</room>
	<slug>gnome-shell-version-%CF%80</slug>
	<title>GNOME Shell version π</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>GNOME Shell is the central new component introduced in GNOME 3. The GNOME 3 Shell integrates window management, application launching, and notification functions into a coherent whole - it is centrally responsible for managing the users workflow as they switch between different tasks and points of attention.At this point, somewhat over halfway through the 3.2 development cycle, we've had the time to get experience with a broad spectrum of users encountering GNOME 3 for the first time. The talk will describe some of the lessons we've learned from seeing GNOME 3 go out to a broad audience: what worked, what new features caught people's fancy, and what didn't work so well. We'll look at what we are planning to do to fill gaps and improve the parts that need improvement.We've also been rapidly working on new features for GNOME 3.2, including integrated file management and input methods and deeper integration between applications and the shell. The talk will describeand demo these new features.Finally, we're at a good point to review the 3.0 development cycle and see what worked out for development processes and what worked less well.  How did formal code review work? What was the right way to handle tester feedback? Are there things that make sense to carry over into other similar projects?</abstract>
	<description/>
	<persons><person id="0">Owen Taylor</person></persons>
	<links></links>
	</event>
	</room>
<room name="Rm2002">
<event id="folks-contact-aggregation-free-software">
	<start>11:20</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>folks-contact-aggregation-free-software</slug>
	<title>Folks: Contact aggregation for Free Software</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Added as an external dependency to GNOME in 2.32, libfolks brought meta-contacts support to Empathy. Since then, Folks has grown beyond just a Telepathy IM contacts aggregator and now has support for Tracker — and will soon have support for libsocialweb and evolution-data-server. Where does libfolks fit into GNOME 3.2 and KDE? How can we use libfolks and libsocialweb to integrate the desktop with social networks? To what extent can we and should we integrate the two?This talk will demonstrate how to use libfolks to integrate the user's aggregated contacts (also known as people) in your GLib-based application. We'll also discuss and provide examples for QtFolks, our QtContacts bindings for Folks, which brings all the contact sources of Folks into your Qt-based application. We'll then explore the future of libfolks, including ideas for desktop/web integration.The talk is aimed at GNOME and KDE developers who are interested in adding contact support to their application or in social networking integration on the desktop.</abstract>
	<description/>
	<persons><person id="0">Travis Reitter</person></persons>
	<links></links>
	</event>
	
<event id="oracle-trusted-extensions-and-gnome-3-migration">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>oracle-trusted-extensions-and-gnome-3-migration</slug>
	<title>Oracle Trusted Extensions and GNOME 3 Migration</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Solaris Trusted Extensions is a unique and successful free software derivative of the GNOME desktop.  This talk will further introduce the design and advanced security features of this exciting project to the free desktop community and discuss the challenges of migrating this product to GNOME 3.  As such, it provides a useful case study in the GNOME 2 to 3 migration.</abstract>
	<description/>
	<persons><person id="0">Brian Cameron</person></persons>
	<links></links>
	</event>
	
<event id="compositing-after-x-kwin-road-wayland">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>compositing-after-x-kwin-road-wayland</slug>
	<title>Compositing after X - KWin on the Road to Wayland</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>After more than 25 years of reign over our desktops, it looks like the X Server is approaching retirement. With Wayland finally a possible successor seems to be found. The year 2010 showed important development efforts in the field of Wayland. Major distributions like Ubuntu and Fedora announced that they want to switch to Wayland and the Qt framework was ported to Wayland - the code is already merged into the Qt tree.Having a possible successor for the X window system is not the only factor for its success. In order to be able to transit to Wayland our desktop environments need to embrace the new environment. Providing a powerful Wayland compositor is one of the most important implementation tasks for the existing desktop environments like the KDE Plasma Workspaces. Without a compositor being on par with the X11 window managers it is unlikely that there is any user acceptance for Wayland.In this talk the possibilities of providing a Wayland compositor for the KDE Plasma Workspaces based on KWin's existing source code will be discussed and presented. KWin has already done a major step towards Wayland by supporting OpenGL ES 2.0 as a compositing backend. The work currently going on in KWin will be presented in the context of the Wayland porting efforts and the steps to go from here will be elaborated.</abstract>
	<description/>
	<persons><person id="0">Martin Gräßlin</person></persons>
	<links></links>
	</event>
	
<event id="gnome-state-union">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>gnome-state-union</slug>
	<title>GNOME: The state of the Union</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>In this talk we will discuss the state of the GNOME project, having some fun, geek cultural references and, also, some serious stuff.</abstract>
	<description/>
	<persons><person id="0">Fernando Herrera and Xan Lopez</person></persons>
	<links></links>
	</event>
	
<event id="improving-quality-video-calls-free-desktop">
	<start>17:15</start>
	<duration>0:45</duration>
	<room>Rm2002</room>
	<slug>improving-quality-video-calls-free-desktop</slug>
	<title>Improving the quality of video calls on the Free Desktop</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Farsight2 has become the leading Free Software implementation of a videoconferencing framework. It is currently used by all of the important free IM applications including Empathy, Pidgin as well as the MeeGo platform.  It implements most of the complex aspects of doing audio and video calls over the Internet, including selecting compatible codecs and establishing the connectivity using advanced techniques like ICE.The next great challenge is to improve the quality of the calls, especially of video calls. Most non-free video calling systems have various proprietary ways to dynamically adjust the parameters during a call to get optimal quality. This is their best kept secret. They use various tricks to try to detect the available bandwidth to maximize its usage while minimizing packet loss. Also, various tricks are used to conceal the loss of packets from the user. We're trying to bring these kind of improvements to the Free Software world.I will describe the efforts that I have undertaken to improve quality in Farstream, as well as efforts that were done as part of other related projects like Telepathy and the XMPP standards.</abstract>
	<description/>
	<persons><person id="0">Olivier Crête</person></persons>
	<links></links>
	</event>
	</room>
<room name="Rm3038">
<event id="simon-open-sourcing-speech-recognition-kde-technology">
	<start>11:20</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>simon-open-sourcing-speech-recognition-kde-technology</slug>
	<title>simon: Open Sourcing Speech Recognition with KDE technology</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>simon is a speech recognition solution based on Julius and the HTK.simon is designed to be as flexible as possible and will work with any language or dialect. The reactions to recognition results are completely configurable and there is not a single voice command that can't be configured to the users needs.To keep the system easy to use we employ "scenarios": Packages of simon configurations for specific tasks. Possible simon scenarios are for example "Firefox" (launching and controlling firefox) or "window management" (closing / moving / resizing windows), etc.. Scenarios can easily be created by users and shared with the community through the Get Hot New Stuff system.At the time of writing, there are already 39 scenarios in three languages published on the  repository at opendesktop.org.simon also supports the use of generic, general models like the GPL models from Voxforge so that users who speak English, German or Portoguese don't need to train the system at all to get started.A demonstration of simon 0.3.0 can be found on youtube (http://www.youtube.com/watch?v=bjJCl72f-Gs).The talk will include technical background on how speech recognition - especially the implementation in simon - works, show how users can benefit from simon and also how developers can get involved in the simon development and how they can use it to enhance their own software.There will of course also be a live demonstration of the current simon version.</abstract>
	<description/>
	<persons><person id="0">Peter Grasch</person></persons>
	<links></links>
	</event>
	
<event id="helpful-help">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>helpful-help</slug>
	<title>Helpful Help</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Most software documentation is stuck in the 80s. Even when it's online, it's stodgy and linear and it feels like a book. Get a glimpse of what user assistance professionals are pushing for, and find out how open source hackers can beat them to the punch. Learn the buzz behind buzzwords like topic-oriented, faceted navigation, and integrated help. Find out what Mallard is all about, how well it worked for GNOME 3.0, where it failed us, and how we can do better. Connect with people who want to fix this documentation mess and create help that's actually helpful.</abstract>
	<description/>
	<persons><person id="0">Shaun McCance</person></persons>
	<links></links>
	</event>
	
<event id="gnome-30-accessibility-state-union">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>gnome-30-accessibility-state-union</slug>
	<title>GNOME 3.0 Accessibility: State of the Union</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>In GNOME, accessibility is a core value that touches all aspects of the system.From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME 2.0 not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work.This year (2011) was released GNOME 3.0, the first major release of GNOME since GNOME 2.0 on 2002.As a major relase GNOME 3.0 involves several changes on the technology layers of GNOME affecting the accessibility support in several aspects. Some examples: bonobo deprecation, new desktop (GNOME Shell) using a new technology (Clutter), etc.Since the annoucement of GNOME 3.0 and those technologies changes the accessibility community was working in order to get the best support on this major release, including two accessibility hackfests during 2010.In general, the purpose of this presentation is:Introduce accessibility on GNOME.Briefly explain the technologies changes between GNOME 2.0 and GNOME 3.0How this affects accessibility support?Community reaction?Briefly explain the status of GNOME 3.0What works?What doesn't works?Plans towards GNOME 3.2</abstract>
	<description/>
	<persons><person id="0">Alejandro Piñeiro</person></persons>
	<links></links>
	</event>
	
<event id="building-bridges-making-kde-accessible">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>building-bridges-making-kde-accessible</slug>
	<title>Building Bridges: Making KDE accessible</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Accessibility, the ability to access, is an important side of the devices we interact with on a daily basis. Enabling as many people as possible to use our applications is important. When it comes to user interfaces, several aspects have to be considered. As an example, imagine someone with visual disabilities wanting to operate a touch-device. There are several different disabilities to be taken into account when designing user interfaces, and in the end, everyone benefits from improvements made for more accessible interfaces.With improvements in Qt's accessibility support on Linux, the focus of this talk will be on making KDE applications more accessible. The good news is, that you get most of the way to an accessible application for free. The KDE widgets need to be checked to work properly with the accessibility support in Qt. Another interesting topic is the support for Qt's graphics view framework and Qt Quick. I will present the ongoing research to make Qt Quick accessible.I will give an overview of what we currently have in Qt when it comes to accessibility.Many things work out of the box. We support big fonts and color schemes with high contrasts, right from KDE's settings.On the other hand there are some missing pieces that I would like to mention as well. I will explain what is required to make new customized widgets accessible. Qt offers the QAccessible API to introspect the application's user interface. I will explain how a screen reader uses these APIs.</abstract>
	<description/>
	<persons><person id="0">Frederik Gladhorn</person></persons>
	<links></links>
	</event>
	
<event id="design-thinking-and-how-free-desktop-may-benefit-it">
	<start>17:15</start>
	<duration>0:45</duration>
	<room>Rm3038</room>
	<slug>design-thinking-and-how-free-desktop-may-benefit-it</slug>
	<title>Design Thinking and how the Free Desktop may benefit from it</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Design Thinking is a powerful methodology to identify and address a user's latent needs. It is executed in a flexible space and makes use of the diversity of multidisciplinary teams. As a third ingredient it incorporates a sophisticated process, which helps to stay focused on the challenge, set free creativity and encourage early prototypes.This talk gives detailed account of Design Thinking as a whole and how the Free Desktop specifically may benefit from it. Here, the range includes the design of a great interface experience for the end-user as well as questions around the open source development process and the community.It is a follow up to last year's GUADEC Workshop and lightning talk by the same speaker and is connected to the Design Thinking Workshop happening at the summit.</abstract>
	<description/>
	<persons><person id="0">Clemens N. Buss</person></persons>
	<links></links>
	</event>
	</room></day>
<day index="2" date="2011-08-07">
<room name="Audimax">
<event id="calligra-office-documents-everwhere">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>calligra-office-documents-everwhere</slug>
	<title>Calligra: office documents everwhere</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The Calligra Suite of applications has offered rich office document handling capabilities on Linux desktops, as well as creativity applications. In the past two years, Calligra has become even more widespread, with Calligra-based office applications running on mobile phones and tablets. This presentation will demonstrate the versatility of Calligra on various platforms and form factors. I will discuss the technical issues we had making this possible in depth. Finally, I will show what we need to do to make the Calligra engine even more the natural choice if you are writing free software applications that need office document rendering, editing or processing capability.Over the past years, Calligra has been picked by a number of companies to integrate with their own products. Nokia has worked closely with the Calligra community to develop Calligra Mobile. This presentation will also describe this process and the lessons which can be learned from it.</abstract>
	<description/>
	<persons><person id="0">Boudewijn Rempt</person></persons>
	<links></links>
	</event>
	
<event id="liberating-open-office-development">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>liberating-open-office-development</slug>
	<title>Liberating Open Office Development</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>LibreOffice is the most powerful and viable Free Softwareoffice suite, available cross-platform. We'll discuss the history, and rational behind the LibreOffice project and its relation toOpenOffice.org. We'll also look at what we've achieved so far, infeatures, infrastructure, governance and development plan.We will survey the lost opportunity to the Free Softwareecosystem that corporate dominated, copyright assignment basedprojects can be, and the dangers involved. Then we'll get stuck into how to develop it - even if you are not (yet) a super-starhacker. Come and get involved with something exciting, and help make tens of millions of user's first experience of Free Software something to be proud of.</abstract>
	<description/>
	<persons><person id="0">Michael Meeks</person></persons>
	<links></links>
	</event>
	
<event id="krita-making-artists-tool">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>krita-making-artists-tool</slug>
	<title>Krita: the making of an artist&#039;s tool</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Last year, Krita (http://www.krita.org) finally left the "promising, but not there yet" state and went into the "ready for artists" state. This would never have happened without the input of artists and the cooperation with people from other graphics projects, like gegl and mypaint. The Libre Graphics Meeting played and continues to play an important role as well. This presentation will look at the way the wide world around a project has a decisive influence on the development of a a free software application. I will show the evolution of Krita through this process, both the user interface evolution and the decisions behind it, and the work artists have been creating with Krita. In the end, the audience will have a solid feel for where Krita is now, where it will be heading as well as what it takes a free software project to get there.</abstract>
	<description/>
	<persons><person id="0">Boudewijn Rempt</person></persons>
	<links></links>
	</event>
	
<event id="coffee-break-2">
	<start>10:50</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>coffee-break-2</slug>
	<title>Coffee Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="ui-design-cloud-diverse-devices">
	<start>11:20</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>ui-design-cloud-diverse-devices</slug>
	<title>UI Design in a Cloud of Diverse Devices</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>An exploration in designing for cross-platform and cloud experiences. The axis of user experience has shifted away from the desktop toward services delivered through multiple platforms of widely differing form factors and the cloud. What does this mean for what users expect from their devices? What does effective design, across platforms and the cloud, look like?This talk is not about detailed device usability, but about what makes a usable service. It also addresses what users increasingly care about the most,and what this means for Operating Systems.</abstract>
	<description/>
	<persons><person id="0">Claire Rowland</person></persons>
	<links></links>
	</event>
	
<event id="towards-marble-20-journey-around-virtual-globe">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>towards-marble-20-journey-around-virtual-globe</slug>
	<title>Towards Marble 2.0 - the journey around a virtual globe</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>In September 2006 the initial source code of the Marble Virtual Globeentered the KDE repository. Since then it has attracted a growing developer community which has turned Marble into an amazing piece of software. With KDE 4.6 Marble has reached the magic version number 1.0: Nowadays Marble covers a wide range of use-cases: Marble 1.0 features advanced routing, turn-by-turn navigation support, Marble can serve as an educational tool and Marble's software library has been used for scientific studies.During this session we will take a quick look at the current state of Marble on the desktop and on mobile platforms (such as the Nokia N900 and MeeGo). Starting from there we will have a look at the challenge how Marble can reinvent itself: We discuss the new road map towards the next big mile stone "Marble 2.0". And we will show our plans how use cases and features such as OpenGL, Panoramic views and augmented reality can find their way into Marble.</abstract>
	<description/>
	<persons><person id="0">Torsten Rahn</person></persons>
	<links></links>
	</event>
	
<event id="lunch-break-0">
	<start>12:30</start>
	<duration>1:30</duration>
	<room>Audimax</room>
	<slug>lunch-break-0</slug>
	<title>Lunch Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="lightning-talks">
	<start>14:00</start>
	<duration>0:45</duration>
	<room>Audimax</room>
	<slug>lightning-talks</slug>
	<title>Lightning Talks</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="group-photo">
	<start>14:45</start>
	<duration>0:25</duration>
	<room>Audimax</room>
	<slug>group-photo</slug>
	<title>Group Photo</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="rekonq-webkit-browser-kde">
	<start>15:10</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>rekonq-webkit-browser-kde</slug>
	<title>Rekonq: a WebKit browser for KDE</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Since its arrival in the rather crowded world of web browsers in 2008, Rekonqhas been steadily improving to offer a nice browsing experiencing whileintegrating well into the KDE desktop. As it gained exposure from being used as the default browser on several distros, we'd like to present an overview of the project and where it's going, and hopefully get a few people on board.One of the challenges ahead is coming up with ways to extend/tailor the browser to one's usage. And as Rekonq intends to stay small and lightweight, a plugin/extension system seems much required at this point. We started our researches on this area studying all possible ways to implement such structure and we decided to go with...(you'll discover it in Berlin!)Another challenge ahead, which is not exactly Rekonq specific has to do with navigation and the concept of tabs in web browsers, and we're eager to explore new ways of organizing the UI in that respect.More plans for the future will be presented and will hopefully be discussed later, possibly in a BoF.</abstract>
	<description/>
	<persons><person id="0">Andrea Diamantini &amp; Pierre Rossi</person></persons>
	<links></links>
	</event>
	
<event id="coffee-break">
	<start>15:40</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>coffee-break</slug>
	<title>Coffee Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="gnome-shell-iterations-what-you-need">
	<start>16:10</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>gnome-shell-iterations-what-you-need</slug>
	<title>GNOME Shell: Iteration&#039;s what you need</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>GNOME 3 is here! But this is just the start, how do we make it better, six months at a time. What are the best bits? What needs to be changed? Who should we listen to? And what processes and tools should we use? Some of these questions will be answered in this keynote but all will be discussed. Listeners will also be thrilled by tales of what the future holds.</abstract>
	<description/>
	<persons><person id="0">Nick Richards</person></persons>
	<links></links>
	</event>
	
<event id="integrating-virtualization-desktop">
	<start>16:50</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>integrating-virtualization-desktop</slug>
	<title>Integrating virtualization into the desktop</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The Spice project aims to provide a complete open source solution for interacting with virtualized desktops. Desktops need not be constrained to a display in distinct windows. Spice is open! We want interaction to feel easy and local. For that, Spice must be fast and capable of sharing client resources: display, clipboard, webcam, printers, folders, and networking ... in full-screen mode and when embedded inside applications. During this talk will be presented some remarkable Spice features and the status of integrating Spice into the Desktop.</abstract>
	<description/>
	<persons><person id="0">Marc-André Lueau</person></persons>
	<links></links>
	</event>
	
<event id="kparts-browser-plugin-%E2%80%93-bringing-kde-components-all-browsers">
	<start>17:30</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>kparts-browser-plugin-%E2%80%93-bringing-kde-components-all-browsers</slug>
	<title>KParts browser plugin – bringing KDE components to all browsers</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>KDE includes a flexible framework known as ‘KParts’ to integrate components from one program into another program. One example is Konqueror, which can show PDF files inside its browser interface using Okular's PDF viewer component. However, as this component technology heavily relies on KDE libraries, it is only accessible to KDE programs.Whereas Konqueror is the the default browser for KDE, many users prefer other browsers such as Firefox, Opera, or Chrome. Being non-KDE programs, these browsers cannot use the KParts components directly, but they support the original Netscape plugin system instead. The Netscape plugin system is used, for instance, to integrate Flash into a browser.The KParts browser plugin combines both worlds: it implements the Netscape plugin system to integrate into any browser that supports this interface, but relies on KDE's component system to display content to the user. This way, the KParts browser plugin can be used to show PDF files in Firefox using Okular's component (replacing Adobe Reader here) or OpenDocument text files using KWord's component.During registration, the KParts plugin scans the KDE subsystem for available KPart components and notifies the browser what mime types it supports. On a typical KDE desktop system with a rich set of applications installed, this can easily include 300 mimetypes.This plugin is an example how KDE software can interact with non-KDE programs. It may be an inspiration for the GNOME community to build something similar, for instance, adding a Netscape plugin interface to Evince.</abstract>
	<description/>
	<persons><person id="0">Thomas Fischer</person></persons>
	<links></links>
	</event>
	
<event id="beach-party">
	<start>19:30</start>
	<duration>6:30</duration>
	<room>Audimax</room>
	<slug>beach-party</slug>
	<title>Beach Party</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	</room>
<room name="Kinosaal">
<event id="blending-web-and-desktop">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>blending-web-and-desktop</slug>
	<title>Blending the web and the desktop</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Blending the web and the desktopIn this talk we will present how GNOME developers can merge theirapplications and our desktop with the web. We'll show how tobuild applications from scratch using a combination of the latestweb technologies like CSS3, SVG and JavaScript and our belovedand venerable platform. We will also present a sneak preview ofour plans for total integration between the Shell and Epiphany,including: how to make popular web applications first classcitizens of our desktop, tab navigation, bookmarks and historymerged into the Shell, and much more!</abstract>
	<description/>
	<persons><person id="0">Xan Lopez</person></persons>
	<links></links>
	</event>
	
<event id="plasma-active-conquering-device-spectrum">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>plasma-active-conquering-device-spectrum</slug>
	<title>Plasma Active - Conquering the Device Spectrum</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>If we -- the Freedesktop community -- want our creations to stay in the hands and hearts of the users we need to extend our thinking beyond desktops. Reducing our reach to the user to just underlying frameworks, rather than complete products marginalises our dreams and visions, and keeps our imagination and innovativity in captivity rather than cultivating it and bringing it to the world.The ongoing widening of the device spectrum opened the market for newly built user experiences that are desirable for its users, explore new interaction concepts and at the same time offer a secure and elegant way of interacting with the content and services of the web, with the social environment of the user, and with her public and private data.In his presentation, Sebastian presents thePlasma Activeproject, a concerted effort within and beyond KDE to create a complete software environment for a wide spectrum of devices based on KDE's Plasma and a typical Freedesktop-stack, including Qt and Qt Quick's QML. The audience learns how the concepts of the social and semantic desktop become useful underpinnings of functional, touch-friendly, elegant and beautiful user interfaces. A birds-eye view leads the audience from Plasma Active's baby steps to the current state and its future goals. For the audience's pleasure, there will be no lack of demonstrations of the progress made so far.This presentation is intended for a broad technical and non-technical audience.</abstract>
	<description/>
	<persons><person id="0">Sebastian Kügler</person></persons>
	<links></links>
	</event>
	
<event id="theming-gtk-3-widgets-css">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>theming-gtk-3-widgets-css</slug>
	<title>Theming GTK+ 3 widgets with CSS</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>With the new 3.0 release, GTK+ migrated its theming infrastructure to use CSS, instead of the old gtkrc format. This presentation outlines the basic principles behind the new theming API for application developers, with real-world porting experience from Nautilus and the Adwaita GTK+ 3 theming engine.</abstract>
	<description/>
	<persons><person id="0">Cosimo Cecchi</person></persons>
	<links></links>
	</event>
	
<event id="gtk-4-future-your-favorite-toolkit">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>gtk-4-future-your-favorite-toolkit</slug>
	<title>GTK 4 - the future of your favorite toolkit</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>With the work culminating in therelease of GTK 3, the development pace of GTK+ has increased a lot. With active development come a lot ofideas about the futureof the toolkit.Among other topics will certainly be when to do GTK4, how to integrate with all the hot new low-level features from gestures to Wayland, living with Clutter and how to capture the mobile market.While we will present our ideas, we also seek input from the audience. We intend to give this talk more of a BoF character and seek input about our ideas or suggestions of things we are missing. So if you are a developer using GTK or just interested to talk about the future of your favorite toolkit, we'll be happy to talk with you.</abstract>
	<description/>
	<persons><person id="0">Benjamin Otte, Matthias Clasen</person></persons>
	<links></links>
	</event>
	
<event id="qml-designers-perspective">
	<start>15:10</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>qml-designers-perspective</slug>
	<title>QML, A designers perspective!</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>QML (Qt Meta-Object Language) is a JavaScript-based, declarative language for quickly designing user interfaces of applications. It is part of the Nokia Qt framework.In a way it is an incredible tool that enables the designer to create an immersive UI experience, providing incredible freedom on how a application can look, feel and how users can interact with it. But it is also surprisingly simple to understand and learn.As such, it has the potential to be used directly by designers, removing the need for the traditional flow of designer-&gt;mock-&gt;developer-&gt;implementation-&gt;review-&gt;designer cycle. The designer can deliver to the developer a working user experience that the developer can use as is combining it with the underlying code providing the data.This is the vision behind QML and it works rather well in traditional development teams. But... In FOSS land the scenario can change a lot. The designer can be the developer, in fact given the scarcity of designers in open source, the most probable outcome will be that the developer will do the UI design himself. And given the flexibility of QML, this can be a very bad idea.On the other hand, tools such as QML can help create for designers in FOSS land the type of ecosystem it created for developers, empowering them to design and share UI's.In this talk I will try to expose some of the risks QML poses for OSS, and point possible solutions to those, as well as go into how we could maximize the benefits Free Software reaps from this great technology.Intended audience-- UI Designers, traditinal desktop application developers, Touch application developers</abstract>
	<description/>
	<persons><person id="0">Nuno Pinheiro</person></persons>
	<links></links>
	</event>
	
<event id="extend-your-kde-application-qml">
	<start>16:50</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>extend-your-kde-application-qml</slug>
	<title>Extend your KDE application with QML</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>QML easily allows any application to have a rich and fluid UI. KDE has Plasma for a couple of years now and after providing a library that enables the development of "next generation" shells for desktops, netbooks and phones, Plasma's developers are now looking into enabling the use and integration of QML into KDE technologies.After years of experience using a canvas to create all the UI of these shells, the Plasma team started integrating QML with KDE, allowing the use of it across the whole project. In order to achieve this it was necessary to extend QML and create UI components that could be used by other applications, avoiding code duplication and inconsistency between them.During this talk we will discuss how QML was extended, the development of UI components for KDE (that followed Qt-components' development) and how you can use QML in your application and still have proper integration with the rest of the KDE environment (widgets, i18n, icons, Plasma's dataengines and services, etc..)</abstract>
	<description/>
	<persons><person id="0">Artur de Souza</person></persons>
	<links></links>
	</event>
	
<event id="kde-platform-4-roadmap">
	<start>17:30</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>kde-platform-4-roadmap</slug>
	<title>KDE Platform 4 Roadmap</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>In June 2011, a development sprint called Platform 11 was held in Randa, Switzerland. It focused exclusively on the KDE Platform with some 25 participants coming together over the course of the week. The last such sprint in terms of focus, length and size was held in Trysil, Norway five years ago. In those intervening five years, many things transpired: Trolltech was purchased by Nokia, Qt development opened up, mobile form factors became more critical, KDE Platform 4 saw 7 major releases and new frameworks matured.It was an opportunity to take a probing look into the current demands and future directions for the platform. Roadmaps were drawn up, plans were made and work has since started on implementing them.This interactive presentation will offer an overview of the results of Platform 11 and delve into the details of the resulting efforts that are of interest to the audience. A panel made up of Platform 11 participants will be on-hand to present this information and take your questions.By examining plans for the shared infrastructure that lies beneath KDE applications, we hope to expand awareness of, increase participation in and solidify a future for the KDE Platform.</abstract>
	<description/>
	<persons><person id="0">Aaron Seigo</person></persons>
	<links></links>
	</event>
	</room>
<room name="Rm2002">
<event id="making-color-management-just-work-using-colord">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>making-color-management-just-work-using-colord</slug>
	<title>Making color management &quot;just work&quot; using colord</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The colord project intends to make color management "just work".In this presentation I will quickly introduce why color management is required, and also the problems introducing a color management workflow. We will compare and contrast the frameworks commonly used in OSX and Windows 7. By discussing the integration points, we will be talking to application developers and platform maintainers in order to shape the future development of colord and the front-ends such as GNOME Color Manager. We will also spend some time exploring the intricacies of a color management framework best suitable for each desktop, and how we can start to provide this functionality.I'll cover what projects have already been fixed, and what maintainers have to do to work with colord.There will be time left for questions and discussion at the end. It is expected the audience will be moderately technically skilled, and possess a basic understanding of color management.</abstract>
	<description/>
	<persons><person id="0">Richard Hughes</person></persons>
	<links></links>
	</event>
	
<event id="network-and-location-awareness-your-application">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>network-and-location-awareness-your-application</slug>
	<title>Network and Location Awareness in Your Application</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>With 24/7 connectivity from their couch to the train on their morning commute, users increasingly want network- and location-aware applications and services.  Without more intelligence about networking, connections, and location, it's hard for applications to make the right choices about what features to offer at any given time.  This talk will show you how to make use ofNetworkManager,ModemManager, and related higher-level frameworks to determine what physical network media is used, what kind of network connection is present, how to display network status, and to read basic geo-location information, all helping to make your app become more aware of the network.  From using pure D-Bus to frameworks like geoclue and KDE's Solid, you'll learn how to help your users out by including network intelligence and location awareness.  If you develop desktop applications or frameworks and you have a modest knowledge of D-Bus, C/C++, and some GNOME or KDE application development experience, this talk might be for you!</abstract>
	<description/>
	<persons><person id="0">Dan Williams</person></persons>
	<links></links>
	</event>
	
<event id="gluing-together-usable-desktop-crypto">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>gluing-together-usable-desktop-crypto</slug>
	<title>Gluing Together Usable Desktop Crypto</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Desktop applications use a bunch of diverse crypto libraries. While in these are generally technically excellent, the diversity represents an obstacle to a consistent user experience for crypto and security stuff.Currently users have to deal with configuring each application separately for things like certificate choices, keys and other crypto stuff. Developers often shy away from implementing solid crypto bits in their application because of the formats, storage, management interfaces and other obstacles involved.This talk will discuss we are gluing together the certificate, key and trust storage across the different crypto libraries and desktops. The effort involves PKCS#11, trust assertions, hardware support, and other new research.We'll talk about how you can participate or start to make use of this stuff no matter what your choice of toolkit or crypto library.This is a solid, pluggable foundation for crypto storage and coordination between libraries and desktops. As a result, the user gets a predictable and simple experience. Developers get a solid foundation not only to better security in current applications, but on which to build cool new solutions to the thorny issues of privacy and identity.</abstract>
	<description/>
	<persons><person id="0">Stef Walter</person></persons>
	<links></links>
	</event>
	
<event id="lightdm-cross-desktop-display-manager">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>lightdm-cross-desktop-display-manager</slug>
	<title>LightDM: Cross Desktop Display Manager</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>LightDM is a new display manager (or login screen from a users point of view) that has been designed to be cross-desktop.  This talk introduces the project, discusses the design and encourages listeners to get involved.  A presentation will show how simple it is to write a GUI for LightDM and demonstrate GUIs using different toolkits.You can find more information about LightDM athttps://launchpad.net/lightdm.Attend this talk if you are:- Interested in making/modifying login screens.- Distributions/projects interested in using LightDM.- Display manager/X/Wayland developers interested in working together to share the maintenance of the display manager.</abstract>
	<description/>
	<persons><person id="0">Robert Ancell</person></persons>
	<links></links>
	</event>
	
<event id="systemd-and-login-sessions">
	<start>15:10</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>systemd-and-login-sessions</slug>
	<title>systemd and Login Sessions</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Most major distributions have adopted or are in the process of adopting systemd as system and service manager, replacing older init systems. However, systemd is not only useful for improving system bootup, but also login session startup. In this talk I will try to explain in detail why we think starting sessions with systemd is a good thing and what win by adopting it. I'll discuss the technical details, where precisely we are with this, and where we want to go, what the requirements are, and what changes will be necessary on other software. This will cover a lot of technologies, such as the new D-Bus user bus, kernel changes, and the relation to existing desktop-specific session managers.The initial focus of this work is making GNOME boot with systemd as login session manager. However, the work is very relevant for other desktops, too. Our hope is that eventually the session manager is considered more part of the OS, and less of the desktop, which would allow us to run all different desktops with the same session manager, and mix and match parts normally part of the different desktops more freely, while making maximum use of the modern features of the Linux kernel which systemd exposes.Other operating systems (such as MacOS with launchd) already use the same implementation for managing the system and the user sessions, and have shown that this brings great advantages. On Linux, we can and should take advantage of the same ideas, and in this talk I hope to explain why and how.</abstract>
	<description/>
	<persons><person id="0">Lennart Poettering</person></persons>
	<links></links>
	</event>
	
<event id="pulseaudio-control-and-command-state-desktop-integration-gnome-kde">
	<start>16:50</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>pulseaudio-control-and-command-state-desktop-integration-gnome-kde</slug>
	<title>PulseAudio: Control and Command - State of Desktop Integration in GNOME &amp; KDE</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>PulseAudio integration has come a long way. The times when detractors derided it for crashing or simply not working are mostly in the past (there are always exceptions!) and the various distributions now have solid integration and configuration options available. ALSA has also come a long way to support the timer-based scheduling that PulseAudio uses by default.Today, a major hurdle is UI and Desktop Environment integration. In this talk I intend to look at the current UIs in both GNOME and KDE and the kind of interfaces that are missing and are still needed and what options still need to be exposed from the underlying ALSA level. I'll look at the routing logic chosen under the (more exposed) KDE and the (more minimal) GNOME interfaces and how we support that at the PA level. I'll also look at how we should be configuring some of the more advanced features of PA in a way that can fit in neatly to the DE with their own, native UI.</abstract>
	<description/>
	<persons><person id="0">Colin Guthrie</person></persons>
	<links></links>
	</event>
	
<event id="slothful-ways-d-bus">
	<start>17:30</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>slothful-ways-d-bus</slug>
	<title>The Slothful Ways of D-Bus</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>It's a common belief that D-Bus is “slow”, but there's relatively  little quantitative data on what exactly is slow about it, how slow it actually is, and—perhaps most importantly—why. This talk will discuss a detailed study—conducted primarily by Alban Crequy and Robin Bate Boerop—into the throughput and latency characteristics of the reference implementation of D-Bus, and the variables affecting these characteristics, such as message size, connected clients, and other factors. Armed with these concrete facts, Will will talk about the areas it might be most beneficial to focus on, and possible approaches to solving the issues discovered.Of course, not every D-Bus issue can be blamed on the transport implementations: many applications fall into pessimal usage patterns, often without realising. So this talk will also discuss the methods that can be used to find and examine inefficient use of D-Bus, such as statistics retrieved from the bus daemon itself. Inevitably, Will will wax lyrical about Bustle, a pointy-clicky D-Bus activity viewer, which is growing statistics built into the UI, as well as searching, filtering, and monitoring activity in real time.</abstract>
	<description/>
	<persons><person id="0">Will Thompson</person></persons>
	<links></links>
	</event>
	</room>
<room name="Rm3038">
<event id="improving-how-we-build-gnome-both-code-and-human-terms">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>improving-how-we-build-gnome-both-code-and-human-terms</slug>
	<title>Improving how we build GNOME, both in code and in human terms</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>This talk will look at GNOME technologies like jhbuild, from both a technical point of view as well as how they work as an entry point for both potential GNOME contributors (as well as people who simply want to follow along with the latest happenings).  I will mention improvements I have in progress, and compare with how successful FOSS projects like Mozilla operate.The intended audience is anyone who is attending GUADEC and interested in GNOME and FOSS software development.</abstract>
	<description/>
	<persons><person id="0">Colin Walters</person></persons>
	<links></links>
	</event>
	
<event id="thoughts-gjs-based-development">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>thoughts-gjs-based-development</slug>
	<title>Thoughts on Gjs-based development</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Gjs allows developers to write GNOME-based software in Javascript. It's based on Mozilla's SpiderMonkey Javascript engine. Gjs is used on the development of interesting projects such as GNOME Shell, The Board, and the litl OS.In this talk, I'll demonstrate Gjs' main features, discuss a bit its strengths and weaknesses, and present some of the best practices when writing Gjs-based code.</abstract>
	<description/>
	<persons><person id="0">Lucas Rocha</person></persons>
	<links></links>
	</event>
	
<event id="vala-are-you-kidding-me">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>vala-are-you-kidding-me</slug>
	<title>Vala? Are you kidding me??</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Vala is a programming language that aims to bring modern programming language features to GNOME developers without imposing any additional runtime requirements and without using a different ABI compared to applications and libraries written in C. Although Vala is a very awesome language and have been around for a few years already, people are still either scared of it and/or still think of it as highly unstable. In this talk, the speaker will attempt to alleviate these fears and shed some light on the most usefulfeatures of this language by sharing a short summary of his two years' experience with this language. Common pitfalls in the Vala world and ways to avoid them will also be discussed in this talk.</abstract>
	<description/>
	<persons><person id="0">Zeeshan Ali (Khattak)</person></persons>
	<links></links>
	</event>
	
<event id="open-build-service-cross-distribution-packaging">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>open-build-service-cross-distribution-packaging</slug>
	<title>Open Build Service - Cross-Distribution  Packaging</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The Open Build Service (OBS) is an open and complete software distribution development platform. It provides the infrastructure to create software packages for a wide range of operating systems and hardware architectures as well as add-ons, appliance images or entire linux distributions.OBS provides the tools to work collaboratively, supporting access rights, merge requests and review functionality. Users can access OBS via a convenient web interface, as well as a commandline tool or via the extensive API.Rather than using "compiler farms" of different hardware to build packages for different architectures and multiple Linux distributions like Fedora, Debian, Ubuntu, the OBS creates a clean virtual instance for each build, saving the user time and resources.OBS takes care of any dependency changes and rebuilds packages when needed. It can directly pull source from Source Code Management systems like SVN and git. It is also possible to link to other projects on OBS to build against theirmore current packages. There's also feature comparison of OBS and similar systems.OBS is free software licensed under GPL and freely available in both source form and as easily deployable appliance.OBS is used by a variety of projects to build packages, appliances or entire distributions. The openSUSE community employs OBS to build openSUSE since 2008 and SUSE builds SUSE Linux Enterprise with OBS. the Linux Foundation has a Open Build Service instance to build their linux distribution MeeGo. Other well known parties using OBS include the VLC project, GNOME3, Dell and Cray Supercomputers.The OBS is developed under the umbrella of the openSUSE project.</abstract>
	<description/>
	<persons><person id="0">Sascha Peilicke</person></persons>
	<links></links>
	</event>
	
<event id="git-full-insert-your-desktop-here-os-image-few-click">
	<start>15:10</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>git-full-insert-your-desktop-here-os-image-few-click</slug>
	<title>From GIT to a full &lt;insert your desktop here&gt; OS image in a few click</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Writing code is important, but getting it to users is even more important, if you want to be able to get it tested, have bug reports and do good quality releases.Unfortunately, many users might have the knowledge to build your software, or are frighten to break their existing system by installing your program, especially when it requires a lot of bleeding edge components.These days, you can easily create a full OS image, from packages built from tarballs or even  checkout, in a few clicks, so your users are able to test your software (it can be just one simple package or an entire desktop environment) stress-free.This talk will describe the tools which were used to createGNOME 3 live image, which was very helpful for GNOME 3.0 development and test (and advocacy).Those tools include things likeSUSE Studio,Open Build ServiceandKiwi.</abstract>
	<description/>
	<persons><person id="0">Frederic Crozat</person></persons>
	<links></links>
	</event>
	
<event id="software-quality-has-no-name">
	<start>16:50</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>software-quality-has-no-name</slug>
	<title>Software with the Quality that Has No Name</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>In the 1970s, Christopher Alexander, a mathematician/architect from the University of Berkeley, researched the question of why there are pleasant and lively places, towns, and buildings, and why they are different from drab, depressing, and unloved ones.  He discovered profound results based on human psychology and the way nature works.Alexander's theory of architecture caught attention from the Computer Science community, and it led to the well-known "Design Patterns" movement.  Over time, Alexander's method of design and construction has been applied to many areas of software.This talk will give a short introduction to Alexander's theory.  Then, it will show examples of how it can be applied to design really good software, both in terms of the technical design of the software's structure, and in terms of the end-user design of the user interface.</abstract>
	<description/>
	<persons><person id="0">Federico Mena Quintero</person></persons>
	<links></links>
	</event>
	
<event id="features-follow-function-design-driven-development-gnome-shell">
	<start>17:30</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>features-follow-function-design-driven-development-gnome-shell</slug>
	<title>Features follow function - design-driven development of GNOME Shell</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Without a doubt, GNOME Shell is the defining technology of GNOME 3. While much has been said and written about changes to the user experience, the developer experience of GNOME Shell deserves more coverage than it has been given - from the first sketch-ups at the 2008 UX hackfest to the first stable release in April 2011, mockups always preceded code.Design-driven development like this is still rare in FOSS projects, and provides challenges to all involved - designers exploring how to do design in the open, developers having to give up some of their "code first" mentality.So how do designers and developers cooperate on GNOME Shell? What worked for designers? What worked for developers? What didn't, and how can we improve the process?</abstract>
	<description/>
	<persons><person id="0">Florian Müllner</person></persons>
	<links></links>
	</event>
	</room></day>
<day index="3" date="2011-08-08">
<room name="Audimax">
<event id="think-semantically-nepomuk-and-social-semantic-desktop">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>think-semantically-nepomuk-and-social-semantic-desktop</slug>
	<title>Think Semantically - Nepomuk and the social semantic desktop</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Nepomuk is known for being a desktop search solution. Searching, however, is just a small part of the project that aims to be the glue to connect all applications in a semantic fashion.Through Nepomuk applications are provided with a lot of data that they normally would not have access to. An email client can directly access images depicting the email sender, a task manager can show files related to the tasks, a web browser can organize web pages by projects or persons and so on. Nepomuk also serves as an important tool in categorization of data and the gathering of statistical usage data.Nepomuk started as a European Research Project in 2006 which aimed to create the foundation for the semantic desktop of the future. The KDE integration was only a small part of this rather large research effort. After the end of the project in 2008 Nepomuk lived on in the KDE implementation which became an integral part of the KDE system.Nepomuk is currently being used by high profile projects like Akonadi and Telepathy. It serves as a powerful backend and allows everything to be linked together in a web of semantic information which ultimately leads to a richer user experience.This talk aims at dispelling common myths about Nepomuk and explain the real goal of the project. The talk will showcase exciting things Nepomuk can do and that can be done with Nepomuk. Finally it will present the road that lies ahead, the dream that is the semantic KDE 5.</abstract>
	<description/>
	<persons><person id="0">Vishesh Handa and Sebastian Trueg</person></persons>
	<links></links>
	</event>
	
<event id="zeitgeist-activity-centric-desktop">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>zeitgeist-activity-centric-desktop</slug>
	<title>Zeitgeist in the activity-centric desktop</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>We will present the status of the activity-centric or document-centric vision that was first presented in GUADEC 2008:  status of the Zeitgeist suite of technologies, software for end users such as gnome-activity-journal and gnome-shell, and which applications log your activities in the Zeitgeist journal.</abstract>
	<description/>
	<persons><person id="0">Federico Mena Quintero</person></persons>
	<links></links>
	</event>
	
<event id="new-activity-based-mobile-user-interface-plasma-and-nepomuk">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>new-activity-based-mobile-user-interface-plasma-and-nepomuk</slug>
	<title>A new activity based mobile user interface with Plasma and Nepomuk</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Over the past few years, for the whole life cycle of the KDE Platform 4th series, an important part of the KDE framework has been developed and improved: the Plasma library. Today, a complete workspace based on Plasma technologies is the primary user interface of the KDE desktop, but this is just the start of the journey.Another important pillar of KDE technologies is Nepomuk, that handles all kinds of metadata like documents, contacts, websites etc to correlate them and help the user to find his/her way in the always increasing amount of data the user is faced with.The classical approach of current mobile systems is based on the idea that the user first chooses the application to reach his goal. He has to search for data and has to order the information himself. This creates a traditional, very static and application-centric User Experience. A few months ago a new project called "Plasma Active" kicked off: the aim is to create a touching and desirable user experience for a spectrum of devices like tablet computers, smartphones and more. Contour is part of Active and handles a completely new UX approach of storing and analyzing usage patterns, current context and current activity toprovide the user a set of smart recommendations/actions.The talk by Marco Martin and Fania Jöck will explain the concept behind Plasma Active and Contour, explain the current UI design and an introduction of the technical details behind the UI, as well showcase a real demo of the current development.Project Website:http://community.kde.org/Plasma/Active</abstract>
	<description/>
	<persons><person id="0">Marco Martin</person></persons>
	<links></links>
	</event>
	
<event id="coffee-break-1">
	<start>10:50</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>coffee-break-1</slug>
	<title>Coffee Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="complexity-everyday-technology">
	<start>11:20</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>complexity-everyday-technology</slug>
	<title>The Complexity of Everyday Technology</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>In an increasingly complex world, the best solutions come from looking at problems from a range of perspectives--technology, science, economics, politics, details/abstractions, mythologies, beliefs and trends.Thomas shares his experience and expertise with:communicating with designcreating from the futureinteracting with diverse kinds of peopleacting across boundaries between many different disciplinestesting ideasHe will demonstrate how design is an effective way of dealing with complexity, and speculate on how technology might change life in the future. Apropos to the collaborative Desktop Summit, Thomas shows how we all need others to produce even simple products.Audience: Creatives, designers, engineers, the curious</abstract>
	<description/>
	<persons><person id="0">Thomas Thwaites</person></persons>
	<links></links>
	</event>
	
<event id="semantic-desktop-application-developers">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>semantic-desktop-application-developers</slug>
	<title>The Semantic Desktop for Application Developers</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Nepomuk has now been with us for several years as a pillar of the KDE Platform. Despite adoption of this technology rising, it has yet to realize its full potential. The only way this can happen is for the wider developer community to get on board, and make use of it throughout their applications.This talk aims to provide an introduction to how and why applications built on the KDE Platform should make use of Nepomuk. Avoiding details of how the Nepomuk infrastructure works internally, we will focus on the important part for application developers - how to use Nepomuk and the Semantic Desktop to create a better, more coherent user experience. The talk will make use of a real-life example, the KDE-Telepathy project, to illustrate how Nepomuk can and should be used.</abstract>
	<description/>
	<persons><person id="0">George Goldberg</person></persons>
	<links></links>
	</event>
	
<event id="lunch-break">
	<start>12:30</start>
	<duration>1:30</duration>
	<room>Audimax</room>
	<slug>lunch-break</slug>
	<title>Lunch Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="activities-helpful-big-brother">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>activities-helpful-big-brother</slug>
	<title>Activities - the helpful Big Brother</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>When working on different tasks, people tend to use different sets of tools, communicate with different groups of people etc. The classic desktop environments are not suitable for this behaviour, since they provide the same interface for all different activities people are involved with.With KDE's activities, we are trying to make it possible for the system to act differently depending on a task at hand.For example, when Alice is in 'Studying cryptology' activity, she doesn't need to have Inkscape and Krita in her application launcher's 'Favourites' section. She needs to have the literature for the course easily reachable, a development environment and example programs she wrote.After studying, Brad comes for a film night they planned. Alice switches to 'Watching films' activity and the system automatically hides everything she was doing until then, and shows her film collection in a media player. It also blocks all less important pop-ups and notifications so that they can enjoy the film without interruptions.Apart from the environment itself, applications can benefit from the concept as well. The e-mail client would be able to show only mails relevant to the current activity, file managers to show places that are tied to it, etc.Along with the technologies like Zeitgeist and Nepomuk, this concept allows to better predict user's behaviours since it provides those systems with a vital contextual information.This talk is meant for both users and developers.</abstract>
	<description/>
	<persons><person id="0">Ivan Čukić</person></persons>
	<links></links>
	</event>
	
<event id="bringing-video-calls-tv-merging-telepathy-and-media-explorer">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>bringing-video-calls-tv-merging-telepathy-and-media-explorer</slug>
	<title>Bringing Video calls to the TV - Merging Telepathy and Media-Explorer</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>With the growth of the MeeGo platform a new range of devices are nowtargeted  by the companies and vendors that are looking for more freedomand flexibility using open source software. Set Top Boxes (STB) are nownot only responsible for bringing the TV signal to the users home but alsoproviding a new multimedia experience, with high definition content,Internet browsing and a completely customized user interface.MeeGo is already there, and already provides several open-source MediaCenter  solutions. One of which is media-explorer, a media center completelyplugin based and built upon Mx and Clutter.Lately social networking and user communication has been growing inimportance,  forcing  new products to offer more and more functionalitythat can let the user interact with other people. Instant messaging, mediasharing and social networks are now in the top trends of the most desirablefeatures to have in a multimedia device. Telepathy to the rescue!We built a plugin which allows the user to have their contact listdisplayedand be able to  initiate and receive video calls straight from within themedia center itself. The result is a great and integrated experience. Inthis talk, we want to show you what we did and how we did it, and why not,even show you the result.Of course, this does not end here: we have a lot of ideas and lots of plansfor the future,  and we want to talk about them, get your feedback, andpossibly help you get involved too.</abstract>
	<description/>
	<persons><person id="0">Dario Freddi</person></persons>
	<links></links>
	</event>
	
<event id="quick-overview-enlightenment-foundation-libraries-and-e17">
	<start>15:20</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>quick-overview-enlightenment-foundation-libraries-and-e17</slug>
	<title>Quick Overview of Enlightenment Foundation Libraries and E17</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The Enlightenment project recently announced the official of its 1.0 libraries that have been in development for 10 years. But what are these libraries? Should they be used by third party? If so, why? Let's attach meaning behind those "e" libraries, clarify the reason they were created and how our experience could collaborate more with other desktops and FreeDesktop.org.This talk will enlighten the audience about the project and the upcoming release of the release 17 of our core application: e17 window manager, its current state and roadmap.</abstract>
	<description/>
	<persons><person id="0">Gustavo Sverzut Barbieri</person></persons>
	<links></links>
	</event>
	
<event id="coffee-break-0">
	<start>15:50</start>
	<duration>0:30</duration>
	<room>Audimax</room>
	<slug>coffee-break-0</slug>
	<title>Coffee Break</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="gnome-kde-working-towards-better-collaboration-learning-each-others-rights-and-wron">
	<start>16:20</start>
	<duration>0:45</duration>
	<room>Audimax</room>
	<slug>gnome-kde-working-towards-better-collaboration-learning-each-others-rights-and-wron</slug>
	<title>GNOME &amp; KDE - Working towards better collaboration by learning from each others rights and wrongs</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>GNOME and KDE are two big Free Software projects working in the same area - sometimes together and sometimes competing. In this talk we’d like to highlight some of the differences between the two communities and what they have in common.The talk will cover 2 main points:Exploring what we can learn from each other in terms of running our projects, shaping our community, interacting with other communities and businesses.Initiating and maintaining more collaboration efforts in sharing/developing code, design and community management.</abstract>
	<description/>
	<persons><person id="0">Seif Lotfy and Lydia Pintscher</person></persons>
	<links></links>
	</event>
	
<event id="akademy-awards-travelling-pants-closing-session-and-award-ceremony-berlins-future-o">
	<start>17:15</start>
	<duration>0:45</duration>
	<room>Audimax</room>
	<slug>akademy-awards-travelling-pants-closing-session-and-award-ceremony-berlins-future-o</slug>
	<title>Akademy Awards, Travelling Pants, Closing Session and Award Ceremony for &quot;Berlin&#039;s future is open&quot;</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="football">
	<start>19:00</start>
	<duration>2:0</duration>
	<room>Audimax</room>
	<slug>football</slug>
	<title>Football and Volleyball</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	</room>
<room name="Kinosaal">
<event id="defining-common-standards-calendar-systems-and-holidays">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>defining-common-standards-calendar-systems-and-holidays</slug>
	<title>Defining Common Standards for Calendar Systems and Holidays</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>KDE is unique in the Linux ecosystem in providing Localization support for alternative Calendar Systems such as the Hebrew, Islamic and Jalali calendars, something Windows and OSX provide natively.  This talk will explain why support for alternative Calendar Systems is important, and how collaboration is needed to create common definitions of the Calendar System calculations, translations and test cases.  The talk will also examine options for using alternative Calendar Systems in conjunction with the iCalendar and vCard standards.KDE also provides a library for calculating Public Holidays and other notable events which makes extensive use of the alternative Calendar Systems support.  The talk will examine why the iCalendar standard is not sufficient for proper Holiday support and will propose a collaboration on a new common file format and library to share the laborious task of maintaining and translating the holiday database.The intended audience will be people interested in Localization and PIM.</abstract>
	<description/>
	<persons><person id="0">John Layt</person></persons>
	<links></links>
	</event>
	
<event id="making-and-distributing-games">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>making-and-distributing-games</slug>
	<title>Making and Distributing Games</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Game construction and distribution in the free software world has traditionally been a difficult one, which does not fit well with the sporadic needs for updates and the fickle nature of inspiration as often required by such artistic endeavours. Gluon and the GamingFreedom.org social gaming network aim to help fix this. Using Gluon Creator, we show how game creation can be both simple and powerful at the same time, and with GamingFreedom.org and Gluon Player we show how these games are played on multiple platforms at the same time. Live demos will happen and audience participation will be welcome!</abstract>
	<description/>
	<persons><person id="0">Dan Leinir Turthra Jensen and Arjen Hiemstra</person></persons>
	<links></links>
	</event>
	
<event id="ends-earth-exploring-limits-portability">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>ends-earth-exploring-limits-portability</slug>
	<title>To the Ends of the Earth - Exploring the Limits of Portability</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Despite their strong roots on Linux and other Free operating systems, both KDE and Gnome have long moved beyond their home bases and started to target and reach a wide variety of platforms. The Free Software library and tools stack has become much more portable and it is now possible to write applications using Qt or Gtk+ that run on may kinds of desktops and devices. Declarative UI technologies such as Qt Quick make it easier to target different form factors, further broadening the spectrum. While the tools and frameworks isolate the programmer from many details of these platforms and devices, a lot remains to be done if one wants to truly integrate and interoperate everywhere. This needs to be considered on an architectural, implementation and process level. This presentation will explore the challenges especially in architecture and process, where they are less obvious than at the implementation level, and relate the lessons learned from mistakes of the past.</abstract>
	<description/>
	<persons><person id="0">Till Adam</person></persons>
	<links></links>
	</event>
	
<event id="massif-visualizer-memory-profiling-ui">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>massif-visualizer-memory-profiling-ui</slug>
	<title>Massif Visualizer - Memory Profiling UI</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Even though memory gets cheaper and cheaper, it is still a good idea for many developers to investigate time in optimizing the memory consumption of their applications. One way to do that is by using the powerful and widely known Massif tool of the Valgrind suite.While Massif and Valgrind have been around for a long time, a decent visualization UI for the generated data fields was still missing - until recently. In my talk I want to introduce Massif Visualizer, an application filling the gap. It was already successfully used by many professional developers, but should also be handy for many others as well.During the presentation I will shortly walk through using Massif on an application and then concentrate on Massif Visualizer and how it helps in evaluating the output generated by Valgrind and Massif.</abstract>
	<description/>
	<persons><person id="0">Milian Wolff</person></persons>
	<links></links>
	</event>
	
<event id="my-sofa-wants-new-form-factor">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>my-sofa-wants-new-form-factor</slug>
	<title>My sofa wants a new form factor</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>After the netbook revolution started by Asus' EeePC, the tablet market that Microsoft said didn't exist got lifted off the ground by Apple's iPad. Following in Apple's footsteps, tablets in various form factors have flooded the market.We'll discuss what it takes for the Free Desktop in general, and GNOME in particular to be a credible alternative on this exciting segment of the market. This talk is targeted at platform and application developers, as well as enthusiast who like cool demos.</abstract>
	<description/>
	<persons><person id="0">Bastien Nocera</person></persons>
	<links></links>
	</event>
	
<event id="introducing-board">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>introducing-board</slug>
	<title>Introducing The Board</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The Boardis a space for quickly placing daily records: photos, video, audio, text, and more. Think of it as a combination of a note-taking app, voice-memo recorder, a photo and video booth, a photo album, a sketching board, and a digital scrapbook.In this talk, I'll demonstrate the core features of the app, talk about some of the technical aspects of the implementation and future plans.</abstract>
	<description/>
	<persons><person id="0">Lucas Rocha</person></persons>
	<links></links>
	</event>
	
<event id="towards-multitouch-gnome-shell">
	<start>15:20</start>
	<duration>0:30</duration>
	<room>Kinosaal</room>
	<slug>towards-multitouch-gnome-shell</slug>
	<title>Towards a multitouch gnome-shell</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>This talk will concentrate on multitouch and the Gnome shell, and how can it turn into a fully touch driven interface:what is done right nowwhat can be done right nowwhat's about to comewhat's left to do</abstract>
	<description/>
	<persons><person id="0">Carlos Garnacho</person></persons>
	<links></links>
	</event>
	
<event id="swimming-upstream-or-downstream-both">
	<start>16:20</start>
	<duration>0:45</duration>
	<room>Kinosaal</room>
	<slug>swimming-upstream-or-downstream-both</slug>
	<title>Swimming upstream or downstream? Both!</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>We live in a world where we are split between upstream and downstream. Code, patches, bugs, translations, documentation, promotion -- all area of contributions are being done upstream and downstream. This is not necessarily a bad thing, but let's be honest: we all feel from time to time that this world could be a better place where upstream and downstream perfectly understand each other, and work hand in hand. Are things that bad? Or are we just asking for too much?This talk is targetted at contributors from both upstream (desktop projects) and downstream (distributions), and will offer examples of great upstream-downstream collaboration, as well as explore ways to improve this collaboration in our communities. It will also be an opportunity to have an open discussion on this topic, with several leaders from projects stepping in.</abstract>
	<description/>
	<persons><person id="0">Vincent Untz</person></persons>
	<links></links>
	</event>
	</room>
<room name="Rm2002">
<event id="they-call-us-crazy-we-store-contacts-tracker">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>they-call-us-crazy-we-store-contacts-tracker</slug>
	<title>They call us crazy, but we store Contacts in Tracker</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Storing contacts inRDFis far from trivial. People will call you nuts for not using a plain text file instead. Still the result is rewarding.You will learn about the benefits of this solution. You'll hear the stories of all the challenges we faced during development ofqtcontacts-tracker. This talk should be interesting for everyone curious to see RDF andSPARQLleaving their academic habitat, facing cruel world of mobile computing. This project also shows how people from cooperate, GNOME and KDE world work together, aiming for the sky.</abstract>
	<description/>
	<persons><person id="0">Mathias Hasselmann</person></persons>
	<links></links>
	</event>
	
<event id="kde-communities-far-far-away">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>kde-communities-far-far-away</slug>
	<title>KDE Communities Far Far Away</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>KDE communities in India, China, Brazil and even Nigeria is quite different from what you generally see mostly in Europe and maybe in North America. They face different challenges that need to be tackled in different ways.The audience is often different from what you would see in a general Free Software conferences in Europe. Audience can be made of people who were less familiar or completely new to KDE or even Free Software. How did we handle that? How not having a registered foundation in India makes it a bit difficult to organise funds? And how we get around that problem and keep it all fair and clean financially? How we slowly built up a team for 3 years that organised conf.kde.in? What were the most important points that we considered as "must-have" while organising conf.kde.in? And how we did went ahead with it? What were the show stoppers and how we got around them?In this talk, I would like to address the above issues with the hope that other communities can learn and gain out of our experiences and put that into use for the growth of their community.</abstract>
	<description/>
	<persons><person id="0">Pradeepto Bhattacharya</person></persons>
	<links></links>
	</event>
	
<event id="gnome-continent-starting-asia">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>gnome-continent-starting-asia</slug>
	<title>GNOME a continent, starting from Asia.</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>GNOME.Asia committee has been growing from organizing an annual conference to running different projects and establishing GNOME User Groups in different countries over the last 4 years. Emily will share her experience building communities and fail-proof leadership for GNOME on the Asian continent. Expect a lot of practical tips applicable to your local user group , or to manage release parties or conferences. Those will definitely work wonders to attract both technical and non-technical contributions to any FOSS project.</abstract>
	<description/>
	<persons><person id="0">Emily Chen</person></persons>
	<links></links>
	</event>
	
<event id="ramblings-retired-release-manager">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>ramblings-retired-release-manager</slug>
	<title>Ramblings of a retired release manager</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Let's step back a bit and look at what happened in our free software world in the last few years. Our world has changed, and our failures and successes tell us a lot.The GNOME community has learnt many things; so has the KDE community, and our wider free desktop community. Our projects are among the biggest free software projects, and if you think a bit about it, they're even among the biggest software projects in general.Where we stand now is a topic we all like to discuss, but we should not forget what is essential: where we are going. And why we are going there.</abstract>
	<description/>
	<persons><person id="0">Vincent Untz</person></persons>
	<links></links>
	</event>
	
<event id="daily-melee-paid-people-within-free-software-initiatives-how-they-tick-how-keep-the">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>daily-melee-paid-people-within-free-software-initiatives-how-they-tick-how-keep-the</slug>
	<title>Daily Melee: paid people within Free Software initiatives -    How they tick, how to keep them and the art of behaving if you are one.</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Any software initiative like GNOME and KDE has paid and non-paid contributors within their community. Often this is percieved as a problem.  While it is true that those people might come from different corners, there is a good chance to make them work together. We cannot miss it if we want the Free Software desktop to succed further.  Too much boring and hart work lies on the way that we could do it without paid professionals. Still having non-paid community people is an absolute must, as they keep your feet on the ground.This talk will explore example behaviour of both sides of the paid work for Free Software, to help understand the fellow contributor. It gives hints how to behave as a professional who shortly dips into an initiative and to the community how to deal with such folks. Often professionals come in with much more hours per day for a short time and then drop off the planet again. In the daily communication they will behave with different patterns and tend to read less about what is going on outside of their focus.Talking about this will soon lead to the question: How much commercial Free Software do we need? Won't it destroy the spirit, if we have to much of it?  For-profit companies will work for who pays. This means that the development of quite a few high profile Free Software products is already controled by large corporate users. There is a bold solution: We desktop users must pay, so we get back control.  And this is how to keep professionals: Allow them to earn money.  After all, we need each other and the Free Software desktop needs us.</abstract>
	<description/>
	<persons><person id="0">Bernhard E. Reiter</person></persons>
	<links></links>
	</event>
	
<event id="open-source-visualization-scientific-data">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>open-source-visualization-scientific-data</slug>
	<title>Open Source Visualization of Scientific Data</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>As computational power increases, scientists are able to run larger and more accurate simulations. This is creating siginificant challenges in scientific research as the amount of data produced increases, previous analysis techniques become less useful. Worse still, if common formats cannot be agreed upon getting the output of one code into a suitable analysis tool can be difficult. This is where open source tools present a strong alternative to traditional software models.This talk introduces some of the open source technology developed by Kitware, and the open source communities that collaborate on these tools and frameworks. Recent advances in open source scientific visualization will be discussed, going from smaller chemical data sets such as those that can be analyzed by Avogadro, through to very large data sets visualized by the Visualization Toolkit and ParaView. The talk will examine current challenges in visualizing scientific data, new efforts to produce common infrastructure to help scientists and how open collaboration platforms are a key component in cutting edge research.The adoption of the Avogadro library by Kalzium will be discussed, and how we might encourage further collaboration between academics and the KDE community. The modularzation of VTK will be discussed, and how developers can use VTK in KDE applications to use advanced visualization techniques such as volume rendering, isosurfaces, contours, 3D interaction widgets, informatics and 2D charts along with an overview of the pipeline mechanism used to build up complex visualizations.</abstract>
	<description/>
	<persons><person id="0">Marcus D. Hanwell</person></persons>
	<links></links>
	</event>
	
<event id="were-family-how-five-years-university-collaboration-changed-our-town-landscape">
	<start>15:20</start>
	<duration>0:30</duration>
	<room>Rm2002</room>
	<slug>were-family-how-five-years-university-collaboration-changed-our-town-landscape</slug>
	<title>We&#039;re a family! -- How five years of University Collaboration changed our town landscape</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Eight years ago, Kevin Ottens was a student at the IUP ISI (Software Engineering) course of study in Toulouse University. As such, he had to go through a long six months student project which ended up in limbo. The very next year, he ended up mentoring such unused projects...Fast forward two years, he pushed the course of study to embrace Free Software communities (KDE in particular) for those projects. He's been teaching the Free Software ways to his students for five years now.Come and witness how those projects influenced the global Free Software community, how they impacted the local Free Software landscape, and how they boosted students personal and professional lives. We'll particularly focus on the different career paths without being short on funny anecdotes.Five generations of students and former students of the IUP ISI will be on stage to tell you this story. Five generations, parts of the same family.</abstract>
	<description/>
	<persons><person id="0">Kevin Ottens</person></persons>
	<links></links>
	</event>
	
<event id="owncloud-next-logical-step-free-software-world">
	<start>16:20</start>
	<duration>0:45</duration>
	<room>Rm2002</room>
	<slug>owncloud-next-logical-step-free-software-world</slug>
	<title>ownCloud - The next logical step for the free software world</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The advantages of storing data in the cloud are many: ubiquitous access to data from multiple devices, social interaction with millions of others on the web and no extra software to install. However, the data is often owned by several different organizations, which don't easily allow interaction or sharing of data among them. Besides these convenience issues, there are also problems with privacy and security as well as the potential for one hardware failure to make the data of thousands of users impossible to access. Taken together, the cloud is not perfect.ownCloud solves this problems because it is designed to run on the server or computer of the user. So the user has the benefits of cloud computing but controls the data. ownCloud integrates perfectly with KDE desktop applications so that the users has cloud features combined with the power of KDE applications.This talk presents the current state of ownCloud and the plans for ownCloud 2.0 and 3.0</abstract>
	<description/>
	<persons><person id="0">Frank Karlitschek</person></persons>
	<links></links>
	</event>
	</room>
<room name="Rm3038">
<event id="winning-organisations-over-free-software">
	<start>09:00</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>winning-organisations-over-free-software</slug>
	<title>Winning organisations over to free software</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>There have been many attempts to get free software onto desktop systems in businesses and public institutions in the last decade. The success is still limited even if we got certain success in education and in fast growing economies as Brazil, India, Russia and China.Real life trials shows that ordinary users like the GNU+Linux desktop. Computer maintainers say they just use half the time maintaining free software compared with the proprietary alternatives. Even after having the upper hand on all important procurement parameters, most organisations go for a proprietary solution, disregarding practical real life evaluations when acquiring a computer solution. Yrvin explains how to get out of this stalemate, zero-sum situation. The talk are intended for all, including experienced and non-experienced free software users and developers.Knut Yrvin has been helping municipalities, cities and states switching to free software for a decade. He got first hand experience why excellent free software developers fail when meeting ordinary users and single minded computer maintenance staff. He has been directly involved in countless cases where free software wins on technical merit, with lower Total Cost of Ownership and with positive user experience.</abstract>
	<description/>
	<persons><person id="0">Knut Yrvin</person></persons>
	<links></links>
	</event>
	
<event id="limux-desktop-retrospective">
	<start>09:40</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>limux-desktop-retrospective</slug>
	<title>LiMux Desktop retrospective</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Within the LiMux project, the City of Munich increases the use of free softwareon the 14,000 administration desktops. The presentation explains our experiences,including but not limited to the challenges involved with customizing a LinuxDesktop for usage in a large governmental infrastructure.</abstract>
	<description/>
	<persons><person id="0">Florian Maier</person></persons>
	<links></links>
	</event>
	
<event id="free-desktops-europes-public-sector">
	<start>10:20</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>free-desktops-europes-public-sector</slug>
	<title>Free desktops for Europe&#039;s public sector</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>15 million civil servants in Europe are a huge group of potential Free Software users. Today, there are hardly any organisations that do not use at least some Free Software somewhere in their systems. Yet only a tiny fraction of public sector workers actually get to use Free Software desktops. What is preventing greater adoption? And what can we do to speed up the process? While several success cases exist, the big breakthrough is still some way off.This is an area of key interest for the small and medium enterprises that make up a large part of the Free Software ecosystem.</abstract>
	<description/>
	<persons><person id="0">Karsten Gerloff</person></persons>
	<links></links>
	</event>
	
<event id="eu-member-states-interoperability-impossible-without-vendor-independent-pcs">
	<start>12:00</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>eu-member-states-interoperability-impossible-without-vendor-independent-pcs</slug>
	<title>EU member states&#039; interoperability impossible without vendor independent PCs</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>Europe's public administrations are needlessly spending millions by not tackling their dependency on a single proprietary system for their desktop computers and office applications. This leads to suboptimal choices in licensing for and use of desktop software and desktop IT applications. In this talk I present unique data, collected over the past four years during my reporting on the EU's public administration's use of open source. This shows that the desktop PCs of Europe's governments are completely locked-in to a single proprietary software vendor and how this results in reduced interoperability and data loss. I will discuss real solutions, put into practice by public administrations across the EU. Their experiences prove that a vendor-independent desktop PC is not only possible but that such a switch saves money and simultaneously offers civil administrations more choice in IT solutions, thereby helping themto improve their performance.</abstract>
	<description/>
	<persons><person id="0">Gijs Hillenius</person></persons>
	<links></links>
	</event>
	
<event id="changing-mindset-adoption-open-source-indian-government-enterprise">
	<start>14:00</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>changing-mindset-adoption-open-source-indian-government-enterprise</slug>
	<title>Changing mindset, adoption of open source in Indian Government Enterprise</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>My talk will address what made change in mindset of Government body in large scale adoption on Open Source Software including the deployment of large number of Desktops in government schools and research organization.I will also mention if money was the single factor for change of heart or the result of OSS periodical evolution or change in our business/support model.Whoever wants to sell Open Source Software to enterprise is welcome :)</abstract>
	<description/>
	<persons><person id="0">Atul Kumar Jha</person></persons>
	<links></links>
	</event>
	
<event id="linux-case-public-schools-and-private-college-brazil">
	<start>14:40</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>linux-case-public-schools-and-private-college-brazil</slug>
	<title>Linux case in Public Schools and in a Private College in Brazil</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>An overview about how public schools and an private college in Brazil are facing and working with Linux from the elementary education to the high technology degree. Public schools working with Linux guided by the Federal Educational Governament Program - Linux Educacional - helping to support free software culture, benefits to the fundamental education, case with some students and another case about a Private College that's support the use and develop opensource in IT courses and Social Comunications such as Journalism, Publicity, Public Relations, Digital Media and TV &amp; Radio. Case showing TV programs and Newspaper using free software tools.</abstract>
	<description/>
	<persons><person id="0">Izabel Valverde</person></persons>
	<links></links>
	</event>
	
<event id="kde4-integration-platform-it-infrastructure-management">
	<start>15:20</start>
	<duration>0:30</duration>
	<room>Rm3038</room>
	<slug>kde4-integration-platform-it-infrastructure-management</slug>
	<title>KDE4 - an integration platform for IT infrastructure management</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>The KDE4 desktop is not only an workplace for office or development issues, the LAX project uses KDE as a portal for network management.The intention is both to visualize the the living IT infrastructure and enable access to the related network objects.We encourage the administrators to organize their work on task-centred desktops by heavy use of virtual desktops, activities and plasmoids.A special role take plasmoids which function both for visualization and control of network objects such as host, services or devices.These plasmoids are generated automatically from a network database, describing the network objects in detail.</abstract>
	<description/>
	<persons><person id="0">Thomas Groß</person></persons>
	<links></links>
	</event>
	
<event id="gstreamer-10">
	<start>16:20</start>
	<duration>0:45</duration>
	<room>Rm3038</room>
	<slug>gstreamer-10</slug>
	<title>GStreamer 1.0</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract>GStreamer 1.0 is scheduled for the end of the year. This talk will go over what it brings for applications and desktop environments. This talk is intended mainly for developers, but users will also be interested in knowing what it means for them in the long run.Since the 0.10.0 release in 2005, GStreamer has been used in an ever increasing range of applications, platforms, devices and use-cases. While the API/ABI stability and ever-increasing range of features it provides enabled it to spread so extensively, there were areas and use-cases that required breaking the API/ABI.During this talk Wim Taymans and Edward Hervey will explain the main changes that GStreamer 1.0 brings to applications and plugin writers and how this helps solving existing and new use-cases in a more efficient manner. They will also demonstrate some use cases that were not possible previously, or that were cumbersome to use.</abstract>
	<description/>
	<persons><person id="0">Wim Taymans and Edward Hervey</person></persons>
	<links></links>
	</event>
	</room></day>
<day index="4" date="2011-08-09">
<room name="Audimax">
<event id="gnome-foundation-and-kde-ev-agms">
	<start>09:00</start>
	<duration>9:0</duration>
	<room>Audimax</room>
	<slug>gnome-foundation-and-kde-ev-agms</slug>
	<title>GNOME Foundation and KDE e.V. AGMs</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	
<event id="island-party">
	<start>19:30</start>
	<duration>6:30</duration>
	<room>Audimax</room>
	<slug>island-party</slug>
	<title>Island Party</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	</room></day>
<day index="5" date="2011-08-10">
<room name="Audimax">
<event id="workshops-and-bofs">
	<start>09:00</start>
	<duration>11:0</duration>
	<room>Audimax</room>
	<slug>workshops-and-bofs</slug>
	<title>Workshops and BoFs</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	</room></day>
<day index="6" date="2011-08-11">
<room name="Audimax">
<event id="workshops-and-bofs-0">
	<start>09:00</start>
	<duration>11:0</duration>
	<room>Audimax</room>
	<slug>workshops-and-bofs-0</slug>
	<title>Workshops and BoFs</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	</room></day>
<day index="7" date="2011-08-12">
<room name="Audimax">
<event id="workshops-and-bofs-1">
	<start>09:00</start>
	<duration>9:0</duration>
	<room>Audimax</room>
	<slug>workshops-and-bofs-1</slug>
	<title>Workshops and BoFs</title>
	<subtitle/>
	<track></track>
	<type/>
	<language>en</language>
	<abstract></abstract>
	<description/>
	<persons><person id="0">None</person></persons>
	<links></links>
	</event>
	</room></day>
    </schedule>
    
