Closed (fixed)
Project:
Drupal.org site moderators
Component:
Other
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
2 Apr 2020 at 16:51 UTC
Updated:
17 Apr 2020 at 14:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
avpadernoYou need to edit the theme (https://www.drupal.org/node/2866094/edit) and select Opt into security advisory coverage, under Security advisory coverage, right after Development status.
Applications to be able to opt into security coverage just give to the users the Drupal role that allows them to edit their projects and be able to opt into security coverage; they don't change the status of the project, which needs to be changed from the project owner.
Comment #3
flashwebcenterThank you for your help. I don't have the permissions to select Opt into security advisory coverage, under Security advisory coverage, right after Development status. It is disabled.

According to this page one-time review process I should be able to mark my project. Please help.
Comment #4
flashwebcenterComment #5
gislekiamlaluno,
if I am not mistaken, flashwebcenter was never given the permission to opt into security coverage. So he/she shall not be able to do what you suggest in comment #2.
flashwebcenter
when looking at your application to opt into security coverage - #2867474: [D8] Drupal8 W3CSS Theme, I think you closed it prematurely, i.e. before it was approved by a git administrator. I try to describe the two mistakes you did below:
To conclude, looking at how your application progressed, it was never really "Fixed", since setting this status yourself accomplishes nothing. You still don't have permission to opt into security coverage, and that is why that radio button is still greyed out in your profile.
You need to be given the permission to opt into security advisories by a git administrator: You can do this either by getting your two year old application reopened (with status set to RTBC), or by starting a new one.
Before doing so, it may be a good idea to read about Issue Queue Etiquette. Pay special attention to recital #11.
Comment #6
neerajsinghHi flashwebcenter,
Your user account does not have access to opt into security advisory coverage. This is provided by Git administrators, for more refer: https://www.drupal.org/node/1125818 .
You also need to check out the workflow to achieve this access: https://www.drupal.org/node/539608 .
Additionally, guidance from gisle in the comments above has detailed out the further todos.
Comment #7
avpaderno@gisle Yes, I noticed. I am closing this as fixed and re-opening the application, which has never been approved (nor has reached the Reviewed & tested by the community point).
Comment #8
gisleYes, it did (in comment #18) - https://www.drupal.org/project/projectapplications/issues/2867474#commen... - however, that was a pretty shallow review, so "Needs review" is probably the right status.
Comment #9
flashwebcenterThank you kiamlaluno, neerajsingh, and gisle for your help. We learn from mistakes. Maybe we can have some custom code to disable "fixed" and "closed fixed" for any maintainer in the project. It will save time for drupal.org webmasters and prevent any project maintainer to do the same mistake.
Again thank you all for your help, and be save.