Oops! I Became an Open Source Maintainer!
summary
First contribution in 2016 and within a year gaining commit rights to a couple projects and shortly after to CPython, involvement centers on code review triage, managing bug trackers and GitHub notifications, and running the python.org site built on Django while handling moderation and code‑of‑conduct incidents (including a mistaken unilateral ban). Time management breakdown leads to burnout. Concrete takeaways are to write a maintenance guide, establish a succession plan, run periodic maintainer sprints, and secure funding like GitHub Sponsors or Patreon.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:19My Story
- 2:25How did it happen
- 3:12Why
- 6:11Mentorship
- 13:33What happens the first time
- 16:27Biggest mistake I made
- 18:21Why am I still contributing
- 20:26Advice
related talks
40mOops! I Became an Open Source Maintainer! 😱
28mBest Practices for an Effective Open Source Contribution
46mClear Your Own Path to Open Source Maintainer
36mWho Will Maintain the Future? Tackling the Graying of Open Source Software
31mGetting Started with Open Source Contributions
27mOpen-source in the eyes of a Minority Contributor
51mMy awesome journey with Open Source
35mFrom Storming to Performing: Growing Your Project's Contributor Experience