Taking over Someone Else's Open-Source Projects
summary
Explains how to rescue widely used Ruby libraries by taking ownership rather than forking: ask for GitHub owner and RubyGems push access so releases actually work, triage a year of stalled PRs (Hashie had no commits for a year), add CI like Travis and rubocop with autogen config plus badges, CONTRIBUTING and CHANGELOG files, and use labels to turn “bug?” into actionable work. Grape reaches ~4,800 stars and community-driven releases prove the approach works.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:36Why take over projects
- 6:03Contacting original maintainer
- 9:17Formal takeover process
- 10:59Life after takeover
- 12:01Project infrastructure
- 13:27Contributor workflows
- 15:53Abandoned PRs management
- 18:43Merging and releasing backlog
- 21:29Long-term maintenance
- 23:38Recruiting maintainers
- 26:04Progress over grand plans
- 26:25Successful maintained projects
- 27:46Why communities matter
related talks
26mFrom 9-to-5 to Pull Requests: Sustainable Open Source Contribution
22mA beginner's guide to Open Source
35mYour First Open-Source Contribution
35mTending Your Open Source Garden
39mMaintaining a big open source project: lessons learned
37mOpen Source Maintenance
33mA Third Way For Open-Source Maintenance
30mFrom no OSS experience to the core team in 15 minutes a day