about

Hi, I'm Scarlett.

I'm a technology professional whose career has taken me from systems administration to Linux distribution engineering, software packaging, and open-source development. I hold a BS in Computer Information Systems from DeVry University. These days, I'm also training as a property tax appraiser with Apache County, Arizona.

How I found my way into technology

My career didn't begin in software or even in IT. I started out as a secretary. Somewhere along the way, people noticed I was good at figuring things out and saw that I had a knack for technology. That opened the door to a network administrator position, and I kept moving forward: first into Linux administration, then into systems management.

Linux became a big part of that journey. I started back in the days when installing Red Hat meant feeding your computer something like ten floppy disks. It was a very different world from today's distributions, but I was hooked. Learning how systems fit together, solving problems, and making technology work became the thread connecting each stage of my career.

A move to the East Coast, after my husband was relocated, changed the direction of my career. I found it extremely difficult to get hired into traditional IT roles there; being a woman in that environment often meant that doors simply didn't open. So I adapted and made a pivot into software. That change turned out to be the beginning of a new chapter, bringing together my systems background and a growing interest in building, packaging, and maintaining software.

The open source side

Open source has been the thread running through much of my working life. What began with KDE documentation in 2012 grew into Linux distribution packaging, reproducible builds, continuous integration, release engineering, and years of maintaining software and infrastructure that other developers depend on. I've worked across the KDE, Kubuntu, Ubuntu, and Debian communities, often moving between the application, distribution, and build-system layers to help make the whole stack work.

My work has ranged from packaging individual applications and libraries to designing CI systems, maintaining runtimes, and helping plan complete distribution platforms. The tools have included Jenkins, GitLab CI, Docker, LXD, Snapcraft, AppImage, and multi-architecture build environments across AMD64, ARM64, and ARMHF, with development and packaging in Python, Ruby, C/C++, and Bash.

From reproducible builds to Debian

My early Debian work began through an Outreach program, which led to an opportunity with the Linux Foundation to work on the emerging reproducible builds effort. I helped make a range of software packages reproducible, including CMake. The goal was important to the wider free software ecosystem: making it possible to independently verify that a source package produces the same binaries when built again.

As my career moved increasingly toward continuous integration and build infrastructure, my Debian work evolved too. I began contributing with the Debian KDE and Qt team, and later spent time in Python packaging, including work with Mycroft before the company sadly ceased operations.

Those different paths eventually led to my becoming an official Debian Developer, with upload privileges. My contributions there have been quieter in recent years as other professional and community commitments have taken priority. I'm still a Debian Developer, and I value that part of my open-source journey; I also recognize that I have some contribution backlog to work through when time allows.

Finding my way into Kubuntu

My KDE story and my Kubuntu story began side by side. After my first KDE documentation contributions in 2012, Jonathan Riddell — one of the people whose work made Kubuntu possible — approached me and asked whether I'd be interested in helping with the project. I said yes, and that invitation began my journey into Linux packaging.

It was an especially interesting time to join. KDE was breaking up the monolithic kdelibs codebase into the smaller, modular KDE Frameworks, and I helped package that major transition for Kubuntu and get the work integrated into Ubuntu. That was my introduction to the depth and complexity of distribution packaging: not just building software, but making a large, interconnected stack work reliably for users.

In those early days, Kubuntu had a remarkable team. We worked hard, built things together, and for a while became a familiar part of the wider Linux ecosystem. I was a significant part of the original team that went on to create KDE neon: a new distribution bringing the latest KDE software to users on a stable Ubuntu LTS foundation, with continuous integration driving its builds and integration. Being part of that team and helping bring the original OS into existence was a defining part of my KDE and Kubuntu years.

Over time, the team went in different directions, moving on to different projects and careers. KDE Neon is still alive today, sustained by a very small volunteer effort. I'm no longer part of its day-to-day maintenance, but the work we did together remains an important part of my history in KDE and Ubuntu.

Returning to Kubuntu

My Kubuntu story didn't end with those early years. I was later brought back for the Noble release. It was a chance to return to a project that had been a formative part of my career, and to contribute again as a Kubuntu Developer.

More recently, Kubuntu Focus brought me on for the Resolute LTS release and the early stages of the Bulletproof KDE software initiative. That work has since been taken over by Techpaladin, a new company formed by members of the Blue Systems team. I don't work for Techpaladin, but I wanted to acknowledge the team: they're good people, and I wish them well as they carry the work forward.

Growing KDE Snaps from an idea

KDE Snaps have been one of the longest-running and most hands-on parts of my open-source work. I was at the conference where Canonical introduced the Snap concept. After the presentation, I approached the speaker and asked whether it would be okay to take that concept and use it to create Snaps for KDE applications. They were enthusiastic about the idea, and that conversation helped set the KDE Snaps effort in motion — a project that has stayed with me ever since.

I've been involved with KDE Snaps from those early days and have been their solo maintainer for much of their existence. That has meant far more than packaging applications: it has meant keeping the infrastructure working, solving build and runtime problems, adapting to changes in Snapcraft and the KDE stack, and doing the persistent maintenance that keeps software available to users. A lot of that work has happened behind the scenes, one bug, build, and release at a time.

Much of this has been volunteer work — a substantial investment of time, energy, and plenty of blood, sweat, and tears — with the occasional short-term contract along the way. I'm especially glad that the work is being funded now. Being paid for it is a welcome change, and a meaningful recognition of the years of effort that went into building and sustaining it.

The work is still evolving. I'm currently focused on the next generation of KDE Snap infrastructure, including KDE Neon support in Snapcraft and the move toward Core26 runtimes. It's a continuation of that original conversation: taking an idea and doing the practical, sometimes difficult engineering needed to make it real and keep it going.

Developing the KDE Neon Core vision

My work with KDE has also extended into product and business planning. I developed a full business plan for KDE Neon Core — a complete operating system initiative built on Ubuntu Core, distinct from the existing KDE Neon desktop distribution. Although I didn't ultimately lead the project myself, enioka took up my proposal and brought it forward, helping deliver the work for Core24.

When enioka was engaged again for Core26, they invited me back to contribute. It's been rewarding to see the KDE Neon Core vision continue to evolve, and to be part of the next stage of that work.

Community involvement

Community has been an important part of my open-source work. 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.

Finding my place in open source

My first open-source conference was in 2014. In those early days, I was often one of the only women in the room. It wasn't always easy navigating that environment, but I found my place through the work, the people who became friends and collaborators, and a shared passion for building better software. I'm genuinely happy to see the community becoming more diverse and welcoming, and I hope the next generation of women entering open source finds more doors open than I did.

The day job

In a bit of a career pivot, I'm now venturing into property appraisal with Apache County, Arizona as a Property Appraiser I. Arizona's dual valuation system, legal classifications, assessment ratios, and the three approaches to value keep things interesting. I'm enjoying learning an entirely new discipline from the ground up.

St. Johns is a long way from a Jenkins server, but the systematic thinking translates surprisingly well.

This blog

This is my engineering notebook: a place for practical write-ups about Linux, KDE, Kubuntu, Snapcraft, packaging, CI/CD, and the occasional lesson from working across two very different disciplines.

Get in touch

emailsgmoore@debian.orggithubgithub.com/scarlettgatelymoorelinkedinlinkedin.com/in/scarlettgatelymoore