Antonio Terceiro

We have the fine tradition of having DebConf N share their experiences with DebConf N+1. The DebConf committee will also be present and we invite a core member of every team to come around and help with the knowledge transfer. The session will begin with a DebConf23 presentation.

Other people: Stefano Rivera Daniel Lange Abhijith PA Raju Devidas Bernelle Verster Sruthi Chandran Anupa Ann Joseph

Session to discuss possible locations for DebConf25! DebConf 24 is planned to be held in Haifa, Israel. But we have no plans for DebConf25, yet.

Other people: Stefano Rivera Daniel Lange Bernelle Verster

`autopkgtest` is a test automation tool for Debian packages, is at the heart of the [Debian Continuous Integration platform](https://ci.debian.net/), and more importantly, a central part of the contemporary Debian release process and quality control efforts. Having more packages with `autopkgtest` support helps both package maintainers and the collective effort of making high quality Debian releases. In this session we will help fellow maintainers with their questions about implementing or improving `autopkgtest` support for their packages. We like to hear your ideas about `autopkgtest` best practices and where you see room for improvement. So, in summary, if you want to learn about `autopkgtest` or want to discuss its use, please join.

Other people: Paul Gevers

How is DebConf organization going, in general, across years? What should we be investing time and energy in? This is the DebConf committee's annual in-person meeting at DebConf.

Other people: Stefano Rivera Daniel Lange Gunnar Wolf Bernelle Verster

autopkgtest is a test automation tool for Debian packages, and is at the heart of the [Debian Continuous Integration platorm](https://ci.debian.net/), and more importantly, a central part of the contemporary Debian release process and quality control efforts. Having more packages with autopkgtest support helps both package maintainers and the collective effort of making high quality Debian releases In this session we will help fellow maintainers with their questions about implementing or improving autopkgtest support for their packages.

Other people: Paul Gevers

By now, we should have conquered the hearts, minds, and bandwidths of Debian contributors all over the world. Traditionally, this is the right spot to present some statistics, give us all a final group hug. See you next year!

Other people: Anisa Stefano Rivera Jonathan Carter Gunnar Wolf Margarita Manterola Nattie Mayer-Hutchings Praveen Arimbrathodiyil Nicolas Dandrimont Andrew Martin Adrian Cater

The idea for this session it to get together and discuss all autopkgtest/Debian CI related aspects. If you have ideas on how to test your package but don’t know exactly how to wire things up for running with autopkgtest, want to share your joy and/or your frustration with the tools or with the environments, or have tips or questions on writing autopkgtest tests, this is for you. autopkgtest runs tests on binary packages. The tests are run on the package as installed on a testbed system (which may be found via a virtualization or containment system). The tests are expected to be supplied in the corresponding Debian source package. See autopkgtest(1) and /usr/share/doc/autopkgtest. Depending on which virtualization server you want to use, you need to install additional packages (schroot, lxc, lxd, or qemu-system) The migration software used by the Release Team (called britney) uses the results from autopkgtest of a package and it's reverse dependencies to determine if a package is ready to migrate to testing. A regression in any of these scheduled tests will block migration. Debian CI ([ci.debian.net](https://ci.debian.net "ci.debian.net")) runs autopkgtest against the entire Debian archive, Adding autopkgtest tests to your package will automatically make those tests run on Debian CI as soon as the package hits the archive. Salsa CI ([salsa.debian.org](https://salsa.debian.org]) can be used to run tests the moment changes are pushed to packaging archives hosted on that server.

Other people: Paul Gevers

We want to give you an update on the current status of the autopkgtest, autodep8 and debci packages and the ci.debian.net infrastructure.

Other people: Paul Gevers

Welcome to DebConf20! Feel at home, grab a drink and snacks, and feel welcome to join us in the largest auditorium we have ever had in the world. We sincerely hope you are not jetlagged and that the facilities are conveniently located. We will make our best effort for you to feel home. Along with all the usual chores, doing the dishes, taking care of the kids, and so on. This session will... Well, basically serve the social purpose of saying "hello and welcome", and kickstarting our exciting week of online activities. We know that it's not the DebConf we usually have every year, but we are striving to provide the closest possible experience to it!

Other people: Judit Foglszinger Anisa Stefano Rivera Daniel Lenharo de Souza Luna Jernberg Gunnar Wolf Sruthi Chandran Nattie Mayer-Hutchings

It's time to finish the show! Let's say goodbye to Curitiba.

Other people: Daniel Lenharo Giovani Ferreira Lucas Kanashiro Samuel Henrique Adriana Costa

Assembléia Geral Extraordinária do ICTL. Se você não é associad@ ao ICTL não tem problema aparecer. Nós temos umas questões burocráticas pra discutir, e isso tende a ser chato, mas se conseguirmos vencer essa pauta rápido, podemos trocar idéias sobre o ICTL em geral.

The content team meets to discuss what we can improve for Debconf 2020.

Other people: Guido Trotter

The Ruby team maintains over 1500 packages in Debian. I have been active in the Ruby team for a while now. And I believe that we, the Ruby team, as a whole, can improve on a lot of things, like, sponsoring new contributor's packages, taking sessions, etcetera. During the BOF session, I'd be discussing a few topics like them, which would encourage more new contributors to join the team and help us in the maintenance of all the gems and applications. Moreover, something that worries me is the "retainment rate" of the new contributors. If this continues, then after few years down the line, the Ruby team would be in a little trouble. There are a lot of packages under the team and so is the need for more contributors. And it'd be lovely to have more DMs and DDs emerging out in this process :)

Other people: Utkarsh Gupta Lucas Kanashiro

Welcome to Curitiba! Opening Ceremony for DebConf19, practical information, and all sorts of Q&A.

Other people: Paulo Henrique de Lima Santana Daniel Lenharo Giovani Ferreira Lucas Kanashiro Samuel Henrique Adriana Costa

In this session we will introduce Open Day, give practical information, and have an open Q&A, addressing the rest of the day as well as DebConf proper which starts the next day.

Other people: Paulo Henrique de Lima Santana Daniel Lenharo Giovani Ferreira Lucas Kanashiro Samuel Henrique Adriana Costa

The idea for this session it to get together and as discuss all things autopkgtest/Debian CI and any related aspects. If you have ideas on how to test your package but don't know exactly how to wire things up for running with autopkgtest, want to share your joy and/or your frustration with the tools or with the environments, or have tips or questions on writing autopkgtest tests, this is for you. autopkgtest runs tests on binary packages. The tests are run on the package as installed on a testbed system (which may be found via a virtualisation or containment system). The tests are expected to be supplied in the corresponding Debian source package. See adt-run(1) and /usr/share/doc/autopkgtest. Depending on which virtualization server you want to use, you need to install additional packages (schroot, lxc, lxd, or qemu-system) Debian CI (ci.debian.net) runs autopkgtest against the entire Debian archive, Adding autopkgtest tests to your package will automatically make those tests run on Debian CI as soon as the package hits the archive.

This talk is based in a paper I have published where I describe a pattern language (as in "design patterns") for automated software testing in production-like environments (a.k.a autopkgtest/DEP8 for us Debian people). The patterns describe common problems and solutions for testing Debian packages, and should be useful for maintainers willing to add tests to their packages. [Full text of the paper (PDF)](https://gitlab.com/terceiro/installed-tests-patterns/raw/pdf/final/installed-tests-patterns.pdf)

I recently adopted pristine-tar, because it has been orphaned for a while and it is a critical piece of infrastructure for several teams and individuals. I am not completely familiar with its internals yet, and would love to get more people onboard, among other reasons, to not have me being a single point of failure.

From the package description: autopkgtest runs tests on binary packages. The tests are run on the package as installed on a testbed system (which may be found via a virtualisation or containment system). The tests are expected to be supplied in the corresponding Debian source package. See adt-run(1) and /usr/share/doc/autopkgtest. Depending on which virtualization server you want to use, you need to install additional packages (schroot, lxc, lxd, or qemu-system) autopkgtest is what Debian CI (ci.debian.net) runs, so adding autopkgtest tests to your package will _automatically_ make those tests run on Debian CI as soon as the package hits the archive. The idea for this session it to get together and write/review autopkgtest test suites as well as discuss any related aspects. If you have ideas on how to test your package but don't know exactly how to wire things up for running with autopkgtest, let's look at that together.

The annual DebConf gathering of the Ruby team, to discuss open issues and plans for the future.

Beyond being used at the Debian CI (ci.debian.net) and the Ubuntu autopkgtest website (autopkgtest.ubuntu.com), debci can be customized to a multitude of use cases, such as: running only a small subset of packages, This session is intended at helping interested people to bootstrap a development environment and start contributing with debci to increase the bus factor.