Offering to co-maintain Flag

This is the message I sent to socketwench, the project owner.

Hello Tess,

I am contacting you because Martin ( https://www.drupal.org/u/mandclu → ) offered to become co-maintainer for Flag ( https://www.drupal.org/project/flag → ), a project for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3453519 → about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
In the case you accept the offer, you can also add Martin as co-maintainer, but this is not necessary, as project moderators can add co-maintainers/maintainers to any project.
Without a comment posted on that issue in the next 14 days, Martin will be probably made co-maintainer.

Neither project moderators nor site moderators will 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.

A last note: This offer is about being co-maintainer, which for us means somebody who does not have all the drupal.org permissions on the 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.

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

The status has been changed because we are waiting for a reply.

Hi folks, I haven't worked on Flag module post D7, so I'm deferring entirely to @socketwench here.

@apaderno it's been over 3 weeks since you messaged @socketwench. What is an appropriate amount of time to wait for a response?

I added mandclu as co-maintainer, since no other maintainer posted a comment on this issue.

Automatically closed - issue fixed for 2 weeks with no activity.