Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
15 May 2023 at 14:57 UTC
Updated:
2 Jun 2023 at 07:54 UTC
Jump to comment: Most recent
Comments
Comment #2
vishal.kadamThank 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 smoother 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.
While this application is open, only the user who opened the application can make commits to the project used for the application.
Reviewers only describe what needs to be changed; they don't provide patches to fix what reported in a review.
Comment #3
vishal.kadamComment #4
vishal.kadamFix phpcs issues.
Comment #5
vishal.kadamComment #6
shashank5563 commentedPlease remove the docker-compose.yml and .docker folder from the branch. No need of these two things in Drupal module contribution.
Comment #7
tgauges@shashank5563 I created a
.gitattributesfile to ignore all development files when packaging a release. I'd like to keep the files inside the git repository for easier development.Comment #8
tgauges@vishal.kadam I fixed the issues reported by phpcs.
Comment #9
vishal.kadam@tgauges I have reviewed the changes, and they look fine to me.
Let’s wait for other reviewers to take a look and if everything goes fine, you will get the role.
Comment #10
shashank5563 commented@tgauges, Rest look fine for me. Let's wait other reviewers.
Comment #11
rajan kumar commented@tgauges
Remove these files from your branch 1.x, these files should not be in any Drupal Contributed module.
docker-compose.yml
.docker folder
.gitattributes
.gitignore
Comment #12
vishal.kadam.gitignore files are allowed. There is no need to delete them.
Comment #13
tgauges@Rajan Kumar Is it not enough to follow the recommendation in https://www.drupal.org/node/1068944#exclude and exclude these files when packaging a release?
Comment #14
tgaugesComment #15
alvar0hurtad0Hello @tgauges,
you should include only the module in the repo.
the repository should be inisialized into the
folder in your case.
Comment #16
avpadernoThere is a main module (Entity Reference Delete Check) and a sub-module (Entity Reference Delete Check Paragraph Url). I guess it has been so because the sub-module could be replaced by another module implemented as a different project; having a sub-module allows users to not install it, if they have a replacement module.
Comment #17
alvar0hurtad0Sorry for the confusion @apaderno @tgauges, you're right.
I learned something today, thanks for that.
I'll do a deeper review of the code.
Comment #18
alvar0hurtad0LGTM
Comment #19
avpadernocore_version_requirement: ^9 || ^10Since the module is using a PHP feature that is available starting with PHP 7.4, and Drupal 9.4 dropped the support for PHP versions lower that PHP 7.4, the required Drupal 9 version should be increased.
Comment #20
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.
I thank all the reviewers.
Comment #21
avpaderno