Rewrite the LDAP-or-email decision tree so it's a tree

equal, it's better to set people up with only an email alias if that's all

they need, since it reduces surface area which is better for security.)

Are they a maintainer for one of our official software projects, meaning

they need to push commits (write) to one of our git repos? If yes,

they should have an LDAP account.

Do they need to access (read) a private git repo, like "dirauth-conf"?

If yes, they should have an LDAP account.

Do they want to make their own personal clones of our git repos, for

example to propose patches and changes? If yes, and also they are a

Core Contributor, they should have an LDAP account. If yes, but they're

not a Core Contributor, they should put their git repos somewhere else,

like github or gitlab.

Do they need to log in to our servers, for example to maintain one of

our websites or services, or to use our shared irc host? If yes, and also

they are a Core Contributor, they should have an LDAP account.

Are they a Core Contributor, but none of the above cases apply to them?

If so, they should have an email alias.

== <a id="new-account">New accounts</a> ==

=== LDAP account reasons ===

Regardless of whether they are a Core Contributor:

* Are they a maintainer for one of our official software projects, meaning

  they need to push commits (write) to one of our git repos?

* Do they need to access (read) a private git repo, like "dirauth-conf"?

Are they a Core Contributor?

* Do they want to make their own personal clones of our git repos, for

  example to propose patches and changes?

  * If they're not a Core Contributor, they should put their git repos

    somewhere else, like github or gitlab.

* Do they need to log in to our servers to use our shared irc host?

  * If they're not a Core Contributor, they should put their IRC somewhere

    else, like pastly's server.

* Do they need to log in to our servers to maintain one of our websites or

  services?

  * If they're not a Core Contributor, but they are a staff member who needs

    to maintain services, then Tor Project Inc should request an LDAP account.

  *  If they are not a staff member, then an existing Core Contributor should

     request an LDAP account, and explain why they need access.

See <a href="new-account">New LDAP accounts</a> for details.

=== Email alias reasons ===

If none of the above cases apply:

* Are they a Core Contributor? An existing Core Contributor should request

  an email alias.

* Are they a staff member? Tor Project Inc should request an email alias.

See <a href="aliases">Changing email aliases</a> for details.

== <a id="new-account">New LDAP accounts</a> ==

New accounts have to be sponsored by somebody who already has a torproject.org

account.  If you need an account created, please find somebody in the project