@@ -60,24 +60,24 @@ What do we want out of this process?
This happens after we go through the recruiting process, and the
candidate has accepted a formal offer.
1. Candidate accepts the offer, in writing, from TPI (with the social contract, code of conduct, and employee handbook). Erin sends the start date to the team the person will be working in.
1. Candidate accepts the offer, in writing, from TPI (with the social contract, code of conduct, and employee handbook). HR sends the start date to the team the person will be working in.
2. Send a mail to the team lead + PM to tell them starting date for new employee.
4.Erin sends mail to new employee with the following information:
4.HR sends mail to new employee with the following information:
* holidays calendar
* org chart
* harvest
* next steps
5.Erin creates a ticket in TPA's gitlab, pgp signed, to:
5.HR creates a ticket in TPA's gitlab, pgp signed, to:
* setup Email/LDAP access. LDAP coordinates accesses to a few services, mostly shell and gitolite, but less and less services are connected to it, so we need to grant access to a *lot* of services when we add new users
6.Erin sends a mail to tor-internal@ introducing new employee (after email is created and tested). Instructions for tor-internal IRC is in intro email.
7.Erin creates a ticket in TPA gitlab group requesting to create following accounts:
6.HR sends a mail to tor-internal@ introducing new employee (after email is created and tested). Instructions for tor-internal IRC is in intro email.
7.HR creates a ticket in TPA gitlab group requesting to create following accounts:
* BBB
* GitLab
* Nextcloud
* ... maybe more? see the [service list](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service)
