Opt-in into security coverage [#3018733]

A little bit more than 2 weeks ago, we published a new module and joined to the coverage
But by mistake of our content manager, machine name of the module was wrong, after some consultation with "drupal.org webmaster" we decide to create a new module page (with right machine name) and delete/hide the old one.

In the old project, we already opt-in into coverage and had a stable release (hidden now).
Now I want to release the same stable code into the new one, but I must wait 10 days to opt-in coverage.
Is there a way to do it (opt-in) faster, given the current situation?
Probably the webmaster can opt-in manually?

Old project - https://www.drupal.org/project/setka
New project - https://www.drupal.org/project/setka_editor

Comments

Comment #1

7 December 2018 at 11:11

kala4ek created an issue. See original summary.

Comment #2

avpaderno

he/him

Italian

Brescia, 🇮🇹 🇪🇺

commented 7 December 2018 at 19:05

Component:

Project/Git problem

» Other

Since you have the vetted role, and you are maintainer of that project, you can edit the project to opt into security coverage. On https://www.drupal.org/node/3018529/edit, select Opt into security advisory coverage (listed under Security advisory coverage).

You just need to wait 10 days since the project has been created. That is a limitation that is set by the module handling that option, and is valid also for Git administrators. In fact, under that option, I read: