Sustainable open source contributions in your business
summary
Argues companies must pay for open source time and gives concrete policies: adopt a 20% rule / Fridays for OSS or set 32 billable hours per week so contributions are budgeted into rates; cites building PHPDocumentor guides at the company and running WeCamp events, translating Zend docs, and publishing a Rector rule to migrate Mockery to Prophecy as practical wins. Warns about single-maintainer risk (Flysystem example) and low corporate support for the PHP Foundation as reasons to fund maintenance.
AI-written summary · about
chapters (11)
- 0:00Open source and business
- 6:32Abandoned projects risks
- 9:06Why companies should support open source
- 12:43Funding contribution rates
- 16:53Getting management buy-in
- 20:10Practical contribution ways
- 23:40Start small with contributions
- 27:28Choosing the right project
- 31:44Business benefits of contributing
- 36:28Why invest in open source
- 37:40Q&A on complexity
related talks
49mSustainable open source contributions in your business
40mSustainable open source contributions in your business
54mWho Pays for Open Source? A Case for Open Governance & Enterprise Contributions
29mOpen Source Business as an Independent, Sustainable way to Fund Open Source
41mHow Your Company Can Help Sustain Open Source
23mOpen Source Contribution Policies that Don't Suck
35mWho Pays for Open Source? A Case for Open Governance & Enterprise Contributions
37mTalking with management about open source
