Offering to maintain Password Reset Landing Page (PRLP)

jitesh doshi and ccrawford91, who are the only people with the Administer maintainers permission, logged it at least once this year. I am going to contact them.

This is the first message I sent (to the project owner).

Hello Jitesh,

I am contacting you because Julian (https://www.drupal.org/u/anybody) offered to become maintainer for Password Reset Landing Page (PRLP) (https://www.drupal.org/project/prlp), a project you created for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3562490 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, Julian will be probably made 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.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3562490. 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

I am still contacting the second maintainer.

This is the second message I sent.

Hello Christian,

I am contacting you because Julian (https://www.drupal.org/u/anybody) offered to become maintainer for Password Reset Landing Page (PRLP) (https://www.drupal.org/project/prlp), a project for which you are maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3562490 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, Julian will be probably made 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.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3562490. 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 is Postponed 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 that a project moderator's action is required.

I see two issues from user @anybody on PRLP. First one was fixed by @ccrawford91 10 days ago. And second one was fixed just now by me.

Do we still need to add him as maintainer?

Hey @anybody,

The module is marked as feature complete so we admittedly don't do a lot of updates nowadays besides security and core compatibility fixes.

I've gone through the outstanding open issues and have taken action on all marked as needs review and RTBC. Once the last outstanding one is confirmed I'll be making a new release.

Jitesh and I appreciate your offer, but I think we're fine maintaining things on our own. If something changes in the future we'll reach out to you.