Problem/Motivation
I am interested in becoming a co-maintainer of the SecKit module.
I use this module on every site I develop and feel I should say thanks and pay for that use, by helping to keep the module up to date and current.
I would like to see a new version released with some of the many improvements in the issue queue and will try to remain active in the queue at least triaging and pruning the queue where I can.
I have been active recently trying to keep on top of some of the issues and aim to help get solutions into the main code base.
I have been helping out recently in these issues submitting code or reviewing where I can:
#3219294: Add form-action directive
#3098417: The base-uri policy is missing
#3208781: CSP: Directive script-src-elem violated with googletagmanager
#3185024: Add Permissions Policy to configurable options
#3219252: Breaks sitemap.xml when JS +CSS + Noscript protection is enabled
#3193443: Avoid using document.write('<!--');
#3193697: default-src has wrong description
#3541096: Remove the term whitelist* from the module
#3537083: cspell issues reported in pipeline
and I will hopefully be able to help get those merged, before tackling some of the others as required.
Comments
Comment #2
the_g_bomb commentedComment #3
mcdruid commentedThank you for the offer to help maintaining seckit Graham!
Appreciate the work you've put into the issue queue already; it'd be great to continue tidying that up and get a new release out.
Welcome!
Comment #5
the_g_bomb commentedThanks for the vote of confidence
Comment #6
mcdruid commenteds/Graham/GarethI used to work with a Graham who's a great developer and a good friend, so it's a positive association.. but I've no idea why my brain seems determined to call you that (I think I also did so when we met at Drupalcon Barcelona).
Apologies Gareth, and thanks again for your help with seckit.