Speakers and Talks

Chromium's process architecture has graphics access restricted to a separate GPU-process. There are several reasons why this could make sense, three common ones are: Security, Robustness and Dependency Separation.

GPU access restricted to a single process requires an efficient framework for communication over IPC from the other processes, and most likely a framework for composition of surfaces. This talk describes both the possible motivations for this kind of architecture and Chromium's solution for the IPC framework. We will demonstrate how a multiprocess program can compose into a single window on Linux.

Take a moment to ask yourself, "what are Pull Requests for?"

Typically PRs are used as a means to communicate that some body of work has been done and is ready to be merged. But is this an optimal use of PRs? If we submit a PR after the work has been completed, have we missed a golden opportunity to collaborate?

PRs should be treated like the basic unit of collaboration within GitHub-based projects. By using PRs as communication medium and not simply as a review mechanism, we can create opportunities to communicate better within our projects, enhance the on-boarding of new contributors and help catch potential problems early.

In this short talk, I show off the good, the bad and the ugly of PRs and provide a template for best practice which encourages communication and collaboration within your community.

VR took off for the consumer with the release of Oculus consumer hardware. But the hardware lacked open source drivers and Linux support in general. The OpenHMD project was created to solve this issue, and as it so happen it was funded by two former Chalmers students.

The consumer VR space has now grown from a crazy inventor in a garage into a large industry. But this growth has its down sides, multiple companies have their own APIs competing. Luckily these companies have agreed to work on a single API under the Khronos umbrella

In this talk, Jakob will cover Khronos' OpenXR standard, give an overview about the current state of open source VR and what lies ahead.

Bring back to life an old software is easy nowadays, you spin some virtual machine with the older operational system and run it (or even compile it).

Bring it back to RUN in modern systems ? This is a completly different history.

Not talking on a full refactoring, or a port of the software, but bring s the real software with none to minor modifications.

There's plenty of reasons to do that, from historical software archeology to real requirements on closed software companies that need to at least access some proprietary format to export for a different used one.

What was done on KDE 1 ( and KDE 2 at the moment ) was an patient exercise in find the best solutions without properly destroy the code, and what is intended on here, is show steps tooke for the process, that can be easily applied to several other cases.

At Integrify Sweden we help newly come software developer immigrants to kick off their careers in Sweden! We sponsor high paced agile projects to allow new immigrants to get an insight of how software development is done in Sweden.

I just want my device to send data somewhere. How hard can it be?

The right IoT platform lets your devices send data somewhere, in a reliable and secure way, and you don't have to care how. This is a talk for those who care about the "how" part, with focus on open source building blocks. What is the basic functionality I need in my cloud? Why do I need this functionality? Then what? There are plenty of questions, let's explore some answers.

Finally, it is possible to run Android on top of mainline Graphics! The recent addition of DRM Atomic Modesetting and Explicit Synchronization to the kernel paved the way, albeit some changes to the Android userspace were necessary.

The Android graphics stack is built on a abstraction layer, thus drm_hwcomposer - a component to connect this abstraction layer to the mainline DRM API - was created. Moreover, changes to MESA and the abstraction layer itself were also needed for a full conversion to mainline.

This talk will cover recent developments in the area which enabled Qualcomm, i.MX and Intel based platforms to run Android using the mainline graphics stack.

On 4 July 2017, one billion people – a large portion of our planet’s population – took time out of their day to watch a one-and-a-half-hour scientific seminar featuring plots, graphs, Greek letters, and comic sans. Why? A deep-rooted survival instinct told these people that the discovery by CERN scientists of a fundamental component of our universe was something worth paying attention to. Or they were just news junkies. But, they were right.

Today, at CERN, and other physics laboratories around the world, we are seeking answers to the most fundamental questions of humankind: What are we made of? Where did we come from? Where are we going? What are the rules behind all this? Although we might never find the answers, the pursuit of them provides us with the knowledge and skills our children need to survive. I discuss current puzzles in particle physics and cosmology, then challenge us to keep opening our research (data, source, results) to take advantage of our culturally rich, diverse population.

This talk gives a quick overview of aspects of Open-Source governence -- the importance of licensing, of structures, of process and procedures and some codified behaviors -- and explains how the KDE community implements them. We also discuss ways in which the governance could be improved.

Sailfish X is a downloadable version of the Sailfish OS for Xperia mobile phones. This speech presents how Jolla, a small company from Finland, created the OS, and the downloadable Sailfish X in collaboration with Sailfish community and partners.

