@@ -9,89 +9,23 @@ After we go through the recruiting process and candidate is offered a contract,
...
@@ -9,89 +9,23 @@ After we go through the recruiting process and candidate is offered a contract,
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:
. holidays calendar
* holidays calendar
. org chart
* org chart
. 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:
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 following agenda (needs better documentation, see agenda template in the wiki, which needs to be updated with the procedure below, 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)
Explain statement of values, social contract and code of conduct.
How the the organization the Tor project works.
It is a non-profit incorporated in the US.
There is a community of contributors (explain core contributors, others, etc)
TPI is divided in teams, etc. Explain which teams we have.
Sponsor work is funded by grants we apply to (there is a fundraising team that bottomline this process).
Sponsor projects are cross-teams. They will be assign to 0, 1 or more projects.
All hands meetings once a week. Some of them are compulsory.
Face to face meetings twice a year.
Security for communications and services: 2FA, GPG, Signal. <- our security policy! it exists!
How your team works and which projects the team maintains
Stakeholders for your work.
Roadmap and the kanban board for the team.
Meetings:
Public meeting happens in IRC every team-date-for-meetings.
Semi-public meetings for sponsored project happens bi-weekly in BBB.
1:1s with team lead
Mailing lists and IRC channels <- duplicates welcome email?
#tor-project, #tor and #tor-dev public channels for the whole community
#tor-internal, #cakeorpie private channels with core Tor members
