Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2015 at 07:12 UTC
Updated:
9 Feb 2016 at 08:44 UTC
Jump to comment: Most recent
Comments
Comment #2
PA robot commentedProject 1: https://www.drupal.org/node/2629388
Project 2: https://www.drupal.org/node/2130235
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxiS2629378git
Fixed the git clone URL in the issue summary for non-maintainer users.
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #4
ItangSanjana commentedComment #5
ItangSanjana commentedComment #6
ItangSanjana commentedComment #7
ItangSanjana commentedComment #8
gauravsood91 commentedManual Review
Individual user account
Yes: Follows guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
Yes: Follows the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements
Coding style & Drupal API usage
Yes: It follows code and API guidelines.
Comment #9
ItangSanjana commentedComment #10
ItangSanjana commentedComment #11
ItangSanjana commentedComment #12
ItangSanjana commentedComment #13
ItangSanjana commentedComment #14
ItangSanjana commentedComment #15
almaudoh commented@ItangSanjana: Here's some code review:
In commerce_rajaongkir.module lines 64 and 89
These nested foreach loops are using the same
$key => $valuevariable names, so the second$key => $valueis overwriting the first. This might be deliberate on your part, but the code is more readable if you use variable names that convey meaning.Comment #16
ItangSanjana commented@almaudoh: fixed. Thank you!
Comment #17
klausiRemoving all reviews from the issue summary that only repeat the automated reviews. When finishing your review comment also set the issue status either to "needs work" (you found some problems with the project) or "reviewed & tested by the community" (you found no major flaws).
Comment #18
klausimanual review:
But otherwise looks good to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Assigning to Naveen as he might have time to take a final look at this.
Comment #19
klausino objections for more than a week, so ...
Thanks for your contribution, Itang!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on 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.
Comment #20
ItangSanjana commentedSorry for the delay in replying to your comments because I had just recovered from a fever. Answering the comment #18:
1. I admit, I was a misunderstanding about the concept of the alter. After reading over and over again, it turns out it is the function to another module.
2. Thank you for the input, has been restyled.
3. Also been addressed.
And for your last comment, great! Glad to hear it.
By the way, what is "ht emight?", I cursory look it up on google but missed :)
Once again thank you Klausi and the community ...
Comment #21
klausiha, "ht emight" should be "he might", fixed above!