Sailfish 3 is the latest generation of the Sailfish OS. Sailfish 3 brings updates to many core components of the OS like Qt and Android app support. Sailfish 3 supports new device categories including wearables and feature phones, and the OS gains many improvements for security and corporate features.

The bug that could had sabotaged a year of work on Firefox didn't slip into production because of the efforts of engineers, program managers, and management to triage bugs. But how do you triage 9,000 bugs over the course of a three month release cycle and not burn out? How do you measure hotspots? And how do you make it sustainable? The Firefox team's bugmaster, Emma Humphries, reports on what one of the largest and longest-lived open source projects learned while building this milestone version of the beloved web browser.

Crowdfunding campaigns enable individuals to bring their ideas to production by appealing directly to the end-market and the global community. A number of these projects are open source, seemingly, counteracting the funding process.

We interviewed founders, developers and managers of 13 crowdfunding initiatives involving open source products to determine how communities, crowdfunding campaigns and open source are associated.

Our findings verified the existence of common characteristics among the cases, the emergence of a family-like relationship between the organizers and the community, as well as the community perceived as a success factor. We suggest that the development of certain niche products inherently leads to the adoption of open source as a licensing model and crowdfunding as the capital gathering process.

Software updates on embedded Linux devices has for a long time been a mess, consisting of "homegrown" solutions specific to a certain project and there was very little re-usage between projects and very little collaboration in our community to solve these complex problems. Luckily for us that time is over and the community around this topic has grown over last couple years and still is growing as the demand increases with the IoT revolution and OTA firmware updates (which introduces even more complexity).

There are now well established open-source solutions that have been "battle tested" that we can collaborate on to make the complexity of software updates manageable. We are heading for a time where a quality Board Support Package should provide an software update implementation because it really should be solved at this level instead of handing this over to application developers which have limited knowledge of low lever architecture on a embedded device.

In this talk Mirza will present some of the challenges of doing software updates on embedded system. He will also present the available open-source projects that help with solving these challenges. The projects are: SWupdate, Mender, RAUC, aktualizr (libostree) and resin.io.

He will also do a head-to-head comparison of them. There is no "one fits all" solution and each one has different goals and approaches to solving the problem. This is something that we have come accustom to in the open-source community and is how we thrive.

In an age increasingly concerned with reducing bugs as well as complying with free software licenses, it is vitally important to thoroughly review audit any changes to the software that powers our technology and infrastructure.

However, existing tools to perform comparisons between two versions of a software package are overly-blunt instruments, either providing too much output or none at all. Binaries such as firmware images or precompiled executables are especially problematic: a single change in the source is presented as a meaningless stream of changes, offering no insight into potentially critical bugs. And these are often precisely the files we care most about…!

Diffoscope is different. Developed as part of the Reproducible Builds effort, it gets to the bottom of what makes files truly different. It recursively unpacks archives of all kinds and transforms various formats into human-readable forms for display. It can compare two tarballs, ISO images, PDFs, Microsoft Word documents, etc. just as easily.

This talk explains the varied and practical usages of diffoscope and how this flexible "diff on steroids" is a long-overdue and fun tool for anyone writing or releasing software today.

How you can implement a lockless inter-process communication (IPC) mechanism on top of shared memory and nothing else. The talk will cover the details of how the speculo library handles its shared memory areas and how a stream of messages can be implemented on shared memory. Despite being low-level, the session does not require knowledge of algorithms or a strong background on IPC.

The talk might touch some philosophical considerations about the evolution of software solutions.

Out of all the Embedded Linux Build System solutions why is the Yocto Project so popular?

This talk aims to introduce the audience with the Yocto Project: how is it different from the other solutions, as well as its architecture and community.

Furthermore, as the focal point of this talk, Gordan will present the reasons why the Yocto Project is his go-to option when creating Embedded Linux solutions. His analysis is be based on personal experience from several different industries, the difficulties faced and the solutions found.

Zipper is an Ethereum based mobile platform which brings blockchain based services to our smartphones in one seamless and user-controlled experience.

At first, Zipper provides everyday smartphone users an easy and safe way to manage their identity and private keys. This makes it possible for anyone to access blockchain based services out-of-the-box in an easy and intuitive way - just like Apple’s services on iOS today - while being in full control of their identity, transactions and data. Zipper works in an isolated compartment in Android and Sailfish OS smartphones, making Zipper and its wallet secure while still easily accessible.

Bad design causes panic and misery, and in some cases, it’s literally lethal. A lot of software is only tested in production, leading to overwhelming amount of support calls and unhappy peers.

