Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
22 Jun 2022 at 19:46 UTC
Updated:
29 Sep 2022 at 19:29 UTC
Jump to comment: Most recent
Comments
Comment #2
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 #3
avpadernoThe project is using wrong branch names. See Release naming conventions / Release branches.
A new branch needs to be created and made the default branch. Then, the branches with the wrong name can be deleted.
Comment #4
wilfred waltman commented@apaderno, thanks for looking into it and your reply.
I fixed the branch and tagging. Hope you can take another look
Comment #5
wilfred waltman commentedComment #6
avpadernoComment #7
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the Slack #contribute channel. So, come hang out and stay involved.
Thank you, 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.