Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Jan 2014 at 15:27 UTC
Updated:
7 Aug 2014 at 10:27 UTC
Jump to comment: Most recent
Comments
Comment #1
ngocketit commentedComment #2
inakilz commentedHello,
Here are some quick issues to get started:
- The git clone is your personal git URL. This is your public Git clone command:
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/ngocketit/2154645.git
- You should delete your master branch, according to https://drupal.org/empty-git-master
- Take a look at the automated code review results here:
http://pareview.sh/pareview/httpgitdrupalorgsandboxngocketit2154645git
Comment #3
inakilz commentedComment #4
ngocketit commentedComment #5
ngocketit commentedHi,
Thank you inakilz for your comment! I updated git repos URL, removed the master branch and fixed the coding convention issues as pointed out by the automatic code review tool. There are still some warnings but I think they shouldn't affect the functionality of the module. Here is the latest automatic review. Please check again.
http://pareview.sh/pareview/httpgitdrupalorgsandboxngocketit2154645git
Comment #6
ngocketit commentedComment #7
PA robot commentedWe 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 #8
Alexxikon commentedHi ngocketit, here are my observations on your project:
The
image_styles_formatter.infoandimage_styles_formatter.modulefiles have the execution bit set (755instead of644).I suppose you could add comment to document the arguments of the functions
_image_styles_formatter_sort_image_styles(),_image_styles_formatter_get_image_info(),_image_styles_formatter_output_list().Comment #9
fernly commentedHi,
I took a look at the code and perhaps the following could be improved:
Good luck!
Lennart
Comment #10
ngocketit commentedThank you all for your reviews! I added more comments to the code and fixed the issues you have listed. Regarding the token display, thanks lennartvv for the info about the function. I knew that function but I didn't want to use it because I just want to have a simple, elegant way of showing the token info. I can of course switch to using token_tree but it seems to be pretty overkill for me.
Comment #11
ngocketit commentedComment #12
drush7 commentedHi ngocketit, as my first review, I installed & tested the module, also had a brief look at the code. I think the code looks good, at least clean and standard. This small module may be helpful to somebody who wants to have the same image field to be displayed in several image styles at the same time.
Comment #13
drush7 commentedComment #14
drush7 commentedComment #15
drush7 commentedComment #16
tr commented@ngocketit: Are you the same person as @drush7?
It sure looks like you created a second account on drupal.org just to push your application along.
Meanwhile, you haven't made any commits to this project since January, and specifically all the Pareview errors that were pointed out in January are still there. See http://pareview.sh/pareview/httpgitdrupalorgsandboxngocketit2154645git
Yes, the review process can be slow, but as long as you respond to the reviewers remarks and make the suggested changes your application *will* be approved. The only way to get it denied is to fail to participate. The documentation on the review process gives you suggestions on how to get through this faster - getting a review bonus (see above) is one way. When I see deceptive practices, however, I personally put my efforts towards looking at other projects.
Comment #17
ngocketit commentedDefinitely no! He's actually my friend who I helped me review the code. He's a junior developer and might not fully understand the process and I think I didn't either. But now I get a better understanding of what I should do. I'll help review other project, earn my bonus as well as fix the errors in the module & probably consider porting it to D8.
Comment #18
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.