Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Jul 2016 at 01:46 UTC
Updated:
23 Jan 2017 at 17:26 UTC
Jump to comment: Most recent
Comments
Comment #2
b.ravanbakhshComment #3
b.ravanbakhshComment #4
PA robot commentedProject 1: https://www.drupal.org/node/2758935
Project 2: https://www.drupal.org/node/2758941
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 #5
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgsandboxbravanbakhsh2709633git
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 #6
b.ravanbakhshComment #7
b.ravanbakhshThe Code style runs and fixed.
Comment #8
hiramanpatilHi b.ravanbakhsh,
There are some issues in this module. Please go through the below pareview.sh URL.
http://pareview.sh/pareview/httpsgitdrupalorgsandboxbravanbakhsh2709633git
Thanks
Comment #9
visabhishek commented@hiramanpatil : Looks like you forgot to change the status. Is this now RTBC after your review or are there application blockers left and this should be "needs work"?
Comment #10
hiramanpatilUpdating status to 'Needs work'.
Comment #11
visabhishek commentedComment #12
b.ravanbakhshCode style is fixed.
Comment #13
b.ravanbakhshComment #14
b.ravanbakhshComment #15
b.ravanbakhshComment #16
b.ravanbakhshComment #17
b.ravanbakhshComment #18
b.ravanbakhshComment #19
ikit-claw commentedHi Have you considered adding in some testing ? https://www.drupal.org/simpletest
It's not required but would get you bonus points in the reviews eyes.
Comment #20
b.ravanbakhshHi @ikit-claw
I will add some testing in future, but don't think so its a blocker to go to production project.
is there any other comments.
Comment #21
ajalan065 commentedHi,
here is my bit of review.
1. Please inject the 'config.factory' service in GobookingsSettingsForm.php
2. Replace the parameters in $config->get() with the actual field names.
i.e.
$config->get('UserID')with
$config->get('user_id')Similarly at other places.
Replace the first parameter in set() accordingly. Make these changes in other files as well, wherever required.
3. Replace the private members with protected in Gobookings.php
4. Remove this commented part in Gobookings.php if not required.
5. Give appropriate whitelines before and after comments in GobookingsHelper.php
6. Inject the logger service in Gobookings.php, instead of using static functions.
I have not gone through the functionality on Drupal site.
Please make these changes.
Removing the PAreview bonus tag as per the Drupal rules.
Comment #22
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #23
b.ravanbakhsh@ajalan065 Thanks for reviewing my project
I have fixed all the review notes.
Comment #24
b.ravanbakhshComment #25
b.ravanbakhshComment #26
b.ravanbakhshComment #27
b.ravanbakhshComment #28
klausiThank you for your reviews. When finishing your review comment also set the issue status either to "needs work" (you found some problems with the project) or "reviewed & tested by the community" (you found no major flaws).
Review of the 8.x-1.x branch (commit f974c82):
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.
manual review:
Comment #29
b.ravanbakhshComment #30
b.ravanbakhshComment #31
b.ravanbakhshComment #32
b.ravanbakhshComment #33
b.ravanbakhshComment #34
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.