Offering to maintain ACL

I tried to contact @salvis at 29 oct 2024 thought contact form, he didn't respond to my message. So I'm pushing this issue to Drupal.org project ownership.

Only salvis has the permission to administer co-maintainers/maintainers. I am going to contact him after my dinner.

This is the message I sent.

Hello Hans,

I am contacting you because Mikhail ( https://www.drupal.org/u/dillix → ) offered to become maintainer for ACL ( https://www.drupal.org/project/acl → ), a project for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3484429 💬 Offering to maintain ACL 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, Mikhail 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 for us means somebody with all the drupal.org permissions on the 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 Mikhail all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3484429 💬 Offering to maintain ACL Active .

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.

Thank you avpaderno and dillix, I will pick this up again myself.

@avpaderno I'm still interested in maintain this module. It hasn't new releases more than a year.

@salvis added me as maintainer but I haven't access to project repository.

@salvis - Drupal Commerce/Centarro recently became maintainers of "Commerce License Access Control" which has the ACL module as a dependency. They probably have a use case/customer and are therefore also interested in an actively maintained ACL module. Maybe it would be an idea to contact them and ask if they are interested in becoming active maintainers, allocating resources and having write access/access to project repository to the ACL module, if you don't have the time and need for the module yourself., The ACL module deserves a stable release with security coverage and be D11> future-proofed :)

@stizzi I have interest to actively maintain ACL, but I haven't access to project git. So now I use patched ACL as custom module for our customers.

@dillix I know that and I also hope that you get full access to the module, but I have been lurking here for a few years and noticed that Salvis is very careful about who he gives full access to the module but opens the door ajar and wants to see extensive and essential contributions from the applicant first. You might think that is a bit too cautious an approach, but we saw last summer how chaotic it became when a (talented) developer got full access to "Inline Entity Form", only had his own use case in mind but ruined it for a lot of others.

I have no talent in development, so I am selfish and just want a stable release with security coverage for ACL, a big hurdle for me was when Drupal Commerce/Centarro recently became maintainers of "Commerce License Access Control" and now just need a stable release with security coverage for ACL before I dare use it in production. That's why I thought Salvis might be a little more lenient if it was a company with an exceptional reputation within the Drupal community that became a co-maintainer.

I wish you the best with your application. :)

@stizzi I can make merge request for D10 & D11 compatibility and other fixes, but I'm waiting 4 month when this issue (RTBC): 📌 Add gitlab CI Active will be commited by @salvis. This is needed for test covering for merge requests & QA control of contributed code.