Differences between revisions 82 and 161 (spanning 79 versions)
Revision 82 as of 2010-07-04 12:38:08
Size: 10032
Editor: HenriLeFoll
Comment: Identification before declaration of intent
Revision 161 as of 2022-11-20 07:20:52
Size: 12962
Editor: ?GianfrancoCostamagna
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||<tablewidth="100%"style="border: 0px hidden ;">~-Translation(s): none-~ ||<style="border: 0px hidden ; text-align: right;"> (!) [[/Discussion]] ||
<<BR>>
||<tablewidth="100%" tablestyle="border: 0px hidden ; text-align: center;"> {{http://www.debian.org/logos/openlogo-nd-50.png}} {{http://www.debian.org/Pics/debian.png}} ||
#language en
##For Translators - to have a constantly up to date translation header in you page, you can just add a line like the following (with the comment's character at the start of the line removed)
##<<Include(DebianMaintainer, ,from="^##TAG:TRANSLATION-HEADER-START",to="^##TAG:TRANSLATION-HEADER-END")>>
##TAG:TRANSLATION-HEADER-START
||<tablewidth="100%"style="border: 0px hidden ;">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: [[DebianMaintainer|English]] - [[ko/DebianMaintainer|한국어]] - [[pt_BR/DebianMaintainer|Português (Brasil)]]-~||<style="border: 0px hidden ; text-align: right;"> (!) [[/Discussion]] ||
##TAG:TRANSLATION-HEADER-END
----
Line 11: Line 14:
'''Debian Maintainers''' (DMs) are people who have a restricted ability to upload packages to the Debian archive. They can maintain packages without [[Glossary#sponsor|sponsor]].

After six months a ''Debian Maintainer'' can apply to the [[http://www.debian.org/devel/join/newmaint|Debian New Maintainers]] process
to become an official [[DebianDeveloper|Debian Developer]]. (see the [[http://www.debian.org/devel/join/nm-checklist|Applicant's Checklist]])

The Debian Maintainers concept was introduced on 5th August 2007 by [[http://www.debian.org/vote/2007/vote_003|General Resolution]].
An up to date list of DMs is available at https://nm.debian.org/dm_list.html .
'''Debian Maintainers''' (DMs) are people who have a restricted ability to upload packages to the Debian archive. <<BR>>
Unlike [[SponsoredMaintainer|Sponsored Maintainers]], t
hey can maintain packages '''without''' a [[Glossary#sponsor|sponsor]].

It is '''highly recommended''' to be a ''Debian Maintainer'' before applying to the [[http://www.debian.org/devel/join/newmaint|Debian New Members]] process to become an official [[DebianDeveloper|Debian Developer]] (see the [[http://www.debian.org/devel/join/nm-checklist|Applicant's Checklist]]).

The Debian Maintainers concept was introduced on 5th August 2007 by [[http://www.debian.org/vote/2007/vote_003|General Resolution]]. <<BR>>
An up to date list of DMs is available at [[https://nm.debian.org/public/people/dm_all|nm.debian.org]].
A [[http://ftp-master.debian.org/dm.txt|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 [[http://qa.debian.org/dm-permissions/|here]].
Line 20: Line 25:
Debian Maintainers have their keys in the ''debian-maintainers'' keyring (available in the {{{debian-maintainers}}} package).

This keyring is used by [[DebianDak|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 this maintainer in the {{{Maintainer}}} or the {{{Uploaders}}} control fields and has the {{{DM-Upload-Allowed}}} control field present.

Debian Maintainer should read this [[DebianMaintainer/Tutorial]] to know more about the annual ping, key changes and uploading packages.
Debian Maintainers have their keys in the ''debian-maintainers'' keyring (available in the {{{debian-keyring}}} package).   

This keyring is used by [[DebianDak|dak]] on the Debian archive as part of the checks as to whether an uploaded package is to be accepted.  <<BR>>
Packages signed by a key in the {{{debian-maintainers}}} keyring will be accepted if the key has upload right for the package. <<BR>>
For the
new interface for managing DM permissions, refer to the mail [[http://lists.debian.org/debian-devel-announce/2012/09/msg00008.html|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.
Line 30: Line 35:
A [[DebianDeveloper|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. A [[DebianDeveloper|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.
Line 34: Line 41:
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 [[DebianDeveloper|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.
 * 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 [[DebianDeveloper|Debian Developer]]?

For example, if the Debian Maintainer candidate has good packaging skills,<<BR>>
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
 * login to the [[https://nm
.debian.org|New Members]] website
 * and find their open application (the direct link can be found at the bottom of their Declaration of Intent email).
 * You can then add your declaration,
GnuPG-signed by your Debian key. <<BR>>
 This
will automatically be sent to the {{{debian-newmaint}}} list as well.  <<BR>>
 (Note that in previous times sending the email directly to the list yourself was sufficient; this is no longer the case. <<BR>>
 Advocacy must be submitted via the NM website for it to be attached to the application.)
Line 46: Line 68:
=== Prerequisite ===

Before becoming a ''Debian Maintainer'' you should have a history of contributions to Debian as a [[SponsoredMaintainer|Sponsored Maintainer]] where you can meet and establish a level of trust with other project members.
Line 47: Line 73:
 * You must have a GnuPG key and it must be [[Keysigning|signed]] by at least one (but ideally more than one) [[DebianDeveloper|Debian Developers]].
  . If signed by only one DD, try to make sure there is at least another trust path to your key.

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

If signed by only one DD, try to make sure there is at least another trust path to your key.
Line 60: Line 89:
 * subscribe to the [[http://lists.debian.org/debian-devel-announce/|debian-devel-announce]] mailing list and are ''highly encouraged'' to subscribe to the [[http://lists.debian.org/debian-devel/|debian-devel]] mailing list.

 * 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:
  {{{
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.
 * subscribe to the [[http://lists.debian.org/debian-devel-announce/|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 DebPkg:signing-party package) for signing keys you will also need to add these lines to ~/.caff/gnupghome/gpg.conf as well.

 * register for a Salsa 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.

The prospective DM is highly encouraged to subscribe to the [[http://lists.debian.org/debian-devel/|debian-devel]] mailing list.

Please check your key and fix any problem with your key. <<BR>>
Please read the document [[https://help.riseup.net/en/security/message-security/openpgp/best-practices|"OpenPGP Best Practices"]] by [[DanielKahnGillmor|Daniel Kahn Gillmor]] (dkg). <<BR>>
Its OpenPGP key checks have been implemented by [[ClintAdams|Clint Adams]] (clint) in the Debian package hopenpgp-tools and dkg's recommended settings has been put together in a gpg.conf file by [[https://en.wikipedia.org/wiki/Jacob_Appelbaum|Jacob Appelbaum]] (error). <<BR>>
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) [[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.

=== 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.


== Debian Maintainer retirement ==

Following each Debian release, all DMs who did not make an upload during the cycle for that release will be automatically retired.

For example: after the release of Stretch, DMs who did not make an upload
since the release of Jessie will be retired.

There used to be an annual "ping" bug procedure to indicate continued interest: that is not required anymore.

Announced [[https://lists.debian.org/debian-devel-announce/2016/08/msg00007.html|here]].

== 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 [[https://lists.debian.org/debian-devel-announce/2012/09/msg00008.html | as described in the FTP-Master's announcement to debian-devel.]] <<BR>>
This process can be simplified with the help of the {{{dcut}}} command from the '''{{{dput-ng}}}''' package. Note that this does not work with the {{{dcut}}} command from the {{{dput}}} package. You can check which one you have via {{{apt list dput*}}}.

For example, both of the following work:

{{{
$ dcut ftp-master dm --uid "Jane Doe" --allow glibc
$ dcut ftp-master dm --uid 0xfedcba9876543210 --allow glibc linux --deny kfreebsd9
Line 75: Line 156:
=== 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.
  {{{
Subject: Support of Debian Maintainer application
Hello <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
<explanation why you believe he has the right skills>
[1] http://lists.debian.org/debian-newmaint/<complete the URL>
Thanks, <your name>.
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 and in all uppercase:

{{{
$ dcut ftp-master --force dm --uid FEDCBA9876543210FEDCBA9876543210 --allow glibc
Line 94: Line 162:
=== 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. install the [[http://packages.debian.org/sid/debian-keyring|debian-keyring package]]
  1. create a copy of the debian-maintainer keyring file and add your key to it
   . {{{
% cp /usr/share/keyrings/debian-maintainers.gpg .
% gpg --export <ID of your key> | gpg --import --no-default-keyring --keyring $PWD/debian-maintainers.gpg
}}}
   The path of the keyring must be absolute. (Note that you must not have a keyring specified in your ~/.gnupg/options for this to work!)
  1. generate the changeset with {{{jetring-gen}}} from the [[http://packages.debian.org/jetring|jetring package]]
   . {{{
% jetring-gen /usr/share/keyrings/debian-maintainers.gpg 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>
}}}

 * 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]]

== Informations ==
Now that you are a Debian Maintainer, you have to read this [[DebianMaintainer/Tutorial]]
Both the DD and DM will receive a mail notification about any changes taken. <<BR>>
 The archive's knowledge about DMs can be [[https://ftp-master.debian.org/dm.txt |checked here.]]
Line 124: Line 168:
 * http://packages.debian.org/debian-maintainers - keyring package
 * http://git.debian.org/?p=d-m/debian-maintainers.git;a=summary - git repo summary
 * http://packages.debian.org/debian-maintainers - old keyring package, no longer exists, as it was merged into debian-keyring in 2009
 * http://packages.debian.org/debian-keyring - keyring package
 * http://
git.debian.org/?p=d-m/debian-maintainers.git;a=summary - git repo summary, until July 2009, when it was merged into debian-keyring
 * http://bzr.debian.org/loggerhead/keyring/debian-keyring/files - bazaar repo summary
Line 129: Line 175:
 * http://lists.debian.org/debian-devel-announce/2010/09/msg00003.html - Debian wants stronger keys
 * http://keyring.debian.org/creating-key.html - Creating a new OpenPGP key
Line 130: Line 178:
 * http://ftp-master.debian.org/dm-uploaders.html - core raw information about DM  * http://ftp-master.debian.org/dm.txt - raw information of DM upload permissions (new interface)
 * https://help.riseup.net/en/security/message-security/openpgp/best-practices - OpenPGP Best Practices
 * http://lists.debian.org/debian-devel/2011/04/msg01058.html - DM upload permissions in detail
 * https://lists.debian.org/debian-devel-announce/2012/09/msg00008.html - Changes to Debian Maintainer upload permissions
Line 133: Line 184:
#debian-newmaint at irc.debian.org  * Packaging and sponsoring questions: [[irc://irc.debian.org/debian-mentors|#debian-mentors]] at irc.debian.org
 * Questions about becoming a DM: [[irc://irc.debian.org/debian-newmaint|#debian-newmaint]] at irc.debian.org
Line 141: Line 193:
<<BR>>
/!\ graph image above was last updated circa 2009
Line 143: Line 197:
{{http://people.debian.org/~glandium/bts/d/debian-maintainers.png}} {{https://qa.debian.org/data/bts/graphs/d/debian-maintainers.png}}
Line 157: Line 211:
## This page is linked from http://www.debian.org/intro/organization for "Debian Maintainer Keyring Team "
CategoryPermalink
## This page is linked from http://www.debian.org/intro/organization for "Debian Maintainer Keyring Team"
## This page is linked from http://www.debian.org/doc/manuals/developers-reference/pkgs
CategoryPermalink CategoryDeveloper

Translation(s): English - 한국어 - Português (Brasil)

(!) /Discussion


Contents

Introduction

Debian Maintainers (DMs) are people who have a restricted ability to upload packages to the Debian archive.
Unlike Sponsored Maintainers, 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

  • login to the New Members website

  • and find their open application (the direct link can be found at the bottom of their Declaration of Intent email).
  • You can then add your declaration, GnuPG-signed by your Debian key.
    This will automatically be sent to the debian-newmaint list as well.
    (Note that in previous times sending the email directly to the list yourself was sufficient; this is no longer the case.
    Advocacy must be submitted via the NM website for it to be attached to the application.)

Becoming a Debian Maintainer

Steps required to become a Debian Maintainer

Prerequisite

Before becoming a Debian Maintainer you should have a history of contributions to Debian as a Sponsored Maintainer where you can meet and establish a level of trust with other project members.

step 1 : Identification

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

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 a Salsa 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.

Debian Maintainer retirement

Following each Debian release, all DMs who did not make an upload during the cycle for that release will be automatically retired.

For example: after the release of Stretch, DMs who did not make an upload since the release of Jessie will be retired.

There used to be an annual "ping" bug procedure to indicate continued interest: that is not required anymore.

Announced here.

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. Note that this does not work with the dcut command from the dput package. You can check which one you have via apt list dput*.

For example, both of the following work:

$ dcut ftp-master dm --uid "Jane Doe" --allow glibc
$ dcut ftp-master dm --uid 0xfedcba9876543210 --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 and in all uppercase:

$ dcut ftp-master --force dm --uid FEDCBA9876543210FEDCBA9876543210 --allow glibc

Both the DD and DM will receive a mail notification about any changes taken.

IRC Channel

Statistics

Data

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

Graph

http://people.debian.org/~anibal/dm/dm.png
/!\ graph image above was last updated circa 2009

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 CategoryDeveloper