How to Explain the Impact of Your Open Source Work
summary
Explains how everyday contributions turn into measurable change: community training and funding produce 250 Rwanda sites maintained by local teams using TYPO3; government procurement shifts create local supplier ecosystems (UK supplier map flips after open source preference); a failed Australian prototype costs $36 million when proprietary vendors outplace open options; examples include Drupal, TYPO3, Postgres and vendor lock‑in cases, plus concrete threats like freemium and “open source in name only” and the need to fund maintainers.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:09Open source career and company
- 8:13Open source vs public domain
- 12:08Government procurement and open source
- 16:08Why open source is special
- 20:46Freedom and responsibility in open source
- 22:31Rwanda case study impact
- 25:01UK government open source shift
- 26:27Conclusion and thanks
related talks
28mTalking with management about open source
57mOpen Source Impact: From Innovation to Positive Change
23mInvesting in Open-Source
28mWhy Open Source Matters by Making People and Companies Better
23mPanel Discussion: Public & Private Support of the Open Source Ecosystem
39mTalking with Management About Open Source
23mMaking the Business Case for Contributing to Open Source
33mThe Open Source Effect