Over 10 years ago, Jazzband started as a cooperative experiment to reduce the stress of maintaining Open Source software projects. The idea was simple – everyone who joins gets access to push code, triage issues, merge pull requests. “We are all part of this.”

It had a good run. More than 10 years, actually.

But it’s time to wind things down.

What happened

The slopocalypse

GitHub’s slopocalypse – the flood of AI-generated spam PRs and issues – has made Jazzband’s model of open membership and shared push access untenable.

Jazzband was designed for a world where the worst case was someone accidentally merging the wrong PR. In a world where only 1 in 10 AI-generated PRs meets project standards, where curl had to shut down its bug bounty because confirmation rates dropped below 5%, and where GitHub’s own response was a kill switch to disable pull requests entirely – an organization that gives push access to everyone who joins simply can’t operate safely anymore.

The one-roadie problem

But honestly, the cracks have been showing for much longer than that.

Jazzband was always a one-roadie operation. People asked for more roadies and offered to help over the years, and I tried a number of times to make it work – but it never stuck. I dropped the ball on organizing it properly, and when volunteers did step up they’d quietly step back after a while. That’s not a criticism of them, it’s just how volunteer work goes when there’s no structure to support it.

The result was the same though: every project transfer, every lead assignment, every PyPI permission change, every infrastructure decision – it all went through me.

The warnings

The sustainability question was raised as early as 2017. I gave a keynote at DjangoCon Europe 2021 about it – five years in. In that talk I said out loud that the “social coding” experiment had failed to create an equitable community, and that a sustainable solution didn’t exist without serious financial support.

The roadmap I presented – revamp infrastructure, grow the management team, formalize guidelines, reach out for funding – none of that happened. The PSF fiscal sponsorship was the one thing that did.

In the years since, I’ve been on the PSF board – which faced its own crises – and now serve as PSF chair. That work matters and I don’t regret prioritizing it, but it meant Jazzband got even less of my time.

GitHub went the other way

Meanwhile, GitHub moved in the opposite direction. Copilot launched in 2022, trained on open source code that maintainers were burning out maintaining for free. 60% of maintainers are still unpaid.

The XZ Utils backdoor in 2024 showed what happens when a lone maintainer burns out and someone malicious fills the gap. And Jazzband’s own infrastructure started getting in the way of the projects it was supposed to help – the release pipeline couldn’t support trusted publishing, projects that needed admin access were stuck.

So projects started leaving. And that’s OK – that was always supposed to be part of the deal.

Django Commons

I want to specifically thank Django Commons and Tim Schilling for picking up where Jazzband fell short. They have 5 admins, 15 active projects (including django-debug-toolbar, django-simple-history, and django-cookie-consent from Jazzband), and django-polymorphic is transferring over right now. They solved the governance problem from day one. If you’re a Jazzband project lead looking for a new home for your Django project, start there.

For non-Django projects like pip-tools, contextlib2, geojson, or tablib – I’m not aware of an equivalent. If someone wants to build one for the broader Python tooling ecosystem, I’d love to see it.

By the numbers

Over 10 years, Jazzband grew to 3,135 members from every continent but Antarctica, maintained 84 projects with ~93,000 GitHub stars, and shipped 1,312 releases to PyPI.

Projects that passed through Jazzband are downloaded over 150 million times a month – pip-tools at 23 million, prettytable at 42 million. django-debug-toolbar spent 8 years under Jazzband and ended up in the official Django tutorial. django-avatar, a repo from 2008, was still getting releases in 2026. And django-axes shipped 129 versions – a release every 13 days in its peak year.

The full 10-year retrospective has all the numbers, the stories, and what actually happened.

What happens next

I’m not pulling the plug overnight. There is a detailed wind-down plan that covers the timeline, but the short version:

If you’re a project lead, expect an email soon.

Thank you

None of this would have been possible without the people who showed up – strangers on the internet who decided to maintain something together. Thanks to the 81 project leads who kept things going despite the bottlenecks I created, and to everyone who joined, contributed, filed issues, and shipped releases over the years.

I started Jazzband because maintaining Open Source alone was exhausting. The irony of then becoming a single point of failure for 71 projects is not lost on me. But the experiment worked in the ways that mattered – projects got maintained, releases got shipped, people collaborated.

Anyways, the projects will move on to new homes, and that’s fine. That was always the point.

We are all part of this.

Written by Jannis Leidel on Mar 14, 2026, 12:00:00 PM