Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 Jun 2014 at 03:29 UTC
Updated:
9 Sep 2018 at 21:28 UTC
Jump to comment: Most recent
Comments
Comment #1
moelius commentedThere are some errors reported by automated review tools, you must check this http://pareview.sh/pareview/httpgitdrupalorgsandboxirinaz2279929git
FOUND 255 ERRORS AND 5 WARNINGS AFFECTING 107 LINES
Comment #2
rob.barnett commentedI would also suggest running your code through CodeSniffer as well. pareview.sh doesn't always catch what CodeSniffer does and you will need to cleanup whatever CodeSniffer finds in order to get accepted.
https://www.drupal.org/node/1419988. Best of luck.
Comment #3
irinaz commentedThanks, I will work on this in August.
Comment #4
irinaz commentedhttp://pareview.sh/pareview/httpgitdrupalorgsandboxirinaz2279929git
-----------------------------------------------------
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
------------------------------------------------------
Comment #5
tim.plunkettOpened #2337777: Coding standards fixes with some fixes.
Comment #6
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 #7
tim.plunkettBot accounts should be banned from d.o
Comment #8
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 #9
tim.plunkettBooooo
Comment #10
klausi@irinaz: does this need review? See the workflow: https://www.drupal.org/node/532400
Otherwise let's leave this closed until we hear back from the applicant.
Comment #11
tim.plunkettThen let's use something that will show up in the queue (open issues will hide closed (won't fix).
Comment #12
irinaz commentedI will do more work on this module this upcoming week and post changes. sorry for delay. Tim, thanks!!
Comment #13
PA robot commentedProject 1: https://www.drupal.org/node/2476823
Project 2: https://www.drupal.org/node/2280911
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
avpaderno