Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process/checklist for when an employee leaves PhET #130

Open
ariel-phet opened this issue Jan 16, 2020 · 2 comments
Open

Process/checklist for when an employee leaves PhET #130

ariel-phet opened this issue Jan 16, 2020 · 2 comments
Assignees

Comments

@ariel-phet
Copy link
Contributor

@amanda-phet suggested awhile back we need a process and checklist to make sure various items get addressed when an employee leaves PhET. This would be good to discuss, potentially even at Status meeting. I have made a draft checklist here:

https://github.com/phetsims/phet-info/blob/master/checklists/employee_leaving_checklist.md

Assigning @amanda-phet @oliver-phet for input.

@oliver-phet
Copy link
Contributor

Here's the CU exit checklist I use, if it helps: https://docs.google.com/document/d/0B3aB5oT9c4e0R2VrTXVWd0pleFU/edit

@amanda-phet
Copy link
Contributor

I think explicit notes to delete from the team page, slack, google group, and google drive are needed, and who is the point person for doing so. I frequently find people no longer affiliated with PhET are still visible in these places. There's an especially important but annoying task of finding all files in google drive that may have been individually shared with them (or created by them) that simply removing from the google group doesn't resolve. I have sometimes taken it upon myself to take care of the task (I've done it in all of the mentioned spaces) but it would be much better if we consistently removed a person from all spaces at once.

@ariel-phet ariel-phet removed their assignment Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants