Open Source Contribution Policies that Don't Suck
summary
Most organizations lack a written contribution policy per New Stack/Linux Foundation surveys and GitHub 2017 data show 47% can contribute off hours 12% must ask and 37% don’t know. Recommend adopting a Balanced Employee IP Agreement to limit employer claims to work related to company business use a <100 lines rule for trivial releases and implement automated allow/deny lists and tooling plus OSPO templates and checklists; Adobe cuts review time from about one week to half a day by automating approvals.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:38Most organizations dont have a policy
- 1:31What does not have an open source policy mean
- 2:11Explicit vs Permissive
- 5:51What is a policy that doesnt suck
- 6:07A good policy is permissive
- 7:15On the legal side
- 8:09On the business side
- 8:35Tension between legal and engineering
- 9:56Coming to agreement
- 11:17What is an open source policy
- 11:34Open source is a well understood problem
- 12:42Contributing outside of work
- 13:14GitHub Survey
- 14:05Why is it so confusing
- 15:02Why its a tedious process
- 15:40A better solution
- 16:33Contributing at work
- 16:53Large open source projects
- 19:01Patching
- 20:35Automation
- 21:32Conclusion
related talks
49mOpen Source At Work - How Contribute On The Clock
42mDoes Your OSPO Help or Hinder Contributions?
44mSustainable open source contributions in your business
32mAsymmetries in Open Source: What Can Research Tell Us about Closing the Consumption-contribution Gap to Improve the Sustainability of OSS?
47mPanel Discussion: A How-to Guide for Contributing to Open Source as an Employee
41mHow Your Company Can Help Sustain Open Source
49mSustainable open source contributions in your business
29mOpen Source Contribution - How does it even work?