OnBoarding-Procedures.md

@@ -27,6 +27,14 @@ What do we want out of this process?
 
 ## Offboarding process
 
+1. They express to the membership audit secretary that they are not going to be a core contributor anymore.
+2. Exit interview is sent (a list of questions replied to by email).
+3. Return of swag or anything else of Tor's that they have
+4. Membership secretary creates a ticket in tpo/web/tpo to remove contributor from the people page
+5. Membership secretary creates a confidential ticket in TPA to remove permissions.
+6. Remove from all private mailing lists and aliases. Handle contributor's email.
+7. Check if they are a security liaison (i.e. on the security@ list), and if so go through the removal process.
+
 ### Priorities
 
 What do we want out of this process?
@@ -79,7 +87,7 @@ What do we want out of this process?
 
 ### Resigns or laid off
 
-Offboarding process right now for Staff that resigns or laid off:
+Offboarding process right now for Staff that resigns or are laid off:
 
  1. Employee sends letter of resignation to HR and team lead.
  2. Exit interview is sent (a list of questions replied by email).
@@ -87,15 +95,17 @@ Offboarding process right now for Staff that resigns or laid off:
  4. Return of company property
  5. Send a reminder to submit all expenses and finish the time sheet through the last day worked.
  6. Remove from payroll
- 7. HR checks with employee if they will continue contributing to the project as a core volunteer. If they volunteer HR needs to ask in which area.
- 8. If they do not volunteer:
-    1. HR creates a ticket in tpo/web/tpo to remove employee from the people page
-    2. Team lead creates a confidential ticket in TPA to remove permissions.
-    3. Remove from all mailing lists and aliases.
-    4. Handle employee's email
- 9. If they will volunteer:
-    1. Team lead creates a ticket in TPA to remove permissions not associated with the area they will continue volunteering with.
-    2. Remove from tor-employees mailing lists.
+ 7. If person is core contributor, HR checks with employee if they will continue contributing to the project as a core volunteer and in which area. At this point forward, the person's tor-internal membership will be subject to the Community membership audit process.
+  7.1 If the person was a core contributor before becoming an employee or contractor and is terminated (fired), TPI and the Community Council will coordinate to decide whether the person should remain on tor-internal. (https://gitweb.torproject.org/community/policies.git/tree/membership.txt#n116) https://gitlab.torproject.org/tpo/team/-/wikis/Onboarding-Procedures#termination
+8. If they are not core contributor or do not volunteer: 
+  8.1 HR creates a ticket in tpo/web/tpo to remove employee from the people page
+  8.2 Team lead creates a confidential ticket in TPA to remove permissions.
+  8.3 Remove from all private mailing lists and aliases.
+  8.4 Disposition of employee's email
+    8.4.1 If they will volunteer: 
+  8.5 Team lead creates a ticket in TPA to remove permissions not associated with the area they will continue volunteering with.
+  8.6 Remove from tor-employees mailing lists.
+  8.7 Check if they are a security liaison (i.e. on the security@ list), and if so go through the removal process.
 
 ### Gets terminated (fired)
 
@@ -129,7 +139,7 @@ The audit process for core members is not happening. We need to have a timeout a
  * 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)
+ * 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