This module brings an easy way to use the Google PHP Client Library, it uses the functionalities provided by Libraries API together with a drush command to install the library if the module was download normally, and an automatic installation of the library if the module is downloaded via drush. The idea is to simplify the work of integration with the library for modules, saving code and performance, as most of the times you have to make the library work to use only one function. This should be a generic module so every other modules can use.
The project page contains even more detailed information about the library. You can also find in the page that there's an old module that used to do this functionality, but it's abandoned and doesn't even have a release available. Also, that module used to work with the old repository of the library(google.code) and the library has moved to github, so there was no way to use it.
You can clone the project by using the command git clone --branch 7.x-1.x https://git.drupal.org/sandbox/davic/2779027.git google_php_client_library
As this project seems really "simple", this is the Project Page of another sandbox project of mine, for further verification if anyone wants to confirm that i have enough knowledge and follow the security and coding standards corretcly enough to maintain a module ;)
Manual Reviews of other projects:
https://www.drupal.org/node/2761385#comment-11476027
https://www.drupal.org/node/2633498#comment-11476245
https://www.drupal.org/node/2775533#comment-11476397
https://www.drupal.org/node/2498097#comment-11553131
Comments
Comment #2
davic commentedComment #3
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgsandboxdavic2779027git
Fixed the git clone URL in the issue summary for non-maintainer users.
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
davic commentedComment #5
davic commentedCorrected common errors found by our PA buddy here.
Comment #6
davic commentedComment #7
davic commentedComment #8
incursus commentedI know how it is to be waiting for reviews of your submitted code. :) I've already done my three requested reviews, but figured I'd look to see if I could do any others FWIW:
Looks solid as far as I can tell. Note: I did not actually install it, just did a quick code review. Given the small scope of this project, that approach seemed viable to me. Setting yours to "Reviewed".
Would appreciate a review of my menu_markup module if you have the time! :D (https://www.drupal.org/node/2782259)
Manual Review
Comment #9
davic commentedComment #10
davic commentedAdded one more review to the list of reviews i made of modules in the project application queue!
And also, forgot to say, Thank You Very Much @incursus for the review, and congratz for having your module approved! :D
Comment #11
PA robot commentedProject 1: https://www.drupal.org/node/2807381
Project 2: https://www.drupal.org/node/2779113
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 #12
avpaderno