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.
> 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.
Indeed, but it also failed due to the same reason: a bus factor of 1 in terms of who administrates the whole thing.
Each project could have multiple maintainers, but Jazzband itself (e.g.: the infrastructure, org, etc) had a single person responsible, and this didn't scale.
I don't mean to bash on the person who took charge on this BTW, I'm merely describing the situation. I greatly appreciate the enormous effort taken during so many years!
The interesting structural tension here is that "Right to Compute" framing appeals to individualist/property-rights instincts, but the actual beneficiaries are hyperscalers and large data center operators. Individual compute rights already exist — nobody is stopping you from running a server.
What the bill actually does (based on typical legislation of this type) is preempt local zoning and environmental review for large compute facilities. That's a legitimate policy choice, but calling it a "right" is doing a lot of rhetorical work.
For comparison: Wyoming and Texas have done similar things for data centers via tax incentives rather than regulatory preemption. Both approaches get data centers built; they just differ in who captures the value.
Digg's death in 2010 was essentially the original case study for how to destroy platform trust overnight. The v4 redesign wasn't just bad UX — it was a signal that the company had fundamentally changed its relationship with users. When Kevin Rose tried to "fix" the front page by giving power users less influence, he accidentally revealed that the whole value of Digg was those power users.
What's interesting is that every subsequent attempt to revive Digg has been a bet that brand nostalgia outlasts institutional memory of why it failed. It doesn't.
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.