Difference between revisions of "Service/Account"
< Service
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
# Intendend purpose of account (cc your sponsors, if any) | # Intendend purpose of account (cc your sponsors, if any) | ||
| − | |||
# Desired username (lowercase, [a-z]+) | # Desired username (lowercase, [a-z]+) | ||
| − | |||
# Desired forwarding email destination for USERNAME@sugarlabs.org | # Desired forwarding email destination for USERNAME@sugarlabs.org | ||
| − | |||
# Your full name | # Your full name | ||
| − | |||
# Public ssh key(s) to be copied to ~/.ssh/authorized_keys (please don't attach, paste each key on one line avoiding word-wrapping) | # Public ssh key(s) to be copied to ~/.ssh/authorized_keys (please don't attach, paste each key on one line avoiding word-wrapping) | ||
| − | |||
# Preferably sign your request with a trusted GPG key and upload it to a public keyserver. | # Preferably sign your request with a trusted GPG key and upload it to a public keyserver. | ||
Within 48 hours, you should receive a welcome email with further instructions. | Within 48 hours, you should receive a welcome email with further instructions. | ||
If you don't see anything, all the sysadmins may be asleep or dead. Try pinging. | If you don't see anything, all the sysadmins may be asleep or dead. Try pinging. | ||
Revision as of 00:04, 9 February 2010
How to request a shell account on people.sugarlabs.org
Send an email to <sysadmin AT sugarlabs DOT org> containing the following information:
- Intendend purpose of account (cc your sponsors, if any)
- Desired username (lowercase, [a-z]+)
- Desired forwarding email destination for USERNAME@sugarlabs.org
- Your full name
- Public ssh key(s) to be copied to ~/.ssh/authorized_keys (please don't attach, paste each key on one line avoiding word-wrapping)
- Preferably sign your request with a trusted GPG key and upload it to a public keyserver.
Within 48 hours, you should receive a welcome email with further instructions. If you don't see anything, all the sysadmins may be asleep or dead. Try pinging.