Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
20 Sep 2016 at 16:02 UTC
Updated:
18 Oct 2018 at 08:18 UTC
Jump to comment: Most recent
Comments
Comment #2
jkamizato commentedComment #3
PA robot commentedWe 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
jkamizato commentedComment #5
jkamizato commentedComment #6
PA robot commentedProject 1: https://www.drupal.org/node/2803261
Project 2: https://www.drupal.org/node/2803167
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 #7
jkamizato commentedComment #8
icurk commentedManual review:
- In the .install file, you are using entityManager service, which is deprecated. Use entityTypeManager instead.
Comment #9
harsh.behl commentedHi @jkamizato,
In .module file you can use hook_page_attachments instead of hook_preprocess_html as hook_page_attachments hook is used to Add attachments (typically assets) to a page before it is rendered.
Comment #10
klausi@icurk and @pen: those are nice tips for improvements, but surely not application blockers. Anything else that you found or should this be RTBC instead?
Comment #11
jkamizato commentedThanks guys.
I committed a new version.
@pen, I changed the hook to hook_page_attachments, and works well :)
@icurk, I don't know how to do this. Can you give me a example, please? I followed the documentation:
https://www.drupal.org/docs/8/api/entity-api/defining-and-using-content-...
I hope you guy approve it. Thanks!
Comment #12
klausiRemoved review links from the issue summary because those are not reviews of other project applications. See https://www.drupal.org/node/1975228
Comment #13
avpadernoTo the reviewers: Please change back the priority to Normal after doing a review.
Comment #14
sleitner commentedAutomated Review
Pareview details: https://pareview.sh/pareview/https-git.drupal.org-project-custom_metatag...
Git errors:
The following git branches do not match the release branch pattern, you should remove/rename them.
Review of the 8.x-1.x branch (commit 80d5fa3):
This automated report was generated with PAReview.sh, your friendly project application review script.
Manual Review
https://www.drupal.org/project/custom_meta ?
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 #15
sleitner commentedComment #16
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 #17
jkamizato commented@kiamlaluno, I'm going to abandon this project.
I have a issue with git that I can't delete the branch 8.x-1.1 because its already related with a release. So, if I can't fix it, its kind demotivate to keep and fix all others issues.
Thanks all for your time
Comment #18
avpaderno