2026-06-16 –, Topaz + Quartz
Two years ago, Microsoft established the Community Linux Engineering team. Last year at Flock, we shared our first year of work with Fedora. This session covers what we delivered in year two, our plans for the year ahead, and why we continue to invest in Fedora.
First, we'll look back at the past year and highlight work we shipped. We automated Fedora Cloud image testing on Azure using LISA (Linux Integration Services Automation), Microsoft's open source testing framework for validating Linux distributions across Azure, HyperV, and other platforms. The signing infrastructure work mentioned at Flock 2025 is nearing completion, with a separate talk submitted on that topic. Various improvements to the WSL image were delivered in Fedora 43. We remain active contributors to the Fedora Cloud SIG and continue to help “keep the lights on” with maintenance work on packages like cloud-init.
We'll share consumption data for Fedora in the Azure Community Gallery, where Fedora was a launch partner in 2024, and present usage trends for Fedora on WSL.
Next, we'll discuss work planned for the year ahead, building on the testing and infrastructure foundations we've built. Of particular interest to the team is enabling post-quantum signatures for RPMs and other artifacts, investigating Unified Kernel Images (UKIs) for, among other things, the Azure cloud images, and ensuring those UKIs contain PCR signatures.
Finally, we'll wrap up by talking about why Microsoft commits resources to the Fedora Project and what we hope to accomplish through this effort.
I work at Microsoft on the Linux Community Engineering team with a focus on Fedora.
I've worked on various Fedora infrastructure tools and projects. Most recently I've focused on signing services and tools to push images we build to popular public clouds. Previously I worked on infrastructure tools like fedora-messaging, release-monitoring.org, and bodhi. I also spent some time as a Fedora kernel maintainer.