* You must have a strong (>= 2048 bit required; 4096 bit recommended) RSA GnuPG key (see line above) and it must be [[Keysigning/Coordination|signed by at least one (but ideally more than one) Debian Developers]].

* You must have a strong (>= 2048 bit required; 4096 bit recommended) RSA GnuPG key (see line above) and it must be [[Keysigning|signed]] by at least one (but ideally more than one) [[DebianDeveloper|Debian Developers]].

Overview

Debian Maintainers have their keys in the debian-maintainers keyring (available in the debian-keyring 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 key has upload right for the package. For the new interface for managing DM permissions, refer to the mail Changes to Debian Maintainer upload permissions. Debian Maintainer should read this DebianMaintainer/Tutorial to know more about the annual ping, key changes and uploading packages.

Advocating a Debian Maintainer

A Debian Developer should only advocate a Debian Maintainer 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.

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

If the Debian Maintainer candidate has done "a great job", please explain what "a great job" means -- is there something special the candidate has done, or is it that whatever the candidate is working on is particularly important, or is the candidate remarkably consistent, or what?

What has the candidate actually done that has earned your trust? What makes the candidate special compared to the other folks who are helping Debian? What in particular about the candidate's work should people lurking on the Debian lists be trying to emulate if they want to be a Debian Maintainer or a Debian Developer?

For example, if the Debian Maintainer candidate has good packaging skills, go into a bit more detail about what's convinced you the candidate has got those skills? Are there any difficult bugs you've worked together on, or new features the candidate has done a good job of getting into Debian, or has the candidate been particularly helpful supporting users, or...?

Once you have decided to advocate a Debian Maintainer applicant, you should compose your advocacy message as a reply to their declaration message. Ensure it is GnuPG-signed with your Debian userid, and addressed to the debian-newmaint list.

Becoming a Debian Maintainer

Steps required to become a Debian Maintainer

step 1 : Identification

You must have a strong (>= 2048 bit required; 4096 bit recommended) RSA GnuPG key (see line above) and it must be signed by at least one (but ideally more than one) Debian Developers.

If signed by only one DD, try to make sure there is at least another trust path to your key.

If you use caff (part of signing-party package) for signing keys you will also need to add these lines to ~/.caff/gnupghome/gpg.conf as well.

publically state your agreement to the above documents, signing your declaration with your OpenPGP key. Most people will post their declaration to the debian-newmaint mailing list. Your mail could look like this one:

Subject: DM application of <your name>
This is my declaration of intent to become a Debian Maintainer
<URL:http://wiki.debian.org/DebianMaintainer>.
I have read the Social Contract, Debian Free Software Guidelines and
Debian Machine Usage Policy and agree with all of them.
Currently, I maintain the packages <insert the names of your packages>
and I co‐maintain the packages <insert the names of your co‐maintained packages>.
My GnuPG key <key ID> is signed by the Debian Developer <name of the developer>.
I look forward to becoming a Debian Maintainer. Thanks for your attention.

step 3 : Advocation

You must have at least one (but preferably more) Debian Developeradvocate you. This is usually a signed mail to debian-newmaint (often a reply to your declaration mail)

You should send a mail to all your advocates, asking them to reply to the message you've send to debian-newmaint. You might forward the message to them, so they have the correct message-ID, or even cc or bcc them on the original message so that they can easily reply to it.

Subject: Support of DM application of <your name>
Hello <advocate name>,
I would like to become a Debian Maintainer. I've sent the e‐mail [1],
also attached to this mail, to the mailinglist debian-newmaint. Now, I'm
looking for one or more Debian Developers to support my application. If
you think I would be a good Debian Maintainer, please post a statement to
debian-newmaint. Something like this:
Subject: Debian Maintainer application for <your name>
I believe that <your name> has the technical skills needed to maintain Debian
packages. I support his application to become a Debian maintainer, because
<detailed and extensive explanation why you believe he has the right skills>
[1] http://lists.debian.org/debian-newmaint/<complete the URL>
Thanks, <your name>.

There will be a delay of four days after the bug report has been submitted to wait in case of objections or any more advocacies from Debian Developers. This delay is a minimum but it might take more time until someone from the DM team processes your application. Note that the key is added to the keyring by the keyring team (not the DM team) and that you must expect another delay (between a few days and a few weeks depending on the case) due to this.

Information

Granting Permissions

After a Debian Maintainer's key has been added to the debian-maintainers keyring, a Debian Developer may grant upload permissions to the DM for specific packages by uploading a signed dak command to ftp.upload.debian.org as described in the FTP-Master's announcement to debian-devel. This process can be simplified with the help of the dcut command from the dput-ng package. For example, both of the following work: