# Offboarding
### Transfer documents and code:
|location|TODO|
|-|-|
| github |- Groom open PRs, hand over any ongoing work<br> - check personal repositories and forks to identify any work that needs to be handed over<br> - Check OWNERS, CODEOWNERS files on relevant [operator-framework](https://github.com/operator-framework) and [openshift](https://github.com/openshift) repositories including:<br> - [operator-framework-olm](https://github.com/openshift/operator-framework-olm)<br> - [operator-framework-rukpak](https://github.com/openshift/operator-framework-rukpak)<br> - [operator-framework-deppy](https://github.com/openshift/operator-framework-deppy)<br><br> - Ensure at least one member for any github teams you are a member of: <br> - [openshift-team-olm](https://github.com/orgs/openshift/teams/openshift-team-olm/members?query=)<br> - [openshift-team-olm-maintainers](https://github.com/orgs/openshift/teams/openshift-team-olm-maintainers/members?query=)<br> - [openshift-team-marketplace](https://github.com/orgs/openshift/teams/openshift-team-marketplace/members?query=)<br> - [openshift-team-marketplace-maintainers](https://github.com/orgs/openshift/teams/openshift-team-marketplace-maintainers/members?query=)<br> - [operator-framework/teams](https://github.com/orgs/operator-framework/teams)<br>- Share any private [gists](https://gist.github.com/)
|[Google Drive](https://drive.google.com/drive/u/0/my-drive)<br>[HackMD](https://hackmd.io/?nav=overview)|- Transfer ownership of documents, videos, spreadsheets etc. to a teammate.<br>- Link relevant documents in the [Hive mind doc](https://docs.google.com/document/d/1-7_bnsSwM4vtpDo1jcdBNyLbMPi-Q39wpr2dx2IsO-I/edit?pli=1#heading=h.ma2uyc701fyb)|
|[Calendar](https://calendar.google.com/calendar/u/0/r)<br>[Zoom](https://zoom.us/)|- Transfer ownership of recurring meetings, if any|
|[Jira](issues.redhat.com/)|Hand off any assigned work to someone on the team. For urgent/complex issues or bugs, this can involve a handoff meeting to discuss the specifics of the work|
|[Hive mind doc](https://docs.google.com/document/d/1-7_bnsSwM4vtpDo1jcdBNyLbMPi-Q39wpr2dx2IsO-I/edit?pli=1#heading=h.ma2uyc701fyb)| Update any missing information/links |
### Knowledge transfer:
For any existing ongoing work, discuss with the team about who will take over. This should be a recorded meeting, to be accessible to those absent from the meeting, or for future contributors. Some useful meetings include:
- Brain dump sessions: general meetings to give an overview of work in progress
- Open Q&A: Sessions to address any questions about the direction of the work
- Focus sessions: Sessions about a specific topic
Also consider making a list of planned work, or a wishlist of TODOs for anything that could not be completed.
### Reassessing team capacity:
With the loss of a team member, the team will have to reevaluate what should be worked on. This includes:
- Reassessing sprint goals to match capacity
- Assigning new POCs for any orphaned component/codebase/meeting
- Reorganizing Bugdoccop schedules to fit with the new capacity
- Reevaluating team process/schedules, if required.
- Ensuring continuation of any assigned mentorship within teams for newer members.
Sign in with Wallet
Connect another wallet