About Stackers Network
What you'll find here, who publishes it, where the facts come from, and how each weekly issue is put together.
What this is
Stackers Network is a resource for everything OpenStack — learning how to run it, following what the community is building, and keeping up week to week. It started as a weekly digest and still is one: every Saturday it summarizes what the community discussed on the public mailing lists and what it merged in code, with links back to the primary source for everything that matters.
Around that digest sits the rest of it:
- Learn OpenStack — an open knowledge base you can work through yourself or hand to an AI agent as a tutor: architecture and core concepts, hands-on training, and guided deployments. Start here if you're new to OpenStack or picking it back up.
- Projects — a page per project pulling together its weekly code activity and the mailing-list threads that touched it, so you can follow Nova or Neutron or Ironic specifically instead of the whole firehose.
- Security advisories — every OSSA and CVE that's come up, linked to the official record and to the issue that covered it.
- The archive and search — every issue published, kept permanently and searchable.
- The Discord — where readers ask questions, compare notes on running OpenStack, and talk about what's in each issue.
Everything here is free to read, has no paywall or signup, and is published as a static site with an RSS feed — plus per-project feeds if you only care about a few.
Who makes it
Stackers Network is edited and published by Antony Messerli.
How each issue is made
The process is deliberately narrow and repeatable. Two pipelines run every week and feed the same site.
The mailing-list digest
- The public archives for
openstack-discussandopenstack-announceare downloaded from lists.openstack.org. - Messages are grouped into threads, and the most active threads of the week are selected as the source material.
- Those threads — and only those threads — are summarized by Claude, an AI model, into the sections you read.
- Every link the model produces is checked against the source material before publishing. Any URL that did not appear in the sources is removed, so citations can't be invented.
- The result is committed to a public content archive and rendered to this site.
The code-activity digest
- Changes merged that week are pulled from OpenStack's Gerrit at review.opendev.org.
- Projects are ranked by a composite of merge count, distinct contributors, and the size of the changes — so one busy team landing many small patches doesn't outrank genuine, broad activity.
- The most active projects get a written summary for that week; each links back to the underlying Gerrit changes. See the projects directory.
Accuracy and corrections
The summaries are written by an AI model from real, cited source material, then published on a schedule. That means two things worth being plain about: the source threads and changes are always linked so you can verify any claim yourself, and mistakes are possible.
If something here is wrong, tell us and it will be corrected. Write to the editor or raise it in the community Discord. Corrections are made to the archived issue itself, so the archive stays accurate rather than accumulating errata.
Security coverage is indexed separately in the advisory tracker. Those entries always link to the official OSSA or CVE record — treat the official advisory as authoritative, and this site as a pointer to it.
Independence
This is an independent, community-run project. It has no affiliation with the OpenInfra Foundation or the OpenStack project, receives no funding or direction from them, and speaks for nobody but itself. Nothing here is official — for anything authoritative, follow the links back to the source.
The OpenStack name is used only to describe what this digest covers, which is what the notice at the bottom of every page sets out.