Event: Community Over Code 2026
Dates: October 11–14, 2026
Location: Glasgow, UK
Website: https://communityovercode.apache.org/events/glasgow-2026/
Community Over Code is the Apache Software Foundation’s flagship conference. Glasgow 2026 ran October 11–14, with a three-day hackathon (Mon–Wed) in the Wee Dram Room alongside the main program. There were also two events (Lakehouse Day, Airflow Contributor Day) on the 10th, before the main event started.
Things that I was particularly interested in
Non-code participation
The strongest cross-cutting thread of the week: open source is more than code, and the projects that thrive treat non-code participation as first-class. Peter Zaitsev (Percona): “users give open source its purpose” — not every user can contribute code, but they can contribute their story, their frustrations, and their complaints.
Evan Rusackas (Superset) built an entire talk around ten distinctly human roles in the age of AI.
I gave at talk, with Kris Freedain, about non-code contributions – in particular, how project maintainers should very intentionally create specific opportunities for non-code work, and go out of their way to welcome and recognize the people that do it.
Governance maturity and leadership succession
Dawn Foster spoke twice (Leadership in OSS; Good Governance), and the themes recurred all week: define the path to leadership; document values, mission, and scope; have an explicit, non-punitive path to emeritus; define how problematic people are removed; and start simple, adding governance complexity only when it solves a real problem.
Documentation as the scalable on-ramp
Docs came up as the highest-leverage, most-neglected lever for onboarding. Highlights: Google’s “Docs Advisor” tool concept for writing better docs – at https://github.com/google/opendocs – provides templates and tools for common docs patterns
I was introduced to the concept of “friction logging”, which is where you journal what was hard, or didn’t work, as a means to capture that beginner’s mind and find places that could be made easier for those beginners. I’m going to start doing that!
AI’s double edge for open source integrity
A theme echoing the PyCon Africa data (70% of developers using AI daily): AI lowers the cost of producing code but not the cost of earning trust — “code is getting cheaper; trust is not.” Practical responses discussed: add a small good-faith hurdle before accepting contributions so you filter AI-gamed contributions from genuine ones, and lean on humans for judgment, mentoring, and the roles AI cannot fill.
Justin McLean noted AI is genuinely useful for anonymizing lessons without the bias of preconceived opinions about specific projects, people, or companies.
Keynotes
We had a number of really great keynotes. I want EVERYONE to watch Russell Spitzer’s keynote when it’s published.
Russell Spitzer — cross-project collaboration
Russell’s keynote was all about how Snowflake recognized the importance of meaningful community engagement in the projects that they were depending on. Since this is what I do in my day job, having someone else say it so eloquently was very affirming, and is something I want all of the managers I work with to watch. Really a great presentation.
Vlad Miricioiu
Transitive and “phantom” dependencies are largely invisible to CVE tooling, and with vendored code most dependencies are “phantom”. This was a fantastic overview of how deep understanding of your supply chain and dependencies is critical to security and sustainability, and how badly we are collectively doing with this. This is also worth watching if you care about those topics.
Stephen Walli
Stephen gave a talk about his last few years in teaching college students to do software engineering better, in collaboration with various open source projects. While I had heard the talk before (and that’s why we invited him!) it was great to see it with a new audience. His points about students self-mentoring, and that all software is social software, landed very well with the Apache audience.
Brian Baglow
Brian talked about the video game industry, which was almost all new information for me. I really don’t know how to summarize here. He talked about the engineering patterns in game development, and how they have evolved over the decades. And about the money that’s in that world, and how it’s distributed. And how it compares to open source development. And many other topics. Definitely worth watching, and hugely informative.
I’ll post links to all of these referenced talks when they’re published.
The Hackathon
It’s been several years since we had a formal Hackathon at Community Over Code, or Apachecon before that. We have almost always provided a *space* for people to collaborate on stuff, but we haven’t done any promotion beforehand for years.
This year, we worked with communities to bring a task list, and promote to their communities. This resulted in three days of a full room, with real work getting done, and new people being onboarded.
I hope to have more stories to tell about this over the coming weeks.
We had 20 projects participate formally – https://events.apache.org/events/2026/community-over-code/hackathon.html – as well as several projects drop by to use the space for more ad-hoc work.
Last week I was at the United Nations Headquarters in New York City for UN Open Source Week — a gathering that, even just by its name, tells you something about how far open source has come. This isn’t a developer conference. It’s not a vendor expo. It’s the United Nations convening governments, NGOs, academics, and technologists to talk about open source as a matter of global policy.
The event ran June 22–25 at UN HQ in the ECOSOC Chamber, then moved on June 26 to the IBM Building at 1 Madison Avenue for a community-led “Open Source Community Day” hosted by Red Hat. It’s not the kind of event I usually attend.
That’s not a developer complaining about vendor lock-in. That’s a government AI regulator saying the architecture of modern AI makes democratic oversight structurally impossible.
One of the more interesting ideas I encountered was the collapse of the distinction between Sovereign AI (nations controlling their own AI infrastructure) and Portfolio AI (diversifying workloads between hyperscalers and local compute). These are the same question at different scales. A country asking “how do we avoid dependence on foreign tech companies?” is asking the same question as an individual asking “can I run some of this locally?” The answer in both cases is open source — open weights, open models, open tooling. It’s the only path to that kind of independence.
The highlight of the event was the “OSPOs for Good” session, opened by Omar Mohsine (UN Open Source Coordinator) and featuring government ministers speaking about open source as a development instrument.
These are government ministers framing open source as national policy — as the tool that prevents their nations from becoming permanent technology colonies of whoever builds the largest proprietary models. The Next Einstein Initiative (“Will the next Einstein come from Africa?”) kept surfacing as a motif — talent exists everywhere; infrastructure and access don’t. Open source is positioned as the equalizer.

