The Yocto Project – Where We’re Going and What’s Next
summary
Project commits to a five‑year plan with concrete tasks, funded by more members and an RFQ for paid work; release cadence stays six months with LTS extended to four years. Existing infrastructure gets specific fixes: revive patch test to work with the current Patchwork, find a maintainer and automated tests for toaster, expand shared-state CDN for binary artifact reuse, modernize recipe-tool/devtool for Rust/Go, formalize CVE and SBOM/SPDX 3.0 handling, and refresh Crops base containers and VS Code SDK integration.
AI-written summary · about
chapters (16)
- 0:00Yocto Project intro
- 3:13Project structure & membership
- 8:55Five-year plan & goals
- 10:46Patch testing & Toaster
- 12:56Shared state & artifacts
- 15:27Layer management challenges
- 17:54Security processes & needs
- 18:59IDE tooling & support
- 21:50Binary distros & prototyping
- 23:11Layer setup & workflows
- 25:36How to contribute
- 28:45Q&A: Security & systemd
- 29:35Q&A: Release cadence & LTS
- 30:38Q&A: Membership & contribution
- 34:02Q&A: RFQ & resources
- 35:06Q&A: CROPS background
related talks
39mYocto Project: 5 Year Plan, Now What?
41mBoF: Yocto Project - What's Next?- 41mSponsored Session - BoF: Yocto Project - What's Next?
26mYocto Project Long Term Support (LTS)
38mBoF: The Yocto Project and OpenEmbedded Organization
01h 02mBoF: The Yocto Project and OpenEmbedded
41mArchitecting for the Long Haul: Technical Strategies for Sustainable Open-Source Support Models
47mBoF: Yocto Project & OpenEmbedded