Open Source Maintenance
summary
Maintains RubyGems, RDoc and http-persistent, explains concrete maintenance habits: integrate Bundler into RubyGems as a real project goal, enforce small atomic commits and descriptive commit messages, and use issue labels/milestones to triage work. Shares surprises — a user hit 750,000 requests on an http client — and documents automation: test runs on Travis CI, releases with rake release (git tag, gem push, docs update). Provides concrete starter steps for contributors.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:21Maintaining open source
- 4:05Open source values
- 6:37Sustaining communities
- 8:43Open source benefits
- 9:04Easier maintenance with small commits
- 12:34Good commit messages
- 16:49Managing issues and PRs
- 19:16Avoiding mistakes
- 21:02Politeness in issues
- 23:07New features caution
- 25:55Keep code simple
- 27:40Refactoring for APIs
- 28:21Good API traits
- 30:06Lowering contributor barriers
- 32:54Automating maintenance
- 33:14Start contributing
- 36:18Q&A
related talks
35mTending Your Open Source Garden
33mA Third Way For Open-Source Maintenance
39mMaintaining a big open source project: lessons learned
20mAutomating maintainers work: The Prototype
44mGitHub Flavored Ruby
29mTaking over Someone Else's Open-Source Projects
26mFrom 9-to-5 to Pull Requests: Sustainable Open Source Contribution
25mGrowing a library ecosystem