[static-web] Update schedule



commit 100883d16064c9b1e44ae27d31de2443d4b1de18
Author: Sam Thursfield <sam thursfield codethink co uk>
Date:   Mon Jul 10 21:00:02 2017 +0100

    Update schedule

 guadec-2017/schedule.xml |   18 +-----------------
 1 files changed, 1 insertions(+), 17 deletions(-)
---
diff --git a/guadec-2017/schedule.xml b/guadec-2017/schedule.xml
index ec4648e..5d93f7d 100644
--- a/guadec-2017/schedule.xml
+++ b/guadec-2017/schedule.xml
@@ -1,17 +1 @@
-<schedule><version>1.0</version><conference><acronym>GUADEC2017</acronym><city>Manchester, 
UK</city><day_change>00:00</day_change><days>3</days><end>2017-07-30</end><start>2017-07-28</start><timeslot_duration>00:15</timeslot_duration><title>GUADEC
 2017</title><venue>Manchester Metropolitan University</venue></conference><day date="2017-07-28" 
end="2017-07-28T19:00:00+02:00" index="1" start="2017-07-28T09:30:00+02:00"><room name="Turing - G29"><event 
guid="fb5e3081-c1f5-5657-9abb-b2ce8a0c4008" id="7"><attachments 
/><date>2017-07-28T12:15:00+02:00</date><description>Another yearly update on what Builder can do for you, 
what has been added, and how your contribution workflow can be simplified.&lt;br&gt;&lt;br&gt;Some topics 
include:&lt;br&gt;&lt;br&gt; - Making your development setup quick &amp; easy w/ Flatpak&lt;br&gt; - 
Profiling your project to find performance issues&lt;br&gt; - New build systems and integration points for 
plugin authors&lt;br&gt; - Debugging your project&
 lt;br&gt; - How to quickly start contributing to an existing 
project</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="1">Christian Hergert</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>7-state_of_the_builder</slug><start>12:15</start><subtitle /><title>State of the 
Builder</title><track /><type>talk</type></event><event guid="b34fba3d-270e-53e2-b533-5fd29e3eb0de" 
id="29"><attachments /><date>2017-07-28T11:30:00+02:00</date><description>Flatpak is an application 
distribution and runtime system that brings sandboxed linux desktop apps to the masses. 
&lt;br&gt;&lt;br&gt;This talk will give a status update of the flatpak project and what has happened in this 
year. It will also talk about new and interesting things happening in the echosystem around flatpak and where 
we're going in the future.</description><duration>00:45</duration><en
 d>12:15</end><language>eng</language><links /><logo /><persons><person id="2">Alexander 
Larsson</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>29-flatpak_status_update_and_future_plans</slug><start>11:30</start><subtitle 
/><title>Flatpak status update and future plans</title><track /><type>talk</type></event><event 
guid="fd063a2c-89c2-526a-ad12-d6d8fb2d3640" id="40"><attachments 
/><date>2017-07-28T14:45:00+02:00</date><description>In the last months Endless achieved another milestone to 
allow their users to transition to learners. A new feature has been developed that let's the user peek at the 
code that runs an application, modify it and run the new version of that application. A very challenging 
series of steps has been simplified: the app source will be located and downloaded automatically, then 
displayed in GNOME Builder and from there it can be explored, modified and run.&lt;br&gt;&lt;br&gt;Th
 e Feature spawns across three core GNOME technologies: the EOS Shell (derivative of the GNOME Shell), 
Flatpak and GNOME Builder.&lt;br&gt;&lt;br&gt;The authors aim is that this talk is suitable for a broad 
audience, hoping to find the right balance between demonstrating the user interaction, talking about design 
decisions and giving an technical overview of the components 
involved.</description><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="3">Simon Schampijer</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>40-seamless_integration_to_hack_desktop_applications</slug><start>14:45</start><subtitle 
/><title>Seamless integration to hack desktop applications</title><track /><type>talk</type></event><event 
guid="6e23ad85-3cf8-516f-804a-97cee4afb231" id="59"><attachments 
/><date>2017-07-28T16:45:00+02:00</date><description>Linux distributions have bee
 n traditionally put together from individual packages. In case of Fedora it's RPM packages. They have served 
us well, but they also have a number of shortcomings: with small individual components the testing matrix 
explodes when we have to consider different package versions, and upgrading such systems is often 
irreversable.&lt;br&gt;&lt;br&gt;In this talk I will lay out a plan how we are going to put together an 
atomic base system in Fedora Workstation with flatpaks for individual applications. I will demo the latest 
progress we've made and show a great many 
screenshots.</description><duration>00:30</duration><end>17:15</end><language>eng</language><links /><logo 
/><persons><person id="4">Kalev Lember</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>59-atomic_workstation</slug><start>16:45</start><subtitle /><title>Atomic 
Workstation</title><track /><type>talk</type></event><event guid="c853dbd8-0f8
 7-5e3b-8fe0-b2bb848bcb2a" id="70"><attachments /><date>2017-07-28T10:30:00+02:00</date><description>The Idea 
is to show our progress with the initiative [1] and show to GNOME Developers how to add a Jenkinsfile and 
tests for their projects.&lt;br&gt;&lt;br&gt;[1] 
https://wiki.gnome.org/Initiatives/ContinuousIntegrationForApps</description><duration>00:30</duration><end>11:00</end><language>eng</language><links
 /><logo /><persons><person id="5">Walter Vargas</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>70-gnome_continuous_integration_for_apps</slug><start>10:30</start><subtitle /><title>GNOME 
Continuous Integration For Apps</title><track /><type>talk</type></event><event 
guid="3a9a1c99-8dd6-5b0e-bcf7-1c0c5df63c00" id="102"><attachments 
/><date>2017-07-28T17:15:00+02:00</date><description>Lightning talks of Google Summer of Code and Outreachy 
interns</description><duration>01:00</duration><end>18:1
 5</end><language>eng</language><links /><logo /><persons><person id="6">GSoC and Outreachy 
Interns</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>102-interns_lightning_talks</slug><start>17:15</start><subtitle /><title>Interns lightning 
talks</title><track /><type>talk</type></event><event guid="436e87eb-2b8e-52c2-95d1-48763a7b07f1" 
id="104"><attachments /><date>2017-07-28T16:00:00+02:00</date><description>25 minute slots for talks and 
discussion panels to be submitted and selected by attendees on-site. This is your chance to present cutting 
edge developments or anything that did not make it into the normal schedule.
- 
-Talks will be selected and posted on the board at 15:30 on Friday and Sunday.
- 
-You can propose talks throughout the day and other attendees will add a vote to the ones that they would 
like to see. At the last break before the talk slot, the talks with the most votes will be selected and 
scheduled, so check the schedule 
board!</description><duration>00:45</duration><end>16:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>104-unconference-1</slug><start>16:00</start><subtitle /><title>Open talk #1</title><track 
/><type>talk</type></event><event guid="93bb2614-9440-5ad3-b7f4-95aa88a9629a" id="108"><attachments 
/><date>2017-07-28T14:00:00+02:00</date><description>Keynote 1: to be 
announced</description><duration>00:45</duration><end>14:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>fals
 e</optout></recording><room>Turing - G29</room><slug>108-keynote_1</slug><start>14:00</start><subtitle 
/><title>Keynote 1</title><track /><type>talk</type></event><event 
guid="41452287-6fc1-595a-a59a-12bd117de029" id="109"><attachments 
/><date>2017-07-28T10:00:00+02:00</date><description 
/><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo /><persons><person 
id="8">GUADEC Team</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>109-conference_opening</slug><start>10:00</start><subtitle /><title>Conference 
opening</title><track /><type>talk</type></event><event guid="363bdbee-1372-5ff6-9c7f-56f62d93dbb4" 
id="200"><attachments /><date>2017-07-28T09:30:00+02:00</date><description 
/><duration>00:30</duration><end>10:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Turing - G29</room><slug>20
 0-registration</slug><start>09:30</start><subtitle /><title>Registration</title><track /><type 
/></event></room><room name="Hopper - G44"><event guid="21cd49d0-45c8-5a83-8c03-8b9a785627aa" 
id="8"><attachments /><date>2017-07-28T16:45:00+02:00</date><description>Due to the amount of bugs in several 
GNU/Linux projects such as GNOME or Fedora, good volunteers and new contributors are crucial to fix them and 
make the projects better. &lt;br&gt;I emphasized the phrase good volunteers and new good contributors because 
is not only to have a positive willing to do things here.&lt;br&gt;Many other factors besides the knowledge 
of the project are fundamental, like interaction, usability, English skills, GNOME style in programming and 
following the pattern of designing.&lt;br&gt;In my local community I have encountered many pros and cons 
during almost six years of promoting the Fedora and GNOME projects in universities and social events. During 
my talk I will share those different expe
 riences and the vulnerabilities and improvements I faced in the 
way.</description><duration>00:30</duration><end>17:15</end><language>eng</language><links /><logo 
/><persons><person id="9">Julita Inca</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>8-different_ways_of_outreaching_newcomers</slug><start>16:45</start><subtitle 
/><title>Different ways of outreaching newcomers</title><track /><type>talk</type></event><event 
guid="f25ee534-b1a2-513e-b8cc-526f695d0153" id="28"><attachments 
/><date>2017-07-28T14:45:00+02:00</date><description>We find ourselves in a world where there are an 
increasing number of ecosystems of computing devices and appliances that (try to) work seamlessly together to 
allow people to listen and watch what they want, when, where and how they want to in their homes -- on their 
TVs, tablets, through multi-room speakers, and so on.&lt;br&gt;&lt;br&gt;We've made some headway in ena
 bling these in GNOME -- via the Sharing panel, and the massive amount of plumbing underneath it -- but there 
is a huge gap between what we have, and where I think we need to be.&lt;br&gt;&lt;br&gt;So this talk is in 
three parts:&lt;br&gt;&lt;br&gt;1. Where we are -- both in terms of the user experience (Sharing) and the 
software stack (Rygel, GUPnP, PulseAudio, GStreamer)&lt;br&gt;&lt;br&gt;2. Where I'd like us to be -- what 
kinds of connectivity do we want to enable? Is it possible to do this with commodity 
hardware?&lt;br&gt;&lt;br&gt;and&lt;br&gt;&lt;br&gt;3. How we can get there -- existing pieces to build on 
top of, missing pieces of the stack to add, and tying it together in a way users can 
"get"</description><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="10">Arun Raghavan</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - G44</room><slug>28-dreaming_of_a_
 better_home_media_experience</slug><start>14:45</start><subtitle /><title>Dreaming of a better home media 
experience</title><track /><type>talk</type></event><event guid="1b0f7a57-4f8e-5897-855a-a1e0fe4a8de5" 
id="43"><attachments /><date>2017-07-28T11:30:00+02:00</date><description>The Endless OS has always been a 
bit different from regular Linux distros in that it offers an immutable system managed by OSTree and thus has 
always had an alternative way of installing applications.&lt;br&gt;It is also one of the first operating 
systems using Flatpak as the main way of managing applications by the user.&lt;br&gt;&lt;br&gt;In this talk I 
will introduce the evolution of the application story in the Endless OS, focusing on the adoption of Flatpak 
applications and the changes to GNOME Software to integrate it better with the EOS desktop and to improve the 
UX for Endless’ users.&lt;br&gt;&lt;br&gt;I will also talk about the problems of shipping apps in a world of 
very unreliable or
  nonexistent internet connection and the solutions we implemented to give the best experiences to our users. 
This talk should be interesting not only for those who want to know more about application management in EOS 
but also for those who want to know more about how GNOME Software works and the and possibilities it offers 
with its plugins 
system.</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="11">Joaquim Rocha</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>43-limited_connectivity_endless_apps</slug><start>11:30</start><subtitle /><title>Limited 
connectivity, Endless apps!</title><track /><type>talk</type></event><event 
guid="bb353abf-cc6c-515a-ae06-d5bfffcae654" id="48"><attachments 
/><date>2017-07-28T12:15:00+02:00</date><description>The newcomer guide is made for newcomers to get started 
with GNOME development. Bastian Ilso a
 nd Carlos Soriano will tell the story of how the newcomer experience changed in the past year and how that 
had a big impact on newcomer contributions, developer workflow and the image of the GNOME 
community.&lt;br&gt;At the end of the talk we will have an open debate about what the next steps should be to 
improve the experience. What do you think newcomers are looking for? What should the ideal workflow 
be?</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="12">Carlos Soriano</person><person id="13">Bastian 
Ilsø</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>48-newcomer_genesis_evolution</slug><start>12:15</start><subtitle /><title>Newcomer Genesis 
Evolution</title><track /><type>talk</type></event><event guid="607c135b-31e8-5b66-ab0e-59f517e81290" 
id="72"><attachments /><date>2017-07-28T10:30:00+02:00</date><description>This year, 
 GNOME turns 20. Over the course of its history, the project has pioneered new ways of working and has set 
