@@ -15,15 +15,15 @@ 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 offer, in writing, from TPI (with social contract, code of conduct and employee handbook). Erin send start date to the team the person will be working in.
1. Candidate accepts offer, in writing, from TPI (with social contract, code of conduct, and employee handbook). Erin sends 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:
* holidays calendar
* org chart
* harvest
* next steps
5. Erin 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 join new users
5. Erin 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:
* BBB
...
...
@@ -39,8 +39,8 @@ candidate has accepted a formal offer.
What do we want out of this process?
- manage access to the systems that we work on
- give people the oportunity to keep collaborating in the Tor community
- understand if there is anything that can be improved at TPI that may have affect their leaving (we try to get this info with the exit interview)
- give people the opportunity to keep collaborating in the Tor community
- understand if there is anything that can be improved at TPI that may have affected their leaving (we try to get this info with the exit interview)
## Lay off or resignation
...
...
@@ -56,7 +56,7 @@ Offboarding process right now for Staff that resigns or laid off:
8. if they do not volunteer:
1. HR creates a ticket in tpo/web/tpo to remove employee from people page
2. Team lead create confidential ticket in TPA to remove permissions.
3. Remove from all mailing lists and aliases.
3. Remove from all mailing lists and aliases.
4. Handle employee's email
9. if they will volunteer:
1. Team lead create ticket in TPA to remove permissions not associated with the area they will continue volunteering with.
...
...
@@ -97,7 +97,7 @@ The audit process for core members is not happening. We need to have a timeout a
## tickets
* user management procedures are poorly documented: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40129
* user management procedures are poorly documented: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40129
* clarify what happens to email when we retire a user: https://gitlab.torproject.org/tpo/tpa/team/-/issues/32558
