9 Years in the Making, the Story of Zephyr, Starting with Commit Nr. 1
summary
Project starts in 2014 and goes public under the Linux Foundation in 2016, grows to over 80,000 commits and over 1 million lines of C, and now supports 13 architectures and more than 500 boards; it adopts GitHub, moves builds to CMake and CI to GitHub Actions, switches to a unified kernel (discarding fibers), ships Bluetooth and networking stacks, and releases multiple LTS versions—concrete tooling, clear license (Apache-2.0), and broad silicon adoption show the effort actually works.
AI-written summary · about
chapters (16)
- 0:00Zephyr’s nine-year journey intro
- 1:06Zephyr’s 2014 origins and 2016 launch
- 9:18First commit and early development
- 14:05Wind River collaboration and codebase
- 16:59Open-sourcing Zephyr and alternatives
- 17:21Cleaning code for public release
- 19:25Hardware abstraction and ABI portability
- 20:27License change to Apache 2.0
- 21:28Naming Zephyr and branding
- 23:17Early hardware support and platforms
- 24:42Zephyr growth and transitions
- 26:28Unified kernel replacing dual-kernel
- 29:26Adoption in critical systems
- 30:32Ensuring Zephyr is not seen as an Intel project
- 32:18Building open ecosystem
- 35:30Future goals and project health
related talks
43mZephyr Project: Results from Applying Open Source and Security Best Practices
43mZephyr at 10 Years: Survey Feedback
16mHow Zephyr is eating the (embedded) software world
16mKeynote: Zephyr RTOS: 10 Years After Applying OSS Best Practices
39mBoF: Meet the Zephyr Community
23m#9 Open Source Forum 2019 Kate Stewart
41mZephyr Documentation BoF
49mThe Zephyr™ Project – An Updated Overview