Offer to co-maintain 403 to 404

skwashd does not have contact form enabled.
Contacted suzymasri via d.o contact form.

Contacted skwashd via davehall.c.a/contact

Response from Dave Hall yesterday; Referred me to and looped me in directly with suzymasri for module maintenance.

Pending reponse from suzymasri.

While I did have an email exchange to David, he deferred to Suzy on the matter of becoming co-maintainer and looped in their email address. I have not received a response from Suzy from either that email or the d.o contact form.

No response on:

• #3253529: Migration from D7 to D9 →
• 🐛 User logout without CSRF token redirect to 404 Active
• ✨ Method to bypass redirection RTBC
• 📌 Fix the issues reported by phpcs Active
• 📌 Automated Drupal 11 compatibility fixes for m4032404 Needs review
• 📌 Add GitlabCI testing Postponed
• 💬 Stable 8.x, 9.x, 10.x, 11.x release with security coverage Active

skwashd last logged in on drupal.org about three years ago; suzymasri logged in at least once the last year. I will contact suzymasri in the next hours.

This is the message I sent.

Hello Suzy,

I am contacting you because Ted ( https://www.drupal.org/u/elc → ) offered to become co-maintainer for 403 to 404 ( https://www.drupal.org/project/m4032404 → ), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3525953 💬 Offer to co-maintain 403 to 404 Active about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Ted will be probably made co-maintainer.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3525953 💬 Offer to co-maintain 403 to 404 Active . We need this to know it was intentional and not a misunderstanding on what the offer required.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

The status has been changed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.

Apologies for the late reply! this one slipped through the cracks.. m4032404 definitely needs some love, and we haven't had the time to properly prep it for Drupal 11, really appreciate you stepping up to help out!
@elc You should now have co-maintainer access. Let me know if anything else is needed.

Being a co-maintainer means having more than just two permissions. That is why the contact message contains the following text.

A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3525953 💬 Offer to co-maintain 403 to 404 Active .

Additional permissions have been granted, stable releases made, and project opted into security coverage.