How to Grow an Open Source Project: A Case Study of Python
summary
Python grows through concrete practices: BDFL/delegation hands real ownership to maintainers, producing more active contributors; PEP + running code means proposals require implementations and many PEPs are explicitly rejected, which preserves stability; tooling like reid code review, buildbot CI, migrations (CVS→Subversion→Mercurial, possible Git), and PyPI + pip automate packaging. A community of ~2,500 attendees and strict backward compatibility (despite a rocky Python 3 bytes/str split) keeps enterprises and educators adopting and maintaining large ecosystems.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:32Sponsors
- 0:53Why Python
- 2:21The MIT of Japan
- 4:11Economic model
- 5:14Why am I doing this
- 6:11What is Python
- 7:41Process
- 8:34Pythons Process
- 10:44Enterprise
- 12:12Python
- 15:19Python Framework
- 16:42BBFL
- 18:21Guido
- 21:50Own modules
- 23:38The benevolent dictator
- 26:13Zen of Python
- 27:55PEPs
- 31:51Automation
- 34:36Backward Compatibility
- 36:18Bottom Line
related talks
01h 34mThe development process of Python
28mGrowing Open Source Seeds
40mOops! I Became an Open Source Maintainer! 😱
27mHow to Grow and Mentor an Open Source Community
26mHow to Succeed with Python Across the Enterprise
38mTools for Maintaining an Open Source Project
25mHow to Grow and Mentor an Open Source Community & Achieve Collaboration with Over 170...
53mA better PyData ecosystem, one commit at a time