Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
23 Oct 2019 at 12:09 UTC
Updated:
17 Nov 2019 at 09:19 UTC
Jump to comment: Most recent
Comments
Comment #2
estoyausenteComment #3
phthlaap commentedPlease change default branch to 8.x-1.x
Comment #4
avpadernoThank you for applying! For these applications, we need a project/branch where you committed most of the code, if not all. In this case, there are more commits from other users.
Since the purpose of these applications is verifying what the user who applies understands about writing secure code that correctly uses the Drupal APIs and follow the Drupal coding standards, we cannot review code written from more users to understand what a single user understands of writing Drupal code.
Comment #5
estoyausenteHi, @kiamlaluno! Thanks for answering. The module is developed by my mate @miguelarber. I just posted the project here because I have more experience developing Drupal and I did a review of his code and manage the project publication. But don't worry! My mate will post here and you can review the code with him :)
Comment #6
miguelarber commentedHi all!
I will be happy to answer any inquiry you might have related to the Splio module. At this moment, my commits in Drupal.org appear as 'unattributed', however I have already created an issue to see if you can solve this situation.
Meanwhile, you can check all the authoring information in the Drupal code repository. I've also changed the default branch to 8.x-1.x. Thanks.
Comment #7
miguelarber commentedComment #8
phthlaap commentedThanks for your contribution.
Please fix some issues reported by PAReview:
Comment #9
miguelarber commentedThanks for your comments and revision phthlaap & kiamlaluno. I followed the steps above and the project is ready to be reviewed again. I will be happy to solve any other issue you may detect.
Comment #10
miguelarber commentedComment #11
avpadernoI know the other commits are from Miguel Arber. The commit pages don't link to the user profile because the email address used for the commits isn't associated with the user profile, but on https://www.drupal.org/node/3089649/commits appears Miguel Arber Magjistari or Miguel Arber.
Miguel Arber can continue the application, since he doesn't have the vetted role.
Comment #12
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 IRC #drupal-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 dedicated reviewers as well.
Comment #13
miguelarber commentedThanks for updating my account @kiamlaluno. I will be happy to contribute as much as I can!
Thanks for the tips too, I will be reading them carefully in my spare time.
See you guys around!