Join to jazzband

[ad-m]

As a meta comment, I also wonder if joining this project into https://jazzband.co/ could help get more eyes on this project, given it's importance in the Django ecosystem.

Originally posted by @johnthagen in #756 (comment)

I am currently not using django-guardian in any project that I maintain. I even write less and less Python on a daily basis, which takes me away from the entire Django ecosystem.

I am not authorized to make such a decision alone, but I am voting in favor.

[johnthagen]

If this is decided, the procedures for this are explained here: https://jazzband.co/about/guidelines

[auvipy]

I use django on regular basis. I would love to join a co maintainer if you need another hand

[ds-clearago]

@ad-m The org page https://github.com/django-guardian only lists you as a person in that org, so if you can't make the decision to move towards Jazzband alone (but you're in favor), who else is involved (or against it)?

[johnthagen]

Just a small note from personal experience, over at django-dbbackup we have come to regret the power over our own project we lost moving to jazzband

• Transfer Out: django-dbbackup jazzband/help#336

This has prevented us from merging basic PRs

• Support Django 4.1, 4.2 and Python 3.11 jazzband/django-dbbackup#485

There is only one person who seems to have the needed jazzband admin power, but he understandably only has so much time to devote to it

• We need more roadies in jazzband jazzband/help#196

It might be better off at the moment to add someone in the community with a proven track record, such as @auvipy , directly to django-guardian/django-guardian

[brianmay]

For what it is worth, I have moved a project to JazzBand - django-revproxy, and while the process wasn't particularly fast and had difficulties along the way (see jazzband/django-revproxy#129), I think it has worked out well for the project in the end.

I haven't seen any problems of the kind mentioned in the previous post.