Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Nov 2014 at 03:36 UTC
Updated:
3 Oct 2015 at 04:26 UTC
Jump to comment: Most recent
Comments
Comment #1
PA robot commentedProject 1: https://www.drupal.org/node/2372249
Project 2: https://www.drupal.org/node/2325531
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxadam_bear2369977git
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 #3
adam_bearShut up robot.
Comment #4
adam_bearComment #5
PA robot commentedProject 1: https://www.drupal.org/node/2372249
Project 2: https://www.drupal.org/node/2325531
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #6
adam_bear86 Drupal, going back to github.
This is why you can't have nice things.
Comment #7
adam_bearReopening in the off chance drupal hasn't been completely abandoned.
Comment #8
sajiniantony commented1)An unwanted space need to be deleted in line no 213 of views_reveal.module
2)Project page needs updation. Your project page should inform users about the features to your module.
3)The function views_reveal_js_alter() in line no 151 of views_reveal.module is commented. If its not required delete the same.
Comment #9
sajiniantony commentedchanged the status to 'Needs work'
Comment #10
adam_bearfixed
Comment #11
adam_bearComment #12
darol100 commented@adam_bear,
No description on your project applicantion ? No link to the sandbox ? These things have to be provide by the developer. Do not worry I fix it for you. Once again you should consider reviewing other project otherwiser your project application is going to take more time.
Automated Review
You have a lot errors and warning detect from the automate test. Can you please fix them ? A great tool that would fix most of them for you is the coder module. Check this article is going to tell you how to auto-fomart your code using drush + coder. https://www.drupal.org/node/2148421
Here is the automatice test - http://pareview.sh/pareview/httpgitdrupalorgsandboxadambear2369977git
Manual Review
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.
This review uses the Project Application Review Template.
I think this is a great start for you to be improving your module.
Comment #13
adam_bear@darol100,
Thanks!
The remaining pareview errors/warnings should be false positives.
@2, 3 & 5: Good catch - Fixed.
@1: I think the css is named appropriately... it accurately describes the context in which the styles will be included, and the path should make it clear that it's part of views_reveal, not draggableviews. The js wasn't being used & has been removed.
@4: Views Reveal namespace is already taken by a module that doesn't work.
@6: I agree a check for dependencies is needed, but don't want to prevent installation- Added a warning in hook_enable() if the lib isn't present.
As for how long the project application takes... It would be nice if my project were approved, but I've had projects in the cue for nearly a year so I'm not exactly in a hurry- The community shouldn't complain be surprised when projects are hosted on github, though. I'm happy to contribute modules I've developed back to the community, but time is finite and drupal isn't the only project I work on.
Comment #14
adam_bearComment #15
babusaheb.vikas commented1) Correct your readme file name.
It should be README.md instead of readme.md
2) There are lots of coder errors in your project. Install coder module, check your module with coder and fix those errors.
Comment #16
adam_bearThe errors/warnings picked up by automated review are false positives- I suggest examining the code manually.
Readme will be changed on the next push.
Comment #17
ajalan065 commentedHi adam_bear,
1. Its not good to instruct your user to keep the library in sites/all only. Its the preferred place, ofcourse, but they may choose a different place.
2. You have made a heavy usage of
drupal_get_path('module', 'views_reveal');So, instead save it in a constance and use it at every place.
define('VIEWS_REVEAL_MODULE_PATH', drupal_get_path('module', 'views_reveal'));3. You have both views_reveal.js and views_reveal.min.js in your project. No need of both. Remove any one.
4. I do not think there is any use of *.install file in your module. Instead, keep the check in the function views_reveal_assets(&$view) itself where you are assigning the value to $lib.
Correct these and commit again. Once done, set back the status to "Needs Review". Would be happy to review your module again.
Comment #18
adam_bearThanks ajalan - I'll take a look at it.
Comment #19
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.