<?xml version='1.0' encoding='utf-8' ?>
<schedule>
<version>0.2</version>
<conference>
<title>Akademy 2017</title>
<start>2017-07-22</start>
<end>2017-07-23</end>
<days>2</days>
<timeslot_duration>00:05</timeslot_duration>
</conference>
<day date='2017-07-22' index='1'>
<room name='Room 1'>
<event id='382'>
<start>10:00</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_10:00_-_opening_-__-_382</slug>
<title>Opening</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract></abstract>
<description></description>
<persons>
<person id='137'>.</person>
</persons>
<links>
</links>
</event>
<event id='385'>
<start>10:15</start>
<duration>00:40</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_10:15_-_tales_of_unicorns_and_cake_open_source_non-profit_lessons_-__-_385</slug>
<title>Tales of Unicorns and Cake: Open Source Non-Profit Lessons</title>
<subtitle></subtitle>
<track>Keynote</track>
<type></type>
<language></language>
<abstract></abstract>
<description>Starting an open source project is easy, but turning it into a business remains a challenging. Introducing money into an open source project brings complexities between volunteers, staff and projects goals and guidelines.

Navigating these spaces, from traditional ‘business models’ to uncharted open source waters can lead to peculiar and also amazing situations. Open source organizations can also expect cultural clashes working with larger companies as bottom up and top down methodologies often present some intense friction points. Robert will share some of his experiences from the past 17 years, from the serious to the ridiculous, including the story of sending Amazon a cake.</description>
<persons>
<person id='680'>Robert Kaye</person>
</persons>
<links>
</links>
</event>
<event id='381'>
<start>11:05</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_11:05_-_plasma_state_of_the_union_-_sebas_-_381</slug>
<title>Plasma: State of the Union</title>
<subtitle>Highlights from the last year, upcoming features and challenges</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>This presentation provides an overview of the most important things that happened over the last year in the development of Plasma. We will talk about current features, future plans and goals, what to expect on your desktop over the next year, and how to help and get involved.</abstract>
<description>The talk will be a high level view of what happened in the development of the Plasma over the last year, it will touch the most important developments and the features landed recently as well many interesting small improvements, that may get easily overlooked but are the little small details that can provide a real productivity boost.

In 2016, we saw the first long-term support version of Plasma with the 5.8 release, which will have a total of more of a year worth of bug fixes and releases  with a particular focus on improving the user experience of multiple monitor users.
The Slimbook, a new laptop that ships Plasma as its primary user interface by default, provides a nice hardware showcase for Plasma.
On the Plasma mobile front, we have worked hard on stabilizing the core operating system after migrating away from Ubuntu touch and added the official support for the Nexus 5x alongide the Nexus 5

The talk will then talk about plans for the future: what lies ahead in terms of features and challenges as well as what to expect from the upcoming Plasma 5.11 release in September, and the current state of the Wayland support, showing off some features that have been designed with Wayland in mind thanks to the technical superiority over X11.</description>
<persons>
<person id='101'>Sebastian Kügler</person>
</persons>
<links>
</links>
</event>
<event id='369'>
<start>11:50</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_11:50_-_why_we_fight_-_miroslav_-_369</slug>
<title>Why we fight</title>
<subtitle>The emergence of governance norms in FLOSS communities</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>A review of the governance norms applied in FSFE, KDE and Wikimedia, how they developed over time and how current debates reflect their evolution.</abstract>
<description>FLOSS communities create free software products in a social
process. Communities with a small number of participants typically organise informally. As the community grows, the need for coordination grows as well and at some point formal organisation is required. Where structure and processes emerge, the principles and norms applied typically reflect voluntary participation and meritocratic peer status. The main interest of the community is to attract and retain contributors and to collect contributions. Based in a qualitative study performed at TU Berlin, the presentation will review the governance norms applied by the FSFE, the KDE Community and Wikimedia as the organisations developed, how the constitutions of the communities reflect the convictions and expectations of their contributors, and how the need to evolve governance norms is at the heart of recent conflicts in all three communities.</description>
<persons>
<person id='134'>Mirko Boehm</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/369-why-we-fight.mp4'>Video</link>
</links>
</event>
<event id='354'>
<start>12:30</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_12:30_-_developing_for_our_users_-_apol_-_354</slug>
<title>Developing for our users</title>
<subtitle>Nobody cares more about KDE software users than KDE</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>In this presentation I&#x27;ll offer a new point of view for development of regular KDE software based on bundling systems. We&#x27;ll see what advantages we are going to get if we embrace these technologies from the developer perspective and what impact it&#x27;s going to have beyond development, by shortening the path between the development, the QA we make and the actual users. It will offer new ways to cater to our users.</abstract>
<description>We will see how adopting bundling technologies (i.e. Snappy, Flatpak, AppImage) can open many doors on how our users not only use our software but also can be more efficient when contributing back upstream, either by testing new versions, submitting feedback or even modifying the software and getting the contribution into our repositories.

To that end, I&#x27;ll propose some small changes we can do on our own software development and distribution process in order to enable these benefits to our users, or at least to some of them.</description>
<persons>
<person id='16'>Aleix Pol Gonzalez</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/354-developing-for-our-users.mp4'>Video</link>
</links>
</event>
<event id='374'>
<start>13:10</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_13:10_-_kdenlive_rewriting_the_timeline_-__-_374</slug>
<title>Kdenlive, rewriting the timeline</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>In 2017, we started a rewrite of some core parts of the Kdenlive video editor. This presentations will be an opportunity to get some details on the process and see a demonstration of the upcoming Kdenlive 17.08.</abstract>
<description>The most visible change that will happen for Kdenlive 17.08  is a switch to QML for many parts of the UI. The timeline, where most interaction happens, now benefits from a more polished look, with enhanced user interaction that will be demonstrated during the presentation. This will also be an opportunity to present the huge work that was done recently to improve the stability and maintainability of the code. </description>
<persons>
<person id='606'>Jean-Baptiste Mardelle</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/374-kdenlive-rewriting-the-timeline.mp4'>Video</link>
</links>
</event>
<event id='387'>
<start>13:40</start>
<duration>01:50</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_13:40_-_lunch_-_387</slug>
<title>Lunch</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract></abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
<event id='334'>
<start>15:30</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_15:30_-_mycroft_ai_plasmoid_plasma_desktop_integration_-_aix_-_334</slug>
<title>Mycroft Ai Plasmoid &amp; Plasma Desktop Integration</title>
<subtitle></subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>This presentation will showcase the demo of the Mycroft Plasmoid  and it’s Interactions with Mycroft Core. This presentation will also discuss and demo how an intelligent digital assistant can enhance your plasma desktop experience. The presentation will further touch upon the points of how other projects on the plasma desktop environment and other individual standalone KDE projects can integrate with Mycroft to provide a new layer of voice control and user interaction.</abstract>
<description>Introduction:
Mycroft Plasmoid is a desktop frontend that intends to interact with the Mycroft Core backend which is developed by the team at Mycroft Ai. It is an open source community committed technology that ties natural language processing, text-to-speech, speech-to-text, and powerful APIs together to create a powerful experience allowing users to manipulate their devices through voice control. Mycroft Ai is the digital implementation of a modern day virtual assistant on the Linux Platform that can help a user conduct a multitude of task via voice / text.

