Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Aug 2022 at 10:05 UTC
Updated:
30 Oct 2022 at 18:34 UTC
Jump to comment: Most recent
Comments
Comment #2
bbu23Hello and thank you for your contribution.
Overall, the module looks pretty good and there are no coding standards/best practices issues, but unfortunately there's not enough code to review from the person who applied.
Looking back in the history, there was another maintainer that doesn't seem to be a maintainer anymore who built the project from scratch and wrote most of the code.
Another note is that the status of the project is "seeking new maintainer" - not sure if this is valid or a mistake -, and the project currently has 3 maintainers, but the other 2 maintainers already have the vetted role.
Not sure what to do here, so I'll leave the issue in "Needs review" for someone else to review as well.
Comment #3
_shyThank you for your notices.
Yes, that's correct, I taken this module from the contrib modules adoption system.
About project status, seems like I forget to change it, because for now I fully maintain this module.
I'm sorry if this is wrong approach for putting security advisory coverage application, I didn't saw requirements or notes about that.
Comment #4
avpadernoThank you for applying! Reviewers will review the project files, describing what needs to be changed.
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smother review.
To reviewers: Please read How to review security advisory coverage applications, What to cover in an application review, and Drupal.org security advisory coverage application workflow.
Since the project is being used for this application, for the time this application is open, only the user who created the application can commit code.
Comment #5
avpadernoUsually, we accept applications that use a project for which the user who applies made most of (or all) the commits. In this case, since the user who created the project and made the first (and most of the) commits did it six years ago, I am going to accept the application.
Comment #6
_shyThanks, @apaderno!
I'm looking forward to any comments or changes request.
Comment #7
avpadernoI am changing priority as per Review process for security advisory coverage: What to expect / Application Review Timelines.
To the reviewers: Please set the priority to Normal after a review.
Comment #8
avpadernoComment #9
klausimanual review:
Otherwise looks good to me!
Thanks for your contribution, Kostia!
I updated your account so you can opt into security advisory coverage now.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on Slack or IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.