From Forks to Sporks: The Journey Behind Creating OpenSearch
summary
Forking a 2M‑line codebase, the team forked Elasticsearch and Kibana into OpenSearch and preserves full git history for legal traceability and auditability. Governance choices matter: the public roadmap shows 260 meta issues with 4 community-originated items (1.5%) and cycle times trend upward, revealing vendor influence like AWS‑specific plugins and Bedrock mentions. A technical steering committee with ~30% AWS representation tries to steer neutrality, and a follow‑on effort creates a hybrid “spork” to push innovation beyond OpenSearch’s constraints.
AI-written summary · about
chapters (15)
- 0:00Introduction and welcome
- 1:27Why OpenSearch was created
- 3:35Early days at Elastic
- 5:21Moving to AWS and forking
- 7:07Forking Elasticsearch
- 8:09Governance challenges
- 10:16AWS culture and trade-offs
- 12:24Roadmap transparency issues
- 14:30Document-driven culture impact
- 15:34Cycle time and community health
- 17:19Vendor neutrality efforts
- 19:44Foundation and governance models
- 20:46Open source business models
- 21:47Open washing debate
- 22:48Q&A discussion
related talks
44mFORK IT ALL if You Fork It
21mWorking in the Open...Search
14mKeynote: OpenSearch: From Project to Community-Driven Ecosystem—Building Sustainable Governance Together
12mLightning Talk: From Fork To Foundation: The OpenSearch Journey To the Linux Found...
46mPower Dynamics, Rug Pulls, and Other Corporate Impacts on OSS Sustainability
40mInnovating in Open Source in Your Enterprise
42mWhen Your Open Source Tool Turns to the Dark Side
06mSponsored Keynote: Foundation-Led Innovation: OpenSearch's Impact on Modern Data I...