Skip to content
Newsletter

Newsletter

A periodic summary of what shipped, what is being designed, and what needs help. Every issue stays readable on the web without subscribing.

5 published

DigestOctober 2026

This week in EmbeddedOS — 2026-10-10

Five reds fixed, ESP-IDF v6.1 final with an S31 errata, the MCP taxonomy gets its CVEs, four new boards in the intake queue, and SKILL.md goes first-party at Google.

DigestNewsletterSecurityHardware
Read
DigestOctober 2026

This week in EmbeddedOS — 2026-10-09

eVera CI restored (fail-closed #52 fix), eCAD KiCad generator fix across 70 files, MCP six-class taxonomy, silicon week (Sapphire RV64, ESP32-S31, DAL-A SBC, S100P), device-CVE series.

DigestNewsletterSecurityHardware
Read
DigestOctober 2026

This week in EmbeddedOS — 2026-10-08

ZDS day 2 (functional safety, CRA readiness), the ~45-issue audit-fix merge wave, four new boards, ESP-IDF v6.1 (P4 Wi-Fi back, ECDSA-SBv2 disabled), and two MCP CVEs.

DigestNewsletterZephyrSecurity
Read
DigestOctober 2026

This week in EmbeddedOS — 2026-10-07

Zephyr Developer Summit Day 1 from Prague (40+ sessions, the first Community Awards, MCP now an LF project), the Synaptics/onsemi bidding war over edge-AI silicon, and the Apple Oct-13 home-hub event to watch.

DigestNewsletterZephyrEdge AI
Read
Issue 01September 2026

Newsletter Issue 01 — Welcome, What Shipped, What Is Next

The first EmbeddedOS Foundation newsletter: who we are, what the site now publishes (news, articles, documentation, free books), and how to follow along or get involved.

NewsletterFoundationWelcome
Read

About Newsletter

What the newsletter is

The Foundation publishes a newsletter: a periodic email rounding up what has actually shipped, what is being discussed, and where help is needed across our projects. The first issue is in the archive above, and every issue stays readable on the web without subscribing.

The newsletter is for people who want to stay in touch without watching every repository. If you read an issue and find nothing relevant to you, that is a sign we did it right — it means we included only what was worth your time.

What each issue will carry

Each issue will cover three things. First, shipped work: what was released or merged since the last issue, in concrete terms. Second, design discussions: open questions in our projects where outside input would genuinely help, with links to the discussions themselves. Third, calls for help: the tasks, reviews, and testing that are currently blocking progress.

What it will not carry: fundraising appeals, announcements of plans with no substance behind them, and rehashes of the News page. If there is not enough real material to justify an issue, we will skip it rather than fill it.

How often it goes out

The newsletter will go out periodically, not on a fixed schedule. The Foundation is volunteer-run, and we would rather send six substantive issues a year than twelve thin ones. You will not receive filler to meet a quota.

When an issue is ready, it will be published to the archive on this site at the same time it is emailed. The email and the archive will always match — there is no subscriber-only content.

How to get notified

To be notified of new issues, use our contact page and mention the newsletter. We will add you to the mailing list and confirm. You can leave the list at any time by replying to any issue or writing to contact@embeddedos.org.

We hold the list only for sending the newsletter and administrative notices about it, such as a change of address. We do not share it, rent it, or use it for anything else. There are no ads in the newsletter and nothing in it is sponsored.

Why the archive stays public

Every issue will be readable on this site without subscribing. The Foundation's work is public by design — our software is MIT licensed and our governance is open — and it would be strange for our own summary of that work to sit behind a signup form.

The public archive also keeps us honest. Anyone can check whether an old issue's claims held up, whether a call for help was answered, and whether our cadence matched our intentions. We consider that scrutiny useful.

How it differs from News and the Blog

The News page carries timely announcements: one item at a time, as things happen. The Blog carries longer pieces: explanations, reflections, and technical writing. The newsletter is the digest: a curated summary for readers who check in occasionally rather than daily.

If you follow the repositories or the News page closely, the newsletter will mostly confirm what you already know. It exists for everyone else.

Readers who want depth should go to the Blog, and readers who want immediacy should go to News. The newsletter is for the third group: people who care about the project but have an inbox-shaped amount of attention for it.