Sunsetting Jazzband

zahlman

Unfortunate. > 60% of maintainers are still unpaid. That's actually not as bad as I would have guessed.

benatkin

The Register post about the Slopocalypse to me feels tongue in cheek while this post seemingly takes it at face value. What's happening on GitHub is a mixed bag. I love what AI is doing to Ghostty.

iqihs

is it unrealistic to think the companies that benefit from orgs such as this could donate a fraction of a percent of their wealth to keep them going? the responsibility always seems to fall most on those with the least resources.

grim_io

Jazzband have done the world a lot of good. They deserve better.

sc68cal

Jazzband maintained some incredible Django packages and tools that made it possible for me to build a system at my $JOB that would have been impossible to do on my own. It is a true tragedy of the commons situation where I was expected do more with less, and I didn't have the ability to contribute back/donate anywhere near the value that these projects provided to $JOB or myself. I did contribute personally, but it's very clear how all of this value has been extracted and used by large companies to build higher and higher walls for themselves, and none of the people that actually make any of this work get more than crumbs.

mey

I don't know how many maintainers that are impacted by this, or what they are getting from Jazzband (I was not previously familiar), but the Apache foundation may be something to look into. https://apache.org/

comet_browser

Jazzband's model was interesting precisely because it tried to solve the bus factor problem by distributing maintainership across a community. The fact that it's sunsetting suggests the problem runs deeper than just individual maintainer burnout. The real gap is that there's no natural mechanism for projects that are critical infrastructure for many companies to capture even a tiny fraction of the value they create. pip, Django, and the whole ecosystem that Jazzband helped steward are worth billions in aggregate business value. Their maintenance costs a few thousand dollars a year in volunteer time. I don't think licensing changes alone fix this. Companies have legal teams that can route around them. What might actually work: large package registries (PyPI, npm) implementing a voluntary but strongly encouraged funding mechanism where companies self-report their usage and contribute to a foundation pool. It would need to be opt-in and friction-free, but even 10% adoption from mid-sized companies would transform the economics.

vova_hn2

> 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. Not sure what exactly prevented him from accepting more people into the role of "roadies"...

UqWBcuFx6NV4r

Bad smells were coming from Jazzband from well before people started churning out vibe-coded PRs. Jannis should’ve let this blog post sit for a few days before publishing it. The post basically says “why is Jazzband shutting down? AI! It’s AI’s fault! Also here’s my little rant about it being trained on open-source code!”, but he then proceeds to walk things back a little bit, “well actually it started a whole lot earlier”. Jazzband’s mismanagement wasn”t the butterfly flapping its wings that AI turned into something unsustainable. It was broken regardless, beyond the usual “oh the maintainers are burnt out”. It’s obvious that he’s got a more philosophical bee in his bonnet about AI, and is attributing more of Jazzband’s demise to it than can really be justified. All I’ll say is, there’s a reason that Django Commons now exists.