Hi folks - I'm using an issue for transparency sake in the maintenance of this project.

I'd like to initiate the transfer of django-cookie-consent from jazzband to django-commons. The reason for this is that the Jazzband organisation and release flow has been blocking rather than enabling. At the time of writing, there is a 0.7.0 tag pushed on Github which was not on PyPI because we're facing outdated infrastructure on the website that must be used to publish packages to PyPI (see jazzband/website#1177 and jazzband/help#390 for the exact same problem). I've now bypassed this because I still have maintainer rights on PyPI, but this weakens trust in the ecosystem. Even though the PR was merged, I suppose the website hasn't been updated yet since the release is not possible yet. Next, the npm package situation is not being addressed: #120. Finally, jazzband/help#196 is a famous issue now and the situation has not changed, putting unreasonable strain on @jezdez time and responsibilities.

So, to address those issues, https://github.com/django-commons was set up which has a different governance model, specifically addressing these sort of issues. I also did the pre-work to investigate the npm situation, see this discussion for the resolution. Transferring will yield the following immediate benefits:

• no more reliance on an external website, everything is visible on Github itself
• ability to use secure verified PyPI publishing, not requiring any secrets/keys
• the npm package will be owned/maintained by the matching github organization too
• no single point of failure, maintainers have full administrative control

However, @Oakwright and @MrCordeiro are also both listed as members for this project, so if you have any concerns or disagree, please speak up. If you're okay with this, I'd appreciate an explicit reply/comment so that it's visible to the rest of the world.