Open Source At Work - How Contribute On The Clock
summary
Concrete how-to for getting employer approval: steps to frame a specific contribution, estimate time, and tie benefits to team or business; avoids vague examples and instead names tools like Mariner and programs like Foss responders and the Foss contributor fund. Recommends starting with noncontroversial fixes (docs, tests, accessibility), avoiding CLA-heavy projects, using inner source to prove value, recruiting allies, and tracking outcomes—highlighting your three to five biggest wins in reviews rather than raw counts.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:45Duanes background
- 2:40Who is this talk for
- 4:10Where to start
- 7:20Dependencies
- 9:41Opening Issues
- 11:20NonControversial Contributions
- 16:15Inner Source
- 17:20Blaze a Trail
- 18:55Have You Asked
- 20:20Ask
- 26:55Talk To Your Employer
- 27:25Find Allies
- 30:25Sample Policies
- 31:47Recognition
- 33:30Keeping Track
- 37:35Benefits
- 41:25Questions
related talks
23mOpen Source Contribution Policies that Don't Suck
24mSo You Want to Contribute to Open Source: ...
01h 10mCareers with Free/Libre and Open Source Software
22mDaunting to Doable: How Institutions can encourage Open Source Contributions
11mContributing to Open Source
47mPanel Discussion: A How-to Guide for Contributing to Open Source as an Employee
45mDeconstructing Open Source Contributions
41mHow Your Company Can Help Sustain Open Source