Goals:
The Mycroft Plasmoid is developed with an aim towards integration of Mycroft Core backend with the Plasma 5 Desktop Environment to provide an open, user rich desktop and an interactive virtual assistant experience to the end users with keeping in mind the principles of free and open source software. This project also aims towards making the virtual assistant a central hub of information and desktop control assistance providing the user a new innovative layer of voice control and desktop interactive technology.</description>
<persons>
<person id='664'>Aditya Mehra</person>
</persons>
<links>
<link href='https://mycroft.ai/mycroft-gets-a-plasmoid/'>Mycroft Gets a Plasmoid</link>
<link href='http://aiix.tk/dev/mycroft-plasmoid-gets-an-update/'>Mycroft Plasmoid Gets an Update</link>
<link href='http://files.kde.org/akademy/2017/334-mycroft-ai-plasmoid-amp-plasma-desktop-integration.mp4'>Video</link>
</links>
</event>
<event id='336'>
<start>15:40</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_15:40_-_kf5_syntaxhighlighting_-_vkrause_-_336</slug>
<title>KF5::SyntaxHighlighting</title>
<subtitle>A stand-alone syntax highlighting engine</subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>Since KF5 5.28 you have the ability to easily integrate the robust and powerful syntax highlighting of Kate into your application even when embedding a fully featured code editor is not an option.</abstract>
<description>KF5::SyntaxHighlighting is a stand-alone implementation of the Kate syntax highlighting engine. Support for more than 250 different file formats is built in, and thanks to being based on XML syntax definition files it is easily extendable to support additional or custom formats.

