Open Source Contribution - How does it even work?
summary
Explains the corporate problem called fork-and-forget: companies vendor and patch three upstream projects, drift off mainline, then face painful upgrades, security holes and incompatible releases (typical release cadence mentioned is ~three months). Describes a real case of paying to upgrade an OpenSSL wrapper only to have the project move and waste effort, and a community that revamps governance and maintainer structure to accept corporate patches. Recommends publish roadmaps, 100% want contributions: contribution guidelines, test suites, reviewer rewards, sponsorships and bounties.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:47What does an Open Source Project want?
- 9:29The impact of the Fork and Forget
- 20:14Adaptation as a Service
- 21:32Use caution in implementing your changes.
- 23:15Publish your roadmaps
- 23:38Publish your contribution guidelines
- 23:56Reward people who review code, not just write it
related talks
17mKeynote: The Double Helix of Open Source Software & Companies
54mWho Pays for Open Source? A Case for Open Governance & Enterprise Contributions
49mOpen Source At Work - How Contribute On The Clock
11mContributing to Open Source
34mFOSS like a Boss!
24m“To define the rule -- why you should go open source"
32mOpen Source - A Journey of Contribution and Collaboration
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..