Holger Levsen

For more than two decades I’ve been using Debian as my primary and only OS on my primary computer (and almost all others computers I’ve been touching), and in February 2017 I finally made the switch and installed Qubes OS, which currently is based on Fedora 23 (while 26 is their latest release).

That said, I’m still (mostly) running and developing Debian inside Qubes OS, as - very roughly said - Qubes OS is just another virtualisation layer between the CPU and the user.

So in this talk I will explain in more detail what Qubes OS is, what advantages using Qubes OS brings, what downsides it has and how I made my transition to a more secure setup, and what challenges I faced. Of course I’ll also explain why I went with using the Fedora based Qubes OS instead of porting it to Debian and what options there are for a future with a Debian based Qubes OS.

https://qubes-os.org https://wiki.debian.org/Qubes https://wiki.debian.org/Qubes/Devel

Whilst anyone can inspect the source code of free software for malicious flaws, software in Debian is distributed pre-compiled to end users.

The motivation behind the Reproducible Builds effort is to permit verification that no flaws have been introduced — either maliciously or accidentally — during this compilation process by promising identical results are always generated from a given source, thus allowing multiple third-parties to come to a consensus on whether a build was compromised.

This talk will explain the current status of the Debian Reproducible Builds project, what has changed in the last year, how this is relevant to you as a maintainer, and how this is relevant for the complete free software eco system and, finally, how you can contribute.

jenkins.debian.org shall become what jenkins.debian.net is, except it should run (the service) on a DSA maintained system (some of the nodes doing the work might not be DSA maintained…)

This workshop is about the transition from jenkins.d.n to jenkins.d.o and how we can make it happen and how we can make it good.

It will also give an overview about the 1400 jobs running on jenknis.d.n and how to contribute new jobs or modify existing ones.

Currently piuparts.debian.org only tests Debian amd64. In this BoF we want to discuss how to scale this to multiple architectures and possible how to rewrite the web UI so that it scales with both more architectures as well as with 10 times more suites than it was written for.

Basically if you are interested to help by writing a nice(!) webapp, you should attend this BoF. Or to put it differently: if you want to help Debian, but don’t know how, this could be your opportunity to contribute to a rather central QA tool in Debian!

Scaling piuparts to support multiple architectures could be done using two ways: the dumb and the smart way, where the latter uses a bit less hardware ressources but will require a bit of python coding. Join if you want to help here. (Also, we could start with the dumb way and later switch to the smart way…)