You Never Know When You Need a Fork: Lessons Learned Building...
Talkat Open Source Summit Japan + AI_dev: Open Source GenAI & ML Summit + Automotive Linux Summit 2025 · 2025-12-08..12-10·
summary
Valkey is a hard fork of Redis 7.2 created after a license change and immediately moves governance to the Linux Foundation stewardship to guarantee openness. The project documents and automates builds and releases so anyone can release, adopts a predictable six‑month cadence, and works with Fedora and Homebrew packagers to restore downstream availability. Practical failures include accidentally deleting tags and broken branches, leading to the rule don’t allow tag deletions and strict branch protection settings.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:52Project background
- 3:34Warning signs before fork
- 11:34Fork creation steps
- 16:30Open and transparent
- 18:54Dependencies and builds
- 20:19Automation and releases
- 23:45GitHub workflow lessons
- 26:36Community communication
- 28:47Summary and takeaways
- 30:53Call to action and Q&A
related talks
25mYou Never Know When You Need a Fork
05mKeynote: Your Core Infrastructure Should Be Vendor Neutral and Open Source
34mTwo Hard Things: Naming Things & Cache Invalidation, Valkey Edition
29mPlan to fork (So you don't have to fork)
33mValkey in Telecom: Leveraging Open Source for Unique Needs and G...
26mMutually Assured Development
11mRules of Engagement for Forking a Dependency
22mLessons from HasGeek's FOSS Journey