Hello,
I am reaching out to request permission to clone and maintain the A11Y project https://www.drupal.org/project/a11y . This module is heavily used within my company, Lukla Group: https://www.luklagroup.com/, for various projects.
Unfortunately, it seems that the project is no longer actively maintained. We would like to take over its maintenance to ensure its continued relevance and stability. Additionally, we plan to enhance the module with new features and ensure it adheres to accessibility standards, making it even more valuable for the Drupal community.
Furthermore, we aim to develop and publish complementary modules that build upon the principles of this project, creating a broader ecosystem around it.
I am happy to provide any additional information or clarification and am willing to follow the necessary steps to assume responsibility for maintaining or contributing to this project.
Thank you in advance for your consideration and assistance.
Best regards, Thomas ROGER
Comments
Comment #2
avpadernoOffers to be maintainers, co-maintainers, or project owners must follow what reported on Offering to become a project owner, maintainer, or co-maintainer.
A request to get an account confirmed does not make that person the new maintainer, co-maintainer, nor project owner.
A confirmed account is not even necessary to create new projects, be maintainer, co-maintainer, project owner, make commits, create new issues, or comment in existing issues.
Comment #3
avpadernoWhat eventually makes a difference in offering to be maintainer/co-maintainer, or even the new project owner, is that project moderators will not add as maintainer, co-maintainer, nor project owner somebody who is not able to opt projects into security advisory coverage, but that does not require a confirmed account.
Comment #4
anzelkiel commentedThank you for the responses. I duplicated the project: https://www.drupal.org/project/accesstools. Currently, the project is private; I’m not quite sure why, probably pending validation. I’m also waiting for it to be covered by the security advisory policy.
Comment #5
avpadernoI am not sure why it was unpublished, but I published it, so everybody can now see it.
As a side note, the correct procedure is explained in Offering to become a project owner, maintainer, or co-maintainer. It does not include cloning the project.
Comment #6
anzelkiel commentedThank you for republishing it. I don’t understand why it was unpublished either. I also didn’t see the option to publish it myself, so ... Thank you.
I’ll take note of the procedure in case this happens again.
I’m now waiting for security advisory coverage application’s approval.
Comment #7
avpadernoI confirmed the account basing on the account activity.