Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Jan 2016 at 18:23 UTC
Updated:
16 May 2016 at 12:04 UTC
Jump to comment: Most recent
Comments
Comment #2
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxjosebc2649374git
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 #3
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #4
josebc commentedComment #5
josebc commentedComment #6
josebc commentedComment #7
josebc commentedComment #8
rlhawkAutomated Review
There are a handful of minor coding standards issues. Evidently, "Namespaced classes, interfaces and traits should not begin with a file doc comment" is a fairly new change to the standards (see #2304909: Relax requirement for @file when using OO Class or Interface per file).
Note that perfect adherence to Drupal Coding Standard is NOT a reason to block an application, except for total disregard of them. However, modules should follow them as closely as possible.
Manual Review
The text in the README documentation for the project is fairly minimal, but covers the basics. If you can provide more a bit more information it would be helpful. Please also include the same information—requirements, in particular—on the project description page.
Not exactly; there are four functions/methods and just about 120 lines of code, but most of the functionality comes from Twig template files and YAML definitions, so more functions are not necessary.
If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.
This review uses the Project Application Review Template.
Comment #9
klausi@rlhawk: I think you forgot to change the status. Are there any blockers left or is this now RTBC?
Comment #10
rlhawkYes, RTBC..
Comment #11
josebc commented@rlhawk Thank you for the review, fixed the coding standards issues
for the "Code long/complex enough for review" as you mentioned most of this module code is in the twig files which are lengthy but quite simple so i don't think this should be a problem.
Ill put some more work on README and project description soon .
Thanx again
Comment #12
josebc commented+review
Comment #13
josebc commentedComment #14
klausimanual review:
Otherwise looks good to me.
Thanks for your contribution, Yousef!
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 #15
josebc commentedThank you klausi for the review and the account change, i will be working on the description/documentation in the upcoming days.