From no OSS experience to the core team in 15 minutes a day
summary
Claim: a path to the core team with 15 minutes a day by using GitHub, reading README/contributing docs, following the issue tracker and reproducing bugs. The concrete steps: read every issue (big projects like Rails have ~2,000 open issues), add docs and clearer error messages, produce reproduction cases and a failing test PR that maintainers can fix. Examples: Bundler and RubyGems history, Left Pad’s 50-package removal that broke many Node apps, and four years of real maintenance experience show this approach leads to real commits and roles.
AI-written summary · about
chapters (19)
- 0:00Start
- 1:13CLOUDCITY DEVELOPMENT
- 1:28The Ruby Way
- 2:38Bundler
- 3:05how to start
- 4:37"real programmers" do not exist
- 5:55what are your goals?
- 9:15benefits!
- 11:49can you work for free?
- 13:31open source means losing control of your work
- 15:45choose a license
- 17:08we made it! here's the plan
- 21:36help with issues
- 22:49reproduce bugs
- 24:28writing patches
- 25:55improve everything
- 27:31you're doing it!
- 28:05now you're in charge
- 28:22what did we learn?
related talks
26mFrom 9-to-5 to Pull Requests: Sustainable Open Source Contribution
29mLevel Up with OSS: Develop Your Rails Dev ...
22mA beginner's guide to Open Source
51mMy awesome journey with Open Source
29mTaking over Someone Else's Open-Source Projects
39mMaintaining a big open source project: lessons learned
32mYour First Open-Source Contribution
46mGetting Started as an OSS Contributor/Maintainer