We're looking to move django-cookie-consent to the Django Commons organization.

Short summary: the jazzband organisation and infrastructure is making maintenance harder rather than enabling it. The majority of my time now goes towards dealing with jazzband-related problems instead of actually improving the package and supporting the community/users.

For the full motivation, please see django-commons/django-cookie-consent#142

Repository and PyPI package transfer should be coordinated with @tim-schilling and @cunla. For the matching NPM package, I have all the access I need already.

Related issues and context

• Discussion issue + coordination with other project members: Plan transfer to django-commons django-commons/django-cookie-consent#142
• Coordination with django-commons team w/r to the NPM package situation: https://github.com/orgs/django-commons/discussions/182
• Transfer-issue at django-commons: 🛬 [INBOUND] - django-cookie-consent django-commons/membership#198

Tasks

I believe that only @jezdez can do these tasks, together with the admins of django-commons:

• Transfer PyPI package ownership (task for bmihelac)
• Transfer readthedocs project ownership (task for @sergei-maertens)
• Transfer Github repository (task for @jezdez)