News » Wind-Down Plan
TL;DR
Signups disabled now. Project leads contacted by May. Transfers
June–December 2026. Org archived early 2027.
This post outlines the plan for winding down Jazzband. If you haven’t
read them yet, see the
sunsetting announcement for
context on why this is happening, and the
10-year retrospective for the
full story.
Timeline
The wind-down will happen in phases over the course of 2026.
Phase 1: Announcement (March 2026)
- New member signups are disabled immediately
- This announcement and wind-down plan are published
- Existing members retain access to the GitHub organization and all
repositories
Phase 2: Outreach (March – May 2026)
- All 80 project leads will be contacted via email to discuss
transferring their projects
- The goal is to have initial conversations with every lead before
PyCon US 2026 (May 13–19 in Long Beach, CA)
- Leads who don’t respond will be followed up with at PyCon US and
through other channels
Phase 3: Project Transfers (June – December 2026)
- Projects will be transferred out of the Jazzband GitHub organization
to their new homes – whether that’s a lead’s personal account,
a new organization, or another collaborative group
- For each project, the transfer includes:
- GitHub repository: transferred to the new owner
- PyPI package ownership: existing maintainers added, Jazzband
credentials removed
- CI/CD configuration: updated to work outside Jazzband
- Projects without an active lead or willing recipient will be
archived in the Jazzband GitHub organization
Phase 4: Wind Down (Early 2027)
- Remaining repositories archived
- The Jazzband GitHub organization set to read-only
- The jazzband.co website archived (with a redirect or static notice)
- PSF Fiscal Sponsorship status concluded, remaining funds
distributed in coordination with the PSF
What happens to…
…existing members?
You remain a member of the GitHub organization until it is archived.
No action is needed on your part. If you’d like to leave earlier,
you can do so from your account dashboard.
…projects I contribute to?
The projects aren’t going away – they’re moving. Your contributions,
issues, and pull requests will transfer with the repository to its
new home. Git history is preserved.
…PyPI packages?
Package ownership on PyPI will be transferred to the project leads
before the Jazzband release credentials are deactivated. If you’re
a project lead, we’ll coordinate this with you directly.
…the Jazzband release pipeline?
The Jazzband-specific release pipeline (uploading via Twine to
jazzband.co, then releasing to PyPI) will remain functional during
the transition period. After transfer, projects will publish to
PyPI directly using standard tooling.
…the website?
The jazzband.co website will remain online through the transition.
After wind-down, it will be replaced with a static page linking to
this announcement and an archive of the project list.
…the PSF Fiscal Sponsorship?
Jazzband’s
PSF Fiscal Sponsorship
status will be formally concluded. Distribution of any remaining
funds will be coordinated with the PSF board.
For project leads
If you’re a project lead, here’s what to expect
- You’ll receive an email with details specific to your
project(s)
- Decide on a new home for your project – your personal GitHub
account, a new organization, or another collaborative group like
Django Commons
- Coordinate the transfer – we’ll handle the GitHub repo
transfer and help with PyPI ownership changes
- Update your project – CI/CD, documentation links, and any
Jazzband-specific references
Several projects have already successfully transferred to
Django Commons, including
django-debug-toolbar and django-simple-history. If you’re looking for
a place with shared maintenance and multiple admins, it’s a good option.
If you have questions or want to start the process early, please
contact the roadies.
Written by Jannis Leidel on Mar 14, 2026, 12:01:00 PM