All Hands on Deck: Mentorship Breakdowns and How You Can Prevent Them!
summary
Draws from a Google Season of Docs placement with CERN and Kubernetes community work to name four concrete failure modes: procedural (no self‑assessment, missing entry prerequisites like Git, need a written scope and contributor ladder), technical (fragile developer environments — use ephemeral dev environments and browser‑based IDEs), personal (mentors overloaded by one‑to‑many loads leading to burnout — cap mentees and track time), and interpersonal (timezones — require asynchronous agendas/recordings; enforce inclusive‑language bots).
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:19What is mentorship
- 3:16Mentorship in Open Source
- 4:09Community Involvement
- 5:29Mentorship Opportunities
- 6:12Mentorship Failures
- 7:41Procedural breakdowns
- 10:59Named roles
- 13:35Gamification
- 16:26Scope in Context
- 20:05Technical Breakdown
- 21:31Dev Environments
- 22:49Personal Breakdowns
- 26:51Working in Public
- 28:02Interpersonal breakdowns
- 30:01What can we do about it
- 35:19Resources
- 35:34Conclusion
related talks
36mScaling Non-Traditional Contributor Mentoring Initiatives - Paris Pittman, Google
32mOvercoming The Challenges Of Mentoring
41mPanel: Mentoring the Next Generation of Global Contrib...
46mMentorship in Three Acts
34mDeep End Diving: Getting Up to Speed on New Codebases
24mHow to be a good mentor
35mBecoming a mentor, why and how?
31mThe Mentor Playbook