Signal / 047 — All Things Open puts maintainers beside the AI demos

Open source is not just the code you can download; it is the people who have to review the next contribution. All Things Open is scheduled for October 19–20, 2026 at the Raleigh Convention Center. Red Hat’s published event agenda offers a useful preview of that tension between more automation and sustainable maintenance.

Its October 20 program includes a session on survey findings about generative AI and open-source development, covering contributor workflows and effects on maintainer workloads. The page describes the research topics but does not provide the results. We are not treating a session description as evidence that AI has improved—or damaged—project sustainability.

Other listed talks cover constructive code reviews, Kubernetes performance testing with Kube-Burner, and running AI agents locally before moving toward Kubernetes. These are scheduled sessions, not reports from talks we attended. Check the event schedule before planning around a particular room or time.

sysVoid take

The best question to carry into an AI-heavy developer event is not simply “How much code can it generate?” Ask who will verify the output, reproduce the bug report and maintain the dependency after the demo ends.

For your next contribution, try a smaller experiment: submit a minimal reproduction, explain why the change is necessary and include a test someone else can run. If a tool helped write it, you still need to understand what you are asking maintainers to accept.

That is our editorial recommendation, not a finding from the forthcoming survey session. Escape the default of measuring participation by line count. A clear, reviewable contribution can be more useful than an impressive pile of unexamined code.

AI-assisted summary checked against the linked sources; no hands-on testing. Featured photo by Chris Ried on Unsplash is illustrative, not a photograph of the conference.