- Issue created by @anzelkiel
- 🇮🇹Italy apaderno Brescia, 🇮🇹
Offers 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 be maintainer, co-maintainer, or project owner. Creating projects, committing code, or creating new issues does not require a confirmed account. - 🇮🇹Italy apaderno Brescia, 🇮🇹
What 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.
- 🇫🇷France anzelkiel
Thank 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.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
I 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.
- 🇫🇷France anzelkiel
Thank 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.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
I confirmed the account basing on the account activity.
Automatically closed - issue fixed for 2 weeks with no activity.