Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 May 2012 at 05:57 UTC
Updated:
26 Jul 2012 at 23:51 UTC
Jump to comment: Most recent
Comments
Comment #1
patrickd commentedwelcome,
good to see you've already fixed the coding style issues.
As installation and usage instructions are quite important for us to review, please take a moment to make your project page follow the tips for a great project page.
We do really need more hands in the application queue and highly recommend to get a review bonus so we can come back to your application sooner.
regards
Comment #2
rho_ commentedThanks for the welcome patrickd!
I've updated the project page per your suggestion, including installation instructions and descriptions/visualizations of usage.
Thank you, and all of the reviewers for what you do. I will jump on this evening and try and knock a few reviews out. Is it sufficient to post the reviewed projects here in the comment thread to obtain the "review bonus?"
Comment #3
patrickd commentedThank you, we really appreciate all help we can get. As you can still edit the issue summary just add the list of reviews (direct link to the comment) into it and add a review bonus tag (PAReview: review bonus) by a new comment.
Comment #4
Cristian.Andrei commentedPlease have your code reviewed by ventral.org/pareview and fix all issues. Right now it states that it
FOUND 6 ERROR(S) AFFECTING 6 LINE(S)Comment #5
rho_ commentedOdd, it was running clean a week or so ago. Fixed the issues, seems to be running clean again.
Comment #6
Cristian.Andrei commentedHi,
Thanks for fixing the issues. Had a look at your code. One small thing to clear might line 53 in messagejs.module :
* See message.api.phpSince this file is not included in the module, please rephrase that so that it is clear that the message.api.php is found in the Message module.
Otherwise, it looks nice & clean. Also, tested the module and it works fine.
Comment #7
rho_ commentedThanks Cristian!
I've changed "See message.api.php" to "See message.api.php found in the message module folder." Changes have been pushed.
Comment #8
eyal shalevHi,
Can you change your default branch to 7.x-1.x (currently master).
And also edit this issue description to include the new git clone command (will be helpful to new reviewers).
Comment #9
rho_ commented7.x-1.x is now set as the default branch, and the issue description here has been updated.
Comment #10
eyal shalevAwsome :)
Comment #11
Anonymous (not verified) commentedthis looks really good to me.
- in the README, change 'mysite.com' to 'example.com'.
- i don't think messagejs_nodejs_handlers_info() is necessary, as you have nodejs_notify as a dependency.
i don't think either of these should hold up this becoming a full project, RTBC.
Comment #12
rho_ commentedIt didn't occur to me, but you are absolutely correct. hook_nodejs_handlers_info is redundant in this module as nodejs_notify does it already.
Removed the function, and made the change to the readme.
Thanks beejeebus!
Comment #13
tim.plunkettWelcome 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.
Comment #14.0
(not verified) commentedUpdating repository information.