= Guest Access to porter machines =
-People who are not DDs but are working on software in Debian are able to obtain
+People who are not DDs but are working on software in Debian can request
access to porter machines for short term (1-2 months) in order to resolve port
issues and the like.
+The final decision about account creation remains with DSA.
+
+== DMs/NMs ==
+
+DMs (i.e. people who have their key in the debian-maintainers keyring) or
+people already in the NM process can apply for a guest account through
+<a href="https://nm.debian.org">the New Members site</a>.
+
+The following information is required to complete your request:
+
+* Preferred username (in your NM profile)
+* Machine(s)/Architecture(s) to which access is needed
+* Short rationale as to //why// access is needed
+
+Other information will be collected during the process.
+
+A member of frontdesk will verify the information for correctness, and create a
+ticket in RT (signed by the frontdesk member) asking DSA to add the new account
+to LDAP.
+
== non-DMs ==
People who are not yet DMs or NMs will need to find a DD who is willing
The guest applicant should supply several details (listed below) to this DD,
and the DD will sign this (clear signed, not PGP mime) and open a ticket
in RT (mail to admin@rt.d.o, put 'Debian RT' somewhere in the subject -
-see <a href="http://wiki.debian.org/rt.debian.org">wiki.d.o</a> for more info).
+see <a href="https://wiki.debian.org/rt.debian.org">wiki.d.o</a> for more info).
This signing and resending is a sponsorship by the DD that the guest
account should be granted access to Debian resources, and should be
* First/Middle/Last-name
* Preferred username
-* GPG key
-* Forwarding email address (for things like cron output etc.)
-* Signed agreement to abide by DMUP
+* Key **fingerprint** of the PGP key, which needs to be on the keyserver network. (fingerprint. Not a keyid. Not a link to a site that has a key or a keyserver. A fingerprint.)
+* email address
+* Signed agreement to abide by <a href="https://www.debian.org/devel/dmup">DMUP</a>
* Machine(s)/Architecture(s) to which access is needed
* Short rationale as to //why// access is needed
=== Information sponsoring DD needs to supply to DSA ===
-* Signed email containing above information
+* DD-signed email containing above information
+* Guest-signed agreement to abide by DMUP
-== DMs/NMs ==
+== Notes ==
-DMs (i.e. people who have their key in the debian-maintainers keyring) or
-people already in the NM process may route their request through the
-<a href="mailto:new-maintainer@debian.org">NM-frontdesk</a>.
+* Requests for "all architectures" are not acceptable.
+* Requests need to be clear-signed. Request-tracker munges PGP/MIME. Also, the signed DMUP agreement needs to be clear-signed.
-The following information should be provided to frontdesk:
+== Expired Accounts ==
-* First/Middle/Last-name
-* Preferred username
-* GPG key fingerprint (if key is in the debian-maintainers keyring), or key if not.
-* Forwarding email address (for things like cron output etc.)
-* Signed agreement to abide by DMUP (or link to the mailinglist archive of debian-newmaint where that already was done)
-* Machine(s)/Architecture(s) to which access is needed
-* Short rationale as to //why// access is needed
+Once an account has expired the user will no longer be able to log into
+debian machines. If access is required again, creating a ticket in RT should
+suffice to get it re-activated (The request should be sent by end-user and pgp signed).
-A member of frontdesk will verify the information for correctness, and create a
-ticket in RT (signed by the frontdesk member) asking DSA to add the new account
-to LDAP.
+Similarly, should access to other hosts become necessary a ticket in RT
+can be opened.
-
-
-The final decision about account creation remains with DSA.
projects / mirror / dsa-wiki.git / blobdiff