[1.0.x] CKEditor5 Fullscreen

Usually, after reviewing a project, we allow the developer to opt projects into security advisory coverage. This project is too small for us and it doesn't contain enough PHP code to really assess your skills as developer.

Have you made any other project (module, theme, distribution) that we could instead review?

Thanks for the feedback apaderno. To answer your question, not on Drupal.org, no. Most of my work (primarily theme layer) is done for internal purposes. I'm happy to give you a link to a GitHub project or two if that would suffice, but I imagine that's not what you're asking for. Alternatively, I can add Joel Pittet → (who I work with) as a co-maintainer. My goal is to have the warning removed more than anything.

If you just aim to remove that warning, then adding somebody who can opt projects into security advisory policy and giving the permission to edit the project page is sufficient. Joel Pittet can opt projects into security advisory policy.

SInce the project has been created on June 26, it is necessary to wait nine days, before the project can be opted into security advisory policy, as that field's description says.

New projects must wait 10 days before opting into security advisory coverage.

That is a restriction that is valid for project moderators like me.

Great, thanks for the info. I must have missed the note about the 10 day waiting period. Thank you!

@occupant Since you cannot opt projects into security advisory policy, the description you see for that field is different; in your case, the description will tell you you cannot change that value. That is why you did not notice the part about the 10 days waiting period.