-
Notifications
You must be signed in to change notification settings - Fork 639
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
[READY FOR REVIEW] Adding onboarding and offboarding documents for core team + general - Community Handbook #3498
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for the-turing-way ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I think it would be easier to have two different PR's for this: one with all the documentation and process to onboard new members of the community and another with the offboarding process. |
Thanks @AlexandraAAJ - meaning maybe I just keep these two for the 'core team' as separate from the broader one? |
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.
HI Anne, I've added some comments :)
# TTW Core Team Onboarding checklists | ||
|
||
## Accounts and Permissions | ||
- [ ] Remove from #ttw-core-team channel on Slack |
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
- [ ] 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 | ||
- [ ] Remove from [Core Team Google group](https://groups.google.com/u/1/g/core-team-2022) (currently dormant) |
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.
It it's dormant I wouldn't mention it or as below add (if applicable)
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.
Thanks Alex, good catch! I have added the 'if applicable' in case we bring back that infrastructure
- [ ] (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 from [promotion pack](https://drive.google.com/drive/u/1/folders/1mzGmbJkPnP5q1goQesxDc_E5zAPL0eTF) folder |
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 would careful that people don't remove the folder, just RCM/RPM should make sure that they don't have unlimited permissions?
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.
Yes - do you think the 'viewer' as opposed to 'editor' permissions should be written more explicitly here? I'm imaging something like a table which could be added even, to distinguish between 'project specific', 'maintainer', and 'working group chair' permissions?
- [ ] (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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
- [ ] Coworking Calls | ||
- [ ] Collaboration Cafes | ||
- [ ] Fireside Chat | ||
- [ ] Community Chats |
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 would add a brief explanation about how to remove these calendar invitations from the calendar.
### If member of working group | ||
|
||
### If member of Turing staff team | ||
|
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.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've asked Arielle.
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.
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'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.
### If member of Turing staff team | ||
|
||
|
||
## Announcement of Leave |
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.
Who will be announcing this? is this voluntary? What is the aim? I can find the value of thanking a community member for their contributions but they should previously approve this ?
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 shifted the sections here as they didn't seem to work well - what do you think?
- [ ] Review [TTW Offboarding document](https://hackmd.io/@turingway/ttw-core-team-offboarding) (not to be used for now!) | ||
|
||
## Accounts and Permissions | ||
- [ ] Add to #ttw-core-team channel on Slack |
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.
As the core team is transitioning to Working groups I would add the link to the WG for newcomers to find common interests.
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.
- [ ] (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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this apply to newcomers outside the Turing?
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.
Historically, yes - this has!
book/website/community-handbook/onboarding-offboarding/onboarding-core-team.md
Outdated
Show resolved
Hide resolved
…uring-way into onboarding-materials
…-institute/the-turing-way into onboarding-materials
…-institute/the-turing-way into onboarding-materials
14 February updates
To do:
Bigger question: should 'core team' be used here? Or something broader like "Maintainers Checklist"? |
After re-reading this material – it might be worth archiving those two "core team" onboarding lists as is, with a qualifier that they are no longer used, in favor of a new onboarding list for 'maintainers'. What do folks think? |
I agree with retiring the phrase "core team" - I'm not sure that maintainers is the right word though - whats the definition in this context? |
Thanks @KirstieJane! I think this would be anyone who is in the broader category of folks who might be members or co-chairs of the working groups – at the mid-levels between the constitutional and the contributor level? Thinking of your slides from the community call? Especially because permissions may be different at this mid-level. What do you think? That could be a new issue though, and these could be archived as is, with a qualifier that they are no longer used, and that the term 'core team' has been retired. Because they were used with 10+ people on what used to the be the 'core team', it would make sense to not let them go to waste or not be archived! |
Uh oh! @aleesteele, the image you shared is missing helpful alt text. Check #3498 (comment). Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image. Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs. |
…titute/the-turing-way into onboarding-notes
…titute/the-turing-way into onboarding-materials
Alright, this is ready for review! Based off of @KirstieJane and @AlexandraAAJ's feedback (thank you very much!) I have done a few changes:
I think it's ready for a final review now, thank you! 🙏 |
Summary
In preparation for the first onboarding call on 31 January 2024 - I am uploading these onboarding and offboarding texts that have been used for the Core Team throughout 2023. One is also being written for 'general', alongside developing a presentation for use at onboarding workshop.
Fixes #1537 #2913 #3459
What should a reviewer concentrate their feedback on?
Still a work in progress - I'll add more here soon!
Acknowledging contributors