Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
2 Sep 2015 at 17:40 UTC
Updated:
9 Sep 2018 at 18:04 UTC
Jump to comment: Most recent
Comments
Comment #2
PA robot commentedFixed the git clone URL in the issue summary for non-maintainer users.
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
rashid_786 commentedAutomated Review
Review of the 7.x-1.x branch (commit 0382b20):
No automated test cases were found, did you consider writing Simpletests or PHPUnit tests? This is not a requirement but encouraged for professional software development.
Manual Review
dependencies[] = linkit (>=3.x)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.
Comment #4
stijnstroobantsThanks for the review.
Implemented hook_help and updated the info-file (dependency)
Comment #5
stijnstroobantsComment #6
ajalan065 commentedGood work.
Can be moved to RTBC
Comment #7
ajalan065 commentedHowever @rashid_786 ,
the project does not follow the project length guidelines of Drupal, as it is neither 120 lines, nor has five or more functions.
Comment #8
klausi@ajalan065: there are no "project length guidelines of Drupal". Short projects are perfectly fine, we just can't give the git vetted user role away in such cases but will promote the single project manually to a full project.
Comment #9
ajalan065 commentedThanks @klausi to correct me. Will take care of it in future
Comment #10
stijnstroobantsThanks again for the review!
Comment #11
PA robot commentedProject 1: https://www.drupal.org/node/2438375
Project 2: https://www.drupal.org/node/2561969
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 #12
stijnstroobantsReopened again.
This is not a duplicate?
Comment #13
PA robot commentedProject 1: https://www.drupal.org/node/2561969
Project 2: https://www.drupal.org/node/2438375
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 #14
klausiplease read the message of the bot, only one application per user should stay open.
Comment #15
avpaderno