Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
3 Jul 2015 at 09:55 UTC
Updated:
15 Jan 2016 at 09:22 UTC
Jump to comment: Most recent
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxachton2292317git
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 #2
koykov commentedComment #3
impol commentedThanks for the module!
Manual Review
Php code generates html - it's not a good practice, you needs to use drupal_add_js function to add your js, and create js behavior to set variables from js (not php).
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.
Comment #4
koykov commentedThanks for your review. I fixed your issues from "Coding standard" section. You can see these changes here: http://cgit.drupalcode.org/sandbox-achton-2292317/commit/?id=4525b87572b...
Comment #5
rrfegade commentedReview of the 6.x-1.x branch (commit 95f5ce1):
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.
Source: http://pareview.sh/ - PAReview.sh online service
Manual Review:
Comment #6
rrfegade commentedComment #7
koykov commentedComment #8
PA robot commentedProject 1: https://www.drupal.org/node/2541320
Project 2: https://www.drupal.org/node/2522976
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 #9
achtonWhile it is true that both those issues were opened by koykov (my colleague), the repo for Instafeed is actually mine, and so is most of the code in it. He has been helping me getting the repo approved so that module could be promoted to full.
So I have reopened this task, and someone with power might wish to assign this node to myself, if that is what determines which user gets the approval. I had the impression that the owner of the repo would receive the approval, not the owner of the application node.
Anyway, the repo is still fully up-to-date according to the latest review comments and IMO ready for real usage: https://www.drupal.org/sandbox/achton/2292317
/Achton
Comment #10
PA robot commentedProject 1: https://www.drupal.org/node/2522976
Project 2: https://www.drupal.org/node/2541320
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 #11
achtonIt seems the approval not going to happen with this project, so I am closing this application.