Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2012 at 15:43 UTC
Updated:
4 Jun 2012 at 21:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
eugene.ilyin commentedHello
I spent a Review of your module.
ventral.org/pareview showed no deficiencies.
There is only one comment:
function snapengage_admin_settings_form
Why do you use a blank description, if so, why should the function t: '# description' => t (''),
Comment #2
arnested commentedProbably left the description blank by mistake.
Fixed in 2ac66cbe9fb6f2e1406073e957aeade385c8f51c (6.x-1.x) and 673888f2b7f36933c8b6622f297cec8e97c6842b (7.x-1.x).
Thank you.
Comment #3
kongoji commentedHi arnested,
Module works very well, I didn't noticed any major problem during a 6.x-1.x branch manual review. The only thing I can suggest is to consider creating a .install file to delete all module's variables during module uninstall (
snapengage_widget_id,snapengage_roles, etc..).From a phpcs scanning I noticed there are some little code cleaning to do, I attach the scanning results.
Greetz
Comment #4
arnested commentedFixed in both 6.x-1.x and 7.x-1x.
Thank you!
Comment #5
musikpirat commentedHi arnested,
your Readme.txt should contain some more information about how to configure your module. You should also add that to your project page.
Why do you add a separate permission for the configuration? I think this is a case where the default roles should be sufficient. Maybe you can explain this.
Rest of the code looks clean to me.
Comment #6
arnested commentedREADME.txt improved with installation/configuration instructions in commits 6c3abe5 (7.x-1.x branch) and 769afe6 (6.x-1.x branch). Same information added to the project page.
The reason we added a permission for configuring the module is so that you would be able to delegate setup if the module to a role of your choice (and not have to be uid 1 to do that). At least for some projects where we have deployed this the module is part of an installation profile where the customer would not have direct access to uid 1 but should be able to configure snapengage (and other stuff) anyway.
Thank you for the feedback!
Arne
Comment #7
arnested commentedI also added a short description of what the SnapEngage service is all about.
Added in b91727e (6.x-1.x branch) and 6055eb2 (7.x-1.x branch) and on the project page.
Comment #8
lucascaro commentedHi @arnested, I've manually reviewed the module for 7.x and It looks really good. I'd maybe add a link to https://secure.snapengage.com/widget in the description for the widget id field at admin/config/system/snapengage but that's not a blocker at all.
The module worked without problems and the code and the UI seem to comply with Drupal coding and documentation standards to the best of my knowledge.
This does seem ready for full project status IMO so marking as RTBC.
Comment #9
klausiSorry for the delay, but you have not listed any reviews of other project applications in your issue summary as strongly recommended in the application documentation.
manual review:
But that are not blockers, so ...
Thanks for your contribution, arnested! Welcome to the community of project contributors on drupal.org.
I've granted you the git vetted user role which will let you promote this to a full project and also create new projects as either sandbox or "full" projects depending on which you feel is best.
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.
As you continue to work on your module, keep in mind: Commit messages - providing history and credit and Release naming conventions.
Thanks to the dedicated reviewer(s) as well.
Comment #10
lucascaro commentedcongrats @arnested!
Comment #11
arnested commentedlucascaro: good idea in #8 to add a link to https://secure.snapengage.com/widget. Done in c2258b5 (7.x-1.x-dev), 0ba31b7 (8.x-1.x-dev), and 997e970 (6.x-1.x-dev).
klausi:
Regarding #9, 1) SnapEngage guides their users to use the document.write way of inserting the link to the external JavaScript. I figured it would be best to follow that. I have experienced that other companies have rejected to give support for JavaScript-snippets if they where not added exactly as they advised (no matter how stupid) and I think I'll spare people for those worries.
I cleaned it up a bit and added a comment in 7017167 (7.x-1x-dev) and d399893 (8.x-1.x-dev).
Regarding #9, 2) Readability (although it doesn't make much of a difference in this case). Is sprintf considered bad practice?
Regarding #9, 3) Good catch. Fixed in 9472ffc (7.x-1.x-dev), ed98a6e (8.x-1.x-dev), and 8588ba3 (6.x-1.x-dev).
Thank you for the feedback and thank you all for the review. I will promote the module to a full project shortly.
Arne