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.

[Stormheg]

Hello 👋

I think Wagtail Nest would be better suited as an alternative home for wagtail-django-recaptcha. Nest is a collective that houses useful third party packages for the Wagtail ecosystem. We'll try to keep a package compatible and maintained together with the community.

Full disclosure: I am an admin of Wagtail Nest and a Wagtail core team member. Seeing as this package is used by - and useful to - the community, I'd like to see it in good health so it continues to be an asset to Wagtail's ecosystem of third-party packages.

Moving to Nest would have the following implications:

• The project moves from the Springload organization to Wagtail Nest on GitHub.
• Anyone at Springload interested in continuing to be a maintainer will get maintainer access and can continue to be involved.
• We'll give a couple folks from the Wagtail core team PyPI access for redundancy. We trust the original authors - Springload will retain the PyPI access.
• Releases to PyPI will be automated through Trusted Publishing
• We'll open an issue to implement the best practices listed in the Python Package Maintenance Guidelines for Wagtail.
  • Note: there is no need to implement all these changes before a move, many projects have been grandfathered into Nest without these changes.
• We'll add a note to the README crediting Springload as the authors of wagtail-django-recaptcha for visibility.

@haydngreatnews hope it is okay that I tag you here. Your name comes up in recent activity and it looks like you work for Springload. Could you please bring this up internally? I'd love to hear if there is interest at Springload in moving this package to a collective and sharing the maintenance burden. If you have any questions, you can ask them here or message me: storm [at] stormbase.digital

Thank you for the consideration.

Best wishes from The Netherlands,
Storm Heg

[haydngreatnews]

Hi Storm,

Thanks for getting in touch, and for your generous offer -- this sounds like a great solution to me. I'll bring it up with our team, but don't expect it to be contentious. I'll reach our shortly

Thanks!

[Stormheg]

Hi @haydngreatnews - any updates?

[haydngreatnews]

Apologies - got lost in the race to the end of the year.

We're happy internally - I'll flick through an email so we can sort the details.

Thanks again