out a powerful mission for itself: from championing usability and accessibility, to establishing the six 
month release cycle, GNOME has been at the forefront of Free Software development. However, there are also 
risks for a project that has been running this long: collective knowledge can be forgotten, and it is easy to 
lose touch with the beliefs that give a project purpose.&lt;br&gt;&lt;br&gt;In this talk, I'll ask the 
question: what is it that defines the GNOME project? In attempting to provide my own answer, I'll describe 
the principles that I think make GNOME so important. I'll also recount stories from GNOME's history, and in 
so doing make a case for what constitutes the project's folklore. Finally, I'll ask the question: how do we 
ensure that, as GNOME looks to the future, the project continues to nurture these 
traditions?</description><duration>00:30</duration><e
 nd>11:00</end><language>eng</language><links /><logo /><persons><person id="14">Allan 
Day</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>72-the_gnome_way</slug><start>10:30</start><subtitle /><title>The GNOME Way</title><track 
/><type>talk</type></event><event guid="01e8a7f0-684c-55b0-8b1c-930962a49729" id="105"><attachments 
/><date>2017-07-28T16:00:00+02:00</date><description>25 minute slots for talks and discussion panels to be 
submitted and selected by attendees on-site. This is your chance to present cutting edge developments or 
anything that did not make it into the normal schedule.
- 
-Talks will be selected and posted on the board at 16:00 on Friday and Sunday.
- 
-You can propose talks throughout the day and other attendees will add a vote to the ones that they would 
like to see. At the last break before the talk slot, the talks with the most votes will be selected and 
scheduled, so check the schedule 
board!</description><duration>00:45</duration><end>16:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>105-unconference-2</slug><start>16:00</start><subtitle /><title>Open talk #2</title><track 
/><type>talk</type></event></room><room name="Elsewhere"><event guid="fd199473-c615-5f85-9975-575ebe87a07a" 
id="201"><attachments /><date>2017-07-28T11:00:00+02:00</date><description 
/><duration>00:30</duration><end>11:30</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>201-break<
 /slug><start>11:00</start><subtitle /><title>Break</title><track /><type /></event><event 
guid="d6b06dee-7e6c-5f25-87fb-3bc31998f997" id="202"><attachments 
/><date>2017-07-28T13:00:00+02:00</date><description 
/><duration>01:00</duration><end>14:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>202-lunch</slug><start>13:00</start><subtitle
 /><title>Lunch</title><track /><type /></event><event guid="b8d33ab3-733c-5dd3-9921-24af014cac4f" 
id="203"><attachments /><date>2017-07-28T15:30:00+02:00</date><description 
/><duration>00:30</duration><end>16:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>203-break</slug><start>15:30</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="abe4e817-53ef-5220-9c78-b15253d0ebc1" 
id="204"><attachments /><da
 te>2017-07-28T18:15:00+02:00</date><description 
/><duration>00:45</duration><end>19:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>204-venue_closes</slug><start>18:15</start><subtitle
 /><title>Venue closes</title><track /><type /></event></room></day><day date="2017-07-29" 
end="2017-07-29T19:00:00+02:00" index="2" start="2017-07-29T09:30:00+02:00"><room name="Turing - G29"><event 
guid="d4776b28-450d-5c72-bbcd-16b813808106" id="5"><attachments 
/><date>2017-07-29T11:30:00+02:00</date><description>I have been working on replacing the C code in librsvg, 
GNOME's SVG rendering library, with Rust.  Rust is one of the few high-level languages that actually 
generates object code, which in turn can be linked into compiled C code.&lt;br&gt;&lt;br&gt;What started as 
an experiment in replacing gnarly C code with clean Rust code, eventually turned into a full porting effort.  
Li
 brsvg's public API/ABI remain the same as before, and only the internals have Rust code in them.  The result 
is a much safer library with trustworthy code.  Not only is the code safe by Rust's nature; it now has a 
bunch of unit tests that would have been very cumbersome to write before.&lt;br&gt;&lt;br&gt;This talk will 
explore:&lt;br&gt;&lt;br&gt;* Brief intro to Rust's benefits and philosophy.&lt;br&gt;&lt;br&gt;* Tips for 
replacing C code with Rust.&lt;br&gt;&lt;br&gt;* Refactorings that are needed in C to replace it with 
Rust.&lt;br&gt;&lt;br&gt;* Refactorings that are possible once Rust is in place.&lt;br&gt;&lt;br&gt;* Going 
from a codebase with zero unit tests to one that has a bunch of tests!&lt;br&gt;&lt;br&gt;* Having a mixture 
of C and Rust code for certain implementation patterns.&lt;br&gt;&lt;br&gt;* Replacing scary C parsers with 
safe Rust parsers.&lt;br&gt;&lt;br&gt;* How Rust clarified my thinking.&lt;br&gt;&lt;br&gt;* Can distros ship 
this?&lt;br&gt;&lt;br&g
 t;* Should we replace GNOME library code with Rust, in 
general?</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="15">Federico Mena Quintero</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>5-replacing_c_library_code_with_rust_what_i_learned</slug><start>11:30</start><subtitle 
/><title>Replacing C library code with Rust: what I learned</title><track /><type>talk</type></event><event 
guid="3e32c3e2-6bdb-5afa-be55-9b15f35398c8" id="14"><attachments 
/><date>2017-07-29T14:45:00+02:00</date><description>In this talk, I'll have a look at some of the challenges 
that GNOME faces at the moment, a brief look into the future, and how we can meet those head on and 
thrive!</description><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="16">Neil McGovern</person></persons><recording><license>CC B
 Y-SA 4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>14-gnome_to_2020_and_beyond</slug><start>14:45</start><subtitle /><title>GNOME to 2020 and 
beyond</title><track /><type>talk</type></event><event guid="6cf0e9df-438b-5b7d-907b-50f4b6f98237" 
id="15"><attachments /><date>2017-07-29T12:15:00+02:00</date><description>Since 2012, a service in the GNOME 
infrastructure has been constantly building GNOME modules, committing the result to Ostree, and running 
automated tests on the whole OS. From a single Git commit to a full blown virtual machine in a matter of 
minutes. This service is called GNOME Continuous, our own continuous integration and delivery 
pipeline.&lt;br&gt;&lt;br&gt;Continuous has been the major driver to improve the quality of the whole GNOME 
project: for developers, by building their work; for designers, by providing a bootable VM to perform design 
iteration and QA; to newcomers, by ensuring that tools like jhbuild would be more relia
 ble; to distributors and OSVs, who could ensure their products would be based on a reliable set of 
components.&lt;br&gt;&lt;br&gt;In this presentation we will talk about how Continuous came to be, thanks to 
the work of Colin Walters; how it works; what are the goals of a CI/CD pipeline like Continuous; and where do 
we go from here.</description><duration>00:45</duration><end>13:00</end><language>eng</language><links 
/><logo /><persons><person id="17">Emmanuele Bassi</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>15-continuous_past_present_and_future</slug><start>12:15</start><subtitle 
/><title>Continuous: Past, Present, and Future</title><track /><type>talk</type></event><event 
guid="bdff2d9f-cbd4-5bf3-8d87-f29e05f6aa61" id="50"><attachments 
/><date>2017-07-29T10:00:00+02:00</date><description>With the new contribution workflow enabled by GNOME 
Builder, it is now trivially easy for newcomers to clo
 ne a project, build it, and hack on it.&lt;br&gt;&lt;br&gt;This talk is about how you can use Meson's 
subprojects and wrapdb to have a very similar experience on any operating system with just Meson and 
git.&lt;br&gt;&lt;br&gt;At the same time, this feature is also distro-friendly since all this machinery can 
be turned off with a single option, telling Meson to only use dependencies provided by the 
system.</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="18">Nirbheek Chauhan</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>50-building_your_gnome_app_anywhere_with_meson</slug><start>10:00</start><subtitle 
/><title>Building your GNOME app anywhere with Meson</title><track /><type>talk</type></event><event 
guid="5d769bed-f310-5afd-a9d5-2b7c1556d5a0" id="60"><attachments 
/><date>2017-07-29T14:00:00+02:00</date><description>Happy Birthday
  GNOME! Ever wonder why the project is the way it is? The GNOME project has had a long and exciting ride to 
this point. I'll go through some of the early moments of the project that led us to the desktop that we know 
and love today.</description><duration>00:45</duration><end>14:45</end><language>eng</language><links /><logo 
/><persons><person id="19">Jonathan Blandford</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>60-the_history_of_gnome</slug><start>14:00</start><subtitle /><title>The History of 
GNOME</title><track /><type>talk</type></event><event guid="9ec3f1f0-0feb-548e-833e-5c38721764c0" 
id="63"><attachments /><date>2017-07-29T10:30:00+02:00</date><description>Shell present and near 
future.</description><duration>00:30</duration><end>11:00</end><language>eng</language><links /><logo 
/><persons><person id="20">Carlos Garnacho</person><person id="21">Florian Müllner</person></persons><recordi
 ng><license>CC BY-SA 4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>63-muttergnomeshell_state_of_the_union</slug><start>10:30</start><subtitle 
/><title>Mutter/gnome-shell state of the union</title><track /><type>talk</type></event><event 
guid="cae033cb-4acd-5194-895c-1cd1dfb66e7c" id="100"><attachments 
/><date>2017-07-29T16:00:00+02:00</date><description>The annual general meeting of the GNOME Foundation: team 
reports</description><duration>01:00</duration><end>17:00</end><language>eng</language><links /><logo 
/><persons><person id="22">GNOME Board</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>100-gnome_foundation_agm_part_1</slug><start>16:00</start><subtitle /><title>GNOME Foundation 
AGM (part 1)</title><track /><type>meeting</type></event><event guid="e92b8310-2623-54c4-be20-ce7391564083" 
id="101"><attachments /><date>2017-07-29T17:15:00+02:00</date><description>T
 he annual general meeting of the GNOME Foundation: Q&amp;A with the 
board.</description><duration>01:00</duration><end>18:15</end><language>eng</language><links /><logo 
/><persons><person id="22">GNOME Board</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>101-gnome_foundation_agm_part_2</slug><start>17:15</start><subtitle /><title>GNOME Foundation 
AGM (part 2)</title><track /><type>meeting</type></event><event guid="05eb0f22-c9af-5862-aae8-4bb34772e1e0" 
id="209"><attachments /><date>2017-07-29T17:00:00+02:00</date><description 
/><duration>00:15</duration><end>17:15</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Turing - 
G29</room><slug>209-group_photo</slug><start>17:00</start><subtitle /><title>Group photo</title><track 
/><type /></event></room><room name="Hopper - G44"><event guid="526ab1a5-9783-528c-9208-6ab1c1
 d7a07d" id="31"><attachments /><date>2017-07-29T11:30:00+02:00</date><description>Matrix.org is a relatively 
