A selection of the ecosystems, tools, and infrastructure I've worked on. Much of this work happens in collaboration with upstream developers and volunteer communities; these notes highlight the engineering problems and the solutions, not just the project names.
KDE Snaps & shared runtimes
I helped bring the Snap model to KDE applications after Canonical introduced the technology, and have been involved with KDE Snaps from the early days — serving as their solo maintainer for much of the project's existence. The work spans application packaging, shared KDE content snaps and runtimes, Qt/KF integration, and the ongoing maintenance that keeps the ecosystem usable.
My current engineering focus includes the KDE Neon Snapcraft extension, Core26 support, launcher and environment integration, and GPU compatibility across Snap base generations.
KDE · Snapcraft · Qt6 · KF6 · Core26 · Ongoing
KDE Neon Core
I developed the business plan for KDE Neon Core: a complete operating-system initiative built on Ubuntu Core, not the existing KDE neon desktop distribution. enioka took up the proposal and brought the work forward for Core24, then invited me back to contribute to the Core26 effort.
KDE · Ubuntu Core · Product planning · Core24 / Core26
KDE continuous integration
During Season of KDE, I built the first iteration of KDE's continuous integration infrastructure, hosted at build.kde.org and powered by Jenkins. That work helped establish automated build infrastructure for KDE's development ecosystem and became a turning point in my engineering career.
KDE · Jenkins · CI/CD · Foundational work
KDE neon — original team
I was a significant part of the original team that brought KDE neon to life: a new way of delivering the latest KDE software on a stable Ubuntu LTS base, with CI-driven builds and integration at its heart. This grew out of the close collaboration and experience of the early Kubuntu team, and became one of the defining projects of that chapter of my career.
KDE · Ubuntu LTS · CI-driven distribution · Original team
Kubuntu & Ubuntu packaging
I joined Kubuntu in 2012 and began my packaging work during the transition from monolithic kdelibs to modular KDE Frameworks, helping package the effort for Kubuntu and integrate it into Ubuntu. I later returned for the Noble release and contributed to the Resolute LTS release and early work on the Bulletproof KDE software initiative through Kubuntu Focus. That work has since moved to Techpaladin, whose team I wish well.
Kubuntu Developer · Kubuntu Council · Ubuntu · Packaging
Reproducible builds
Through an early Outreach program, I was hired by the Linux Foundation to contribute to the early reproducible builds effort. I worked on making software packages reproducible, including CMake, helping improve the ability to independently verify that builds can be recreated from their source.
Linux Foundation · Reproducible Builds · Packaging
DCI & Netrunner
After my KDE CI work, I joined Blue Systems to maintain DCI, a Debian-based continuous integration system that underpinned the Netrunner distribution. This brought together my experience in Debian, build automation, and the practical engineering of a Linux distribution.
Blue Systems · Debian · CI/CD · Netrunner
Debian packaging & Python
My Debian work has included contributions with the Debian KDE/Qt team, Python packaging work with Mycroft, and earlier reproducible-builds contributions. I am an official Debian Developer with upload privileges. My Debian activity is quieter while I balance other commitments, but it remains an important part of my open-source work.
Debian Developer · KDE/Qt · Python · Packaging
Open-source community service
Alongside engineering, I've served two terms on the Ubuntu Community Council, first around 2015 and then returning for a second term more recently. I'm also a member of KDE e.V. and the Kubuntu Council, staying involved in the communities and projects that have shaped my career.
Ubuntu Community Council · KDE e.V. · Kubuntu Council