Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
8 Jun 2012 at 19:54 UTC
Updated:
14 Oct 2012 at 00:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
klausiWelcome!
you have not listed any reviews of other project applications in your issue summary as strongly recommended in the application documentation.
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
Comment #2
jswainst commentedMost of the issues found above have now been fixed.
Comment #3
rrbambrey commentedHi there,
Automated review:
There's still a few outstanding issues from the automated review, check them out here http://ventral.org/pareview/httpgitdrupalorgsandboxjswainst1547216git
It also looks like you've got extra files in your master branch still too. Have a read of http://drupal.org/node/1127732
Manual review:
Other than that for a first look through it looks like nice tidy code. Good stuff!
Comment #4
jswainst commentedThanks for looking over the code and for the suggestions.
I committed another update to fix the issues mentioned above and in the automated review.
Comment #5
muneer1st commentedStill I can find some error with Drupal Code Sniffer, Refer to the attached file.
Comment #6
klausiVery minor coding standards errors do not justify "needs work". Please provide a manual review.
Comment #7
jswainst commentedComment #8
Elvar commentedHi jswainst.
I have taken a look at your code, this is what i came up with
1. A suggestion, would be to do some cleaning in your file structure, putting css files under a css folder, and templates under a template folder & js etc.
in a template file? 3. you got 2 stylesheet files, both have less 15 lines of code, why not just use one file, and use a comment as seperator? 4. post.theme.inc: this should use Drupal.behaviors, right? http://drupal.org/node/756722 Last, your README, seems a bit short on info, maybe you should work on it a bit :). Hope you can use my tips, happy developing :-)2. post_button.tpl.php: keep in mind that i'm not familiar with the the po.st API, but is it really necessary to have a
Comment #9
jswainst commentedThanks for the review Elvar.
Below are my comments on the items above:
1. I agree additional structure is important, but not necessary for a small module.
2. The tpl.php file makes it easy for a themer to override the generated html code.
3. The two stylesheets have a purpose. One is for an admin page, and the other for when content is loaded.
4. I changed the js to use Drupal.behaviors.
Comment #10
jswainst commentedComment #11
Anonymous (not verified) commentedWhy do you keep putting a higher priority ? If you want to get there faster get a review bonus
Comment #12
Bartuc commentedI reviewed the module and everything looks good. I use separate tpl.php files for much of my theming and, at least for me, it seems to make things cleaner and easy to work with.
Comment #13
greggmarshallI too have reviewed the module and it looks fine by me.
I don't see the automated review messages as any major issue worth blocking this.
Comment #14
sreynen commentedThanks for your contribution, jswainst!
I updated your account to let you 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 get 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 reviewers as well.