Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Jun 2017 at 13:11 UTC
Updated:
22 Oct 2018 at 07:02 UTC
Jump to comment: Most recent
Comments
Comment #2
PA robot commentedProject 1: https://www.drupal.org/node/2884075
Project 2: https://www.drupal.org/node/2878817
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 #3
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 #4
pavnish commentedComment #5
pavnish commentedComment #6
pavnish commentedComment #7
jadhavdevendra commentedGit default branch is not set, see the documentation on setting a default branch.
https://pareview.sh/node/2002
Comment #8
pavnish commentedHi jadhavdevendra Thanks for review
I have set the default branch now
Comment #9
jadhavdevendra commentedSorry to open it again..
Can you please remove all variables you have created in uninstall hook
https://api.drupal.org/api/drupal/includes%21bootstrap.inc/function/vari...
https://api.drupal.org/api/drupal/modules%21system%21system.api.php/func...
Comment #10
pavnish commentedHi jadhavdevendra
I have done the changes
Comment #11
ankush_03Hi pavnish,
Please fix below issue :
1. FILE: ...t/repos/pareviewsh/pareview_temp/apachesolr_entity_jit_index.install
--------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------
14 | ERROR | [x] Expected 1 newline at end of file; 2 found
--------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
2. Implement
hook_help()in your module file.Comment #12
pavnish commentedHi Ankush
I have fix these issues
Comment #13
ankush_03Hi pavnish ,
I have checked above changes, it is fixed now.
Comment #14
mario steinitzNo obvious coding standard issues, indeed. A minor thing to fix: Your README.txt should follow the provisions by the README Template. See https://www.drupal.org/node/2181737 .
You can review your project yourself on https://pareview.cc/pareview/https-git.drupal.org-project-apachesolr_ent...
Comment #15
avpadernoThat is a minor issue. Are there other issues that need to be fixed, and they are security issues?
Comment #16
sleitner commentedAutomated Review
Pareview details: https://pareview.sh/pareview/https-git.drupal.org-project-apachesolr_ent...
Review of the 7.x-1.x branch (commit fc35108):
This automated report was generated with PAReview.sh, your friendly project application review script.
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.
Comment #17
avpadernoIf you are still working on this application, you should fix all known problems and set the status to Needs review. (See also the project application workflow.)
Please don't change status of this application if you aren't sure you have time to dedicate to this application, or it will be closed again as won't fix.
I am closing this application due to lack of activity.
Comment #18
avpadernoActually, this is a duplicate application. We accept just an application per user.