Open Source: When Nights & Weekends Are Not Enough
summary
Argues that contributions often happen during the workweek (an opensource survey surprised him), not just nights and weekends, and shows practical habits: use bundle open and byebug to debug libraries, submit small, well‑contextualized issues and one‑liner PRs, keep gems current (examples: updated a sequel adapter for Rails 5.1), and publish reusable code (built and published an Argentina invoice gem that later accepted a PR). Recommends company practices like open source Fridays and recruiting co‑maintainers to avoid stalled PRs and orphaned projects.
AI-written summary · about
chapters (20)
- 0:00Open Source: When Nights & Weekends Are Not Enough
- 0:42Founder & Software Engineer
- 5:10Every Night Some Nights
- 5:57Entire Weekends Some Weekend Nights
- 6:46Using and contributing to open source often happens on the job
- 7:13What is an open source contribution anyway?
- 8:06Creating an open source project
- 9:03Adding additional info to an existing issue
- 9:27Proposing a workaround
- 10:00Answering a question in Stack Overflow
- 10:30Contribution: Adding value to on open source project
- 11:488 Tips for Contributors
- 12:03A Workflow Without Contributions
- 13:23A Workflow with Contributions
- 14:42bundle open & byebug are your friends
- 18:37Keep up with the latest versions
- 25:15database_cleaner & email-spec
- 25:512 Tips for Maintainers
- 28:582 Tips for Managers
- 29:39Encourage your team members to make contributions
related talks
26mFrom 9-to-5 to Pull Requests: Sustainable Open Source Contribution
16mThere's More to Open Source than Code
35mTending Your Open Source Garden
31mOpen Source: Power and the Passion
27mDesign Your Open Source Project
44mSustainable open source contributions in your business
22mA beginner's guide to Open Source
10mMy Year In Open Source : 10 Lessons in 10 Minutes