Consider transfering package maintainership to Torchbox?

[brylie]

Since Torchbox are the primary maintainers now of the django-recaptcha package as well as Wagtail, it may make sense to transfer ownership of this package to them to ensure compatibility going forward. Would you consider transferring maintainership of the repository to Torchbox?

[thibaudcolas]

👋 I’d like Torchbox to help with maintenance as we currently use this package and contribute to it (#49), but I don’t think we’re best placed to be the sole maintainers.

Torchbox aren’t the primary maintainers of django-recaptcha, we only had this project under the Torchbox org as a stop-gap because we had a good relationship with the previous maintainers of the package and they were looking to hand it over. We currently have 7 people involved with maintenance of the project, only two of which work at Torchbox. See New maintainers – and more needed #249 for more details. To reflect this, the package now lives at django-recaptcha/django-recaptcha.

---

My recommendation for wagtail-django-recaptcha would be to add maintainers with enough access to make maintenance-related changes to the repository ("Maintainers" level in GitHub permissions), and a rule that all code changes must receive at least one review. And add a few more people in PyPI.

This can either happen with the package staying at springload/wagtail-django-recaptcha, with members added as "Outside collaborators", or we can move the package to Wagtail Nest to do the same thing but with the more established process that organization already uses for other projects. Or have the package at django-recaptcha/wagtail-django-recaptcha perhaps, though that doesn’t feel like it’d be that beneficial.