How To Get A Project Unstuck
summary
Case studies show concrete moves that unstick projects: consolidating scattered todo lists and choosing the platform most active contributors use, adding missing continuous integration, and doing release-management work that produces outcomes like autoconf 2.70 released after five beta releases and 157 patches merged. Small interventions also work — about 15 hours donated can catalyze a stalled release — and targeted funding from individuals and organizations (Keith Bloomberg Free Software Foundation New Toolchain Fund) pays for concentrated work that actually gets things shipped.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:13How To Get a Project Unstuck
- 10:31Gathering Funding
- 11:30Corporate Funding
- 19:34Working Assumptions
- 22:49Skills Are Fungible Domain Knowledge Can Be Learned and Credibility Can Be Earned
- 23:41Domain Knowledge Can Be Learned
- 30:08How Can You Set Yourself Up for Success
- 32:17Taking Charge
- 34:18Making Change
- 36:50Financial Infrastructure
- 37:49Passing the Baton
related talks
47mHow To Get A Project Unstuck -- And Fixing The Skill Gaps That Got Us Here
49mCommunities Over Code: How to Build a Successful Project
34mBreaking Out of the Open Source Burnout Cycle
42mBuilding On-Ramps for Non-Code Contributors in Open Source
43mJust Keep Swimming: Don't drown in your open source project!
58mResponsibly Abandoning Open Source Projects
46mMove Slow and Try Not to Break Each Other
38mSimple Steps for a Calm “Sunset”