Offering to co-maintain Simple Mail

These offers must be first opened in the project queue and moved here after 14 days, if no maintainer has declined the offer.

Sorry, I only check Slack every month or so nowadays, and I'm guessing your email may have gotten into spam somehow :(

I don't really maintain this module at all anymore, so I'd be okay with someone else taking over as I don't have the time to get it upgraded for full Drupal 10 compatibility.

Could you do me co-maintain Simple Mail with all needed rights and I will continue learning issues and adapting this module with Drupal 10?

Project is opted in to security coverage. Only the owner can add a new co-maintainer if that person does not have permission to opt in to security coverage.

Moving back to the project's own issue queue to be processed there.

I'm open to someone else taking ownership of this module (I don't use it anymore, so the motivation to keep maintaining it is not quite there), but as it is an active module in use many places, I need to ensure whoever takes over the module will keep it running smoothly (email is a fickle beast) above all else.

Having been away from Drupal dev (besides keeping my blog up to date), I would not qualify myself as the best judge for who could or couldn't take over maintainership for my projects...

@geerlingguy This is a request to be co-maintainer. ankondrat4 will not be made the new project owner (which at the actual state is not done from site moderators, since ankondrat4 cannot opt projects into security advisory coverage).

Just to expand on what apaderno and I have said earlier: The Drupal.org site moderators are not in a position to make judgements about who could or couldn't be added as maintainer for any projects hosted on Drupal.org. We simply follow rules, as described here: How to become project owner, maintainer, or co-maintainer → . Quoting from that page, there is the following rule:

The site moderators will not add as owner, maintainer, or co-maintainer a user who cannot opt projects into security coverage. See Apply for permission to opt into security advisory coverage → for details on how to obtain that permission.

Because of this rule, ankondrat4 cannot be added to the team by a site moderator. You can add him as co-maintainer, but the implied assumption is that as long as you are the project's owner, you will provide oversight, including monitoring the security implications of any changes made by ankondrat4 to the code base.

IMHO, if you no longer have the motivation/time to provide such oversight, you should not add a co-maintainer. Instead you need to actively find a new project owner to take charge. Please read: Finding a new project owner or new maintainers/co-maintainers → .

I am closing this issue because there has not been any follow-up action as described in How to become project owner, maintainer, or co-maintainer → from the person who opened this offer.