Differences between revisions 1 and 29 (spanning 28 versions)
Revision 1 as of 2009-01-03 16:54:54
Size: 755
Comment: Collect some mails so I don't need to google for them every time
Revision 29 as of 2014-02-09 22:30:02
Size: 3220
Editor: ?JonathanWiltshire
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Interesting mails: == Task description ==

The Debian Account Managers (DAM) are responsible for maintaining the
list of members of the Debian Project, also known as Debian Developers.
DAMs are authoritative in deciding who is a member of the Debian Project
and can take subsequent actions such as approving and expelling Project
members.

DAMs are helped in the task by the [[Teams/FrontDesk|Front Desk]] team,
which run the [[http://www.debian.org/devel/join/|New Maintainer process]].

=== Delegation ===

DAM members are DPL delegates (as per [[http://www.debian.org/devel/constitution#item-8|Debian Constitution §8]]).
The [[https://lists.debian.org/debian-devel-announce/2013/12/msg00006.html|current delegation text]] is available.


== Interesting mails ==
Line 8: Line 25:
 * Bits from the DAMs: http://lists.debian.org/debian-devel-announce/2005/02/msg00003.html  * Procedure for the expulsion of Debian Developers: http://lists.debian.org/debian-devel-announce/2005/08/msg00005.html
* Bits from the DAMs (NM rules, Emeritus, MIA handling): http://lists.debian.org/debian-devel-announce/2005/02/msg00003.html
Line 12: Line 30:
 * Legal Names: http://lists.debian.org/debian-newmaint/2009/07/msg00044.html
 * on the need of using templates for tasks and skills (or not) and more: http://lists.debian.org/debian-devel-announce/2009/11/msg00005.html
   * see also [[FrontDesk/Tips]]
 * Account name change policy: http://lists.debian.org/debian-project/2010/09/msg00032.html
 * [DSA] handling of guest accounts on debian.org machines: http://lists.debian.org/debian-project/2010/09/msg00026.html
 * Keyring-maint demands stronger keys: http://lists.debian.org/debian-devel-announce/2010/09/msg00003.html
 * collab-maint requests: http://lists.debian.org/debian-devel-announce/2012/01/msg00006.html
 * Advocacy guidelines: https://lists.debian.org/debian-devel-announce/2010/05/msg00003.html

== Account Name Policy ==

 * account names must consist entirely of lower-case letters and digits, must contain at least one letter, and should start with a letter. There is a natural exception for ham radio callsigns starting with a digit.
 * there is no upper limit on the length, but we will reject very long names (Django limits user names to 30 characters)
 * account names should be at least three letters long
 * we reserve the right to reject names if they are overly generic, or are similar to role names in the project
 * "should" means that you might be able to convince us otherwise if you have good reasons

== Related wiki pages ==

 * [[DebianDeveloper]]
 * [[DebianMaintainer]]
 * [[MigrateToDDAccount]]
 * [[FrontDesk/BitsDraft]]
 * [[qa.debian.org/MIATeam]]

Debian Account Manager (DAM) resources

Task description

The Debian Account Managers (DAM) are responsible for maintaining the list of members of the Debian Project, also known as Debian Developers. DAMs are authoritative in deciding who is a member of the Debian Project and can take subsequent actions such as approving and expelling Project members.

DAMs are helped in the task by the Front Desk team, which run the New Maintainer process.

Delegation

DAM members are DPL delegates (as per Debian Constitution §8). The current delegation text is available.

Interesting mails

Account Name Policy

  • account names must consist entirely of lower-case letters and digits, must contain at least one letter, and should start with a letter. There is a natural exception for ham radio callsigns starting with a digit.
  • there is no upper limit on the length, but we will reject very long names (Django limits user names to 30 characters)
  • account names should be at least three letters long
  • we reserve the right to reject names if they are overly generic, or are similar to role names in the project
  • "should" means that you might be able to convince us otherwise if you have good reasons