Do you wish that people would give you design feedback before you hit the deploy button?

In this talk I’ll show you how you can anticipate design issues using simple user testing methods. These methods will streamline your development process as well as increase the impact that your project has on your community through more intentional design.

I’ll be sharing my experience user testing Cockpit, a server management web console for Linux boxes, and how it has improved the experience we deliver to our customers.

The Nordic Free Software Award is given to people, projects or organisations in the nordic countries that have made a prominent contribution to the advancement of Free Software.

There are quite many closed solutions for home automation like Telekom's agenta SmartHome, Google Home, Apples HomePod, etc. What most of them have in common is that they don't like to play with the rest of the eco system.

Home Assistant is an open-source home automation platform running on Python 3 with a humongous amount of integration into all sorts of systems. Track and control all devices at home and automate control. Perfect to run on a Raspberry Pi.

In this talk Jeena will explain how he automated his home, what hardware he used and what it took to integrate it with Home Assistant.

The Atari ST was released in 1985, with a simple but efficient operating system: TOS. Later, a multitasking kernel named MiNT was adopted by Atari, and finally released as Free Software under the name FreeMiNT. GCC was ported to FreeMiNT and allowed to compile many other GNU software for the Atari platform. Emulators appeared in the '90s. As Atari TOS is still non-Free, independent developers created EmuTOS: a Free TOS clone based on open-sourced components. GCC was later upgraded to newer versions, and ready-to-use binaries of the cross-compiler were made available for Ubuntu, Cygwin, and more. This brought a new impulse to the platform. EmuTOS and FreeMiNT are still actively developed nowadays. They have been improved over the ages, and extended to support special features of emulators as well as extra hardware. They even support non-Atari hardware, such as Amiga and ColdFire processor. Moreover, development environment has been modernized to use GitHub facilities and Travis CI for automatic builds. This is a good example to see how modern tools can advantageously be used for development on old platforms.

The IT industry is a diverse and dynamic world where applications and functions may be spread out - and move between a multitude of providers and technologies such as Amazon AWS, Rackspace, KVM, volatile containers, and your internal traditional IT infrastructure with physical servers.

Monitoring all of these might require one monitoring tool per platform, or at least a few to seamlessly blend metrics, events and logs to get true Observability on your environment. OP5's intention is to address this with Project Omega. Designed from the ground up using cloud-native technologies packaged in a container environment to be running on premise or as SaaS, scaling horizontally with Kubernetes.

Initially the focus is on monitoring OpenStack with the Monasca project and developing the agent in and for the community providing patches and reviews since the Queens release of OpenStack, using modern REST API’s, time series database for metrics, message queues using Kafka and preparing the stack to for real-time analysis using Apache Storm.

The first thing that jumps to one's mind when someone mentions "pooling" in the context of media codecs is usually patents. Alliance of Open Media's first codec, AV1 breaks this stereotype by actually pooling *contributors*, as it consolidates the best parts, ideas and developer talent of Google's AV9/AV10, Cisco's Thor and Xiph's Daala codecs into a royalty-free and open source video codec that's not only supported by several other industry giants like Microsoft, Netflix and Apple, but is set to even beat the top-of-the-line (and patent-encumbered) HEVC codec in compression ratio. Mozilla Research has been a contributor to the development of Daala for years now and as AV1 shapes up to be the open and free codec the Internet always deserved (and one Mozilla has been fighting for) the Emerging Technologies division have further upped the stakes. As developing a cutting-edge codec requires cutting-edge technologies, Mozilla's ET division has been working on various, distributed browser-based tools to ease collaboration and hasten the solidification of such a diverse codebase.

In the talk I will introduce AV1, what industry dynamics contributed to its inception and how Mozilla has developed and employed several, in-browser tools, incorporating bleeding-edge technologies like Emscripten-compiled library modules in ASM.js and WebAssembly to help the contributors iterate and bugfix newer versions of the bitstream itself, as well as the encoder and decoder.

This is both a talk and a workshop to get you kickstarted with Python on a micro controller in no time.

You will learn how to put the MicroPython firmware on a NodeMcu (ESP8266) development board, write some code in interactive, use som cool libs like the Neopixel and HTTP to achieve awesome blinkenlights.

This workshop is aimed at beginners, including the more advanced programmers who never touched electronics.

You are required to bring a laptop and some basic programming knowledge (no, not BASIC the language, basic as in beginner).

There is a limited set of hardware that participants can keep after the workshop. First come, first served!