Differences between revisions 141 and 142
⇤ ← Revision 141 as of 2016-04-11 02:11:52 →
Size: 14171
Editor: TiagoIlieve
Comment: Drops non-ASCII hyphen
← Revision 142 as of 2016-07-01 17:38:39 → ⇥
Size: 10735
Editor: ?JonathanWiltshire
Comment:
Deletions are marked like this. Additions are marked like this.
Line 65: Line 65:
 * publically state your agreement to the above documents, signing your declaration with your OpenPGP key. Most people will post their declaration to the [[http://lists.debian.org/debian-newmaint|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.
 }}}		  * register for an Alioth account if you do not have one
 * register for a [[https://nm.debian.org|New Members]] account
 * in [[https://nm.debian.org|New Members]], apply for the Debian Maintainer status
 * a mail will automatically be sent to the {{{debian-newmaint}}} mailing list.
Line 83: Line 74:
=== step 3 : Advocation ===
 * You must have at least one (but preferably more) [[DebianDeveloper|Debian Developer]] '''advocate''' 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:		 === step 3 : Advocacy ===
 * You must have at least one (but preferably more) [[DebianDeveloper|Debian Developer]] '''advocate''' you. You should send a mail to all your advocates, asking them to log into [[https://nm.debian.org|New Members]], find your open application, and advocate you. Their comments will also be sent to the {{{debian-newmaint}}} mailing list.
Line 95: Line 77:
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>.
}}}		 === step 4 : Objections ===
Line 103: Line 79:
=== step 4 : Account creation ===
 * Submit a bug report with a ''jetring changeset'' to the bug tracking system, filed against the [[http://www.debian.org/Bugs/pseudo-packages|debian-maintainers pseudo package]] (see [[http://bugs.debian.org/debian-maintainers|existing pending reports]]). Use only URLs from {{{debian.org}}} for the ''agreement'' and ''advocates'' fields of the jetring changeset
  1. You have to get the latest debian-maintainer keyring, e.g. download the [[http://packages.debian.org/sid/debian-keyring|debian-keyring package]]
  1. If the email address you use for packaging work is not the ''primary UID'' of your key, indicate that in the bug report
  1. Generate the changeset with {{{jetring-gen}}} from the [[http://packages.debian.org/jetring|jetring package]]
   . {{{
% apt-get install jetring
% apt-get download debian-keyring
% dpkg-deb -x debian-keyring*.deb keyring
% cp keyring/usr/share/keyrings/debian-maintainers.gpg .
% cp debian-maintainers.gpg debian-maintainers.gpg.orig
% gpg --export yourmail@example.com | gpg --import --no-default-keyring --keyring `pwd`/debian-maintainers.gpg
# note that `pwd`/debian-maintainers.gpg is not the same as debian-maintainers.gpg even when you are in corresponding directory. `pwd`/ is REQUIRED.
% jetring-gen debian-maintainers.gpg.orig debian-maintainers.gpg 'Add <your name and e-mail address> as a Debian Maintainer'
}}}
  1. Edit the file {{{add-*}}} and add these fields; after the colon should be a space before the end of line
   . {{{
Recommended-By:
  <names and e-mail addresses of all your advocates (comma separated)>
Agreement:
  http://lists.debian.org/debian-newmaint/<complete the URL of your agreement>
Advocates:
  http://lists.debian.org/debian-newmaint/<complete the URL>
}}}		 Your application will stay pending for four days, to allow time for any objections to be filed.
Line 128: Line 81:
 * 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 [[DebianDeveloper|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. === step 5 : Keyring update ===

When your application is complete, it will be sent to the keyring maintainers who will actually update the keyring. This can take anything from days to weeks, and you will be notified when it happens.

Translation(s): none

(!) /Discussion


Contents

Contents

  1. Contents
  2. Introduction
  3. Overview
  4. Advocating a Debian Maintainer
  5. Becoming a Debian Maintainer
    1. step 1 : Identification
    2. step 2 : Declaration of intent
    3. step 3 : Advocacy
    4. step 4 : Objections
    5. step 5 : Keyring update
  6. Information
    1. Granting Permissions
    2. External links
    3. Statistics

Introduction

Debian Maintainers (DMs) are people who have a restricted ability to upload packages to the Debian archive. They can maintain packages without a sponsor.

It is highly recommended to be a Debian Maintainer before applying to the Debian New Members process to become an official Debian Developer (see the Applicant's Checklist).

The Debian Maintainers concept was introduced on 5th August 2007 by General Resolution. An up to date list of DMs is available at nm.debian.org. A list of the upload rights held by DMs is maintained by the Debian ftp-masters, and a few reports with the same information are maintained here.

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.

step 2 : Declaration of intent

To become a Debian Maintainer, you must:

  • agree to the social contract

  • agree to the DFSG

  • agree to the Debian Machine Usage Policies (dmup)

  • subscribe to the debian-devel-announce mailing list.

  • ensure that GnuPG uses SHA2 signatures (in preference to SHA1); an example is having the following content in ~/.gnupg/gpg.conf: 
    personal-digest-preferences SHA512
cert-digest-algo SHA512
default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed

    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.

  • register for an Alioth account if you do not have one

  • register for a New Members account

  • in New Members, apply for the Debian Maintainer status

  • a mail will automatically be sent to the debian-newmaint mailing list.

The prospective DM is highly encouraged to subscribe to the debian-devel mailing list.

Please check your key and fix any problem with your key. Please read the document "OpenPGP Best Practices" by Daniel Kahn Gillmor (dkg). Its OpenPGP key checks have been implemented by Clint Adams (clint) in the Debian package hopenpgp-tools and dkg's recommended settings has been put together in a gpg.conf file by Jacob Appelbaum (error). Please check your key with clint's hokey lint command and use error's gpg.conf file as explained in dkg's document.

step 3 : Advocacy

  • You must have at least one (but preferably more) Debian Developer advocate you. You should send a mail to all your advocates, asking them to log into New Members, find your open application, and advocate you. Their comments will also be sent to the debian-newmaint mailing list.

step 4 : Objections

Your application will stay pending for four days, to allow time for any objections to be filed.

step 5 : Keyring update

When your application is complete, it will be sent to the keyring maintainers who will actually update the keyring. This can take anything from days to weeks, and you will be notified when it happens.

Information

Now that you are a Debian Maintainer, you have to read this DebianMaintainer/Tutorial

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: 

$ dcut dm --uid "Jane Doe" --allow glibc
$ dcut dm --uid 0x0DEFACED --allow glibc linux --deny kfreebsd9

If the DM's key is not in the keyring package yet but in the DD's local keyring, use the --force option and the fingerprint, without spaces and, in this special case, without the 0x prefix: 

$ dcut --force dm --uid fedcba9876543210fedcba9876543210 --allow glibc

Both the DD and DM will receive a mail notification about any changes taken. The archive's knowledge about DMs can be checked here.

IRC Channel

Statistics

Data

http://people.debian.org/~anibal/dm/dm-history

Graph

http://people.debian.org/~anibal/dm/dm.png

Bugs

https://qa.debian.org/data/bts/graphs/d/debian-maintainers.png

Page Copyright

License

GPLv2

Authors

JonDowland AnibalMonsalveSalazar

see DebianWiki/LicencingTerms for info about wiki content copyright.

CategoryPermalink