new open standard for decentralised realtime communication - providing an open global network (including 
end-to-end encryption) that links together communication silos such as Slack, IRC, Gitter, Telegram, XMPP 
etc.  Matrix has gained some popularity in the GNOME developer community since GIMPNet was bridged into the 
wider Matrix ecosystem in March 
(https://mail.gnome.org/archives/desktop-devel-list/2017-March/msg00033.html), and meanwhile Matrix's goals 
of entirely open source and democratised communication are quite aligned with the ethos of the GNOME 
project.&lt;br&gt;&lt;br&gt;This talk will be a formal introduction and demonstration of the Matrix 
ecosystem, its APIs and spec, its clients/servers/bridges/bots, its end-to-end encryption, its goals and its 
current status, as given by the project 
lead.</description><duration>00:45</duration><end>12:15</end><language>
 eng</language><links /><logo /><persons><person id="23">Matthew 
Hodgson</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>31-decentralised_open_communication_with_matrixorg</slug><start>11:30</start><subtitle 
/><title>Decentralised open communication with Matrix.org</title><track /><type>talk</type></event><event 
guid="c27e346f-5ef5-5845-aad6-f741a15a36a9" id="41"><attachments 
/><date>2017-07-29T10:00:00+02:00</date><description>Emeus is a constraint-based layout manager and container 
widget for GTK+.&lt;br&gt;&lt;br&gt;Emeus allows programmers and designers to describe the UI in a way that 
can be more natural from the UI building perspective, more expressive and efficient than stacking boxes 
inside boxes.&lt;br&gt;&lt;br&gt;At Endless we have been developing Emeus to provide richer visual 
experiences in our apps and better tools for engineers and designers to work 
together.&lt;br&gt;&lt;br&gt;Here's 
 what you'll see in this talk:&lt;br&gt;&lt;br&gt;* A new way of creating rich layouts for your GTK+ 
app.&lt;br&gt;* A display of layouts and widgets that we created at Endless.&lt;br&gt;* How it brings 
programmers and designers 
together.</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="24">Martin Abente Lahaye</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>41-fantastic_layouts_and_where_to_find_them</slug><start>10:00</start><subtitle 
/><title>Fantastic Layouts And Where To Find Them</title><track /><type>talk</type></event><event 
guid="5068c0d6-7857-510f-9a2b-373c560b519b" id="62"><attachments 
/><date>2017-07-29T12:15:00+02:00</date><description>Tracker has become a foundation for many core apps. It 
has provided a common metadata store for applications to share, making all of the data a giant interconnected 
graph.&lt;br&gt;&lt;br&
 gt;However, times change. There's now initiatives like flatpak that make this interconnected graph more 
accessory, or even not desirable. This talk will cover the plans to make Tracker a good citizen in the 
sandboxing world, and what this means for 
applications.</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="20">Carlos Garnacho</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>62-tracker__present_and_future</slug><start>12:15</start><subtitle /><title>Tracker - present 
and future</title><track /><type>talk</type></event><event guid="eaaf9612-272e-59df-81c0-406d441e9376" 
id="65"><attachments /><date>2017-07-29T10:30:00+02:00</date><description>Come and hear about the latest 
developments in LibreOffice and see how we continue to make the Linux Desktop and Free Software ever more 
useful for business users.&lt;br&gt;&lt;br&gt;Get an upd
 ate on the awesome work from Caolan polishing our gtk3 and wayland support. Checkout the latest new features 
in the LibreOfficeKit API - ripe for deeper use in GNOME Documents - and the potential for testing out 
innovative new GNOME editors here. See LibreOffice Online - inspired by gtk+/broadway - and what it can 
do&lt;br&gt;for you.&lt;br&gt;&lt;br&gt;Also catch random thoughts and demos on whatever seems 
apposite.</description><duration>00:30</duration><end>11:00</end><language>eng</language><links /><logo 
/><persons><person id="25">Michael Meeks</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>65-libreoffice_and_gnome</slug><start>10:30</start><subtitle /><title>LibreOffice and 
GNOME</title><track /><type>talk</type></event></room><room name="Elsewhere"><event 
guid="a74eebdc-899a-579d-a84f-ba8d18667403" id="205"><attachments 
/><date>2017-07-29T09:30:00+02:00</date><description /><duration>00:30</
 duration><end>10:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>205-venue_opens</slug><start>09:30</start><subtitle
 /><title>Venue opens</title><track /><type /></event><event guid="4049ad77-c1eb-5e0a-b4c2-ca3c0de54f10" 
id="206"><attachments /><date>2017-07-29T11:00:00+02:00</date><description 
/><duration>00:30</duration><end>11:30</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>206-break</slug><start>11:00</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="cdffc551-86dc-5f92-8d61-efe3fc4276fa" 
id="207"><attachments /><date>2017-07-29T13:00:00+02:00</date><description 
/><duration>01:00</duration><end>14:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><
 room>Elsewhere</room><slug>207-lunch</slug><start>13:00</start><subtitle /><title>Lunch</title><track 
/><type /></event><event guid="53f0a9ac-99b8-5eb9-9fa3-3e914a2a89c7" id="208"><attachments 
/><date>2017-07-29T15:30:00+02:00</date><description 
/><duration>00:30</duration><end>16:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>208-break</slug><start>15:30</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="0e481de3-2119-5f57-8d28-87c17229c2dd" 
id="210"><attachments /><date>2017-07-29T18:15:00+02:00</date><description 
/><duration>00:45</duration><end>19:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>210-venue_closes</slug><start>18:15</start><subtitle
 /><title>Venue closes</title><track /><type /></event></room></day><day date="201
 7-07-30" end="2017-07-30T19:00:00+02:00" index="3" start="2017-07-30T09:30:00+02:00"><room name="Turing - 
G29"><event guid="24652dae-8d39-5a73-a8e5-aaddd983e107" id="22"><attachments 
/><date>2017-07-30T10:30:00+02:00</date><description>Various GNOME modules have been building on Coverity 
Scan for the last year. Has it been finding legitimate bugs, or ones which people are almost never going to 
hit? What’s the best way to use static analysis? Why should developers care?&lt;br&gt;&lt;br&gt;Warning: This 
talk will contain Jenkins and 
graphs.</description><duration>00:30</duration><end>11:00</end><language>eng</language><links /><logo 
/><persons><person id="26">Philip Withnall</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>22-whats_coverity_static_analysis_ever_done_for_us</slug><start>10:30</start><subtitle 
/><title>What’s Coverity static analysis ever done for us?</title><track /><type>talk</type
</event><event guid="c3cc55a3-5b08-5358-99f1-666bd7c54501" id="23"><attachments 
/><date>2017-07-30T11:30:00+02:00</date><description>Cooking and recipes is not a new topic for the GNOME 
community.&lt;br&gt;All the way back to 2007, the idea of a GNOME cook book was already around 
(https://wiki.gnome.org/GnomeCookbook). For one reason or another, we never quite got there - but the idea 
has stuck around, and after Guadec last year, the two of us got together to finally make GNOME recipes a 
reality.&lt;br&gt;&lt;br&gt;Our talk will cover the original design goals and the evolution of the design 
from paper mock-ups and ideas, to refining a raw prototype and to the complete application that we have to 
today. We will touch on the interaction between design and development and how you can be successful in 
this even when you have to bridge a 7 hour time differential.&lt;br&gt;&lt;br&gt;We will take a look ahead 
at whats coming in 3.26, and how the original design goals are evolving
  and expanding as we build out the application.&lt;br&gt; &lt;br&gt;On the technical side, we will explore 
some of the challenges and lessons learned during the development of recipes, and we will explain how writing 
this application was useful for developing and refining new technologies such as sandboxes, portals and new 
build systems. There may be an aside about portability.&lt;br&gt;&lt;br&gt;Of course, there will be a demo of 
recipes.</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="27">Matthias Clasen</person><person id="28">Emel Elvin 
Yildiz</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>23-recipes__lessons_learned_from_creating_a_new_app</slug><start>11:30</start><subtitle 
/><title>Recipes - Lessons learned from creating a new app</title><track /><type>talk</type></event><event 
guid="c6ee3b58-3a6e-5330-9d4f-9739b72a2c95" id
 ="26"><attachments /><date>2017-07-30T10:00:00+02:00</date><description>GNOME 3.24 brought a lot of 
improvements in GJS, the Javascript language bindings for GNOME, that power GNOME Shell, Polari, GNOME 
Documents, and many other apps.&lt;br&gt;&lt;br&gt;We moved to a more modern version of the Javascript 
engine. We gained support for a lot of cool language features that take some of the rough edges off of 
Javascript's shady reputation. For GNOME 3.26 we'll continue this modernizing process, and start improving 
the developer experience in GJS as well.&lt;br&gt;&lt;br&gt;Here's what you'll see in this talk:&lt;br&gt;- 
Cool stuff you never knew you could do in GJS!&lt;br&gt;- How to modernize your app with ES6 
features!&lt;br&gt;- Debugging, documentation, and other developer tools!&lt;br&gt;- Sneak peek of what's to 
come in 3.26 and how you can 
help!</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="29">Philip 
 Chimento</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>26-modern_javascript_in_gnome</slug><start>10:00</start><subtitle /><title>Modern Javascript 
in GNOME</title><track /><type>talk</type></event><event guid="5b5c389e-170b-5bcf-9e4d-74f8ff49c677" 
id="38"><attachments /><date>2017-07-30T12:15:00+02:00</date><description>In this talk, I will start by 
outlining our motivations behind creating this new meta build system, based both on the emergence of new 
distribution models and also lessons learned from existing meta build system 
implementations.&lt;br&gt;&lt;br&gt;Then we will briefly explore the abstract and rather simple design of 
BuildStream: A format and engine for the modeling and processing of pipelines composed of elements which 
perform mutations on filesystem data from inside an isolated sandbox environment.&lt;br&gt;&lt;br&gt;Finally 
we will explore the various use cases of building GNOME
  modules and outline how we intend to apply this new technology to improve the GNOME Developer experience in 
various ways.</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="30">Tristan Van Berkom</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>38-gnome_build_strategies_and_buildstream</slug><start>12:15</start><subtitle /><title>GNOME 
Build Strategies and BuildStream</title><track /><type>talk</type></event><event 
guid="6d2e7e92-c56f-5358-be16-4c22e07f2daf" id="44"><attachments 
/><date>2017-07-30T16:45:00+02:00</date><description>In this talk we will go trough most of the not so known 
features of Glade and introduce a refreshed UI which will improve the regular design workflow by replacing 
the good old tool palette.&lt;br&gt;&lt;br&gt;The walk trough will include:&lt;br&gt; - creating custom 
composite widgets&lt;br&gt; - a catalog to
  add support for them&lt;br&gt; - JavaScript objects in Glade&lt;br&gt;&lt;br&gt;As a bonus, I might, just 
might, show my crazy idea to rewrite Glade from scratch for Gtk4, just so that we can discuss it over some 
beers!</description><duration>00:30</duration><end>17:15</end><language>eng</language><links /><logo 
/><persons><person id="31">Juan Pablo Ugarte</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>44-how_to_get_better_mileage_out_of_glade</slug><start>16:45</start><subtitle /><title>How to 
get better mileage out of Glade</title><track /><type>talk</type></event><event 
guid="cd873c69-aae6-5edd-b537-cad7fbed6d67" id="52"><attachments 
/><date>2017-07-30T14:00:00+02:00</date><description>I am a co-founder and technical lead of Ubuntu GNOME, 
with our goal to bring a pure GNOME experience to Ubuntu some might wonder where that might be heading given 
the recently annouced decision for Canonical to d
 rop Unity and switch to GNOME. This will bring a new set of challenges for the Ubuntu GNOME team, while our 
distro will not likely exist as a seperate entity and we will merge development resources with the Canonical 
desktop team, we will remain as a community team to avoid the possible distinction between community and 
Canonical may getting blurred.&lt;br&gt;&lt;br&gt;I will open my talk with a brief history of the Ubuntu 
GNOME project, why we started it and what our goals were. We started the project with goal of bring pure 
gnome-shell to Ubuntu. At the time GNOME 3 was incredibly broken on both Ubuntu and Debian to the the point 
of being unusable. We managed to get things into really good shape over the years but there have been 
challenges, mostly relating to the co-existence with Unity, and having to maintain large patch delta’s to 
work with Unity also.&lt;br&gt;&lt;br&gt;Then comes the exciting stuff what is the future of GNOME on Ubuntu, 
where does the Ubuntu GNOME t
 eam stand in the future? Canonical are already showing some resistance towards core components of the GNOME 
stack, for example things like tracker and gdm. What part will Ubuntu GNOME play in pushing our visions into 
the core Ubuntu Future GNOME desktop? I can’t be incredibly specific on this at this point we are still in 
discussions with Canonical teams at this stage, but all should be clear by GUADEC. This should fill the bulk 
of my talk, I see exciting oppurtunities ahead and some more challenges going forward before we can get 
Canonical aligned with GNOME. I will discuss these in detail during my 
talk.</description><duration>00:45</duration><end>14:45</end><language>eng</language><links /><logo 
/><persons><person id="32">Tim Lunn</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>52-bringing_gnome_home_to_ubuntu</slug><start>14:00</start><subtitle /><title>Bringing GNOME 
home to Ubuntu</title><tr
 ack /><type>talk</type></event><event guid="343b5c9d-c4fa-5aa4-8563-1e271c788435" id="103"><attachments 
/><date>2017-07-30T17:15:00+02:00</date><description>Fast-paced and focused talks on any and all subjects. 
You will be able to sign up for these on the day! Talks will be accepted on a first come, first serve basis 
so turn up early if you want to make it on to the schedule. All talks will be subject to a strict time limit 
of 5 minutes on stage (including setup). Slides are welcome, but not 
compulsory.</description><duration>00:45</duration><end>18:00</end><language>eng</language><links /><logo 
/><persons /><recording><license>CC BY-SA 4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>103-lightning_talks</slug><start>17:15</start><subtitle /><title>Lightning 
talks</title><track /><type>talk</type></event><event guid="bbfbd734-10aa-5f7a-8bb3-4255d7949690" 
id="106"><attachments /><date>2017-07-30T16:00:00+02:00</date><description>25 minute slots fo
 r talks and discussion panels to be submitted and selected by attendees on-site. This is your chance to 
present cutting edge developments or anything that did not make it into the normal schedule.
- 
-Talks will be selected and posted on the board at 16:00 on Friday and Sunday.
- 
-You can propose talks throughout the day and other attendees will add a vote to the ones that they would 
like to see. At the last break before the talk slot, the talks with the most votes will be selected and 
scheduled, so check the schedule 
board!</description><duration>00:45</duration><end>16:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>106-unconference-3</slug><start>16:00</start><subtitle /><title>Open talk #3</title><track 
/><type>talk</type></event><event guid="9482c5aa-b3ef-5cc5-bfdc-ffef6d4b7045" id="110"><attachments 
/><date>2017-07-30T18:00:00+02:00</date><description 
/><duration>00:15</duration><end>18:15</end><language>eng</language><links /><logo /><persons><person 
id="8">GUADEC Team</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - G29</
 room><slug>110-conference_closing</slug><start>18:00</start><subtitle /><title>Conference 
closing</title><track /><type>talk</type></event><event guid="da0daac0-3475-583a-9ffa-7e0ed82aa044" 
id="214"><attachments /><date>2017-07-30T14:45:00+02:00</date><description 
/><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Turing - 
G29</room><slug>214-tbd</slug><start>14:45</start><subtitle /><title>TBD</title><track /><type 
/></event></room><room name="Hopper - G44"><event guid="8e9c9810-06ed-5b96-af10-68729ba32773" 
id="1"><attachments /><date>2017-07-30T14:45:00+02:00</date><description>Containerised Application 
technologies like AppImage, Snappy and Flatpak promise a brave new world for Linux applications, free from 
the worries of shared libraries and dependency issues. Just one problem, this is a road long travelled 
before, such as in the application dark ages
  of Win32 applications and DLLs. And it worked out so wonderfully there... Do we risk a future where, like 
the resurrected dinosaurs of Jurassic Park, this family of applications will break their containment and 
start eating our users? This session will try to present a balanced argument about the situation, frankly 
discussing the benefits promised by these technologies, but highlighting the very real issues and risks their 
widespread adoption could, and in some cases are, already bringing to the table.&lt;br&gt;&lt;br&gt;The talk 
with cover the promised benefits of application containers, such as AppImage, Snappy and Flatpak. It will 
detail the empowerment of developers who use the technologies, the ability for upstream projects to have a 
much closer role in delivering their software, and the benefits that brings to both the upstream projects and 
their users. But as a counter to those benefits, the session will detail some of the risks and 
responsibilities that come with th
 at technology. The complexities of library integration, the risk of introducing new forms of dependency 
issues, and the transference of responsibility for those issues, plus security, away from the current 
Distributions delivering upstream projects towards those upstream projects directly. As a conclusion, the 
session will present some suggestions to upstream projects adopting these technologies to start them down the 
road of accepting those responsibilities directly, or working more closely with existing Distribution 
projects to share the burdens these technologies now 
provide.</description><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="33">Richard Brown</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>1-resurrecting_dinosaurs_what_can_possibly_go_wrong</slug><start>14:45</start><subtitle 
/><title>Resurrecting dinosaurs, what can possibly go w
 rong</title><track /><type>talk</type></event><event guid="23c23699-fdc5-5e08-aa98-ddc1aac45dae" 
id="6"><attachments /><date>2017-07-30T10:00:00+02:00</date><description>After spending considerable amount 
of time prototyping designs for GNOME, over and over again I've met with resistance to transitions as being a 
"waste of CPU/GPU time" and not enjoying a wide acceptance among developers.&lt;br&gt;&lt;br&gt;I'll present 
my case as to why transitions are helpful conveying meaning and spatial 
awareness.</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="34">Jakub Steiner</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>6-the_inbetweens__why_transitions_matter</slug><start>10:00</start><subtitle /><title>The 
Inbetweens — why transitions matter.</title><track /><type>talk</type></event><event 
guid="dc201b85-f588-533c-b7c2-4498bc53e9dc" i
 d="11"><attachments /><date>2017-07-30T14:00:00+02:00</date><description>Flatpak is a tool providing new and 
easy way how to distribute desktop applications. While it is pretty well supported in Gnome, we in KDE have 
been trying to catch up and offer same experience. In this talk, Jan Grulich will share with you what KDE has 
been lately up to and what has been accomplished during last year.  &lt;br&gt;&lt;br&gt; Martin Bříza will 
also cover how we advanced with how well are Qt applications integrated into the overall GNOME experience.  
&lt;br&gt;&lt;br&gt; Topics covered will include the state of the Adwaita and Highcontrast themes, new 
QGnomePlatform (abstract platform theme backend for GNOME) features and Wayland 
support.</description><duration>00:45</duration><end>14:45</end><language>eng</language><links /><logo 
/><persons><person id="35">Jan Grulich</person><person id="36">Martin 
Bříza</person></persons><recording><license>CC BY-SA 4.0</license><optout>false</optout
</recording><room>Hopper - 
G44</room><slug>11-flatpak_and_kde_and_the_state_of_qt_integration_in_gnome</slug><start>14:00</start><subtitle
/><title>Flatpak and KDE, and the state of Qt integration in GNOME</title><track 
/><type>talk</type></event><event guid="adbb36c1-257e-5bc9-81a8-9cd5077e031b" id="16"><attachments 
/><date>2017-07-30T10:30:00+02:00</date><description>Animations are the future of interface design. They 
enable developers to make interfaces more understandable by offloading processes from the user's brain to 
the screen. However, in many cases animations are simply added as transitions between independently 
designed screens. This can result in animations contradicting each other spatially. I co-wrote an article 
about why this is a problem [1] and outlined a solution: Designing semantic components which change over 
time, and then using these to compose interfaces.&lt;br&gt;&lt;br&gt;Even though the industry seems to 
largely agree that this is the way forward, 
 there are very few interfaces implementing these ideas. I believe the main reason for this is that the 
current generation of layout technologies is built for static layouts with strict hierarchies. This makes it 
prohibitively difficult to build interfaces where components move fluidly between different 
states.&lt;br&gt;&lt;br&gt;I will show some interface prototypes I built and explain why they were so 
difficult to implement with current technology. Finally, I will outline some ideas for a better layout API, 
to make building awesome, fluid interfaces from the future more feasible.&lt;br&gt;&lt;br&gt;[1] 
https://alistapart.com/article/motion-with-meaning-semantic-animation-in-interface-design</description><duration>00:30</duration><end>11:00</end><language>eng</language><links
 /><logo /><persons><person id="37">Tobias Bernard</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - G44</room><slug>16-building_interfaces_from
 _the_future</slug><start>10:30</start><subtitle /><title>Building interfaces from the future</title><track 
/><type>talk</type></event><event guid="b5162e55-01c1-5dd8-8f17-b78ff5e85d25" id="20"><attachments 
/><date>2017-07-30T12:15:00+02:00</date><description>I'm Jonathan Kang, a GNOME hacker from China. I 
currently maintain Logs, and contribute to other projects. My copresenter is Chingkai Chu who is a QA 
engineer at SUSE and he has been        focused on Gnome testing and openQA for two 
years.&lt;br&gt;&lt;br&gt;We'll talk about how currently GNOME applications are tested using different 
technologies. And then introduce the approach of using openQA to test GNOME 
applications.&lt;br&gt;&lt;br&gt;Our talk can be divided into three parts:&lt;br&gt;1. Why should we do 
quality assurance&lt;br&gt;    - We'll talk about this from a GNOME hacker and a GNOME QA tester's 
view.&lt;br&gt;&lt;br&gt;2. The current technologies used in GNOME projects for testing&lt;br&gt;    - It's 
mainly
  about the methods GNOME community currently uses to do the testing, like dogtail, glib unit test, gnome 
continuous and etc.&lt;br&gt;&lt;br&gt;3. Introduce what I did with openQA for testing my maintained project 
and discuss the possibility of using it for other projects&lt;br&gt;    - openQA features overview and how we 
use it in SLE Desktop team&lt;br&gt;    - Gnome automation testing approach using 
openQA</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="38">Jonathan Kang</person><person id="39">Chingkai 
Chu</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>20-robustness_of_gnome</slug><start>12:15</start><subtitle /><title>Robustness of 
GNOME</title><track /><type>talk</type></event><event guid="8db7a86f-7cdc-5710-a270-b84b04f81984" 
id="64"><attachments /><date>2017-07-30T16:45:00+02:00</date><description>GTK+4 is getting more gen
 eric and simple, and less X11-centric. This talk will cover what this means for GtkWidget development, and 
the main differences with 
GTK+3.</description><duration>00:30</duration><end>17:15</end><language>eng</language><links /><logo 
/><persons><person id="20">Carlos Garnacho</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>64-ding_dong_gdkwindow_is_dead</slug><start>16:45</start><subtitle /><title>Ding dong, 
GdkWindow is dead</title><track /><type>talk</type></event><event guid="3a961a4e-1d46-597f-b7b1-397ad89b325a" 
id="68"><attachments /><date>2017-07-30T11:30:00+02:00</date><description>The move towards Wayland and 
container-isolated application deployment brings a range of security benefits. But broad isolation isn't 
enough - we still need fine-grained control over access to resources, otherwise it's still practical for a 
single compromised application to leak significant quantities of personal d
 ata.&lt;br&gt;&lt;br&gt;This presentation will examine existing application isolation mechanisms and 
identify cases where they fall short. It will then go on to cover existing kernel technologies that allow us 
to provide even stronger restrictions and control, and how it's possible for us to build environments that 
provide high levels of security without forcing users to give up the freedom to run whatever software they 
want.</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="40">Matthew Garrett</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>68-building_a_secure_desktop_with_gnome_technologies</slug><start>11:30</start><subtitle 
/><title>Building a secure desktop with GNOME technologies</title><track /><type>talk</type></event><event 
guid="46647784-a003-5e87-9fcf-881d1c42efb6" id="107"><attachments /><date>2017-07-30T16:00:00+02:00</
 date><description>25 minute slots for talks and discussion panels to be submitted and selected by attendees 
on-site. This is your chance to present cutting edge developments or anything that did not make it into the 
normal schedule.
- 
-Talks will be selected and posted on the board at 16:00 on Friday and Sunday.
- 
-You can propose talks throughout the day and other attendees will add a vote to the ones that they would 
like to see. At the last break before the talk slot, the talks with the most votes will be selected and 
scheduled, so check the schedule 
board!</description><duration>00:45</duration><end>16:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>107-unconference-4</slug><start>16:00</start><subtitle /><title>Open talk #4</title><track 
/><type>talk</type></event></room><room name="Elsewhere"><event guid="f33e9765-bd8d-55a8-a166-a3acce71554d" 
id="211"><attachments /><date>2017-07-30T09:30:00+02:00</date><description 
/><duration>00:30</duration><end>10:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>211-venue_
 opens</slug><start>09:30</start><subtitle /><title>Venue opens</title><track /><type /></event><event 
guid="1cf98b5b-9980-5b3d-a84e-c57c4e90dd64" id="212"><attachments 
/><date>2017-07-30T11:00:00+02:00</date><description 
/><duration>00:30</duration><end>11:30</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>212-break</slug><start>11:00</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="ff50c8ad-efb4-50c3-b6b0-a9bc834a8797" 
id="213"><attachments /><date>2017-07-30T13:00:00+02:00</date><description 
/><duration>01:00</duration><end>14:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>213-lunch</slug><start>13:00</start><subtitle
 /><title>Lunch</title><track /><type /></event><event guid="52bf8eb3-8601-50bb-8c9d-437e91dcdfbf" 
id="215"><attac
 hments /><date>2017-07-30T15:30:00+02:00</date><description 
/><duration>00:30</duration><end>16:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>215-break</slug><start>15:30</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="50d3da06-b5bc-5c71-88fc-f2c9e19254a2" 
id="216"><attachments /><date>2017-07-30T18:15:00+02:00</date><description 
/><duration>00:45</duration><end>19:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>216-venue_closes</slug><start>18:15</start><subtitle
 /><title>Venue closes</title><track /><type /></event></room></day></schedule>
\ No newline at end of file
+<schedule><version>1.0</version><conference><acronym>GUADEC2017</acronym><city>Manchester, 
UK</city><day_change>00:00</day_change><days>3</days><end>2017-07-30</end><start>2017-07-28</start><timeslot_duration>00:15</timeslot_duration><title>GUADEC
 2017</title><venue>Manchester Metropolitan University</venue></conference><day date="2017-07-28" 
end="2017-07-28T19:00:00+02:00" index="1" start="2017-07-28T09:30:00+02:00"><room name="Turing - G29"><event 
guid="fb5e3081-c1f5-5657-9abb-b2ce8a0c4008" id="7"><attachments 
/><date>2017-07-28T12:15:00+02:00</date><description>Another yearly update on what Builder can do for you, 
what has been added, and how your contribution workflow can be simplified.&lt;br&gt;&lt;br&gt;Some topics 
include:&lt;br&gt;&lt;br&gt; - Making your development setup quick &amp; easy w/ Flatpak&lt;br&gt; - 
Profiling your project to find performance issues&lt;br&gt; - New build systems and integration points for 
plugin authors&lt;br&gt; - Debugging your project&
 lt;br&gt; - How to quickly start contributing to an existing 
project</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="1">Christian Hergert</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>7-state_of_the_builder</slug><start>12:15</start><subtitle /><title>State of the 
Builder</title><track /><type>talk</type></event><event guid="b34fba3d-270e-53e2-b533-5fd29e3eb0de" 
id="29"><attachments /><date>2017-07-28T11:30:00+02:00</date><description>Flatpak is an application 
distribution and runtime system that brings sandboxed linux desktop apps to the masses. 
&lt;br&gt;&lt;br&gt;This talk will give a status update of the flatpak project and what has happened in this 
year. It will also talk about new and interesting things happening in the echosystem around flatpak and where 
we're going in the future.</description><duration>00:45</duration><en
 d>12:15</end><language>eng</language><links /><logo /><persons><person id="2">Alexander 
Larsson</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>29-flatpak_status_update_and_future_plans</slug><start>11:30</start><subtitle 
/><title>Flatpak status update and future plans</title><track /><type>talk</type></event><event 
guid="fd063a2c-89c2-526a-ad12-d6d8fb2d3640" id="40"><attachments 
/><date>2017-07-28T14:45:00+02:00</date><description>In the last months Endless achieved another milestone to 
allow their users to transition to learners. A new feature has been developed that let's the user peek at the 
code that runs an application, modify it and run the new version of that application. A very challenging 
series of steps has been simplified: the app source will be located and downloaded automatically, then 
displayed in GNOME Builder and from there it can be explored, modified and run.&lt;br&gt;&lt;br&gt;Th
 e Feature spawns across three core GNOME technologies: the EOS Shell (derivative of the GNOME Shell), 
Flatpak and GNOME Builder.&lt;br&gt;&lt;br&gt;The authors aim is that this talk is suitable for a broad 
audience, hoping to find the right balance between demonstrating the user interaction, talking about design 
decisions and giving an technical overview of the components 
involved.</description><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="3">Simon Schampijer</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>40-seamless_integration_to_hack_desktop_applications</slug><start>14:45</start><subtitle 
/><title>Seamless integration to hack desktop applications</title><track /><type>talk</type></event><event 
guid="6e23ad85-3cf8-516f-804a-97cee4afb231" id="59"><attachments 
/><date>2017-07-28T16:45:00+02:00</date><description>Linux distributions have bee
 n traditionally put together from individual packages. In case of Fedora it's RPM packages. They have served 
us well, but they also have a number of shortcomings: with small individual components the testing matrix 
explodes when we have to consider different package versions, and upgrading such systems is often 
irreversable.&lt;br&gt;&lt;br&gt;In this talk I will lay out a plan how we are going to put together an 
atomic base system in Fedora Workstation with flatpaks for individual applications. I will demo the latest 
progress we've made and show a great many 
screenshots.</description><duration>00:30</duration><end>17:15</end><language>eng</language><links /><logo 
/><persons><person id="4">Kalev Lember</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>59-atomic_workstation</slug><start>16:45</start><subtitle /><title>Atomic 
Workstation</title><track /><type>talk</type></event><event guid="c853dbd8-0f8
 7-5e3b-8fe0-b2bb848bcb2a" id="70"><attachments /><date>2017-07-28T10:30:00+02:00</date><description>The Idea 
is to show our progress with the initiative [1] and show to GNOME Developers how to add a Jenkinsfile and 
tests for their projects.&lt;br&gt;&lt;br&gt;[1] 
https://wiki.gnome.org/Initiatives/ContinuousIntegrationForApps</description><duration>00:30</duration><end>11:00</end><language>eng</language><links
 /><logo /><persons><person id="5">Walter Vargas</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>70-gnome_continuous_integration_for_apps</slug><start>10:30</start><subtitle /><title>GNOME 
Continuous Integration For Apps</title><track /><type>talk</type></event><event 
guid="3a9a1c99-8dd6-5b0e-bcf7-1c0c5df63c00" id="102"><attachments 
/><date>2017-07-28T17:15:00+02:00</date><description>Lightning talks of Google Summer of Code and Outreachy 
interns</description><duration>01:00</duration><end>18:1
 5</end><language>eng</language><links /><logo /><persons><person id="6">GSoC and Outreachy 
Interns</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>102-interns_lightning_talks</slug><start>17:15</start><subtitle /><title>Interns lightning 
talks</title><track /><type>talk</type></event><event guid="436e87eb-2b8e-52c2-95d1-48763a7b07f1" 
id="104"><attachments /><date>2017-07-28T16:00:00+02:00</date><description>45 minute slots for talks and 
discussion panels to be submitted and selected by attendees on-site. This is your chance to present cutting 
edge developments or anything that did not make it into the normal schedule.&lt;br&gt;&lt;br&gt;You can 
propose talks from 11.00, and other attendees will add a vote to the ones that they would like to see. At 
15.30, the talk with the most votes will be selected and scheduled, so keep an eye on schedule 
board!</description><duration>00:45</duration><end>16:45</
 end><language>eng</language><links /><logo /><persons><person id="7">to be 
announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>104-unconference-1</slug><start>16:00</start><subtitle /><title>Open talk #1</title><track 
/><type>talk</type></event><event guid="93bb2614-9440-5ad3-b7f4-95aa88a9629a" id="108"><attachments 
/><date>2017-07-28T14:00:00+02:00</date><description>Keynote 1: to be 
announced</description><duration>00:45</duration><end>14:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>108-keynote_1</slug><start>14:00</start><subtitle /><title>Keynote 1</title><track 
/><type>talk</type></event><event guid="41452287-6fc1-595a-a59a-12bd117de029" id="109"><attachments 
/><date>2017-07-28T10:00:00+02:00</date><description /><duration
00:30</duration><end>10:30</end><language>eng</language><links /><logo /><persons><person id="8">GUADEC 
Team</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>109-conference_opening</slug><start>10:00</start><subtitle /><title>Conference 
opening</title><track /><type>talk</type></event><event guid="363bdbee-1372-5ff6-9c7f-56f62d93dbb4" 
id="200"><attachments /><date>2017-07-28T09:30:00+02:00</date><description 
/><duration>00:30</duration><end>10:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Turing - 
G29</room><slug>200-registration</slug><start>09:30</start><subtitle /><title>Registration</title><track 
/><type /></event></room><room name="Hopper - G44"><event guid="21cd49d0-45c8-5a83-8c03-8b9a785627aa" 
id="8"><attachments /><date>2017-07-28T16:45:00+02:00</date><description>Due to the amount of bugs in 
several G
 NU/Linux projects such as GNOME or Fedora, good volunteers and new contributors are crucial to fix them and 
make the projects better. &lt;br&gt;I emphasized the phrase good volunteers and new good contributors because 
is not only to have a positive willing to do things here.&lt;br&gt;Many other factors besides the knowledge 
of the project are fundamental, like interaction, usability, English skills, GNOME style in programming and 
following the pattern of designing.&lt;br&gt;In my local community I have encountered many pros and cons 
during almost six years of promoting the Fedora and GNOME projects in universities and social events. During 
my talk I will share those different experiences and the vulnerabilities and improvements I faced in the 
way.</description><duration>00:30</duration><end>17:15</end><language>eng</language><links /><logo 
/><persons><person id="9">Julita Inca</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room
Hopper - G44</room><slug>8-different_ways_of_outreaching_newcomers</slug><start>16:45</start><subtitle 
/><title>Different ways of outreaching newcomers</title><track /><type>talk</type></event><event 
guid="f25ee534-b1a2-513e-b8cc-526f695d0153" id="28"><attachments 
/><date>2017-07-28T14:45:00+02:00</date><description>We find ourselves in a world where there are an 
increasing number of ecosystems of computing devices and appliances that (try to) work seamlessly together 
to allow people to listen and watch what they want, when, where and how they want to in their homes -- on 
their TVs, tablets, through multi-room speakers, and so on.&lt;br&gt;&lt;br&gt;We've made some headway in 
enabling these in GNOME -- via the Sharing panel, and the massive amount of plumbing underneath it -- but 
there is a huge gap between what we have, and where I think we need to be.&lt;br&gt;&lt;br&gt;So this talk 
is in three parts:&lt;br&gt;&lt;br&gt;1. Where we are -- both in terms of the user experie
 nce (Sharing) and the software stack (Rygel, GUPnP, PulseAudio, GStreamer)&lt;br&gt;&lt;br&gt;2. Where I'd 
like us to be -- what kinds of connectivity do we want to enable? Is it possible to do this with commodity 
hardware?&lt;br&gt;&lt;br&gt;and&lt;br&gt;&lt;br&gt;3. How we can get there -- existing pieces to build on 
top of, missing pieces of the stack to add, and tying it together in a way users can 
"get"</description><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="10">Arun Raghavan</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>28-dreaming_of_a_better_home_media_experience</slug><start>14:45</start><subtitle 
/><title>Dreaming of a better home media experience</title><track /><type>talk</type></event><event 
guid="1b0f7a57-4f8e-5897-855a-a1e0fe4a8de5" id="43"><attachments 
/><date>2017-07-28T11:30:00+02:00</date><description>The Endless OS ha
 s always been a bit different from regular Linux distros in that it offers an immutable system managed by 
OSTree and thus has always had an alternative way of installing applications.&lt;br&gt;It is also one of the 
first operating systems using Flatpak as the main way of managing applications by the 
user.&lt;br&gt;&lt;br&gt;In this talk I will introduce the evolution of the application story in the Endless 
OS, focusing on the adoption of Flatpak applications and the changes to GNOME Software to integrate it better 
with the EOS desktop and to improve the UX for Endless’ users.&lt;br&gt;&lt;br&gt;I will also talk about the 
problems of shipping apps in a world of very unreliable or nonexistent internet connection and the solutions 
we implemented to give the best experiences to our users. This talk should be interesting not only for those 
who want to know more about application management in EOS but also for those who want to know more about how 
GNOME Software works and the an
 d possibilities it offers with its plugins 
system.</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="11">Joaquim Rocha</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>43-limited_connectivity_endless_apps</slug><start>11:30</start><subtitle /><title>Limited 
connectivity, Endless apps!</title><track /><type>talk</type></event><event 
guid="bb353abf-cc6c-515a-ae06-d5bfffcae654" id="48"><attachments 
/><date>2017-07-28T12:15:00+02:00</date><description>The newcomer guide is made for newcomers to get started 
with GNOME development. Bastian Ilso and Carlos Soriano will tell the story of how the newcomer experience 
changed in the past year and how that had a big impact on newcomer contributions, developer workflow and the 
image of the GNOME community.&lt;br&gt;At the end of the talk we will have an open debate about what the next 
steps should
  be to improve the experience. What do you think newcomers are looking for? What should the ideal workflow 
be?</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="12">Carlos Soriano</person><person id="13">Bastian 
Ilsø</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>48-newcomer_genesis_evolution</slug><start>12:15</start><subtitle /><title>Newcomer Genesis 
Evolution</title><track /><type>talk</type></event><event guid="607c135b-31e8-5b66-ab0e-59f517e81290" 
id="72"><attachments /><date>2017-07-28T10:30:00+02:00</date><description>This year, GNOME turns 20. Over the 
course of its history, the project has pioneered new ways of working and has set out a powerful mission for 
itself: from championing usability and accessibility, to establishing the six month release cycle, GNOME has 
been at the forefront of Free Software development. Howeve
 r, there are also risks for a project that has been running this long: collective knowledge can be 
forgotten, and it is easy to lose touch with the beliefs that give a project purpose.&lt;br&gt;&lt;br&gt;In 
this talk, I'll ask the question: what is it that defines the GNOME project? In attempting to provide my own 
answer, I'll describe the principles that I think make GNOME so important. I'll also recount stories from 
GNOME's history, and in so doing make a case for what constitutes the project's folklore. Finally, I'll ask 
the question: how do we ensure that, as GNOME looks to the future, the project continues to nurture these 
traditions?</description><duration>00:30</duration><end>11:00</end><language>eng</language><links /><logo 
/><persons><person id="14">Allan Day</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>72-the_gnome_way</slug><start>10:30</start><subtitle /><title>The GNOME Way</title><t
 rack /><type>talk</type></event><event guid="01e8a7f0-684c-55b0-8b1c-930962a49729" id="105"><attachments 
/><date>2017-07-28T16:00:00+02:00</date><description>45 minute slots for talks and discussion panels to be 
submitted and selected by attendees on-site. This is your chance to present cutting edge developments or 
anything that did not make it into the normal schedule.&lt;br&gt;&lt;br&gt;You can propose talks from 11.00, 
and other attendees will add a vote to the ones that they would like to see. At 15.30, the talk with the most 
votes will be selected and scheduled, so keep an eye on schedule 
board!</description><duration>00:45</duration><end>16:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>105-unconference-2</slug><start>16:00</start><subtitle /><title>Open talk #2</title><track 
/><type>talk</type></event></
 room><room name="Elsewhere"><event guid="fd199473-c615-5f85-9975-575ebe87a07a" id="201"><attachments 
/><date>2017-07-28T11:00:00+02:00</date><description 
/><duration>00:30</duration><end>11:30</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>201-break</slug><start>11:00</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="d6b06dee-7e6c-5f25-87fb-3bc31998f997" 
id="202"><attachments /><date>2017-07-28T13:00:00+02:00</date><description 
/><duration>01:00</duration><end>14:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>202-lunch</slug><start>13:00</start><subtitle
 /><title>Lunch</title><track /><type /></event><event guid="b8d33ab3-733c-5dd3-9921-24af014cac4f" 
id="203"><attachments /><date>2017-07-28T15:30:00+02:00</date><description /><dura
 tion>00:30</duration><end>16:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>203-break</slug><start>15:30</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="abe4e817-53ef-5220-9c78-b15253d0ebc1" 
id="204"><attachments /><date>2017-07-28T18:15:00+02:00</date><description 
/><duration>00:45</duration><end>19:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>204-venue_closes</slug><start>18:15</start><subtitle
 /><title>Venue closes</title><track /><type /></event></room></day><day date="2017-07-29" 
end="2017-07-29T19:00:00+02:00" index="2" start="2017-07-29T09:30:00+02:00"><room name="Turing - G29"><event 
guid="d4776b28-450d-5c72-bbcd-16b813808106" id="5"><attachments 
/><date>2017-07-29T11:30:00+02:00</date><description>I have been workin
 g on replacing the C code in librsvg, GNOME's SVG rendering library, with Rust.  Rust is one of the few 
high-level languages that actually generates object code, which in turn can be linked into compiled C 
code.&lt;br&gt;&lt;br&gt;What started as an experiment in replacing gnarly C code with clean Rust code, 
eventually turned into a full porting effort.  Librsvg's public API/ABI remain the same as before, and only 
the internals have Rust code in them.  The result is a much safer library with trustworthy code.  Not only is 
the code safe by Rust's nature; it now has a bunch of unit tests that would have been very cumbersome to 
write before.&lt;br&gt;&lt;br&gt;This talk will explore:&lt;br&gt;&lt;br&gt;* Brief intro to Rust's benefits 
and philosophy.&lt;br&gt;&lt;br&gt;* Tips for replacing C code with Rust.&lt;br&gt;&lt;br&gt;* Refactorings 
that are needed in C to replace it with Rust.&lt;br&gt;&lt;br&gt;* Refactorings that are possible once Rust 
is in place.&lt;br&gt;&lt;br&gt
 ;* Going from a codebase with zero unit tests to one that has a bunch of tests!&lt;br&gt;&lt;br&gt;* Having 
a mixture of C and Rust code for certain implementation patterns.&lt;br&gt;&lt;br&gt;* Replacing scary C 
parsers with safe Rust parsers.&lt;br&gt;&lt;br&gt;* How Rust clarified my thinking.&lt;br&gt;&lt;br&gt;* Can 
distros ship this?&lt;br&gt;&lt;br&gt;* Should we replace GNOME library code with Rust, in 
general?</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="15">Federico Mena Quintero</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>5-replacing_c_library_code_with_rust_what_i_learned</slug><start>11:30</start><subtitle 
/><title>Replacing C library code with Rust: what I learned</title><track /><type>talk</type></event><event 
guid="3e32c3e2-6bdb-5afa-be55-9b15f35398c8" id="14"><attachments /><date>2017-07-29T15:00:00+02:00</d
 ate><description>In this talk, I'll have a look at some of the challenges that GNOME faces at the moment, a 
brief look into the future, and how we can meet those head on and 
thrive!</description><duration>00:30</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="16">Neil McGovern</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>14-gnome_to_2020_and_beyond</slug><start>15:00</start><subtitle /><title>GNOME to 2020 and 
beyond</title><track /><type>talk</type></event><event guid="6cf0e9df-438b-5b7d-907b-50f4b6f98237" 
id="15"><attachments /><date>2017-07-29T12:15:00+02:00</date><description>Since 2012, a service in the GNOME 
infrastructure has been constantly building GNOME modules, committing the result to Ostree, and running 
automated tests on the whole OS. From a single Git commit to a full blown virtual machine in a matter of 
minutes. This service is called GNOME C
 ontinuous, our own continuous integration and delivery pipeline.&lt;br&gt;&lt;br&gt;Continuous has been the 
major driver to improve the quality of the whole GNOME project: for developers, by building their work; for 
designers, by providing a bootable VM to perform design iteration and QA; to newcomers, by ensuring that 
tools like jhbuild would be more reliable; to distributors and OSVs, who could ensure their products would be 
based on a reliable set of components.&lt;br&gt;&lt;br&gt;In this presentation we will talk about how 
Continuous came to be, thanks to the work of Colin Walters; how it works; what are the goals of a CI/CD 
pipeline like Continuous; and where do we go from 
here.</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="17">Emmanuele Bassi</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>15-continuous_past_present_and_fut
 ure</slug><start>12:15</start><subtitle /><title>Continuous: Past, Present, and Future</title><track 
/><type>talk</type></event><event guid="bdff2d9f-cbd4-5bf3-8d87-f29e05f6aa61" id="50"><attachments 
/><date>2017-07-29T10:00:00+02:00</date><description>With the new contribution workflow enabled by GNOME 
Builder, it is now trivially easy for newcomers to clone a project, build it, and hack on 
it.&lt;br&gt;&lt;br&gt;This talk is about how you can use Meson's subprojects and wrapdb to have a very 
similar experience on any operating system with just Meson and git.&lt;br&gt;&lt;br&gt;At the same time, this 
feature is also distro-friendly since all this machinery can be turned off with a single option, telling 
Meson to only use dependencies provided by the 
system.</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="18">Nirbheek Chauhan</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout>
 </recording><room>Turing - 
G29</room><slug>50-building_your_gnome_app_anywhere_with_meson</slug><start>10:00</start><subtitle 
/><title>Building your GNOME app anywhere with Meson</title><track /><type>talk</type></event><event 
guid="5d769bed-f310-5afd-a9d5-2b7c1556d5a0" id="60"><attachments 
/><date>2017-07-29T14:00:00+02:00</date><description>Happy Birthday GNOME! Ever wonder why the project is the 
way it is? The GNOME project has had a long and exciting ride to this point. I'll go through some of the 
early moments of the project that led us to the desktop that we know and love 
today.</description><duration>01:00</duration><end>15:00</end><language>eng</language><links /><logo 
/><persons><person id="19">Jonathan Blandford</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>60-the_history_of_gnome</slug><start>14:00</start><subtitle /><title>The History of 
GNOME</title><track /><type>talk</type></event><
 event guid="9ec3f1f0-0feb-548e-833e-5c38721764c0" id="63"><attachments 
/><date>2017-07-29T10:30:00+02:00</date><description>Shell present and near 
future.</description><duration>00:30</duration><end>11:00</end><language>eng</language><links /><logo 
/><persons><person id="20">Carlos Garnacho</person><person id="21">Florian 
Müllner</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>63-muttergnomeshell_state_of_the_union</slug><start>10:30</start><subtitle 
/><title>Mutter/gnome-shell state of the union</title><track /><type>talk</type></event><event 
guid="cae033cb-4acd-5194-895c-1cd1dfb66e7c" id="100"><attachments 
/><date>2017-07-29T16:00:00+02:00</date><description>The annual general meeting of the GNOME Foundation: team 
reports</description><duration>01:00</duration><end>17:00</end><language>eng</language><links /><logo 
/><persons><person id="22">GNOME Board</person></persons><recording><license>CC BY-
 SA 4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>100-gnome_foundation_agm_part_1</slug><start>16:00</start><subtitle /><title>GNOME Foundation 
AGM (part 1)</title><track /><type>meeting</type></event><event guid="e92b8310-2623-54c4-be20-ce7391564083" 
id="101"><attachments /><date>2017-07-29T17:15:00+02:00</date><description>The annual general meeting of the 
GNOME Foundation: Q&amp;A with the 
board.</description><duration>01:00</duration><end>18:15</end><language>eng</language><links /><logo 
/><persons><person id="22">GNOME Board</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>101-gnome_foundation_agm_part_2</slug><start>17:15</start><subtitle /><title>GNOME Foundation 
AGM (part 2)</title><track /><type>meeting</type></event><event guid="05eb0f22-c9af-5862-aae8-4bb34772e1e0" 
id="209"><attachments /><date>2017-07-29T17:00:00+02:00</date><description /><duration>00:15</d
 uration><end>17:15</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Turing - 
G29</room><slug>209-group_photo</slug><start>17:00</start><subtitle /><title>Group photo</title><track 
/><type /></event></room><room name="Hopper - G44"><event guid="526ab1a5-9783-528c-9208-6ab1c1d7a07d" 
id="31"><attachments /><date>2017-07-29T11:30:00+02:00</date><description>Matrix.org is a relatively new open 
standard for decentralised realtime communication - providing an open global network (including end-to-end 
encryption) that links together communication silos such as Slack, IRC, Gitter, Telegram, XMPP etc.  Matrix 
has gained some popularity in the GNOME developer community since GIMPNet was bridged into the wider Matrix 
ecosystem in March (https://mail.gnome.org/archives/desktop-devel-list/2017-March/msg00033.html), and 
meanwhile Matrix's goals of entirely open source and democratised communication are qui
 te aligned with the ethos of the GNOME project.&lt;br&gt;&lt;br&gt;This talk will be a formal introduction 
and demonstration of the Matrix ecosystem, its APIs and spec, its clients/servers/bridges/bots, its 
end-to-end encryption, its goals and its current status, as given by the project 
lead.</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="23">Matthew Hodgson</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>31-decentralised_open_communication_with_matrixorg</slug><start>11:30</start><subtitle 
/><title>Decentralised open communication with Matrix.org</title><track /><type>talk</type></event><event 
guid="c27e346f-5ef5-5845-aad6-f741a15a36a9" id="41"><attachments 
/><date>2017-07-29T10:00:00+02:00</date><description>Emeus is a constraint-based layout manager and container 
widget for GTK+.&lt;br&gt;&lt;br&gt;Emeus allows programmers and 
 designers to describe the UI in a way that can be more natural from the UI building perspective, more 
expressive and efficient than stacking boxes inside boxes.&lt;br&gt;&lt;br&gt;At Endless we have been 
developing Emeus to provide richer visual experiences in our apps and better tools for engineers and 
designers to work together.&lt;br&gt;&lt;br&gt;Here's what you'll see in this talk:&lt;br&gt;&lt;br&gt;* A 
new way of creating rich layouts for your GTK+ app.&lt;br&gt;* A display of layouts and widgets that we 
created at Endless.&lt;br&gt;* How it brings programmers and designers 
together.</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="24">Martin Abente Lahaye</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>41-fantastic_layouts_and_where_to_find_them</slug><start>10:00</start><subtitle 
/><title>Fantastic Layouts And Where To Find 
 Them</title><track /><type>talk</type></event><event guid="5068c0d6-7857-510f-9a2b-373c560b519b" 
id="62"><attachments /><date>2017-07-29T12:15:00+02:00</date><description>Tracker has become a foundation for 
many core apps. It has provided a common metadata store for applications to share, making all of the data a 
giant interconnected graph.&lt;br&gt;&lt;br&gt;However, times change. There's now initiatives like flatpak 
that make this interconnected graph more accessory, or even not desirable. This talk will cover the plans to 
make Tracker a good citizen in the sandboxing world, and what this means for 
applications.</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="20">Carlos Garnacho</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>62-tracker__present_and_future</slug><start>12:15</start><subtitle /><title>Tracker - present 
and future<
 /title><track /><type>talk</type></event><event guid="eaaf9612-272e-59df-81c0-406d441e9376" 
id="65"><attachments /><date>2017-07-29T10:30:00+02:00</date><description>Come and hear about the latest 
developments in LibreOffice and see how we continue to make the Linux Desktop and Free Software ever more 
useful for business users.&lt;br&gt;&lt;br&gt;Get an update on the awesome work from Caolan polishing our 
gtk3 and wayland support. Checkout the latest new features in the LibreOfficeKit API - ripe for deeper use in 
GNOME Documents - and the potential for testing out innovative new GNOME editors here. See LibreOffice Online 
- inspired by gtk+/broadway - and what it can do&lt;br&gt;for you.&lt;br&gt;&lt;br&gt;Also catch random 
thoughts and demos on whatever seems 
apposite.</description><duration>00:30</duration><end>11:00</end><language>eng</language><links /><logo 
/><persons><person id="25">Michael Meeks</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false<
 /optout></recording><room>Hopper - 
G44</room><slug>65-libreoffice_and_gnome</slug><start>10:30</start><subtitle /><title>LibreOffice and 
GNOME</title><track /><type>talk</type></event></room><room name="Elsewhere"><event 
guid="a74eebdc-899a-579d-a84f-ba8d18667403" id="205"><attachments 
/><date>2017-07-29T09:30:00+02:00</date><description 
/><duration>00:30</duration><end>10:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>205-venue_opens</slug><start>09:30</start><subtitle
 /><title>Venue opens</title><track /><type /></event><event guid="4049ad77-c1eb-5e0a-b4c2-ca3c0de54f10" 
id="206"><attachments /><date>2017-07-29T11:00:00+02:00</date><description 
/><duration>00:30</duration><end>11:30</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>206-break</slug><start>11:00
 </start><subtitle /><title>Break</title><track /><type /></event><event 
guid="cdffc551-86dc-5f92-8d61-efe3fc4276fa" id="207"><attachments 
/><date>2017-07-29T13:00:00+02:00</date><description 
/><duration>01:00</duration><end>14:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>207-lunch</slug><start>13:00</start><subtitle
 /><title>Lunch</title><track /><type /></event><event guid="53f0a9ac-99b8-5eb9-9fa3-3e914a2a89c7" 
id="208"><attachments /><date>2017-07-29T15:30:00+02:00</date><description 
/><duration>00:30</duration><end>16:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>208-break</slug><start>15:30</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="0e481de3-2119-5f57-8d28-87c17229c2dd" 
id="210"><attachments /><date>2017-07-29T18:1
 5:00+02:00</date><description /><duration>00:45</duration><end>19:00</end><language>eng</language><links 
/><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>210-venue_closes</slug><start>18:15</start><subtitle
 /><title>Venue closes</title><track /><type /></event></room></day><day date="2017-07-30" 
end="2017-07-30T19:00:00+02:00" index="3" start="2017-07-30T09:30:00+02:00"><room name="Turing - G29"><event 
guid="24652dae-8d39-5a73-a8e5-aaddd983e107" id="22"><attachments 
/><date>2017-07-30T10:30:00+02:00</date><description>Various GNOME modules have been building on Coverity 
Scan for the last year. Has it been finding legitimate bugs, or ones which people are almost never going to 
hit? What’s the best way to use static analysis? Why should developers care?&lt;br&gt;&lt;br&gt;Warning: This 
talk will contain Jenkins and 
graphs.</description><duration>00:30</duration><end>11:00</end><language>eng</language><lin
 ks /><logo /><persons><person id="26">Philip Withnall</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>22-whats_coverity_static_analysis_ever_done_for_us</slug><start>10:30</start><subtitle 
/><title>What’s Coverity static analysis ever done for us?</title><track /><type>talk</type></event><event 
guid="c3cc55a3-5b08-5358-99f1-666bd7c54501" id="23"><attachments 
/><date>2017-07-30T11:30:00+02:00</date><description>Cooking and recipes is not a new topic for the GNOME 
community.&lt;br&gt;All the way back to 2007, the idea of a GNOME cook book was already around 
(https://wiki.gnome.org/GnomeCookbook). For one reason or another, we never quite got there - but the idea 
has stuck around, and after Guadec last year, the two of us got together to finally make GNOME recipes a 
reality.&lt;br&gt;&lt;br&gt;Our talk will cover the original design goals and the evolution of the design 
from paper mock-ups and ideas,
  to refining a raw prototype and to the complete application that we have to today. We will touch on the 
interaction between design and development and how you can be successful in this even when you have to bridge 
a 7 hour time differential.&lt;br&gt;&lt;br&gt;We will take a look ahead at whats coming in 3.26, and how the 
original design goals are evolving and expanding as we build out the application.&lt;br&gt; &lt;br&gt;On the 
technical side, we will explore some of the challenges and lessons learned during the development of recipes, 
and we will explain how writing this application was useful for developing and refining new technologies such 
as sandboxes, portals and new build systems. There may be an aside about portability.&lt;br&gt;&lt;br&gt;Of 
course, there will be a demo of 
recipes.</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="27">Matthias Clasen</person><person id="28">Emel Elvin Yildiz</person
</persons><recording><license>CC BY-SA 4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>23-recipes__lessons_learned_from_creating_a_new_app</slug><start>11:30</start><subtitle 
/><title>Recipes - Lessons learned from creating a new app</title><track /><type>talk</type></event><event 
guid="c6ee3b58-3a6e-5330-9d4f-9739b72a2c95" id="26"><attachments 
/><date>2017-07-30T10:00:00+02:00</date><description>GNOME 3.24 brought a lot of improvements in GJS, the 
Javascript language bindings for GNOME, that power GNOME Shell, Polari, GNOME Documents, and many other 
apps.&lt;br&gt;&lt;br&gt;We moved to a more modern version of the Javascript engine. We gained support for 
a lot of cool language features that take some of the rough edges off of Javascript's shady reputation. For 
GNOME 3.26 we'll continue this modernizing process, and start improving the developer experience in GJS as 
well.&lt;br&gt;&lt;br&gt;Here's what you'll see in this talk:&lt;br&gt;- Cool s
 tuff you never knew you could do in GJS!&lt;br&gt;- How to modernize your app with ES6 features!&lt;br&gt;- 
Debugging, documentation, and other developer tools!&lt;br&gt;- Sneak peek of what's to come in 3.26 and how 
you can help!</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="29">Philip Chimento</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>26-modern_javascript_in_gnome</slug><start>10:00</start><subtitle /><title>Modern Javascript 
in GNOME</title><track /><type>talk</type></event><event guid="5b5c389e-170b-5bcf-9e4d-74f8ff49c677" 
id="38"><attachments /><date>2017-07-30T12:15:00+02:00</date><description>In this talk, I will start by 
outlining our motivations behind creating this new meta build system, based both on the emergence of new 
distribution models and also lessons learned from existing meta build system implementations.
 &lt;br&gt;&lt;br&gt;Then we will briefly explore the abstract and rather simple design of BuildStream: A 
format and engine for the modeling and processing of pipelines composed of elements which perform mutations 
on filesystem data from inside an isolated sandbox environment.&lt;br&gt;&lt;br&gt;Finally we will explore 
the various use cases of building GNOME modules and outline how we intend to apply this new technology to 
improve the GNOME Developer experience in various 
ways.</description><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo 
/><persons><person id="30">Tristan Van Berkom</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>38-gnome_build_strategies_and_buildstream</slug><start>12:15</start><subtitle /><title>GNOME 
Build Strategies and BuildStream</title><track /><type>talk</type></event><event 
guid="6d2e7e92-c56f-5358-be16-4c22e07f2daf" id="44"><attachments /><
 date>2017-07-30T16:45:00+02:00</date><description>In this talk we will go trough most of the not so known 
features of Glade and introduce a refreshed UI which will improve the regular design workflow by replacing 
the good old tool palette.&lt;br&gt;&lt;br&gt;The walk trough will include:&lt;br&gt; - creating custom 
composite widgets&lt;br&gt; - a catalog to add support for them&lt;br&gt; - JavaScript objects in 
Glade&lt;br&gt;&lt;br&gt;As a bonus, I might, just might, show my crazy idea to rewrite Glade from scratch 
for Gtk4, just so that we can discuss it over some 
beers!</description><duration>00:30</duration><end>17:15</end><language>eng</language><links /><logo 
/><persons><person id="31">Juan Pablo Ugarte</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>44-how_to_get_better_mileage_out_of_glade</slug><start>16:45</start><subtitle /><title>How to 
get better mileage out of Glade</title><track /><ty
 pe>talk</type></event><event guid="cd873c69-aae6-5edd-b537-cad7fbed6d67" id="52"><attachments 
/><date>2017-07-30T14:00:00+02:00</date><description>I am a co-founder and technical lead of Ubuntu GNOME, 
with our goal to bring a pure GNOME experience to Ubuntu some might wonder where that might be heading given 
the recently annouced decision for Canonical to drop Unity and switch to GNOME. This will bring a new set of 
challenges for the Ubuntu GNOME team, while our distro will not likely exist as a seperate entity and we will 
merge development resources with the Canonical desktop team, we will remain as a community team to avoid the 
possible distinction between community and Canonical may getting blurred.&lt;br&gt;&lt;br&gt;I will open my 
talk with a brief history of the Ubuntu GNOME project, why we started it and what our goals were. We started 
the project with goal of bring pure gnome-shell to Ubuntu. At the time GNOME 3 was incredibly broken on both 
Ubuntu and Debian to the 
 the point of being unusable. We managed to get things into really good shape over the years but there have 
been challenges, mostly relating to the co-existence with Unity, and having to maintain large patch delta’s 
to work with Unity also.&lt;br&gt;&lt;br&gt;Then comes the exciting stuff what is the future of GNOME on 
Ubuntu, where does the Ubuntu GNOME team stand in the future? Canonical are already showing some resistance 
towards core components of the GNOME stack, for example things like tracker and gdm. What part will Ubuntu 
GNOME play in pushing our visions into the core Ubuntu Future GNOME desktop? I can’t be incredibly specific 
on this at this point we are still in discussions with Canonical teams at this stage, but all should be clear 
by GUADEC. This should fill the bulk of my talk, I see exciting oppurtunities ahead and some more challenges 
going forward before we can get Canonical aligned with GNOME. I will discuss these in detail during my 
talk.</description><
 duration>00:45</duration><end>14:45</end><language>eng</language><links /><logo /><persons><person 
id="32">Tim Lunn</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>52-bringing_gnome_home_to_ubuntu</slug><start>14:00</start><subtitle /><title>Bringing GNOME 
home to Ubuntu</title><track /><type>talk</type></event><event guid="343b5c9d-c4fa-5aa4-8563-1e271c788435" 
id="103"><attachments /><date>2017-07-30T17:15:00+02:00</date><description>Fast-paced and focused talks on 
any and all subjects. All talks will be subject to a strict time limit of 5 minutes on stage (including 
setup). Slides are welcome, but not compulsory.&lt;br&gt;&lt;br&gt;You will be able to sign up for a 
lightning talk slot from 11.00AM on Sunday 29th on a signup sheet at the info desk. Talks will be accepted on 
a first come, first serve 
basis.</description><duration>00:45</duration><end>18:00</end><language>eng</language><links /><logo
  /><persons /><recording><license>CC BY-SA 4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>103-lightning_talks</slug><start>17:15</start><subtitle /><title>Lightning 
talks</title><track /><type>talk</type></event><event guid="bbfbd734-10aa-5f7a-8bb3-4255d7949690" 
id="106"><attachments /><date>2017-07-30T16:00:00+02:00</date><description>45 minute slots for talks and 
discussion panels to be submitted and selected by attendees on-site. This is your chance to present cutting 
edge developments or anything that did not make it into the normal schedule.&lt;br&gt;&lt;br&gt;You can 
propose talks from 11.00, and other attendees will add a vote to the ones that they would like to see. At 
15.30, the talk with the most votes will be selected and scheduled, so keep an eye on schedule 
board!</description><duration>00:45</duration><end>16:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><lice
 nse>CC BY-SA 4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>106-unconference-3</slug><start>16:00</start><subtitle /><title>Open talk #3</title><track 
/><type>talk</type></event><event guid="9482c5aa-b3ef-5cc5-bfdc-ffef6d4b7045" id="110"><attachments 
/><date>2017-07-30T18:00:00+02:00</date><description 
/><duration>00:15</duration><end>18:15</end><language>eng</language><links /><logo /><persons><person 
id="8">GUADEC Team</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Turing - 
G29</room><slug>110-conference_closing</slug><start>18:00</start><subtitle /><title>Conference 
closing</title><track /><type>talk</type></event><event guid="da0daac0-3475-583a-9ffa-7e0ed82aa044" 
id="214"><attachments /><date>2017-07-30T14:45:00+02:00</date><description 
/><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout
</recording><room>Turing - G29</room><slug>214-tbd</slug><start>14:45</start><subtitle 
/><title>TBD</title><track /><type /></event></room><room name="Hopper - G44"><event 
guid="8e9c9810-06ed-5b96-af10-68729ba32773" id="1"><attachments 
/><date>2017-07-30T14:45:00+02:00</date><description>Containerised Application technologies like AppImage, 
Snappy and Flatpak promise a brave new world for Linux applications, free from the worries of shared 
libraries and dependency issues. Just one problem, this is a road long travelled before, such as in the 
application dark ages of Win32 applications and DLLs. And it worked out so wonderfully there... Do we risk 
a future where, like the resurrected dinosaurs of Jurassic Park, this family of applications will break 
their containment and start eating our users? This session will try to present a balanced argument about 
the situation, frankly discussing the benefits promised by these technologies, but highlighting the very 
real issues and ris
 ks their widespread adoption could, and in some cases are, already bringing to the 
table.&lt;br&gt;&lt;br&gt;The talk with cover the promised benefits of application containers, such as 
AppImage, Snappy and Flatpak. It will detail the empowerment of developers who use the technologies, the 
ability for upstream projects to have a much closer role in delivering their software, and the benefits that 
brings to both the upstream projects and their users. But as a counter to those benefits, the session will 
detail some of the risks and responsibilities that come with that technology. The complexities of library 
integration, the risk of introducing new forms of dependency issues, and the transference of responsibility 
for those issues, plus security, away from the current Distributions delivering upstream projects towards 
those upstream projects directly. As a conclusion, the session will present some suggestions to upstream 
projects adopting these technologies to start them down t
 he road of accepting those responsibilities directly, or working more closely with existing Distribution 
projects to share the burdens these technologies now 
provide.</description><duration>00:45</duration><end>15:30</end><language>eng</language><links /><logo 
/><persons><person id="33">Richard Brown</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>1-resurrecting_dinosaurs_what_can_possibly_go_wrong</slug><start>14:45</start><subtitle 
/><title>Resurrecting dinosaurs, what can possibly go wrong</title><track /><type>talk</type></event><event 
guid="23c23699-fdc5-5e08-aa98-ddc1aac45dae" id="6"><attachments 
/><date>2017-07-30T10:00:00+02:00</date><description>After spending considerable amount of time prototyping 
designs for GNOME, over and over again I've met with resistance to transitions as being a "waste of CPU/GPU 
time" and not enjoying a wide acceptance among developers.&lt;br&gt;&lt;br&gt;I'll pre
 sent my case as to why transitions are helpful conveying meaning and spatial 
awareness.</description><duration>00:30</duration><end>10:30</end><language>eng</language><links /><logo 
/><persons><person id="34">Jakub Steiner</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>6-the_inbetweens__why_transitions_matter</slug><start>10:00</start><subtitle /><title>The 
Inbetweens — why transitions matter.</title><track /><type>talk</type></event><event 
guid="dc201b85-f588-533c-b7c2-4498bc53e9dc" id="11"><attachments 
/><date>2017-07-30T14:00:00+02:00</date><description>Flatpak is a tool providing new and easy way how to 
distribute desktop applications. While it is pretty well supported in Gnome, we in KDE have been trying to 
catch up and offer same experience. In this talk, Jan Grulich will share with you what KDE has been lately up 
to and what has been accomplished during last year.  &lt;br&gt;&lt;br&gt; Mar
 tin Bříza will also cover how we advanced with how well are Qt applications integrated into the overall 
GNOME experience.  &lt;br&gt;&lt;br&gt; Topics covered will include the state of the Adwaita and Highcontrast 
themes, new QGnomePlatform (abstract platform theme backend for GNOME) features and Wayland 
support.</description><duration>00:45</duration><end>14:45</end><language>eng</language><links /><logo 
/><persons><person id="35">Jan Grulich</person><person id="36">Martin 
Bříza</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>11-flatpak_and_kde_and_the_state_of_qt_integration_in_gnome</slug><start>14:00</start><subtitle
 /><title>Flatpak and KDE, and the state of Qt integration in GNOME</title><track 
/><type>talk</type></event><event guid="adbb36c1-257e-5bc9-81a8-9cd5077e031b" id="16"><attachments 
/><date>2017-07-30T10:30:00+02:00</date><description>Animations are the future of interface design.
  They enable developers to make interfaces more understandable by offloading processes from the user's brain 
to the screen. However, in many cases animations are simply added as transitions between independently 
designed screens. This can result in animations contradicting each other spatially. I co-wrote an article 
about why this is a problem [1] and outlined a solution: Designing semantic components which change over 
time, and then using these to compose interfaces.&lt;br&gt;&lt;br&gt;Even though the industry seems to 
largely agree that this is the way forward, there are very few interfaces implementing these ideas. I believe 
the main reason for this is that the current generation of layout technologies is built for static layouts 
with strict hierarchies. This makes it prohibitively difficult to build interfaces where components move 
fluidly between different states.&lt;br&gt;&lt;br&gt;I will show some interface prototypes I built and 
explain why they were so difficult to 
 implement with current technology. Finally, I will outline some ideas for a better layout API, to make 
building awesome, fluid interfaces from the future more feasible.&lt;br&gt;&lt;br&gt;[1] 
https://alistapart.com/article/motion-with-meaning-semantic-animation-in-interface-design</description><duration>00:30</duration><end>11:00</end><language>eng</language><links
 /><logo /><persons><person id="37">Tobias Bernard</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>16-building_interfaces_from_the_future</slug><start>10:30</start><subtitle /><title>Building 
interfaces from the future</title><track /><type>talk</type></event><event 
guid="b5162e55-01c1-5dd8-8f17-b78ff5e85d25" id="20"><attachments 
/><date>2017-07-30T12:15:00+02:00</date><description>I'm Jonathan Kang, a GNOME hacker from China. I 
currently maintain Logs, and contribute to other projects. My copresenter is Chingkai Chu who is a QA 
engineer a
 t SUSE and he has been        focused on Gnome testing and openQA for two years.&lt;br&gt;&lt;br&gt;We'll 
talk about how currently GNOME applications are tested using different technologies. And then introduce the 
approach of using openQA to test GNOME applications.&lt;br&gt;&lt;br&gt;Our talk can be divided into three 
parts:&lt;br&gt;1. Why should we do quality assurance&lt;br&gt;    - We'll talk about this from a GNOME 
hacker and a GNOME QA tester's view.&lt;br&gt;&lt;br&gt;2. The current technologies used in GNOME projects 
for testing&lt;br&gt;    - It's mainly about the methods GNOME community currently uses to do the testing, 
like dogtail, glib unit test, gnome continuous and etc.&lt;br&gt;&lt;br&gt;3. Introduce what I did with 
openQA for testing my maintained project and discuss the possibility of using it for other projects&lt;br&gt; 
   - openQA features overview and how we use it in SLE Desktop team&lt;br&gt;    - Gnome automation testing 
approach using openQA</descr
 iption><duration>00:45</duration><end>13:00</end><language>eng</language><links /><logo /><persons><person 
id="38">Jonathan Kang</person><person id="39">Chingkai Chu</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>20-robustness_of_gnome</slug><start>12:15</start><subtitle /><title>Robustness of 
GNOME</title><track /><type>talk</type></event><event guid="8db7a86f-7cdc-5710-a270-b84b04f81984" 
id="64"><attachments /><date>2017-07-30T16:45:00+02:00</date><description>GTK+4 is getting more generic and 
simple, and less X11-centric. This talk will cover what this means for GtkWidget development, and the main 
differences with GTK+3.</description><duration>00:30</duration><end>17:15</end><language>eng</language><links 
/><logo /><persons><person id="20">Carlos Garnacho</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - G44</room><slug>64-ding_dong_gdkw
 indow_is_dead</slug><start>16:45</start><subtitle /><title>Ding dong, GdkWindow is dead</title><track 
/><type>talk</type></event><event guid="3a961a4e-1d46-597f-b7b1-397ad89b325a" id="68"><attachments 
/><date>2017-07-30T11:30:00+02:00</date><description>The move towards Wayland and container-isolated 
application deployment brings a range of security benefits. But broad isolation isn't enough - we still need 
fine-grained control over access to resources, otherwise it's still practical for a single compromised 
application to leak significant quantities of personal data.&lt;br&gt;&lt;br&gt;This presentation will 
examine existing application isolation mechanisms and identify cases where they fall short. It will then go 
on to cover existing kernel technologies that allow us to provide even stronger restrictions and control, and 
how it's possible for us to build environments that provide high levels of security without forcing users to 
give up the freedom to run whatever software 
 they want.</description><duration>00:45</duration><end>12:15</end><language>eng</language><links /><logo 
/><persons><person id="40">Matthew Garrett</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>68-building_a_secure_desktop_with_gnome_technologies</slug><start>11:30</start><subtitle 
/><title>Building a secure desktop with GNOME technologies</title><track /><type>talk</type></event><event 
guid="46647784-a003-5e87-9fcf-881d1c42efb6" id="107"><attachments 
/><date>2017-07-30T16:00:00+02:00</date><description>45 minute slots for talks and discussion panels to be 
submitted and selected by attendees on-site. This is your chance to present cutting edge developments or 
anything that did not make it into the normal schedule.&lt;br&gt;&lt;br&gt;You can propose talks from 11.00, 
and other attendees will add a vote to the ones that they would like to see. At 15.30, the talk with the most 
votes will be selected 
 and scheduled, so keep an eye on schedule 
board!</description><duration>00:45</duration><end>16:45</end><language>eng</language><links /><logo 
/><persons><person id="7">to be announced</person></persons><recording><license>CC BY-SA 
4.0</license><optout>false</optout></recording><room>Hopper - 
G44</room><slug>107-unconference-4</slug><start>16:00</start><subtitle /><title>Open talk #4</title><track 
/><type>talk</type></event></room><room name="Elsewhere"><event guid="f33e9765-bd8d-55a8-a166-a3acce71554d" 
id="211"><attachments /><date>2017-07-30T09:30:00+02:00</date><description 
/><duration>00:30</duration><end>10:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>211-venue_opens</slug><start>09:30</start><subtitle
 /><title>Venue opens</title><track /><type /></event><event guid="1cf98b5b-9980-5b3d-a84e-c57c4e90dd64" 
id="212"><attachments /><date>2017-07-30T11:00:00+02:0
 0</date><description /><duration>00:30</duration><end>11:30</end><language>eng</language><links /><logo 
/><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>212-break</slug><start>11:00</start><subtitle
 /><title>Break</title><track /><type /></event><event guid="ff50c8ad-efb4-50c3-b6b0-a9bc834a8797" 
id="213"><attachments /><date>2017-07-30T13:00:00+02:00</date><description 
/><duration>01:00</duration><end>14:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>213-lunch</slug><start>13:00</start><subtitle
 /><title>Lunch</title><track /><type /></event><event guid="52bf8eb3-8601-50bb-8c9d-437e91dcdfbf" 
id="215"><attachments /><date>2017-07-30T15:30:00+02:00</date><description 
/><duration>00:30</duration><end>16:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optou
 t>true</optout></recording><room>Elsewhere</room><slug>215-break</slug><start>15:30</start><subtitle 
/><title>Break</title><track /><type /></event><event guid="50d3da06-b5bc-5c71-88fc-f2c9e19254a2" 
id="216"><attachments /><date>2017-07-30T18:15:00+02:00</date><description 
/><duration>00:45</duration><end>19:00</end><language>eng</language><links /><logo /><persons 
/><recording><license>no-video</license><optout>true</optout></recording><room>Elsewhere</room><slug>216-venue_closes</slug><start>18:15</start><subtitle
 /><title>Venue closes</title><track /><type /></event></room></day></schedule>
\ No newline at end of file


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]