Offering to co-maintain Countries info

rrotari, please see: How to become project owner, maintainer, or co-maintainer → for an overview of the process to be added to a project as co-maintainer.

For instance, you're required to first post your offer in the project's issue queue (i.e. do not post it in the Drupal.org Project Ownership issue queue). By posting your offer in the project's issue queue, you make sure that the project's current owner and most active users see your offer and can comment on it. I am moving it to the right issue queue.

It also says that when opening an issue offering to co.maintain, it is useful to contact the current project owner via the contact tab on their Drupal.org user profile page (and/or other means of contact that exists) to let them know about the issue you posted regarding maintainership.

Finally, the procedure for How to become project owner, maintainer, or co-maintainer → says:

When the project is covered by Drupal's security advisory policy, you need to have permission to opt into security advisory coverage, or the offer must be approved by the project's owner. 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.

For more information, see How site moderators handle requests to be project owner, maintainer, or co-maintainer → .

You may want to read: Apply for permission to opt into security advisory coverage → .

Hi @gisle
thank you for your message.
I opened those request representing an organization because we have quite a lengthy list of projects we want to co-mantain.
We already contacted maintainers and/or owners of several projects that we use and that didn't have any activity for a long time. Problem is that usually there was no response or the response was that maintainers/owners moved to different stacks and don't have time for Drupal.
Should we still open a issue in project's issue queue if the project has not activity and we already contacted maintainers/owners ?

Should we still open a issue in project's issue queue if the project has not activity and we already contacted maintainers/owners?

Yes. You need to open an issue in project's issue queue where you demonstrate that you've contacted maintainers and owners (by placing a record of the attempt to contact in the issue summary).

Adding a new co-maintainer to the team is the prerogative of the owner and the team members trusted with the permission "administer maintainers" on the project's current team.

Site moderators (like me) only intervene and overrule this prerogative if it has been clearly demonstrated that nobody in the current team monitors the issue queue, and that all PMs sent the about the situation are ignored.

We already contacted maintainers and/or owners of several projects that we use and that didn't have any activity for a long time. Problem is that usually there was no response or the response was that maintainers/owners moved to different stacks and don't have time for Drupal.

That is where you want to request that the site moderators help out with getting new people onboard. But: How is the site moderators supposed to know that these efforts have been made, if there is no record of them being carried out in the issue summary of the offer to co-maintain?

As for Countries info, the project is opted into security coverage, so the site moderators shall no be able to help you becoming co-maintainer. If there is anyone in the organization you represent that have this permission, it may be a good idea for that person to open a new issue offering to maintain this project or even take over ownership. A co-maintainer will not be allowed to administer maintainer, so it gives you very little flexibility in terms of managing the project over time.

I think it's important that this module gets a new maintainer or a co-maintainer. Looking at the commit log, the last commit to the module was 3 years ago and all that commit did was fix Drupal 9 deprecated errors so it could be compatible with D8 + D9.

It doesn't look like the current maintainer is actively maintaining this module.

markconroy, I agree. This project look pretty abandoned. It has three issues that are RTBC that no maintainer has acted upon.

It has 810 reported installs, and with Drupal 9 scheduled for EOL in November this year, finding a new owner to maintain this is important.

However, whether we are able to find a new owner depends on somebody from the community with the required qualifications (permissions to opt into security advisory coverage) is willing to step forward and go through this process: How to become project owner, maintainer, or co-maintainer → .

Until that happens there is nothing the site moderators can do.

You can put me down as co-maintainer if you wish. I have permissions to opt-into security advisories.

To be honest, all I want to do currently is mark the .info.yml file as ^9 || ^10 so we can upgrade sites using this module.

markconroy, please see: How to become project owner, maintainer, or co-maintainer → for an overview of the process to be added to a project as co-maintainer.

It describes the steps you need to take to become a co-maintainer of a project if the project's owner does not respond to offers to co-maintain (which seems to be the case here).

I understand how the process works, I'm a maintainer/co-maintainer of a number of modules and also a Drupal core maintainer for the Umami profile and theme (Out of the Box initiative). However, in the case of this module it's a little hard - there are very few open issues (50% of which are now RTBC), one which may not be an actual issue, and one which is simply a feature request, so it's hard to demonstrate being "actively" involved in a project's issues, if that project is to all intents and purposes abandoned.

• I've made a comment on issues in this project and moved one to RTBC (there are very few issues) and all we really want is a D10 release.
• I've emailed the maintainer of the project and asked them if they can make a D10 release.
• I've offered here to become a maintainer of the module.
• I've offered to become a maintainer of the module to the project owner as well.

This issue was created by rrotari to be added as co-maintainer.

The project's owner is probably no longer around to mange the project team. It is likely that to be added a co-maintainer, you need assistance from a site moderator. If you want to be added as co-maintainer by a site-moderator, you need to understand how this process works: How to become project owner, maintainer, or co-maintainer → . It states clearly:

The site moderators will only consider the offer from one person per issue. Please do not use an issue created by another user, even if that issue has not been completed for some reason; instead, open your own issue.

What's blocking this from moving forward is not that you've not sufficiently actively involved in a project's issues, it is that you've:

1. Not yet opened up your own issue offering to co-maintain.
2. Not requested assistance from the site moderators by moving that issue to the Drupal.org project ownership issue queue after sending the PM to the owner.

I am sorry about the red tape, but overriding a project owner's right to manage their project team is a very sensitive matter, and we've found it prudent not to cut corners in these matters.

Ooops, sorry. I had forgotten this wasn't my issue and I was hijacking it. I've created 💬 Offering to co-maintain Countries info by markconroy Active now to see about becoming a maintainer myself for this module.

We've begun updating the module code to ensure compatibility with Drupal 10 and 11, and will soon release a stable version. Therefore, we're closing this issue.