After we go through the recruiting process and candidate is offered a contract, etc.
## Priorities
What do we want out of this process?
- getting people into the systems to work with their teams
- getting people to understand Tor culture
- getting people to know where to look for information
## TPI hiring procedure
## TPI hiring procedure
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 send 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.
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. Erin sends mail to new employee with the following information:
...
@@ -14,24 +23,24 @@ After we go through the recruiting process and candidate is offered a contract,
...
@@ -14,24 +23,24 @@ After we go through the recruiting process and candidate is offered a contract,
* harvest
* harvest
* next steps
* next steps
5. Erin creates a ticket in TPA's gitlab pgp signed to:
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
. 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
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.
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:
7. Erin creates a ticket in TPA gitlab group requesting to create following accounts:
* BBB
* BBB
*gitlab
*GitLab
*nextcloud
*Nextcloud
* ... maybe more? see the [service list](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service)
* ... maybe more? see the [service list](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service)
8. gaba: New employee receives email from team lead to schedule a meeting with the team for onboarding.
8. gaba: New employee receives email from team lead to schedule a meeting with the team for onboarding.
9. gaba: New employee meets with the team with the [agenda template](https://gitlab.torproject.org/tpo/team/-/wikis/OnBoardingAgendaTemplate)
9. gaba: New employee meets with the team with the [agenda template](https://gitlab.torproject.org/tpo/team/-/wikis/OnBoardingAgendaTemplate)
TODO: core-only onboarding procedure?
# Offboarding process
TODO: can we have buddies? mentors? whatever you call those, the person you ask questions when you're new and confused.
What do we want out of this process?
# Offboarding 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)
## Lay off or resignation
## Lay off or resignation
...
@@ -64,15 +73,6 @@ Offboarding process right now for Staff that gets terminated (fired):
...
@@ -64,15 +73,6 @@ Offboarding process right now for Staff that gets terminated (fired):
7. HR creates a ticket in tpo/web/tpo to schedule employee removal from people page.
7. HR creates a ticket in tpo/web/tpo to schedule employee removal from people page.
8. Handle employee's email.
8. Handle employee's email.
* TODO: emergency termination
* TODO: core-only offboarding procedure
* TODO: what happens with email: https://gitlab.torproject.org/tpo/tpa/team/-/issues/32558 propose that we auto-reply with a bounce explaining the replacement email, to give agency to the sender, expiry 12 months, remove existing forwards older than 12 months
* TODO Need template for auditing services for removal/changes of accounts when offboarding https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service - maybe instead of a template, make some automation to parse the service.md list and ask the operator to act (or not) on each
Next steps:
- discussion on onboarding/offboarding procedures for core-only contributors. Send a msg to cecylia and roger to be included in this discussion. (gaba)
# what is missing
# what is missing
a systematic process by which people get the accesses they need when they join, and it gets removed when they leave
a systematic process by which people get the accesses they need when they join, and it gets removed when they leave
...
@@ -81,30 +81,23 @@ in particular, we often seem to forget to remove people from the tor-internal ma
...
@@ -81,30 +81,23 @@ in particular, we often seem to forget to remove people from the tor-internal ma
> Part of the problem with removing people from tor-internal is that there's no process for tracking people who say they want to stay involved and then don't, now that Damian doesn't do a membership audit anymore. This mostly applies to people who were part of the community before becoming an employee, there's no way to follow up on their participation, but because they had email and/or were on tor-internal beforehand.
> Part of the problem with removing people from tor-internal is that there's no process for tracking people who say they want to stay involved and then don't, now that Damian doesn't do a membership audit anymore. This mostly applies to people who were part of the community before becoming an employee, there's no way to follow up on their participation, but because they had email and/or were on tor-internal beforehand.
> The only person who wasn't added to LDAP when they needed to be was Ian Jackson, and we set up his email several months before he started, and that's how the LDAP issue slipped (because we didn't do LDAP at the same time like we usually do).
The audit process for core members is not happening. We need to have a timeout after which someone is removed or at least checked for membership (?)
The audit process for core members is not happening. We need to have a timeout after which someone is removed or at least checked for membership (?)
# priorities
## TODO list
what do we want out of the onboarding and offboarding processes?
## onboarding
- getting people into the systems to work with their teams
- getting people to understand Tor culture
- getting people to know where to look for information
## offboarding
- 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)
* TODO: core-only onboarding procedure?
* TODO: can we have buddies? mentors? whatever you call those, the person you ask questions when you're new and confused.
* TODO: emergency termination
* TODO: core-only offboarding procedure
* TODO: what happens with email: https://gitlab.torproject.org/tpo/tpa/team/-/issues/32558 propose that we auto-reply with a bounce explaining the replacement email, to give agency to the sender, expiry 12 months, remove existing forwards older than 12 months
* TODO Need template for auditing services for removal/changes of accounts when offboarding https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service - maybe instead of a template, make some automation to parse the service.md list and ask the operator to act (or not) on each
* TODO: discussion on onboarding/offboarding procedures for core-only contributors. Send a msg to cecylia and roger to be included in this discussion. (gaba)
# tickets
## 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
*clarify what happens to email when we retire a user: https://gitlab.torproject.org/tpo/tpa/team/-/issues/32558
