[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Updating the delegation for the Debian System Administrators (DSA)

Dear Developers,

It is my pleasure to announce that Aurélien Jarno (aurel32) is now an
official member of the Debian System Administrators team. Aurélien has
been helping the team since last DebConf, and this announcement makes
his membership in the team official.

In other (bad) news, Faidon Liambotis (paravoid) has decided to step
down as Debian System Administrator. Let's thank him for all the work
he did as DSA!


DSA delegation

I hereby appoint the following developers as members of the Debian
System Administrators (DSA) team:

 - Aurélien Jarno (aurel32)
 - Julien Cristau (jcristau)
 - Luca Filipozzi (lfilipoz)
 - Paul Wise (pabs)
 - Stephen Gran (sgran)
 - Tollef Fog Heen (tfheen)
 - Peter Palfrader (weasel)
 - Martin Zobel-Helas (zobel)
 - Héctor Orón Martínez (zumbi)

Any previous Debian System Administrators delegation, not explicitly
listed above, is revoked. The delegation is not time-limited. It will
be effective until further changes by present or future DPLs.

Task Description

Debian System Administrator team members handle the basic infrastructure
of the project. They are responsible for tasks that include:

- Maintaining the central user (LDAP) database listing all the Debian
  developers. This includes:
  - account creation and deletion based on requests from the Debian
    Account Managers
  - correlation of GPG keys to the according accounts based on requests
    from the Debian Keyring Maintainers
- Setting up and administering most of Debian-owned machines, ensuring
  that they are kept secure, operational, and running
- Coordinating with local admins of the machines regarding network
  connectivity and (if needed) asking for remote hands
- Granting required rights to other developers who need them to maintain
  a particular service
- Handle standard services like the debian.org email alias that each
  developer has or keeping DNS up to date
- maintaining the Debian Machine Usage Policies (DMUP), within the
  following limits:
  - the DMUP cannot directly cause the expulsion of a developer from the
    project; it can however propose the developer for expulsion to DAM,
    on the basis of DMUP violation
  - changes to the DMUP shall be announced to the debian-devel-announce
    mailing list at least 2 months in advance with respect to when they
    are supposed to become effective




Attachment: signature.asc
Description: PGP signature

Reply to: