Jazzband sunsetting - where to transfer this project?

[vgrozdanic]

As Jannis wrote here - Jazzband is sunsetting.

Signups disabled now. Project leads contacted by May. Transfers June–December 2026. Org archived early 2027.

Not sure what the best place for this project is, probably Django Commons, I assume that @Andrew-Chen-Wang should receive the email soon from Jannis, but this is just an issue to start a discussion about it.

If we'd to chose Django Commons, here are instructions on how to switch project over there: https://django-commons.org/#how-to-transfer-a-project-in

[Andrew-Chen-Wang]

Though I've interacted with the admins in Django Commons from other collaborative OSS maintenance, I'm a little weary of the governance model of these organizations. I've felt slowed down in what I can do in this project especially (e.g. GitHub actions permission issues, can't access our ReadTheDocs, our release pipeline, can't access GitHub settings just in general, lack of interaction from our busy but amazing roadie) which contributed to partial demotivation in actively building out more features from my end. Everyone's busy, so the async communication makes really long spanning wait times to do things; I'm sure Django commons faces a similar issue.

I do love Jazzband's community. The volunteers have been amazing and caring. Personally, I haven't seen too much AI and actively encourage AI for large projects so long as the review is good and performed at high standard. Slop can be overwhelming for some projects, but, given how simple our project is, I'm not bothered as much. That said, I don't think giving everyone merge permission is necessarily beneficial; as the head maintainer, before each release, I do check every merged PR. So I'm leaning on this project first being transferred to my personal account or an org while I chat with Django commons folks to see how active the admins are; from previous experience, I do think the admins are already stretched quite thin from their own current commitments. If many Jazzband projects move to Django commons, I'd be a little hesitant to move our project until Django commons has matured and expanded a little post-Jazzband-migration.

Also, this is original @davesque 's package, so I believe a couple of things are still under his ownership.