After more than 10 years, @jazzband is sunsetting.

I started it in 2015 because maintaining Open Source alone was exhausting. The idea was simple: shared access, shared responsibility. It's been an honor to watch it grow: 3,135 members, 84 projects, and a lot of code shipped together.

https://jazzband.co/news/2026/03/14/sunsetting-jazzband

(1/3)

Jazzband - News - Sunsetting Jazzband

GitHub's slopocalypse made the open membership model untenable, but the cracks were older than that. I was the only roadie for the entire run and never managed to fix that. The full story, with 10 years of data and some honest reflection:

https://jazzband.co/news/2026/03/14/10-years-of-jazzband

(2/3)

Jazzband - News - 10 Years of Jazzband

If you maintain a @jazzband project, expect an email before @pycon. django-commons is a great option if you're looking for a new home, they've already taken on several projects and got the governance right from day one.

Wind-down plan: https://jazzband.co/news/2026/03/14/wind-down-plan

#Python #OpenSource

(3/3)

Jazzband - News - Wind-Down Plan

@jezdez Thanks for the attempt, even though this particular experiment didn't work out in the long run. I'll consider potential homes for contextlib2 (I have a couple of ideas already), and likely check in with the pip-tools folks as well.
@ancoghlan It's been my pleasure :) I thought you might have ideas, thanks! I haven't started the email run yet, but if you have ideas, it'll be easier to coordinate.
@jezdez My ideas are fairly specific to those projects rather than being generally available options (contextlib2 will likely find a home with core dev, the PSF, or OpenStack, while pip-tools presumably has a potential home under PyPA)
@ancoghlan Seems reasonable to me!