- Issue created by @AstonVictor
- 🇪🇸Spain cbccharlie
Hello Viktor,
I cannot make you a co-maintainer because I am not the owner of the module. In any case, I have solved the issue that I had opened and published a stable version for Drupal 10.
If you want to contribute to the module, even if you are not a co-maintainer, you can create issues with their corresponding MR (this way the corresponding attribution will be automatically generated) and I will be in charge of reviewing it and generating new versions.
Thank you so much.
All the best. - 🇮🇹Italy apaderno Brescia, 🇮🇹
Since this project is covered by the security advisory policy, site moderators will not add as maintainers/co-maintainers people who cannot opt projects into security advisory policy. Moving this issue to the Drupal.org project ownership queue will have the get this offer back to this queue.
- 🇺🇦Ukraine AstonVictor
Hi @apaderno,
thanks for your reply.
I know about thecannot opt projects into security advisory policy
mark and I already created an issue to receive it but unfortunately, issues are not moving so quickly (my issue has the 'needs review' status for more than 1 month). - 🇳🇴Norway gisle Norway
AstonVictor → now has permission to opt projects into security advisory coverage.
apaderno, is there a reason that this should not move forwards?
AstonVictor, are you still interested in being added to the team?
- 🇮🇹Italy apaderno Brescia, 🇮🇹
cbccharlie, co-maintainer who cannot administer co-maintainers/maintainers (but has all the other permissions on the project) already replied, asking to create issues with their corresponding MR.
This offer needs to be handled on the project issue queue.