Differences between revisions 26 and 27
Revision 26 as of 2007-12-10 09:09:19
Size: 4400
Revision 27 as of 2008-01-08 09:57:36
Size: 4500
Deletions are marked like this. Additions are marked like this.
Line 24: Line 24:
 * submit a jetring changeset as a patch to the bug tracking system, filed against the [http://packages.qa.debian.org/debian-maintainers debian-maintainers package]
 * submit a bugreport with a jetring changeset to the bug tracking system, filed against the [http://packages.qa.debian.org/debian-maintainers debian-maintainers package]. Use only URLs from debian.org for the agreement and advocates fields of the jetring changeset.


Debian Maintainers are people who are not full developers but have a restricted ability to upload packages to the Debian archive.

The Debian Maintainers concept was introduced on 5th August 2007 by [http://www.debian.org/vote/2007/vote_003 General Resolution].


A Debian Maintainer has their key in the debian-maintainers keyring (available in the debian-maintainers package).

This keyring is used by dak on the Debian archive as part of the checks as to whether an uploaded package is to be accepted.

Packages signed by a key in the debian-maintainers keyring will be accepted if the package is not new and the previous version of the package contains both the maintainer in the Maintainer control field and has the DM-Upload-Allowed control field present.

Becoming a Maintainer

To become a Debian Maintainer, you must:

Annual ping

The DMs must reconfirm their interest annually.

Uploading packages

Once you have your key in the keyring, you will be able to upload packages, where the following conditions hold:

  • the package already lists you in the Maintainers or the Uploaders control fields

  • the package already has the DM-Upload-Allowed: yes control field

  • the package is not NEW

dpkg caveat

At the moment, dpkg does not understand the DM-Upload-Allowed field and will not add it to the DSC. You need to prefix it with 'XS-' for it to make it into the DSC file (see [http://lists.debian.org/debian-newmaint/2007/11/msg00201.html discussion on newmaint] and [http://bugs.debian.org/453400 a bug covering this issue])

Advocating a Maintainer

A developer should only advocate a candidate if they are familiar with the candidate's existing work in Debian and believe it to be of a suitable standard both technically and socially.

Developers advocating DMs (or potential DDs for that matter) must go into a bit more detail in their advocacy.

If the prospective DM has done "a great job", please explain what "a great job" means -- is there something special she/he's done, or is it that whatever she/he's working on is particularly important, or is she/he remarkably consistent, or what? What's she/he actually done that's earnt your trust? What makes her/him special compared to the other folks who're helping Debian? What in particular about her/his work should people lurking on the debian lists be trying to emulate if they want to be a DM or a DD?

IRC Channel

#debian-maintainer at irc.debian.org

Page Copyright




JonDowland AnibalMonsalveSalazar

see ["?LicencingTerms"] for info about wiki content copyright.