Debian Maintainer vs Debian Developer Differences
In the Debian ecosystem, the package workflow and governance structure rely heavily on two contributor tiers: Debian Maintainers (DMs) and Debian Developers (DDs). While both roles allow individuals to maintain and introduce software into the official Debian archives, they fundamentally differ in their package upload privileges, access to project infrastructure, onboarding rigor, and governance rights within the Debian Project.
Package Upload Permissions
The primary operational difference between a Debian Maintainer and a Debian Developer lies in their level of autonomy when pushing packages to the Debian archive.
- Debian Maintainer (DM): A DM has limited, package-specific upload permissions. They cannot upload arbitrary packages. Instead, a full Debian Developer must grant them explicit permission to upload specific packages that the DM actively maintains. Furthermore, DMs cannot introduce completely new source packages into the archive on their own; new packages must always be sponsored and initially uploaded by a Debian Developer.
- Debian Developer (DD - Uploading): An uploading Debian Developer holds unrestricted access to the Debian archive. They can upload new packages directly, modify existing packages, and perform "Non-Maintainer Uploads" (NMUs) to fix critical bugs in other maintainers' packages across the distribution. Additionally, DDs have the authority to grant upload permissions to DMs and act as sponsors for new contributors.
Governance and Voting Rights
Debian operates as a democratic project governed by the Debian Constitution, but voting privileges are strictly defined by membership status.
- Debian Maintainer: DMs are not formal members of the Debian Project. Consequently, they do not possess voting rights. They cannot vote in General Resolutions (GRs), participate in the annual Debian Project Leader (DPL) elections, or stand as candidates for official project roles.
- Debian Developer: DDs are recognized as official members of the Debian Project. Regardless of whether they are uploading developers or non-uploading developers (such as translators, documentation writers, or infrastructure administrators), all DDs have full voting rights on project decisions, constitutional amendments, and leadership elections.
Infrastructure Access and Identity
Official Debian infrastructure access distinguishes maintainers from full project members.
- Debian Maintainer: DMs do not receive an official
@debian.orgemail alias. They also lack direct shell access to Debian Project machines and internal build infrastructure. Their cryptographic GPG keys reside in a distinct, limited-access keyring managed by Debian's archive software (dak). - Debian Developer: Upon acceptance, DDs are granted
an
@debian.orgemail address, access to the Debian LDAP database, and shell access to project servers and porter machines used for debugging architecture-specific issues. Their GPG keys are added to the authoritative Debian Developer keyring.
The Application and Vetting Process
Achieving DM status is designed to be a lightweight milestone, whereas becoming a DD requires extensive vetting.
- Debian Maintainer Process: The DM process focuses strictly on basic technical competence and identity verification. An applicant must possess a valid GPG key signed by at least one Debian Developer and demonstrate prior maintenance work through sponsored uploads. Once endorsed by existing DDs, the Debian Account Managers (DAM) review and approve the application relatively quickly.
- Debian Developer Process (New Member Process): Becoming a DD requires undergoing the comprehensive New Member (NM) process. Applicants work with an Application Manager (AM) to complete rigorous checks across multiple areas: identity verification, deep technical packaging competence, and an in-depth understanding of Debian's philosophy, including the Debian Social Contract and the Debian Free Software Guidelines (DFSG). Final approval must be granted by both the Front Desk and the Debian Account Managers.