Are we inclusive yet? (Diversity Panel)
summary
Panelists give concrete practices: spend real time onboarding (one story gives five months ramp before asking for production code), do deliberate pair programming and patient mentoring, teach basics like why to source GOPATH, and pause in meetings to ask quieter people for input. Examples include rebuilding confidence after a lonely GopherCon moment, a mentor who met for lunches to solve specific problems, and moving from retail or non‑CS backgrounds into Go and infrastructure roles through sustained community support.
AI-written summary · about
chapters (7)
- 0:00Introduction and panel intros
- 10:24Why inclusivity feels uncomfortable
- 18:13Healthy communities and welcoming spaces
- 25:05Listening and giving space to others
- 31:14Patience and mentorship for beginners
- 36:31Time and trust for new team members
- 39:02Closing remarks and Q&A
related talks
46mPanel Discussion: How to Work with Other Po
39mInclusive Leaders in Tech
46mPanel Discussion | Building Strong Testing Teams: Management, Development, and Diversity
33mExpanding the Contributor Pipeline Through Inclusion
46mPanel: Birds of a Different Feather Soar Together
44mTen Practical Approaches for Building Inclusive Open Source and InnerSource..
26mOpen Source Inclusivity: Empowering Newcomers
34mPanel: Platform Resilience, Built...