Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Feb 2014 at 12:11 UTC
Updated:
24 Aug 2014 at 19:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave bagler commentedDo you have a link the sandbox project and have the code in a git repo?
You should remove the generated fields from your info file:
You need a function comment block for:
You need a file comment block for:
Comment #2
dave bagler commentedComment #3
askom commentedhello
thanks for the comments.
here is the sandbox projet
https://drupal.org/sandbox/askom/2190447
no code in a git repo, cause i just don't understand how it works, sorry.
Comment #4
PA robot commentedGit clone command for the sandbox is missing in the issue summary, please add it.
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 #5
dave bagler commentedI'm almost certain that you'll need to have your code in your sandbox's git repo in order to be granted full project status.
Comment #6
askom commentedhere is the git repo
http://drupalcode.org/sandbox/askom/2190447.git
Comment #7
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxdialogfeed2195517git
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #8
askom commentednew commit on git repo
Comment #9
feyisayo commentedHello Askom,
Thanks for the work.
The Git repository link you have in the comments is not correct. I had to infer what your Git link was from the PA Robot's comment.
Please add the correct link to your description ie
In addition, there are numerous formatting issues with your code. Please see http://pareview.sh/pareview/httpgitdrupalorgsandboxdialogfeed2195517git for the current report.
Best wishes,
Feyisayo
Comment #10
askom commentedThanks
it's seems like if it's not the good Git repo ...
here is the correct one with new files commited:
git clone --branch master http://git.drupal.org/sandbox/askom/2190447.gitComment #11
askom commentedComment #12
askom commentedComment #13
askom commentedComment #14
askom commentedComment #15
imgio commentedDear askom,
thanks for your work so far on the module.
Firstly, you should be working in a version-specific branch, not master.
View https://drupal.org/empty-git-master and perform that change.
Secondly, you have to fix all errors presented by pareview.sh:
http://pareview.sh/pareview/httpgitdrupalorgsandboxaskom2190447git
These will probably seem tedious and many will not make sense at first,
but they are important in keeping up the "standard practices" of the
Drupal community.
Good luck,
imgio
Comment #16
imgio commentedComment #17
askom commentedthanks for the review
I'm now working in a version-specific branch (7.x-1.x) and have fixed many errors presented by pareview.
There is just one error i can't fix cause i don't understand ... i hope it's possible to review now !
Comment #18
askom commentedComment #19
askom commentedPriority Normal TO Major cause "awaiting response from a reviewer for 2+ weeks" as described here:
https://drupal.org/node/894256
Comment #20
Binu Varghese commented@askom, while waiting for others to review your project, the very first thing you can do yourself is to fix all warnings and errors in - http://pareview.sh/pareview/httpgitdrupalorgsandboxdialogfeed2195517git
You can fix these as mentioned below:
README.txt
=========
All 5 warnings relate to: "Line exceeds 80 characters"
Solution: You can shorten it by just hitting Enter key (just before the 80th character) and start on new line. That's it. For more details please check: https://drupal.org/coding-standards#linelength
askom.admin.inc
============
The 2 warnings relate to: 'Format should be "* Implements hook_foo()" '
Solution: Replace function doc comment on line 9 with:
/**
* Implements askom_admin_settings_form()
* @return array
*/
and
Replace function doc comment on line 42 with:
/**
* Implements askom_admin_settings_form_validate()
* @param $form
* @param $form_state
*/
askom.install
=============
Likewise, on line 9 and 27 respectively add these function doc comments:
/**
* Implements hook_install().
*/
and
/**
* Implements hook_uninstall().
*/
askom.module
=============
Similarly, please fix other warnings here in this file.
The lone ERROR is self explanatory: "askom_requirements() is an installation hook and must be declared in an install file"
Let me guide you to this link: http://webwash.net/articles/how-notify-site-builders-if-something-requir...
Hope it helps!!
Comment #21
askom commentedI really thank you for your advices.
I have fixed all errors in http://pareview.sh/pareview/httpgitdrupalorgsandboxaskom2190447git
Comment #22
Binu Varghese commented@askom, in your .install file, as you have declared $t = get_t();
Line 18 should follow the below syntax:
'title' => $t('askom module'),
rather than
'title' => $t = 'askom module',
Similarly, fix the lines 19 & 21 as well. More info here - https://drupal.org/node/322731
Leaving you on "Needs review", with the hope that you fix these. Also, that should take care of the lone warning that is left :-).
Comment #23
askom commentedit's ok now. Thanks Binu !
Comment #24
askom commentedPriority Normal TO Major cause "awaiting response from a reviewer for 2+ weeks" as described here:
https://drupal.org/node/894256
Comment #25
askom commentedPriority MajorTO Critical cause "awaiting response from a reviewer for 2+ weeks"
Comment #26
znaeff commentedHi!
Way to speed up approving is to do PAReview bonus https://drupal.org/node/1975228
Having a review bonus will put your module application on the high priority list, see https://groups.drupal.org/node/142454
Comment #27
klausiThat is not an application blocker, please do a real review of the source code.
Comment #28
dbcollies commentedGenerally I found this to look good. I only found a couple of things that I think need to be cleaned up before this is ready to be released:
There are still things missing, like the help text, and the ability to administer other settings, but I assume that those are coming.
Comment #29
dbcollies commentedComment #30
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.