Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Dec 2014 at 23:22 UTC
Updated:
30 Jul 2015 at 15:55 UTC
Jump to comment: Most recent

Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxedutrul2394985git
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 #2
edutrul commentedI've just fixed! the supposedly "errors" @PA robot besides most of them are camel case issue but if you look at views plugins they are lowercase and use underscores so that wouldn't make sense. I understand that it should be with CamelCase but That's what I see in views plugins and other core plugins. Unless that the rules changed. Let me know
It needs review! thanks
Comment #3
mcrittenden commentedChanging status back.
I reviewed the code and couldn't find anything worth complaining about. Very nice work!
Comment #4
srjoshLatest version in the repo still reports a lot of code style errors - did you commit and push your latest?
I'd suggest removing the 'I hate checkboxes' commentary.
Comment #5
edutrul commentedFixed doxygen issues
there are just the following that do not make much sense since class plugins and methods are in lowercase and method visibility
FILE: /var/www/drupal-7-pareview/pareview_temp/vaogr_plugin_access_role.inc
--------------------------------------------------------------------------------
FOUND 15 ERRORS AFFECTING 8 LINES
--------------------------------------------------------------------------------
13 | ERROR | Class name must begin with a capital letter
13 | ERROR | Class name must use UpperCamel naming without underscores
18 | ERROR | Visibility must be declared on method "access"
26 | ERROR | Method name "vaogr_plugin_access_role::get_access_callback" is
| | not in lowerCamel format, it must not contain underscores
26 | ERROR | Visibility must be declared on method "get_access_callback"
34 | ERROR | Method name "vaogr_plugin_access_role::summary_title" is not in
| | lowerCamel format, it must not contain underscores
34 | ERROR | Visibility must be declared on method "summary_title"
53 | ERROR | Method name "vaogr_plugin_access_role::option_definition" is not
| | in lowerCamel format, it must not contain underscores
53 | ERROR | Visibility must be declared on method "option_definition"
64 | ERROR | Method name "vaogr_plugin_access_role::options_form" is not in
| | lowerCamel format, it must not contain underscores
64 | ERROR | Visibility must be declared on method "options_form"
79 | ERROR | Method name "vaogr_plugin_access_role::options_validate" is not
| | in lowerCamel format, it must not contain underscores
79 | ERROR | Visibility must be declared on method "options_validate"
89 | ERROR | Method name "vaogr_plugin_access_role::options_submit" is not in
| | lowerCamel format, it must not contain underscores
89 | ERROR | Visibility must be declared on method "options_submit"
--------------------------------------------------------------------------------
Changing status to need review
Comment #6
rzan commentedHi edutrul
I took a look at your module. It seems to work exactly as it should and the code seems pretty clear. Nice work.
Individual user account
Yes
No duplication
Yes. Your module seems pretty specific and I could not find anything else which does the same.
Master Branch
Yes
Licensing
Yes
3rd party assets/code
Yes. No third party code present
README.txt/README.md
Yes. You could maybe add a little more detail, but your module's function is pretty simple and the screenshot on your project page is nice.
Code long/complex enough for review
Yes. Exceeds the limits set by https://groups.drupal.org/node/195848
Secure code
Yes
Coding style & Drupal API usage
* As mentioned above, your module still has some issues with coding style, with your class definition in particular. However, you are following the conventions set out by the Views module which does not follow the coding guidelines. This makes it impossible for you to not have method name errors so I can understand the frustration. You can still defer to the Drupal standards for your class name and you should be able to add the "public" visibility declaration where applicable.
Comment #7
mouhammed commentedI've tested this module on a clean install and It work just fine. You should fix these issues from automatic review : http://pareview.sh/pareview/httpgitdrupalorgsandboxedutrul2394985git
Comment #8
klausiThose are most likely false positives because of Views coding standard violations and surely not application blockers - anything else that you found or should this be RTBC instead?
Comment #9
ajitsAdding shortname to the git clone command.
Comment #10
ajitsComment #11
edutrul commentedWorks well! Please RTBC
Comment #12
mcrittenden commentedComment #13
edutrul commentedComment #14
edutrul commentedPlease guys! this is being RTBC for more than 4 months, please let this be a drupal project. Thanks
Comment #15
pravin ajaaz commentedReview other projects and Add pareview bonus to speed up this
Comment #16
cweagansThanks for your contribution!
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.