Commit bdb797f5 authored by anarcat's avatar anarcat
Browse files

Merge branch 'sysadmin-webdev-role' into 'master' 

Assuming this new person is the sysadmin-web developer, adds information to onboard a web developer.

See merge request tpo/tpa/wiki-replica!10
parents 34318289 4a4da273

howto/new-person.md

+11 −9
Original line number Diff line number Diff line 
---

title: How to get a new Tor System Administrator on board

title: How to get a new Tor System Administrator (with web developer duties) on board

---



Note that this documentation needs work, as it overlaps with normal
@@ -53,6 +53,7 @@ user management procedures, see [issue 40129](https://gitlab.torproject.org/tpo/ 
   * `#tor-project` - general Tor project channel

   * `#tpo-admin` - channel for TPA specific stuff

   * `#tor-www` - Tor websites development channel

   * `#tor-l10n` - Tor localization channel

   * `#tor-internal` - channel for private discussions, need secret

     password and being added to the `@tor-tpomember` with `GroupServ`,

     part of the `tor-internal@lists.tpo` welcome email)
@@ -71,6 +72,7 @@ user management procedures, see [issue 40129](https://gitlab.torproject.org/tpo/ 
 4. [Puppet primer: adding yourself to the allow list](howto/puppet#adding-an-ip-address-to-the-global-allow-list)

 5. [New machine creation](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/new-machine)

 6. [Updating status.tpo](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/status#creating-new-issues)

 7. [Tor Websites](https://gitlab.torproject.org/tpo/web/team)



# More advanced documentation
@@ -114,14 +116,14 @@ Here's a checklist that should be copy-pasted in a ticket: 
    `ssh://git@git-rw.torproject.org/admin/tor-nagios`, password in

    `/etc/icinga/htpasswd.users` directly on the server

 10. [ ] Sunet cloud access (e.g. `Message-ID: <87bm1gb5wk.fsf@nordberg.se>`)

 11. [ ] [Nextcloud](https://nc.torproject.net) account with groups TPI and TPA.



Extra services we are not directly responsible for, but that new TPA

staff will typically *have* to deal with:

Extra services we are not directly responsible for, but that TPA

staff may administer at some point:



 1. [ ] [BBB](howto/conference) access

 2. [ ] [Nextcloud](service/nextcloud) (undocumented: add to TPA group at least)

 3. [ ] [RT](howto/rt#new-rt-admin)

 4. [ ] [blog](service/blog)

 5. [ ] [btcpayserver](service/BTCpayserver)

 6. [ ] [gitolite admin](howto/git)

 7. [ ] [schleuder](service/schleuder)
 
 2. [ ] [RT](howto/rt#new-rt-admin)

 3. [ ] [blog](service/blog)

 4. [ ] [btcpayserver](service/BTCpayserver)

 5. [ ] [gitolite admin](howto/git)

 6. [ ] [schleuder](service/schleuder)