- Issue created by @japerry
- 🇺🇸United States japerry KVUO
Similar to admin_toolbar -- I was originally going to push D11 only changes as a member of the Project Update Working Group, but due to the vast amount of other issues in the queue and lack of maintainer response for quite a while, it seems like ongoing maintainership is needed here.
I sent a msg to nicksanta both via email and on Slack July 21st. Escalating a bit sooner due to the for this module amongst high security sites and the upcoming D11 release.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
These requests must stay in the project queue for at least two weeks.
Furthermore, a request to co-maintain a project cannot become a request to maintain a project after it is moved in the Drupal.org project ownership queue. - 🇮🇹Italy apaderno Brescia, 🇮🇹
Only nicksanta (the project owner) has the Administer maintainers permission. (Note to myself: Check out what shown on https://www.drupal.org/admin/people/advanced?name_op=%3D&name=nicksanta&... → .)
- 🇺🇸United States japerry KVUO
Since its been 2 weeks with no maintainer response, pushing this back to the Drupal.org ownership queue. Co-maintainer is fine, as long as it includes the 'administer maintainers' permission, since it appears the maintainer has been inactive for a while (and haven't received a response as of yet)
But this is blocking enterprise customers (and some associated distributions) from updating to Drupal 11, so its fairly important to resolve this soon.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
Since nicksanta last logged in about a year ago, I am going to add japerry as co-maintainer.
The project link is https://www.drupal.org/project/username_enumeration_prevention → .
- Assigned to apaderno
- Status changed to Fixed
26 days ago 6:10pm 12 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.