[READY FOR REVIEW] Adding onboarding and offboarding documents for core team + general - Community Handbook #3498
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| (ch-onboarding-offboarding)= | ||
| # Onboarding and Offboarding | ||
|
|
||
| As a project, our goal is to provide individuals and organizations in academia, industry, government, and the public sectors the information they need to ensure that their projects are easy to reproduce and reuse. | ||
|
|
||
| We encourage all stakeholders in data science to utilise _The Turing Way_ to understand their roles and responsibilities for reproducibility. | ||
|
|
||
| These onboarding and offboarding documents are living documents – as is _The Turing Way_ itself. | ||
|
|
||
| As you will learn from being in this community: this is a constantly-evolving project that holds [emergence as a core value](https://hackmd.io/kVkwKSYuSLWWhLzlNSuT0g). In other words: as the project evolves – so will the team that enables its sustainability as a project. | ||
|
|
||
| Or alternatively, whether it's changed responsibilities, a new job, shifting interests, or any other reason –– we understand that life happens, and that communities will always be shifting and evolving! While we are sad to see you go for now, we hope that you'll stay engaged with us in *The Turing Way* community! | ||
|
|
||
| Whether you are joining |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,66 @@ | ||
| (ch-core-team-offboarding-checklist)= | ||
| # Core Team Offboarding Checklist | ||
|
|
||
| 🌙 **We are sad to see you leave *The Turing Way* Core Team!** 🌙 | ||
|
|
||
| ```{admonition} Note | ||
| :class: tip | ||
| This document was prepared and shared from 2022-2023 for 10-15 community members who were identified to have a leadership role within the community, either transitioning out or stepping out of that role. At the time, this group was called the "Core Team" of _The Turing Way_, used as umbrella term for all community members who have taken on an maintenance role within the community. | ||
|
|
||
| This onboarding checklist is no longer in active use, it has been added to the Community Handbook for archival purposes. | ||
| ``` | ||
|
|
||
| ## Accounts and Permissions | ||
| - [ ] Remove from #ttw-core-team channel on Slack | ||
| - [ ] Change [TTW Github repository](https://github.com/alan-turing-institute/the-turing-way) permissions as needed | ||
| - [ ] Add to 'Alumni' section of [Ways of Working](https://github.com/alan-turing-institute/the-turing-way/blob/main/ways_of_working.md) page on TTW Github repository | ||
| - [ ] (If applicable) Follow the [HR Operations process](https://mathison.turing.ac.uk/page/2936) for Change of Conditions Forms (CoCs) and Leavers/Resignations for the Alan Turing Institute | ||
| - [ ] (If applicable) Participate in [Enrichment Exit Process](https://mathison.turing.ac.uk/page/3021?SearchId=0) for the Alan Turing Institute | ||
| - [ ] (If applicable) Remove from HackMD team for The Turing Way | ||
| - [ ] (If applicable) Give Accounts/Password Access on Keybase | ||
| - [ ] (If applicable) Remove from [The Turing Way Core Google Drive](https://drive.google.com/drive/u/0/folders/1bdjA-fBotMi9CnjDqu84d5hPZWwjgi-x) | ||
| - [ ] Remove email from [promotion pack](https://drive.google.com/drive/u/1/folders/1mzGmbJkPnP5q1goQesxDc_E5zAPL0eTF) folder | ||
| - [ ] Remove email from [conference talks/workshop applications](https://drive.google.com/drive/u/0/folders/1eNHq9sXq6Z8Q5Ep0MzNS0GsB3FKgTi3E) folder | ||
| - [ ] (If applicable) Remove from [Core Team Google group](https://groups.google.com/u/1/g/core-team-2022) (currently dormant) | ||
| - [ ] (If applicable) Remove from Canva team | ||
| - [ ] (If applicable) Remove from Penpot team | ||
| - [ ] (If applicable) Remove from Keybase group | ||
|
|
||
|
There was a problem hiding this comment. Are members able to remove themselves or is this something an administrator has to do? At Keybase, I would say remove the TTW folder from your app |
||
| ## Personal information | ||
| - [ ] Move information on [TTW Team slides](https://docs.google.com/presentation/d/1PeQ_gg5tOJVhOA4aSnVumsowD-bfRFEroWfGsxxaGCw/edit#slide=id.g1aee8e18598_0_0) to 'Alumni' section | ||
| - [ ] (If applicable) remove [TTW project page](https://www.turing.ac.uk/research/research-projects/turing-way) on Alan Turing website | ||
| - [ ] (If applicable) remove yourself to [TPS/Whitaker Lab slide deck](https://docs.google.com/presentation/d/1g-plncmi00FK97QuYDfqq7oPzUmL0xkHm1hy4X81IX8/edit#slide=id.gf5e62e1b31_1_0) | ||
|
|
||
| ## Events & Calendars | ||
| - [ ] Remove from TTW Community Calendars | ||
| - [ ] The Turing Way Community (public-facing) | ||
| - [ ] The Turing Way Core Team (internal) | ||
| - [ ] Remove from calendar invites for The Turing Way core team | ||
| - [ ] Coworking Calls | ||
| - [ ] Collaboration Cafes | ||
| - [ ] Fireside Chat | ||
| - [ ] Community Calls | ||
|
|
||
| If applicable, see [TPS Project Management Repository](https://github.com/alan-turing-institute/tps-project-management) about being onboarded onto the Tools, Practices, and Systems programme more broadly at the Alan Turing Institute. Other research teams and/or groups may have their own onboarding practices and/or repositories (i.e. the [Research Application Manager (RAM) team](https://github.com/alan-turing-institute/research-application-management) or [Community Management (CM) team](https://github.com/alan-turing-institute/open-community-building)). | ||
|
|
||
| ## Documenting your Experiences | ||
|
|
||
| We understand that wrapping up chapters and projects with _The Turing Way_ may take some time! | ||
|
|
||
| If you need support completing your tasks, please reach out to the Research Community Manager or Research Project Manager to help support you through the process. | ||
|
|
||
|
There was a problem hiding this comment. Can we check if there is a some Turing offboarding policy? I would add that policy and that apart from it, this onboarding applies to everyone, with specific attention on accounts and permissions (all the "if applicable ones") There was a problem hiding this comment. There was a problem hiding this comment. I'll add this as a direct link for folks – but most important is adding the qualifying that this was in active use from 2022 to 2023. |
||
| They can schedule an offboarding call with you in order to help document your work with _The Turing Way_ community. | ||
|
|
||
| Remember, everyone has expertise to share – and documentation will help us to ensure that others can learn from your experiences too. | ||
|
|
||
| We ask that you please update your [Record of Contributions](https://the-turing-way.netlify.app/afterword/contributors-record.html) to document your experiences with contributing to _The Turing Way_. | ||
|
|
||
| ## Celebrating your Contributions | ||
|
|
||
| Thank you so much for all your contributions to *The Turing Way*. We really appreciate you sharing your time and expertise with us in this community! | ||
|
|
||
| The Research Community Manager or Research Project Manager will reach out to discuss how to celebrate you in a way you prefer. | ||
|
|
||
| We are hoping to develop a "emiritus contributor programme" or other means of keeping you involved in our community moving forward. | ||
|
|
||
| Remember, you can always re-engage with us if you are interested in re-joining the project. You are always welcome! | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,68 @@ | ||
| (ch-core-team-onboarding-checklist)= | ||
| # Core Team Offboarding Checklist | ||
|
|
||
| **☀️ Welcome to *The Turing Way* Core Team!☀️** | ||
|
|
||
| ```{admonition} Note | ||
| :class: tip | ||
| This document was prepared and shared from 2022-2023 for 10-15 community members who were identified to have a leadership role within the community. At the time, this group was called the "Core Team" of _The Turing Way_, used as umbrella term for all community members who have taken on an maintenance role within the community. | ||
|
|
||
| This may have included the following: | ||
| - Chairs or co-chairs of working groups within the community | ||
| - Organisers of events such as Book Dashes | ||
| - Staff members of the Alan Turing Institute leading on different initiatives | ||
|
|
||
| This onboarding checklist is no longer in active use, it has been added to the Community Handbook for archival purposes. | ||
| ``` | ||
|
|
||
| ## Accounts and Permissions | ||
| - [ ] Add to #ttw-core-team channel on Slack | ||
|
There was a problem hiding this comment. As the core team is transitioning to Working groups I would add the link to the WG for newcomers to find common interests. |
||
| - [ ] Add to [TTW Github repository](https://github.com/alan-turing-institute/the-turing-way) with "Maintainer" permissions (change as needed for role) | ||
| - [ ] Add to [Ways of Working](https://github.com/alan-turing-institute/the-turing-way/blob/main/ways_of_working.md) page on TTW Github repository | ||
| - [ ] Share [zenodo link for The Turing Way community](https://zenodo.org/communities/the-turing-way/?page=1&size=20) | ||
| - [ ] (If applicable) Read [Onboarding guidebook and Information for New Starters](https://mathison.turing.ac.uk/Interact/Pages/Section/ContentListing.aspx?subsection=3363) at the Alan Turing Institute | ||
| - [ ] (If applicable) Add to HackMD team for The Turing Way | ||
| - [ ] (If applicable) Give Accounts/Password Access on Keybase | ||
| - [ ] (If applicable) Add directly to [The Turing Way Core Google Drive](https://drive.google.com/drive/u/0/folders/1bdjA-fBotMi9CnjDqu84d5hPZWwjgi-x) | ||
| - [ ] Share [promotion pack](https://drive.google.com/drive/u/1/folders/1mzGmbJkPnP5q1goQesxDc_E5zAPL0eTF) folder | ||
| - [ ] Share [conference talks/workshop applications](https://drive.google.com/drive/u/0/folders/1eNHq9sXq6Z8Q5Ep0MzNS0GsB3FKgTi3E) folder | ||
| - [ ] (If applicable) Add to [Core Team Google group](https://groups.google.com/u/1/g/core-team-2022) (currently dormant) | ||
| - [ ] (If applicable) Add to Canva team | ||
| - [ ] (If applicable) Add to Penpot team | ||
| - [ ] (If applicable) Add to Keybase group | ||
|
|
||
| ## About yourself | ||
| - [ ] Add your information to [TTW Team slides](https://docs.google.com/presentation/d/1PeQ_gg5tOJVhOA4aSnVumsowD-bfRFEroWfGsxxaGCw/edit#slide=id.g1aee8e18598_0_0) | ||
|
There was a problem hiding this comment. Does this apply to newcomers outside the Turing? There was a problem hiding this comment. Historically, yes - this has! |
||
| - [ ] (If applicable) add yourself to [TTW project page](https://www.turing.ac.uk/research/research-projects/turing-way) on Alan Turing website | ||
| - [ ] (If applicable) add yourself to [TPS/Whitaker Lab slide deck](https://docs.google.com/presentation/d/1g-plncmi00FK97QuYDfqq7oPzUmL0xkHm1hy4X81IX8/edit#slide=id.gf5e62e1b31_1_0) | ||
| - [ ] Introduce yourself on the Turing Way slack (in #introductions) | ||
|
|
||
| ## Events & Calendars | ||
|
|
||
| - [ ] Give links to TTW Community Calendars | ||
| - [ ] The Turing Way Community (public-facing) | ||
| - [ ] The Turing Way Core Team (internal) | ||
| - [ ] Add to calendar invites for The Turing Way core team | ||
| - [ ] Coworking Calls | ||
| - [ ] Collaboration Cafes | ||
| - [ ] Fireside Chat | ||
| - [ ] Community Calls | ||
|
|
||
| ## Communication Channels + Platforms | ||
| - [ ] Share links | ||
| - [ ] [Slack](https://theturingway.slack.com/) | ||
| - [ ] [Twitter](https://twitter.com/turingway) | ||
| - [ ] [Mastodon](fosstodon.org/turingway) | ||
| - [ ] [Newsletter](https://buttondown.email/turingway/) | ||
| - [ ] [Linkedin](https://www.linkedin.com/company/the-turing-way/) | ||
| - [ ] Useful Links/Information Hub | ||
| - [ ] [Core Team note of notes](https://hackmd.io/@turingway/ttw-team-note-of-notes) | ||
|
|
||
| If applicable, see [TPS Project Management Repository](https://github.com/alan-turing-institute/tps-project-management) about being onboarded onto the Tools, Practices, and Systems programme more broadly at the Alan Turing Institute. Other research teams and/or groups may have their own onboarding practices and/or repositories (i.e. the [Research Application Manager (RAM) team](https://github.com/alan-turing-institute/research-application-management) or [Community Management (CM) team](https://github.com/alan-turing-institute/open-community-building)). | ||
|
|
||
| ## Useful links | ||
| - [The Turing Way Core Google Drive](https://drive.google.com/drive/u/0/folders/1bdjA-fBotMi9CnjDqu84d5hPZWwjgi-x) | ||
| - [Community Handbook](https://the-turing-way.netlify.app/community-handbook/community-handbook.html) | ||
| - [TTW Guide to Using Slack](https://hackmd.io/@turingway/ttw-slack-intro) | ||
| - [TTW Github repository guide](https://docs.google.com/spreadsheets/d/19IfeIxtWQpDglzfOY8vpq6TFhM1jEJa1OnNdAYWjzg8/edit#gid=1136871433) | ||
| - [TTW Translation Github team](https://github.com/TWTranslation) | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| (ch-general-onboarding)= | ||
| # General Onboarding Calls | ||
|
|
||
| **Welcome to The Turing Way!** | ||
|
|
||
| We're so glad to have you here! On this page, you can learn more about our Onboarding Calls, which has been re-initiated in 2024. | ||
|
|
||
| ## About the Onboarding Call | ||
|
|
||
| Historically, onboarding in _The Turing Way_ community has happened through 1:1 connections, between the Community Manager or Community Leaders and prospective community members of the project. As the project has grown, so have the number of entry points: where folks may be interacting with different parts of project and community in . | ||
|
|
||
| Starting in 2024, these calls are hosted every two months, where community leaders meet new members and create a space for them to connect with our community and available resources, ensuring they have the support they need to navigate and kickstart their journey with _The Turing Way_. These calls create an open space for questions, discussions, and a warm welcome into our community. | ||
|
|
||
| During this hour-long call, participants learn about _The Turing Way_ project in a group setting and how to contribute to different sub-projects and working groups within the community, and may gain hands-on experience in contributing to _The Turing Way_ guides (in some cases, even making their first pull request!). | ||
|
|
||
| This is a space to bring your questions and interests – we're so excited to meet you! | ||
|
|
||
| ## Agenda | ||
|
|
||
| As of January 2024, onboarding calls are being trialed using the following format: | ||
|
|
||
| 1. Introduction, icebreaker | ||
| 2. The Turing Way - What is it? | ||
| 3. How to get involved with The Turing Way? | ||
| 4. Do you have any questions for us? | ||
| 5. Feedback | ||
|
|
||
| ## Want to onboard other community members? | ||
|
|
||
| Please join the [#onboarding](https://theturingway.slack.com/archives/C06EVT7GKK3) channel on _The Turing Way_ slack! | ||
|
|
||
| We would love to have more community members join in welcoming others to the community. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this offboarding document only applicable for people who are/were part of core team? Or can anyone deciding to leave be able to take what they need?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added in a bit more of an introduction for who is defined as the 'core team' - what do you think?
Maybe this is more broader a 'maintainers' checklist - not necessarily a 'core team checklist'? Will post this comment for greater visibility below