How do we feel about joining Django Commons?

[Stormheg]

Pre-face: I'm heavily biased on this, as I am one of the administrators of Django Commons.

---

Hello folks,

How would you feel about moving the project under the Django Commons umbrella? It's a GitHub organization with goals similar to Jazzband, but with more redundancy built-in in the form of multiple administrators.

After @thibaudcolas and @tbrlpld took over the package from Praekelt a couple years ago, they considered applying for a move to Jazzband but we ended up hosting the package under its own django recaptcha GitHub organisation. The main motivation for that was so we can stay in control and are not blocked by administrative tasks that require a roadie. See jazzband/help#196 for a lot of context on what influenced that decision at the time.

@Andrew-Chen-Wang mentioned that Jazzband has a specific release process where only a select group of designated people can make a release. This sort of exists in Django Commons, only people on the admin team for the project can approve a release to PyPI.

Benefits of a move to Django Commons

• Active community
• Active administrators
  • As a current administrator myself, I can confirm the team holds video meetings every two weeks to discuss and reach consensus on topics. As of time of writing (February 2025), we are working on establishing governance documents
• Lower barrier of entry for new people that are interested in helping out. We do not currently have a process in place for people to indicate their interest in helping out.
• Easier to add new people should the current maintainer team go AWOL - the Django Commons admin team will respond if such a situation were to occur. The same goes for the keys to PyPI, which are held by a dedicated group of org-wide volunteers.

What would change?

Not all that much. We would adopt the recommended team structure and automation around making PyPI releases.

I'd say we meet nearly all of the requirements already. The only one that I believe to be missing is documentation around contributing, I'm happy to add that and do all the steps necessary for the transfer.

And consensus from all us current admins on a transfer.

Would love to hear thoughts. Do you think joining is a good idea?

Further reading: https://www.better-simple.com/django/2024/05/22/looking-for-help-django-commons/

cc @django-recaptcha/admins @django-recaptcha/committers @django-recaptcha/contributors @django-recaptcha/triagers

[tbrlpld]

I don't have any specific concern at this time, but wondering what others think.

[Andrew-Chen-Wang]

No comment nor any concerns; I feel more removed from OSS in recent years with my startup.

[Stormheg]

Earlier discussion: https://github.com/orgs/django-recaptcha/discussions/248

[alanverresen]

I'm not an admin nor a maintainer, so I have no weight in the final decision, but I think this would be a good decision.

Since it's @Stormheg who proposes the idea, and he's already heavily involved in both django-recaptcha and Django Commons, I trust that this will be for the best of the project, and not have a negative impact. Also, the improved robustness and potential for extra voices seems welcome right now.

[thibaudcolas]

👍 It makes sense to me! Yep as far as I can see we do meet all requirements already aside from contributing docs.

[Stormheg]

Thank you all for your replies so far. I'll interpret them as in agreement.

@rgs258 – given you are on the current maintainers team as well – could I have you opinion on this, please?