Request to assume module maintenance

Emailed the existing maintainer to ask.

Will vouch for @zenphp. He's a co-worker and I've worked on several complex issues and modules with him so +1 for adding as a maintainer

Link to project: https://www.drupal.org/project/pug →

I've not received any response from the original maintainer at this time.

Let's start over: The issue title needs to contain the project name and the issue needs to explicitly say which role is asked.

Bump

The issue needs to be moved from the person who offers to maintain, co-maintain, or be the new project owner.

We do not contact the project maintainers without the confirmation the person who created the issue is still interested, which is implicitly given when that person moves the issue. In this case, zenphp last commented on this issue a month ago.

He’s a co worker of mine so definitely believe still interested.

Yes, I am still interested in taking this module on.

Let me know if there is anything else I need to do in order to take on maintaining it.

This is the message I sent.

Hello Shobhit,

I am contacting you because Jason ( https://www.drupal.org/u/zenphp → ) offered to become maintainer for "Password Suggestions (PUG)" ( https://www.drupal.org/project/pug → ), a project you created for which you are project owner and sole maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3491413 📌 Request to assume module maintenance 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, Jason 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.

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/3491413 📌 Request to assume module maintenance Active .

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

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.

@zenphp Are you still interested?

@avpaderno Believe he still is interested (co-worker of mine)

@avpaderno Believe he still is interested (co-worker of mine)

Yes, I am still interested.

shobhit_juyal last logged in more than a week ago, but he did not comment on this issue. I added zenphp as maintainer.

I am removing the tags, since:

• No evidence has been shown of anything wrong being done
• The purpose of tags is not building a personal list

For context of others.
#19 was part of an attempt Discussed on Slack with @hestenet to avoid increased tensions on issues by only tagging them without comments that might tensions. @avpaderno was in the Slack thread where it was discussed.

The concerned being tagged in #19 was that @zenphp does not appear to have the "Can opt projects into security advisory coverage" permission and that the Password Suggestions (PUG) project is enrolled in the Security Advisory Program.

It has since been stated by @avpaderno in https://www.drupal.org/project/drupalorg/issues/3452333#comment-16095263 📌 Automate the majority of the ownership transfer process (retain human approval) Active that project moderators will not add as maintainer/co-maintainer, is treated by Project Ownership Admins to mean that Project Ownership Admins have the free will to approve/deny such requests and that there is no policy prohibiting such transfers.

This is a co-worker of mine and I have the opt in security coverage if that helps.

@smustgrave I was just filling in the record explaining why the tag and why no-comment since it was quesiton by a Project Ownership Queue admin.

Based on the statements from @avpaderno it is not policy that the permission is actually required so should not be a concern. There is some ongoing discussion in 📌 Create governance dcoumentation stored in repo/GitLab Pages Active to try and avoid this type of confusion going forward.