X-Git-Url: https://git.adam-barratt.org.uk/?a=blobdiff_plain;f=input%2Fdoc%2Fguest-account.creole;h=83adc7df2b2c1972a2967154b5d6d4a6bab11cab;hb=9afdd09eeab729979f89f0c628b06cf6a6914c49;hp=8a52d4070e44681c52b141d009fb1bbfb7f50aa2;hpb=57499e1fd8f3ac5724593811e461d715cd77b588;p=mirror%2Fdsa-wiki.git diff --git a/input/doc/guest-account.creole b/input/doc/guest-account.creole index 8a52d40..83adc7d 100644 --- a/input/doc/guest-account.creole +++ b/input/doc/guest-account.creole @@ -1,14 +1,39 @@ = Guest Access to porter machines = +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 +the New Members site. + +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 DDs, DMs or NMs but are working on software in Debian are -able to obtain access to porter machines for short term (1-2 months) in -order to resolve port issues and the like. The procedure for this is that -the guest applicant should supply several details (listed below) to a DD, +People who are not yet DMs or NMs will need to find a DD who is willing +to sponsor their request. People requesting access should already have +a track record of working on Debian for some time. + +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 wiki.d.o for more info). +see wiki.d.o 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 @@ -18,31 +43,28 @@ regarded as such. * 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 DMUP * 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 -NM-frontdesk. +* 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 shall 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 +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.