Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 May 2016 at 20:46 UTC
Updated:
6 Nov 2018 at 12:12 UTC
Jump to comment: Most recent, Most recent file




Comments
Comment #2
hedrickbt commentedComment #3
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgsandboxhedrickbt2728667git
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
hedrickbt commentedComment #5
hedrickbt commentedI have resolved all of the pareview.sh items.
Comment #6
hedrickbt commentedComment #7
hedrickbt commentedThe branch with -dev in the name has been removed and the default branch for the project has been set.
Comment #8
hedrickbt commentedComment #9
hedrickbt commentedComment #10
hedrickbt commentedComment #11
hedrickbt commentedComment #12
hedrickbt commentedComment #13
hedrickbt commentedComment #14
hedrickbt commentedComment #15
hedrickbt commentedComment #16
hedrickbt commentedComment #17
Gorka Guridi commentedChecked the branch 8.x-1.x and it still has errors in pareview.sh:
http://pareview.sh/pareview/httpsgitdrupalorgsandboxhedrickbt2728667git-...
Am I using the correct branch?
Comment #18
hedrickbt commentedI have completely cleaned up all of the code formatting warnings/errors now.
http://pareview.sh/pareview/httpsgitdrupalorgsandboxhedrickbt2728667git-...
Comment #19
warped commentedThank you for your contribution!
After 2017 March 7 everyone can promote a project to a full project. A full project has a short project name and a drupal.org/project URL. It can also have releases (like alpha1 or 1.0). Edit your sandbox project, and then choose the 'Promote' tab.
https://www.drupal.org/docs/8/understanding-drupal-version-numbers/drupa...
https://www.drupal.org/docs/8/choosing-a-drupal-version/what-do-version-...
https://www.drupal.org/docs/8/understanding-drupal-version-numbers/what-...
https://www.drupal.org/docs/8/choosing-a-drupal-version/release-stable-v...
If you'd like to opt into security coverage, please ensure your module is ready for a full release, and then set this issue back to 'needs' review
Immense apologies for how long it took to get to this review completed.
Comment #20
avpadernoI am closing this application for the lack for replies. I take the OP just needed to be able to promote the project.
Comment #21
hedrickbt commentedSorry I hadn't replied. I lost track of it. It took a couple of years from when I had completed the requirements and when it was approved, but got closed 2 months after it was approved!!
Thanks for helping me get moved along. I have gone to the sandbox and promoted it.
Comment #22
hedrickbt commentedCan someone help me understand what "won't fix" means, though? As far as I knew, I did everything I was supposed to, I was waiting on Drupal admins to run with the ball.
I put the ticket back to needs review just to make sure someone sees it and can comment. From what I can tell there isn't anything else I need to do. The Close Won't Fix status confuses me, and probably anyone else that submits a sandbox project.
Thanks
Brooke
Comment #23
hedrickbt commentedComment #24
sleitner commentedAutomated Review
Pareview details: https://pareview.sh/pareview/https-git.drupal.org-project-feeds_auth_ope...
Review of the 8.x-1.x branch (commit 6b9a995):
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 #25
sleitner commentedComment #26
avpaderno@#22: #19 was asking if you wanted to apply to be able to opt into security coverage, or you were fine with being able to create full projects but not opt into security coverage.
This application has never been approved from any reviewers, so far.
Comment #27
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.