It's not just code: managing an open source project
summary
Claims that most projects run on one or two people do most work and that success depends on explicit choices about goals, stage, governance, licensing, and funding. Actual tools and templates named include GitHub code of conduct, README Project, tidyverse PR review principles, Python packaging guides, and GitHub Sponsors. Examples: an obsolete 454 genomics package is retired; Posit runs a virtuous cycle with 43 people working full-time on open source to fund maintenance.
AI-written summary · about
chapters (15)
- 0:00Open source management intro
- 1:03Open source backbone
- 2:51Open source roles pyramid
- 4:36Developer to maintainer
- 6:01Open source challenges
- 7:03Project core goals
- 10:38Managing expectations
- 14:18PR standards
- 16:26Maintainer templates
- 17:50Licensing and governance
- 18:32Funding open source
- 23:50Posit’s funding cycle
- 25:57Building community
- 26:42Learning management
- 27:45Q&A
related talks
27mDesign Your Open Source Project
48mAnatomy of an Open Source Project
16mThere's More to Open Source than Code
23mGrowing A Successful and Sustainable Project
25mThere's More to Open Source than Code
39mManaging an Open Source Project
49mCommunities Over Code: How to Build a Successful Project
16mBeyond Pull Requests: How Non-Code Contributions Scale Open Source Projects