New co-maintainer

The current co-maintainers can merge these these patches to a new dev-snapshot, but they cannot create new releases.

See https://www.drupal.org/project/acl/maintainers.json → for permissons.

thanks @gisle!

What do you think of this idea...

- Remove co-maintainers without any permissions as a simple clean up task and to reduce instances of module users messaging these maintainers asking for assistance that they cannot provide

- reach out to @merlinofchaos and @EclipseGc to see if they are still active. If so, would either/both be interested in gaining the additional Administer Release privilege given @salvis's latest update 💬 Offering to maintain RoleAssign Fixed

If either are available and willing, I'd be happy to work with them directly to push the Drupal 10 issue through and get a new release out. If neither are available or are otherwise uninterested, I'm willing to take on Write To VCS and Administer Release permissions to take care of it. The reason I suggest appealing to @merlinofchaos and @EclipseGc first is because they have more experience with the code base, they already have Write To VCS permissions, and they are therefore more appropriate candidates than myself. I do have the bandwidth right now to get Drupal 10 compatibility through, but do not have the bandwidth to become a full-time maintainer of the module.

Site moderators does not interfere with the owner's management of the team of any project hosted on Drupal.org. Even if the owner is not very active, we do not have permission to interfere.

You may want to reach out to merlinofchaos (last Drupal.org post 2019-02-07) and EclipseGc (last Drupal.org post 2023-02-28) to request that they work with you to push the Drupal 10 issue through in the dev-branch. Only Salvis has the required permission to get a new release out.

It is nice to hear that you're willing to take on the project. If you want to pursue this, reach out to Salvis and ask to be added to the team as maibtainer, following the here → .

Please that the project is opted in to security coverage, so Salvis is the only person that can add you as maintainer.

@gisle, I will message all of them again, but I have messaged them multiple times with no response. This is what lead me down this rabbit hole. Didn't @salvis basically acknowledge in his latest update 💬 Offering to maintain RoleAssign Fixed that he's lost touch with the Drupal community and is no longer active in it?

According to these instructions → , I should open an issue in the project ownership issue queue → to request moderator intervention if I don't hear back from the ACL maintainers. As I said, I will message them all again, but if I don't here back (by how many days?) can I open a new issue there to have the moderators step in?

@gisle I have messaged the following to @EclipseGc, and sent a similar message to @salvis. There is no option on @merlinofchaos's profile to contact them... do you have some way of doing this? As I mentioned elsewhere, I've also emailed @salvis through his company's website with no response.

Hello,

I am reaching out to see if you are still maintaining the ACL module. We have a Drupal 10 issue that is RTBC: https://www.drupal.org/project/acl/issues/3285916 📌 Automated Drupal 10 compatibility fixes Fixed

Seeing as Drupal 10 has been out for multiple months and Drupal 9 loses support later this year, I think its crucial to get this patch merged and released.

I've also opened a maintainership issue on ACL to determine the current state of the module's maintainership. If you could chime in on the discussion there, that would be helpful: https://www.drupal.org/project/acl/issues/3348765 📌 New co-maintainer Closed: duplicate

It appears that @salvis, the project owner and sole user with Administer Release privileges may no longer be active in the Drupal.org community: https://www.drupal.org/project/roleassign/issues/3346751#comment-14962943 💬 Offering to maintain RoleAssign Fixed

If so, the module may need a new maintainer or, at the very least, someone with Administer Release privileges. If you think you could take on that permission and push the Drupal 10 issue through and cut a new release, we would love to hear from you here: https://www.drupal.org/project/acl/issues/3348765 📌 New co-maintainer Closed: duplicate

Thank you very much,

The instructions you link to explain how existing maintainers can use the project ownership issue queue to recruit new maintainers to their project. That route is not open to you.

And no, I have no means to contact merlinofchaos. If he has disabled his contact form, he probably does not want to b3 contacted.

Thanks @gisle.

So, if I still don't hear from @salvis or @EclipseGc after, say, 1 month from now, despite repeated attempts to reach out over the past 4 months, is there still no way for site moderators to intervene? We have to let the modules just go dark?

I appreciate your assistance :)

There is a broad community initiative to get new people to adopt contributed projects for Drupal 10 readiness. Please take a look at #3342443: META: Adopt contributed projects for Drupal 10 readiness → .

If you want want to adopt this project yourself, as already pointed out by me in comment #4, you need to initiate the process described on this page: How to become project owner, maintainer, or co-maintainer → .

If you decide to do so, start by posting an issue in this issue queue. For the title, use "Offering to maintain ACL".

duplicate, see: https://www.drupal.org/project/acl/issues/3352734 📌 Offering to co-maintain ACL Active