Offboarding - ganong-noel/lab_manual GitHub Wiki
Six weeks before leaving
Objective
Clarify which work will be handed off to an RA, a PI, or closed
- Create an exit memo named "YYYY last_name Offboarding memo". Save it here.
- Review all open tickets
- Review slide decks you worked on (since this work is often not memorialized in tickets)
- Branches
- In a repo, you can see your open branches by clicking Code -> Branches -> Yours
- Send PIs in slack a list of unmerged branches in git that you are responsible for.
- Each branch should have a short note with it (a) explaining how you will make sure this branch is merged before you leave or (b) explaining why this branch should be deleted
One month before leaving
- Send a handoff proposal to PIs which enumerates which work will be closed, handed off to RA, or handed off to PI
- PI reviews and approves or suggests revisions
- Code handed off to another RA, this code must be re-run by the receiving RA
- Work you are proud of
- Record the backgrounder you are most proud of in examples
- Record the issue ticket(s) you are most proud of by sending them to us in Slack
- Start thinking about your answers to our exit interview questions here and make sure this exit interview has been scheduled.
- Fill out this form with information on classes you took as an RP (if any), which will serve as a resource for future RPs.
- Add to
staff_ids
a good email address to reach out at after you leave
If you have access inside the JPMCI firewall
- Give read/write permissions on all the files that you have written to the edge nodes in the
gnlab
directory - Delete your personal scratch directory
- Move your user directory to
gnlab_alums
- PN note from live discussion with PG 5/6/2024: This was a legacy from when we worked on the edge node in MTD. Now we don’t do this. However, we still might want to create a
gnlab_alums
directory if we have uncommitted code or files that we want to preserve.
- PN note from live discussion with PG 5/6/2024: This was a legacy from when we worked on the edge node in MTD. Now we don’t do this. However, we still might want to create a
Policies
- PI unshares RP from repos.
- PI writes an email asking RP to delete source data.
- It is acceptable to keep local copies of repos that RP worked on.
- If an RP wants to share code more broadly (e.g. as part of a job application), they need to ask PI for written permission and say who they are sharing the code with
RPs Only
- Return keys to Harris storage units
PI notes to self
- Note: This list is based on “cloud accounts” listed here
- Github
- Gsuite
- Slack
- Zotero
- Calendars -- gnlab and gnlab_ra