Transfer to django-commons?

[kytta]

Hey everyone. I am thinking about transferring django-simple-menu from Jazzband to django-commons. I was going to name the reasons for this in the issue, but, in django-commons/django-cookie-consent#142, Sergei has put it in words better than I ever could've. So instead, I'll just name his points and give my comments to it.

1. Recent problems with publishing

   As with many other packages, chore: Update Python pip packages website#1177 and Error releasing - Metadata version 2.4 help#390 have blocked the release of new versions of django-simple-menu as well. It took a long time to fix, and even after the PR was merged, the updated version was not deployed, so I had to retry again and again. Unlike other maintainers of other projects, I do not have maintainer access to the package on the PyPI, making it impossible for me to publish the update without reaching out to others.

   django-commons solves this differently: Release publishing and signing happens all from GitHub directly to PyPI, as opposed to Jazzband's two-step approach, and thanks to Trusted Publishers, the releases are way easier and more secure. As such, no maintainers have access to the PyPI package, other than the django-commons admins (think of them as roadies), while all package maintainers (people with push access to the repo) can make verifyably signed releases.

2. Roadies

   We need more roadies in jazzband help#196 has not seen significant progress since its creation, leaving Jazzband in an unstable state with a bus factor of 1. It's unfair and stressful to put the strain on Jannis to fix issues that may arise seemingly out of nowhere (like old Twine not supporting new Metadata version).

---

Other reads that are useful for context:

• What are the differences between Django Commons and Jazzband?
• Django Commons Code of Conduct
• Requirements for Incoming Repositories

---

@borgstrom, @mbeijen, you are still the leads on this project, and @pdessauw, you are a member, so I would need input and approval (or disapproval) from all of you. Let me know what you think about this. If anyone disagrees, we will not transfer.

[mbeijen]

Hi @kytta - I am 100% in favor of this, and thanks for taking the initiative!

[jezdez]

I would strongly suggest discussing this with django-commons, to explore if they have the capacity.