Project
Problem/Motivation
I'm offering to be the new project owner.
There has been little to no maintainer activity in the past few years (no commits in 3 years), and I've been waiting for a long time on one RTBC issue that will make the module compatible with Drupal 11.
Drupal 10 end of life is a few months away!
Steps to reproduce
https://git.drupalcode.org/project/webform_submissions_delete/-/commits/...
I contacted @geoanders via the user contact form and never heard back.
I've been trying to support the module in the last couple years, but I lack the access to actually merge the changes and create releases. If the module doesn't get the needed updates before Drupal 10's end of life this year, I will have to create a fork or custom module with this module's code, or drop the module.
As of August, 2026, I now have access to opt into security advisory coverage. I have also created and maintain dozens of custom modules that I actively use, and I use phpstan, phpcs, eslint, Drupal rector, etc.
Proposed resolution
I will maintain the module with maintenance fixes only, as it's feature-complete.
Comments
Comment #2
solideogloria commentedI will also note that since there are basically no active maintainers on the project, it might make sense for me to become Project Owner, not just Maintainer. I will leave that to the discretion of the Drupal.org team.
Comment #3
avpadernoIf you want to be the new project owner, you can still change the issue summary to state that, since the issue was created two days ago.
If you wait 14 days, and then move this issue to the Drupal.org project ownership queue, you will be added as maintainer.
Comment #4
solideogloria commentedI'll change it to be "owner", since there's been only a few commits and it's a very simple module.
Comment #5
avpadernoComment #6
solideogloria commentedComment #7
avpadernoThe only person with the Administer maintainers permission, gkrishna.drupal (the project owner), last logged in more than a year ago.
I made solideogloria the new project owner.