While the history of Kate&#x27;s highlighting engine goes back to the late 90s, it used to be heavily tied to the Kate editor. The same is true for the alternative implementation inside QtCreator, making re-use elsewhere usually infeasible. KF5::SyntaxHighlighting addresses this by only depending on Qt5::Gui and providing an abstraction for the output format, be it a complex custom text editor, a QSyntaxHighlighter or simple HTML, allowing you to easily integrate syntax highlighting into your application.</description>
<persons>
<person id='118'>Volker Krause</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/336-kf5-syntaxhighlighting.mp4'>Video</link>
</links>
</event>
<event id='379'>
<start>15:50</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_15:50_-_clazy_-_qt_oriented_code_checker_-_tsdgeos_-_379</slug>
<title>Clazy - Qt Oriented code checker</title>
<subtitle></subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>A quick overview on Clazy, a static code checker for Qt code.</abstract>
<description></description>
<persons>
<person id='14'>Albert Astals Cid</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/379-clazy-qt-oriented-code-checker.mp4'>Video</link>
</links>
</event>
<event id='378'>
<start>16:00</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_16:00_-_kirigami_applications_and_designers_-_notmart_-_378</slug>
<title>kirigami, applications and designers</title>
<subtitle></subtitle>
<track>Lightning (5m)</track>
<type></type>
<language></language>
<abstract>Lessons learned in balancing the development of an User Interface framework and designing an application: a virtuous feedback loop.</abstract>
<description>Were we want rigidity and where we want freedom. While designing  the Kirigami user interface framework, was of course not possible to predict every possible use case of applications using it. During  the design of applications like Discover, the feedback loop between the design and implementation of the application, improved significantly the quality of the framework, and new design elements percolated upwards in the framework and in the human interface guidelines. The quick talk will look at some of those examples, trough demos, code and pretty pictures.</description>
<persons>
<person id='72'>Marco Martin</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/378-kirigami-applications-and-designers.mp4'>Video</link>
</links>
</event>
<event id='350'>
<start>16:10</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_16:10_-_ruqola_a_qt_qml_interface_to_rocket_chat_-__-_350</slug>
<title>Ruqola, a Qt/QML interface to Rocket.Chat</title>
<subtitle></subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>Ruqola is the first generic chat application based on Rocket.Chat. The application is a Qt/QML/C++ app, thus providing multi-platform portability. Ruqola will currently run on both Desktop and mobile (Android) platforms. </abstract>
<description>Ruqola is a Qt/QML interface to Rocket Chat, with a library implementing DDP semantics, and a QML UI for both desktop and mobile phones. Rocket Chat is a Web Chat Server, developed in JavaScript, using the Meteor framework. In Ruqola application, DDPClient class implements Meteor&#x27;s DDP and Rocketchat backend class uses this &quot;library&quot; to pull in Rocket.Chat data.
Rocket.Chat is a great solution for communities wanting to privately host their own chat service or for developers looking forward to build and evolve their own chat platforms, and Ruqola is built on Rocket.Chat.
Ruqola is the first of its kind. After its initial release, it can be used by entire KDE organisation as a medium of communication. 
Particularly for WikiToLearn, there is no application/platform where people can discuss the content (and its fidelity) provided at WikiToLearn Portal (https://en.wikitolearn.org/Main_Page). Since WikiToLearn chat exists for discussing development issues, there is a need for such an application for making discussing the content easier. 

Ruqola will support following features (before the release of Ruqola 1.0)-
1. Support for notifications (on both desktop and mobile application).
2. Support for OAuth/federated login.
3. Generic UI which works for all servers.
4. Support for reactions.
5. Support for images.</description>
<persons>
<person id='670'>.</person>
</persons>
<links>
<link href='https://github.com/WikiToLearn/Ruqola'>Ruqola GitHub Link</link>
<link href='http://files.kde.org/akademy/2017/350-ruqola-a-qt-qml-interface-to-rocket-chat.mp4'>Video</link>
</links>
</event>
<event id='355'>
<start>16:30</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_16:30_-_architecting_qt_mobile_applications_frameworks_code_generators_and_beyond_-_sandroandrade_-_355</slug>
<title>Architecting Qt Mobile Applications: Frameworks, Code Generators and Beyond</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Although Qt has evolved, over the past years, into a quite effective toolkit for building cross-platform mobile applications, the lack of reusable architectural solutions and productivity tools still hampers a wider adoption of Qt by mobile development industry. This talk presents the initial thoughts and preliminary implementation of a modular and flexible framework for building Qt mobile applications. The solution relies on the use of code generators and a plugin-based architecture to automate the implementation of recurrent tasks, such as user authentication, CRUD implementation, local storage, and client-server communication via RESTful.</abstract>
<description>Although Qt has evolved, over the past years, into a quite effective toolkit for building cross-platform mobile applications, the lack of reusable architectural solutions and productivity tools still hampers a wider adoption of Qt by the mobile development industry. Novice Qt mobile developers usually spend a lot of time thinking about how to correctly partition functionality, deciding about local and remote communication patterns, choosing effective UI strategies, and coping with specific platform idiosyncrasies. Unless appropriate engineering and experience are put in place, this usually results in applications which are hard to develop/maintain, difficult to reuse, and highly prone to bugs.

This talk presents the initial thoughts and preliminary implementation of a modular and flexible framework for building Qt mobile applications. The solution relies on the use of code generators and a plugin-based architecture to automate the implementation of recurrent tasks, such as user authentication, CRUD implementation, local storage, and client-server communication via RESTful.

The framework provides two main technologies: i) a command-line tool which works as a code generator; and ii) a modular and flexible architecture for mobile information systems. The command-line tool has been developed in Ruby, using the Thor toolkit (http://whatisthor.com/) and already provides basic commands for generating new application&#x27;s skeletons and adding new models and views for CRUD operations. It also provides generators for building RESTful services based on Ruby Sinatra framework. Generated code automatically implements a flexible architecture where functionality, navigation drawer construction, and CRUD operations are added by plugins. We believe such a tool may be useful to support the rapid construction of well-designed Qt mobile applications by automating the generation of core functionality and setting the stage for reusable and easy-to-maintain applications.</description>
<persons>
<person id='541'>Sandro Andrade</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/355-architecting-qt-mobile-applications-frameworks-code-generators-and-beyond.mp4'>Video</link>
</links>
</event>
<event id='333'>
<start>17:10</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_17:10_-_kde_e_v_board_ask_us_anything_-_nightrose_-_333</slug>
<title>KDE e.V. board: Ask Us Anything</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>The board is doing a lot of work throughout the year to support KDE. In this session you can ask us anything you&#x27;d like to know about our work and plans or anything else that comes to your mind.</abstract>
<description></description>
<persons>
<person id='50'>Lydia Pintscher</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/333-kde-e-v-board-ask-us-anything.mp4'>Video</link>
</links>
</event>
<event id='343'>
<start>17:55</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_17:55_-_wikidata_exploring_more_visibility_and_coverage_of_kde_applications_-__-_343</slug>
<title>Wikidata: Exploring more visibility and coverage of KDE Applications</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>KDE has a number of great applications. Yet their coverage on Wikipedia is very low and sometimes even outdated. A careful look at current versions of English Wikipedia articles on KDE applications proves this point. For other languages, the situation is even worse. However, this is not just a problem with KDE community, but can be found in many other open source software projects and it remains an open challenge. Enter Wikidata, the new open, free, collaborative, linked, multilingual and structured data store and it seems that the future of open knowledge graph is very bright. In this talk (or tutorial), I would like to present how Wikidata can play an important role for the visibility of KDE applications and how developers can build tools to integrate their applications with Wikidata to present an up to date view of their applications and the cool features. Integration with Wikidata also ensures that KDE applications can be easily discovered, compared with other similar solutions and easily analysed.</abstract>
<description>The talk (or tutorial) will have four parts:
1. Identifying the key information related to KDE applications and other open source softwares
2. Explanation of Wikidata, its goals and its potential as a open knowledge graph
3. Hands-on experience (demonstration with existing KDE applications)
4. Introduction to various Python libraries (for accessing and editing Wikidata)
</description>
<persons>
<person id='666'>John Samuel</person>
</persons>
<links>
</links>
</event>
<event id='349'>
<start>18:35</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_18:35_-_on_the_road_to_gcompris-qt_1_0_-_animtim_-_349</slug>
<title>On the road to gcompris-qt 1.0</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>This talk is about the recent activity in GCompris, the issues we faced, and how the community can join us.</abstract>
<description>During the last year a lot of things happened in GCompris. We finally officially shipped the new Qt-based version instead of the old one, and people are mostly happy with it.

In this talk, I&#x27;d like to show the progress we made, and some shiny new activities. I&#x27;ll also talk about the few issues that some users have been facing with the new version compared to the old one. We found workarounds for some issues, but a few are inevitable.

We are slowly getting closer to 1.0, but there is still some big work to do. I&#x27;ll try to summarize the remaining tasks, and point to the parts where the community can help.</description>
<persons>
<person id='105'>Timothée Giet</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/349-on-the-road-to-gcompris-qt-1-0.mp4'>Video</link>
</links>
</event>
<event id='357'>
<start>19:15</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_19:15_-_opening_new_doors_kde_in_embedded_-_toscalix_-_357</slug>
<title>Opening new doors: KDE in embedded</title>
<subtitle></subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>Automotive and other tradition embedded industries are moving beyond their traditional role as Open Source consumers only. KDE project might have an interesting role to play if we open ourselves to this sector. This talk will describe why is such an interest move for the project and what challenges we will face on the journey.</abstract>
<description>On October 2016, while being in charge of the GENIVI Development Platform for automotive, Agustin wrote an article about the opportunity that represents for KDE the automotive sector today. This is true for other embedded industries that lack a &quot;desktop&quot; and applications done in the open to supports the different platform development efforts. The opportunity is even greater if we look at embedded as a collection of industries that are currently in early stages in terms of Open Source development practices. Big players are investing effort in supporting R&amp;D projects in the open and they know very little about us. And those who do know about KDE, limit our efforts, technologies and focus on &quot;non-touch&quot; screens.

From the variety of distribution efforts that bring bring Open Source to embedded, Agustin finds particularly interesting the Yocto project, the most popular &quot;distribution effort&quot; within embedded nowadays. Other projects like Buildstream have interest too.

Today Agustin is involved in the development of another automotive platform, driven by the Linux Foundation (AGL), that is getting momentum and has a weak equivalent solution compared to Plasma. The same applies to the very limited set of applications, specially if we compare them with what KDE might offer.

Agustin will describe why embedded Linux represents such an opportunity for KDE, what are the areas we should look at and what are the main challenges we need to overcome. Another interesting topic is the synergies that such a move would bring with the Qt community.</description>
<persons>
<person id='18'>Agustin Benito Bethencourt</person>
</persons>
<links>
<link href='http://www.toscalix.com'>Personal site</link>
<link href='http://files.kde.org/akademy/2017/357-opening-new-doors-kde-in-embedded.mp4'>Video</link>
</links>
</event>
<event id='383'>
<start>19:25</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-22_19:25_-_looking_for_love_-_bro666_-_383</slug>
<title>Looking for Love</title>
<subtitle>Increasing your audience&#x27;s appreciation for your project</subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>Learn three things you can do to improve how you present your project to users, collaborators and sponsors.</abstract>
<description>Good ideas often go unnoticed because they are described in an opaque, convoluted or jargon-heavy way. In this talk we will show that, by shifting focus, it is possible to explain a project in simple terms that can help garner support.</description>
<persons>
<person id='293'>Paul Brown</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/383-looking-for-love.mp4'>Video</link>
</links>
</event>
</room>
<room name='Room 2'>
<event id='388'>
<start>09:30</start>
<duration>00:20</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_09:30_-_registration_-_388</slug>
<title>Registration</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract>At the Hall of Aulario IV</abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
<event id='371'>
<start>11:05</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_11:05_-_odf_support_in_calligra_-_vandenoever_-_371</slug>
<title>ODF support in Calligra</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language>en</language>
<abstract>Calligra has native support of ODF. That does not mean that it&#x27;s perfect. In this talk we&#x27;ll look at a number of areas of ODF and see how well they are supported. This is compared to other office suites.</abstract>
<description>The ODF plugfests have resulted in many tests to check ODF compliance. These can be run against Calligra and this shows some points that could do with improvements.

The talk will highlight easy and harder tasks that can be undertaken to extend ODF support in Calligra.</description>
<persons>
<person id='341'>Jos van den Oever</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/371-odf-support-in-calligra.mp4'>Video</link>
</links>
</event>
<event id='395'>
<start>11:35</start>
<duration>00:15</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_11:35_-_coffee_break_-_395</slug>
<title>Coffee Break</title>
<subtitle></subtitle>
<track></track>
<type></type>
<language></language>
<abstract>At Aulario IV: Complimentary coffee, juices, pastries and cake</abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
<event id='335'>
<start>11:50</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_11:50_-_userfeedback_-_vkrause_-_335</slug>
<title>UserFeedback</title>
<subtitle>A framework for application telemetry and targeted surveys</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>The UserFeedback framework enables you to engage your users directly in the application and encourage them to contribute by providing statistical data or participate in surveys, without compromising their privacy and while keeping full control over their data.</abstract>
<description>Knowing who our users are, and what they are using our applications for is essential in order to tailor our software to what people actually need. In the KDE community, our access to this information is very limited though, as on the one hand we take the user&#x27;s privacy very seriously, and on the other hand we so far lack the tools to easily obtain this data. Applications collecting statistical data are the exception (e.g. Kexi), and our channels to invite users for surveys are limited to blogs and social media.

This talk will present the UserFeedback framework (https://cgit.kde.org/kuserfeedback.git/), which provides generic infrastructure for engaging users directly inside the application. This involves the collection of system or usage statistics, as well as asking an interested set of users that match a specific set of criteria to participate in an online survey. Ensuring the user&#x27;s privacy has been a primary design goal, given the user full transparency of the collected and transmitted data, as well as full opt-in control over their participation. Furthermore, the entire system works without the need for unique identifiers in any form.</description>
<persons>
<person id='118'>Volker Krause</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/335-userfeedback.mp4'>Video</link>
</links>
</event>
<event id='394'>
<start>12:30</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_12:30_-_rust_support_for_kdevelop_-_-_-_394</slug>
<title>Rust support for KDevelop</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type>technicaltalk</type>
<language></language>
<abstract>Rust is a rather new programming language, but it has already gained a lot of  traction. It was voted “most loved” language by developers for the second year in a row in the StackOverflow developer survey. There have been projects made using Rust on everything from operating systems to game engines for Minecraft-like games. Despite this, IDE support is still lacking. KDevelop currently does not support Rust at all. The goal of this Google Summer of Code project is to add the standard features an IDE should support for a language such as semantic highlighting, code completion, refactoring, debugging and project management.</abstract>
<description></description>
<persons>
<person id='681'>Emma Gospodinova</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/394-rust-support-for-kdevelop.mp4'>Video</link>
</links>
</event>
<event id='331'>
<start>13:10</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_13:10_-_a_bit_on_functional_programming_-_ivan_home_-_331</slug>
<title>A bit on functional programming</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Functional programming is often said to be necessary in multi-threaded environments, but that is only one part of the story. Avoiding mutation helps avoid explicit synchronization of concurrent processes, but it can also be helpful in other circumstances.</abstract>
<description>This talk will cover a selection of topics related to functional programming, and how it can improve our day-to-day work, make our code safer, cleaner and more correct.</description>
<persons>
<person id='155'>Ivan Čukić</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/331-a-bit-on-functional-programming.mp4'>Video</link>
</links>
</event>
<event id='362'>
<start>16:30</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_16:30_-_introducing_babe_and_a_contextual_approach_to_multimedia_desktop_apps_-__-_362</slug>
<title>Introducing Babe and a contextual approach to multimedia desktop apps.</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Babe is a new music collection manager for KDE with focus on design and user experience. Babe aims to introduce a contextual way to experience music by making use of online resources and A.I to find relationships between the music metadata and its context in order to generate personalized queries and suggestions. 
</abstract>
<description>Recently Babe has joined the KDE Incubator project, with the prospect of becoming a well integrated KDE/Plasma desktop application by making use of the framework’s available technologies in order to give a tight and integrated experience to the final user. 

Babe aims to incorporate a contextual way of managing the user’s music collection, and also let the user to easily collect music information and their favorite music from online free streaming services. 

Those two points: contextual managing and online collecting are the body that composes the main idea of bringing into the multimedia desktop apps (MDA) an approach towards an A.I contextual managing; with the use of information retrieval strategies, based on processes of information detection, like data mining, in order to discover patterns in sets of MDA ‘s data, this so to carry tasks of extraction, compilation and characterization. 

These systems can be used on the development of decentralised MDA, to access and also generate contextual information from different sources to establish relationships between the data, with the purpose of giving to the end user dynamic and contextual information about their multimedia content (music, videos, books, images, games.. etc).  

Such system would run only locally without collecting, in any way, sensitive information about the user, in that way protecting their rights to privacy.

In this case Babe wants to propose a local system of music characterization.

The points to talk about in the presentation are the following ones:

-Introduce Babe and the features implemented so far

-Talk about the progress of the KDE Incubator project and some related community subjects around Babe, such as possible areas for collaboration with other projects and the benefits it would bring to the end user

-Introduce the idea of contextual multimedia managing apps

-Describe the benefits of using a contextual system for managing multimedia collections

-Display progress made so far and talk about possible implementations

-Overview about the road ahead and current problems on the area of semantic annotation of multimedia files and music information retrieval mechanisms
</description>
<persons>
<person id='672'>camilo higuita</person>
</persons>
<links>
<link href='https://milohr.github.io/cv_CamiloHiguita/'>C.V</link>
<link href='http://files.kde.org/akademy/2017/362-introducing-babe-and-a-contextual-approach-to-multimedia-desktop-apps.mp4'>Video</link>
</links>
</event>
<event id='329'>
<start>17:10</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_17:10_-_digikam_ninja_tricks_-__-_329</slug>
<title>digiKam Ninja Tricks</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type>technicaltalk</type>
<language></language>
<abstract>Discover digiKam tools and features that can help you manage and process photos in the most efficient manner.</abstract>
<description>Take your digiKam skills to the next level by mastering its advanced functionality. The talk will introduce several useful features and tools, including filtering, batch processing, curve presets, and much more.</description>
<persons>
<person id='567'>Dmitri Popov</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/329-digikam-ninja-tricks.mp4'>Video</link>
</links>
</event>
<event id='397'>
<start>17:40</start>
<duration>00:15</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_17:40_-_coffee_break_-_397</slug>
<title>Coffee Break</title>
<subtitle></subtitle>
<track></track>
<type></type>
<language></language>
<abstract>At Aulario IV: Complimentary coffee, juices, pastries and mini-sandwiches</abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
<event id='337'>
<start>17:55</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_17:55_-_an_introduction_to_the_kio_library_-_shortstheory_-_337</slug>
<title>An introduction to the KIO Library</title>
<subtitle>The KDE Input Output Subsystem</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>The KDE Input Output (KIO) library in KDE is an integral part to KDE Frameworks 5 and provides a uniform wrapper API for accessing data from a number of different protcols such as protocols for files, ssh, https, samba shares, ftp, and network file systems. Several KDE applications use the KIO library such as Dolphin and KDE Connect use this API extensively for file management operations.

My talk will be an introduction to KIO library in KDE. I will explain the need for KIO, how KIO works, KIO slaves, and how to develop for the same. I will also discuss some recent developments in the KIO world. If time permits, I will also take questions from the audience. </abstract>
<description>My talk will be an introduction to the KIO library used in several KDE Applications. I will start with a brief introduction to the uses of KIO and how it is applied in several KDE applications such as Dolphin and Plasma Plasmoids. After this, I will demonstrate some examples of the KIO abstraction layer in action using kioclient and with some KDE applications. I will also talk about how KDE applications tap into KIO&#x27;s functionality to execute the same file management operation (e.g. move, copy, delete), across a number of different protocols without needing to code separately for each protocol.

Following this, I will talk about how KIO slaves complete the KIO abstraction layer and how KIO slaves can be written to accomplish a number of nifty use cases (such as my kio-stash GSoC project and the Google Drive KIO slave). I will talk briefly about how to develop a simple KIO slave using the KIO slave base classes such as SlaveBase and ForwardingSlaveBase. After this, if time permits, I will take some questions from the audience.
</description>
<persons>
<person id='653'>arnav dhamija</person>
</persons>
<links>
<link href='https://www.youtube.com/watch?v=zRJznj2jNsw&amp;list=PLsHpGlwPdtMogitRYzwPz4dWTVsZRGwts&amp;index=19'>My presentation at QtCon 2016</link>
<link href='http://arnavdhamija.com/blog/tag/gsoc.html'>My GSoC articles</link>
<link href='https://github.com/KDE/kio-stash'>Project Source Code</link>
<link href='http://files.kde.org/akademy/2017/337-an-introduction-to-the-kio-library.mp4'>Video</link>
</links>
</event>
<event id='380'>
<start>18:35</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-22_18:35_-_binding_loop_detected_for_property_title_-_d_ed_-_380</slug>
<title>Binding loop detected for property &quot;title&quot;</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Everyone developing QML at some point will experience the pain that is binding loops.

In this presentation I will talk about what this warning really means, and most importantly how you can tackle even the most complicated loops with various tools like GDB.

</abstract>
<description></description>
<persons>
<person id='150'>David Edmundson</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/380-binding-loop-detected-for-property-quot-title-quot.mp4'>Video</link>
</links>
</event>
</room>
</day>
<day date='2017-07-23' index='2'>
<room name='Room 1'>
<event id='386'>
<start>10:00</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_10:00_-_the_kde_community_and_its_ecosystem_-_antlarr_-_386</slug>
<title>The KDE Community and its Ecosystem</title>
<subtitle></subtitle>
<track>Keynote</track>
<type></type>
<language>en</language>
<abstract>The KDE Community is large and diverse. It encompasses persons with different cultures and different views on many topics but still all share a common goal on the KDE project.

At the same time, the KDE community is not alone in the digital world. There are other communities around us which may have different goals but also may share some of our ideas. How can we take advantage of this? Which are those communities? How can we collaborate more with those other communities and let them collaborate with us too?</abstract>
<description></description>
<persons>
<person id='170'>Antonio Larrosa Jimenez</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/386-the-kde-community-and-its-ecosystem.mp4'>Video</link>
</links>
</event>
<event id='364'>
<start>10:40</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_10:40_-_plasma_mobile_-_bshah_-_364</slug>
<title>Plasma Mobile</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Plasma Mobile offer a Free (as in Freedom and beer), user-friendly, privacy-enabling and customizable platform for mobile devices. This talk aims to discuss and demonstrate the recent developments of Plasma Mobile project</abstract>
<description>In course of one year, lots of underlying stack for Plasma Mobile changed, lots of new developments happened on user-facing side of the Plasma Mobile.

We also integrated Plasma Mobile to newer Android Marshmallow based devices like Nexus 5X.</description>
<persons>
<person id='371'>Bhushan Shah</person>
</persons>
<links>
<link href='http://blog.bshah.in/slides/akademy2017'>Slides</link>
<link href='http://files.kde.org/akademy/2017/364-plasma-mobile.mp4'>Video</link>
</links>
</event>
<event id='359'>
<start>11:20</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_11:20_-_input_methods_in_plasma_5_-_sho_-_359</slug>
<title>Input Methods in Plasma 5</title>
<subtitle>Modern and global text input</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>An overview over the How and Why of Input Methods support (including examples of international writing systems, emoji and word completion) in Plasma on both X11 and Wayland, its current status and challenges, and the work ahead of us.</abstract>
<description>Text input is the foundational means of human-computer interaction: We configure or systems, program them, and express ourselves through them by writing. Input Methods help us along by converting hardware events into text - complex conversion being a requirement for many international writing systems, new writing systems such as emoji, and at the heart of assistive text technologies such as word completion and spell-checking.

This talk will illustrate the application areas for Input Methods by example, presenting short introductions to several international writing systems as well as emoji input. It will explain why solid Input Methods support is vital to KDE&#x27;s goal of inclusivity and how Input Methods can make the act of writing easier for all of us.

It will consolidate input from the Input Methods development and user community to provide a detailed overview over the current Input Methods technical architecture and user experience in Plasma, as well as free systems in general. It will dive into existing pain points and present both ongoing work and plans to address them.</description>
<persons>
<person id='674'>Eike Hein</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/359-input-methods-in-plasma-5.mp4'>Video</link>
</links>
</event>
<event id='348'>
<start>12:05</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_12:05_-_folding_your_applications_-_leinir_-_348</slug>
<title>Folding Your Applications</title>
<subtitle>Convergent User Experiences with Kirigami</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Have you got an application, or an idea for one, which you want to work well on more than one kind of device? In more than one form factor? Come and see how to use Kirigami and the guidelines it implements to create comfortable and effective user experiences, with tips and tricks from applications already using it.</abstract>
<description>Over the course of the last few years, and especially with the advent of powerful mobile devices of many sizes, convergence has become an much discussed topic. They employ various input methods, with the traditional mouse and keyboard, or with pure touch, or a combination of the options. They have a wide range of screen sizes, and distances of operation, from small and in your hand, to far away and on the wall.

Applications need to work across as many of these as possible, and so KDE has been working on a variety of frameworks to support the creation of applications with convergent user experiences. Most recently, this effort has brought about the creation of the Kirigami framework, which includes both a software stack, and a set of guidelines which shows you how to use the components.

We will show you techniques for implementing these experiences, and present some of the thoughts behind the designs. Examples will be presented, from applications both made by ourselves, and by others out in the wild, which show how the tools Kirigami gives you can be used most effectively. We hope to show you not only how to create convergent applications and why we think it is a good idea, but why we think you will want to start doing this with your own applications.</description>
<persons>
<person id='549'>Dan Leinir Turthra Jensen</person>
</persons>
<links>
<link href='https://techbase.kde.org/Kirigami'>Kirigami Information</link>
<link href='http://files.kde.org/akademy/2017/348-folding-your-applications.mp4'>Video</link>
</links>
</event>
<event id='370'>
<start>12:45</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_12:45_-_advances_in_qt_3d_-_ervin_-_370</slug>
<title>Advances in Qt 3D</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Having 3D scenes in your application is becoming a clear trend and is likely
to become even more important in the future with the growth of Virtual Reality
and Augmented Reality. So far Qt was allowing you to integrate with Open GL
fairly easily, but managing the rendering code itself was still a very
challenging task.

That&#x27;s why Qt 5.7 introduced Qt 3D. Of course, it keeps evolving and in this
talk we will highlight the novelties coming with 5.8, 5.9 and 5.10.</abstract>
<description>Since writing 3D code from scratch can be very difficult and since getting the
architecture of your rendering engine right is critical to your application,
Qt 3D will offload those risks from you so that you can focus on your actual
simulation and 3D scene content.

In this talk, we will first do a quick recap of Qt 3D&#x27;s API principles. In
particular it is structured around an Entity Component System (ECS) architecture
which will be presented.

Then we&#x27;ll have a tour of the newest features available in 5.8 and 5.9. Of
particular interest to the community we will talk about painting to texture
and we will show how to integrate a QtQuick 2 scene inside of a 3D scene. We
will also present the new PBR materials, the new animation aspect and more...

If time permits, we will also give a sneak peak to a feature in the work meant
to help managing shader code. This is currently private API but will be
leveraged and exposed both in QtQuick and Qt 3D.

This talk will be interesting to any developer having to implement a 3D scene
inside an application using Qt or thinking about bringing VR or AR use cases
in the KDE community. No prior knowledge of Open GL or GPU programming is
required for this talk.</description>
<persons>
<person id='124'>Kevin Ottens</person>
</persons>
<links>
<link href='https://ervin.ipsquad.net/slides/talks/ak2017-qt3d-advances/'>Slides</link>
<link href='http://files.kde.org/akademy/2017/370-advances-in-qt-3d.mp4'>Video</link>
</links>
</event>
<event id='389'>
<start>13:15</start>
<duration>00:15</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_13:15_-_group_photo_-_389</slug>
<title>Group Photo</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract></abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
<event id='390'>
<start>13:30</start>
<duration>02:00</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_13:30_-_lunch_-_390</slug>
<title>Lunch</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract></abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
<event id='341'>
<start>15:30</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_15:30_-_challenges_in_translation_team_-_s8321414_-_341</slug>
<title>Challenges in translation team</title>
<subtitle>For example: Taiwan</subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>I will talk something about current challenges in translation team, take Taiwan as an example.</abstract>
<description>I will talk something about current challenges in translation team, take Taiwan as an example.</description>
<persons>
<person id='668'>Jeff Huang</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/341-challenges-in-translation-team.mp4'>Video</link>
</links>
</event>
<event id='347'>
<start>15:40</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_15:40_-_kde_neon_docker_images_-_riddell_-_347</slug>
<title>KDE neon Docker Images</title>
<subtitle></subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>If you need to test your fix in master but you only run releases, or ask someone else to test it, you can use KDE neon Docker images.  This talk shows to do so.
</abstract>
<description></description>
<persons>
<person id='145'>Jonathan Riddell</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/347-kde-neon-docker-images.mp4'>Video</link>
</links>
</event>
<event id='344'>
<start>15:50</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_15:50_-_adopting_odf_--_what_we_need_in_calligra_-_franklin_-_344</slug>
<title>Adopting ODF -- What We Need in Calligra</title>
<subtitle>Missing features in Calligra</subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>In Taiwan the National Development Council (NDC) launched a three-year project to adopt ODF as national standard file format.  Recently we mainly use and promote LibreOffice but it&#x27;s always better to have more choices.  Can Calligra meet our requirement?</abstract>
<description>Open Document Format (ODF) has been the national standard in Taiwan since 2009, but nobody cared until 2014.  The National Development Council (NDC) in Taiwan launched a three-year project to moving from Microsoft Office format (including old doc/ppt/xls to OOXML) to ODF.  

For the software we have LibreOffice, OpenOffice, Abiword, Calligra, Google Docs, ... etc to choose.  However besides LibreOffice and OpenOffice, Calligra couldn&#x27;t meet the requirement for now.  In this short talk I&#x27;ll show what&#x27;s missing in Calligra Words/Sheets/Stage and hope that they can be improved for users in Taiwan.</description>
<persons>
<person id='393'>Franklin Weng</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/344-adopting-odf-what-we-need-in-calligra.mp4'>Video</link>
</links>
</event>
<event id='346'>
<start>16:00</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_16:00_-_end_to_end_trust_-_riddell_-_346</slug>
<title>End to End Trust</title>
<subtitle>Why You Should Sign You Tars</subtitle>
<track>Fast Track (10m)</track>
<type></type>
<language></language>
<abstract>Talk to explain why KDE software should be released with GPG signatures, how to add them and how we try to ensure end-to-end trust in KDE neon.
</abstract>
<description></description>
<persons>
<person id='145'>Jonathan Riddell</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/346-end-to-end-trust.mp4'>Video</link>
</links>
</event>
<event id='353'>
<start>16:30</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_16:30_-_a_laptop_by_kde_-_apol_-_353</slug>
<title>A laptop by KDE</title>
<subtitle>How does KDE conceive a device?</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>We&#x27;ll go over the process we went through between the opportunity, the set up of the initial idea and how it evolved with time and different people&#x27;s contributions until we were able to have a product to deliver.

Furthermore, we&#x27;ll look into what&#x27;s the state of the project, what&#x27;s the next steps and whether could we replicate the experience.</abstract>
<description></description>
<persons>
<person id='16'>Aleix Pol Gonzalez</person>
</persons>
<links>
<link href='http://kde.slimbook.es/'>KDE Slimbook</link>
<link href='http://files.kde.org/akademy/2017/353-a-laptop-by-kde.mp4'>Video</link>
</links>
</event>
<event id='372'>
<start>17:10</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_17:10_-_looking_at_the_application_developer_story_-_ervin_-_372</slug>
<title>Looking at the Application Developer Story</title>
<subtitle>More Elitism Anyone?</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>We love to get new contributors and for that we need top notch technology and
a very welcoming community. In this talk we propose to look at our Application 
Developer Story and see what it says on how our technology and community 
perception.</abstract>
<description>After years organizing student projects it is time to admit it gets harder to
attract them to KDE contribution. Our technology is nice but our applications
are developed mostly like our frameworks which makes for a very steep learning 
curve for wannabe contributors. 
 
Also, the expectations of the hobbyist developer or the student have changed
radically in the past years. They are less keen to fiddle with build 
systems... which doesn&#x27;t mean they wouldn&#x27;t have anything interesting to 
contribute to our applications.

The aim of this talk is to kickstart the discussion in the community on how we
could walk toward a unified application developer story. For that we will take
a look at the different developer stories we present to potential application
contributors and how they fare. We will look at other ecosystems solutions 
used to address similar issues. Armed with this knowledge, we will present the
ideal application developer story we should strive for.

Finally, we will give a few ideas to improve the situation and will push the
audience to share more experience and ideas to get closer to the ideal 
application developer story.</description>
<persons>
<person id='124'>Kevin Ottens</person>
</persons>
<links>
<link href='https://ervin.ipsquad.net/slides/talks/ak2017-developer-story/'>Slides</link>
<link href='http://files.kde.org/akademy/2017/372-looking-at-the-application-developer-story.mp4'>Video</link>
</links>
</event>
<event id='356'>
<start>17:55</start>
<duration>00:30</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_17:55_-_c_17_and_20_-_ivan_home_-_356</slug>
<title>C++17 and 20</title>
<subtitle>Goodies we&#x27;ll be getting soon</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>C++ was asleep for a long time, but as Jon Kalb put it &quot;the beast is back&quot;. We are getting a new version of the standard every few years.

Also, the compiler support is getting better with each day, with GCC and Clang leading the bunch.

C++17 included a few interesting features and many technical specifications of the features planned for C++20.

We will cover quite a few of them - from ranges, through concepts, to coroutines.</abstract>
<description></description>
<persons>
<person id='155'>Ivan Čukić</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/356-c-17-and-20.mp4'>Video</link>
</links>
</event>
<event id='391'>
<start>18:35</start>
<duration>00:20</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_18:35_-_sponsors_presentations_-_391</slug>
<title>Sponsors Presentations</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract></abstract>
<description></description>
<persons>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/391-sponsors-presentations.mp4'>Video</link>
</links>
</event>
<event id='392'>
<start>18:55</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_18:55_-_akademy_awards_-_392</slug>
<title>Akademy Awards</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract></abstract>
<description></description>
<persons>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/392-akademy-awards.mp4'>Video</link>
</links>
</event>
<event id='393'>
<start>19:05</start>
<duration>00:10</duration>
<room>Room 1</room>
<slug>room_1_-_2017-07-23_19:05_-_closing_-_393</slug>
<title>Closing</title>
<subtitle></subtitle>
<track>Special</track>
<type></type>
<language></language>
<abstract></abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
</room>
<room name='Room 2'>
<event id='340'>
<start>10:40</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-23_10:40_-_qt_webgl_streaming_-_jefernan_-_340</slug>
<title>Qt WebGL Streaming</title>
<subtitle>Create network applications using QtQuick &amp; </subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>How to use the QtWebGL QPA plugin to access remote applications.</abstract>
<description></description>
<persons>
<person id='667'>Jesus Fernandez</person>
</persons>
<links>
<link href='http://blog.qt.io/blog/2017/02/22/qt-quick-webgl-streaming/'>Qt Quick WebGL Streaming</link>
<link href='http://blog.qt.io/blog/2017/03/24/webgl-streaming-raspberry-pi-zero-w/'>WebGL streaming in a Raspberry PI Zero W</link>
<link href='http://files.kde.org/akademy/2017/340-qt-webgl-streaming.mp4'>Video</link>
</links>
</event>
<event id='360'>
<start>11:20</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-23_11:20_-_supporting_content_creators_-_leinir_-_360</slug>
<title>Supporting Content Creators</title>
<subtitle>or Satisfying Your Inner Capitalist</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>Would it not be lovely if everybody was free to simply do what they wanted, without having to worry about the movement of small, coloured pieces of paper? Unfortunately that is not the world in which we live. So, how so you satisfy your need to eat and pay bills and the like when publishing on the KDE Store? How do you let people do so if you use the store, either as a consumer, or as a software developer? Well, take a seat, and you shall see!</abstract>
<description>The KDE Store is primarily used by people to provide a very great deal of free content for the software created by both the KDE community and other communities. However, while it does support paid downloads, there are other ways of supporting the amazingly creative people out there, who may not want to put a price tag on their content, but still want to pay their bills and eat food from time to time.

In this talk you will see what options exist, and how they are made available to both the creative people who provide their amazing content, and to people who want to make use of that content. Finally, we will touch on how you might use this in applications, using the KNewStuff frameworks.</description>
<persons>
<person id='549'>Dan Leinir Turthra Jensen</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/360-supporting-content-creators.mp4'>Video</link>
</links>
</event>
<event id='396'>
<start>11:50</start>
<duration>00:15</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-23_11:50_-_coffee_break_-_396</slug>
<title>Coffee Break</title>
<subtitle></subtitle>
<track></track>
<type></type>
<language></language>
<abstract>At Aulario IV: Complimentary coffee, juices, pastries and cake</abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
<event id='377'>
<start>12:05</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-23_12:05_-_translation_and_user_documentation_in_the_kde_community_an_overview_-_tosky_-_377</slug>
<title>Translation and user documentation in the KDE community: an overview</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>A working program is not enough if its potential users can not use it. The availability of translation and user documentation can make the life of the users easier. What does this mean in the KDE community?</abstract>
<description>Even if the knowledge of the English language is more widespread than in the past, a properly localized program can be accessed by more users, and translation is central part of it. On the other side, while the default behavior of a program should be &quot;good enough&quot;, not everything can be directly self-discoverable. User documentation (and its translation!) can&#x27;t simply go away. 
The talk will try to answer questions like: how are the translation and documentation processes implemented in the context of the KDE community? What are the challenges? What are the possible future developments?</description>
<persons>
<person id='184'>Luigi Toscano</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/377-translation-and-user-documentation-in-the-kde-community-an-overview.mp4'>Video</link>
</links>
</event>
<event id='330'>
<start>16:30</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-23_16:30_-_customizing_kde_plasma_5_in_kubuntu_-_franklin_-_330</slug>
<title>Customizing KDE Plasma 5 in Kubuntu</title>
<subtitle>Beautiful, amazing, but not easy to go</subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>We keep making our &quot;ezgo&quot; with KDE Plasma.  However there were a lot more difficulties when customizing KDE Plasma 5...</abstract>
<description>ezgo is a customized Linux distribution derived from Kubuntu, Lubuntu and Xubuntu.  In ezgo12 we used Kubuntu 14.04 and Plasma 4, which was wonderful and easy to customize.  However in Kubuntu 16.04 with Plasma 5, many things changed...</description>
<persons>
<person id='393'>Franklin Weng</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/330-customizing-kde-plasma-5-in-kubuntu.mp4'>Video</link>
</links>
</event>
<event id='376'>
<start>17:10</start>
<duration>00:30</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-23_17:10_-_mentoring_in_student_programs_-_rahulyadav_-_376</slug>
<title>Mentoring in Student Programs</title>
<subtitle></subtitle>
<track>Technical Talk</track>
<type></type>
<language></language>
<abstract>I recently mentored in Google Code-In would like to share my experience with everyone. During that time i felt that is room for improvement on our side with some small changes. I would also like to discuss some challenges faced by children while participating in the program.</abstract>
<description>Talking points :

1) About some student programs with stress on Google Code-In
2) Sharing my experiences and talking about how time intensive it was, challenges faced, response from students etc
3) Challenges : 
         a) Encouraging students to try harder tasks ( more code 
             intensive )
         b) Using some methodologies to help them setup the 
              project more easily [ Automation ,Videos ]
         c) Task Qualities
         d) Sharing/Discussing ideas and make them more 
              interested in contributing to community
4) Getting more mentors into the program : Explaining how 
     the amount of time mentoring consumes.
5) Showing some Student testimonials explaining their experiences along with some interesting statistics.</description>
<persons>
<person id='654'>rahul yadav</person>
</persons>
<links>
<link href='http://files.kde.org/akademy/2017/376-mentoring-in-student-programs.mp4'>Video</link>
</links>
</event>
<event id='398'>
<start>17:40</start>
<duration>00:15</duration>
<room>Room 2</room>
<slug>room_2_-_2017-07-23_17:40_-_coffee_break_-_398</slug>
<title>Coffee Break</title>
<subtitle></subtitle>
<track></track>
<type></type>
<language></language>
<abstract>At Aulario IV: Complimentary coffee, juices, pastries and mini-sandwiches</abstract>
<description></description>
<persons>
</persons>
<links>
</links>
</event>
</room>
</day>
</schedule>
