Advice to Incubator Mentors
summary
Projects get three mentors as a typical minimum and usually take two to three years to graduate; mentors must help bootstrap infra, move sites onto ASF hosting, and sort trademark/branding early or graduation stalls. Practical fixes include publishing a release checklist to stop dozens of RCs, keeping the committer bar deliberately low, forcing decisions back onto the mailing list instead of private or instant channels, and using the maturity model to show concrete gaps.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 4:22Mentor responsibilities and project guidance
- 11:25Common incubator project issues
- 22:17Off-list discussions and private list misuse
- 27:19Video meetings and asynchronous communication
- 30:49Website control and branding policies
- 32:34Mentor availability and project longevity
- 35:24Early graduation risks and maturity model
- 37:12Closing remarks and session wrap-up
related talks
55mNavigating the Incubator Trenches
14mMentorship as a Pathway to Open-Source Project Sustainability
37mBuilding mentoring into an os community that welcomes and values new contributors
26mCloud Native Mentorship: Tips for Being a Great Mentor to CNCF Students
36mScaling Non-Traditional Contributor Mentoring Initiatives - Paris Pittman, Google
27mHow to Grow and Mentor an Open Source Community
50mSupporting your peers' growth as a tech lead
47mPanel Discussion: Creating your Community Mentorship Program