Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Jun 2014 at 09:22 UTC
Updated:
1 Aug 2014 at 14:10 UTC
Jump to comment: Most recent
Comments
Comment #1
olivierg commentedComment #2
PA robot commentedProject 1: https://www.drupal.org/node/2288977
Project 2: https://www.drupal.org/node/2222137
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 #3
dbcollies commentedHere is my review of the code
Comment #4
olivierg commentedHi @dbcollies,
Coding standards: Done.
Documentation: I have to complete it.
Licensing/Third Party: Ok.
Manual code review: Done.
Other concerns:
The name is standard like Media: Youtube.
Branch name changed.
Comment #5
gisledbcollies wrote:
From the TOU:
In what way is this term of the TOU fulfilled by the project?
Comment #6
olivierg commentedHi @gisle,
And so, what do you recommend ?
Comment #7
dbcollies commented@gisle You are correct. I didn't read through the entire text.
@blobsmith The only options you have, as I see it, would be to:
Comment #8
olivierg commentedOk, I changed the logo.
Comment #9
gisleblobsmith said:
Currently, I recommend nothing.
And I am not even sure if the license terms are only referring to the logo. Isn't the project designed specifically for using "Prezi content"?
The TOU speaks about "Prezi content", so I need to be able to install and start to use the module in order to see how "Prezi content" is used by the module. I haven't got that far yet. Both the project page and the README.txt is too sparse to get me started on a review.
My preliminary notes below:
Please take a moment to make your project page follow tips for a great project page. In particular, you need to say what external service this module is for, how one can get access to Prezi content for test purposes.
It should also list up-front all non-core modules that the module depends on, and what versions to install when full releases do not exist. It currently says that it "Work only with Media version 7.x-2.x", but it doesn't say that there is no full release and that one must use the dev version. Ditto with the File Entity module.
Comment #10
olivierg commentedDocumentation updated.
Comment #11
pushpinderchauhan commented@blobsmith, it's a little bit complex module and need more time to review complete code of your module. But as I was reviewing your code found one issue in following code, there is no return type for the case if your 'if' condition fails but this hook functions must return an array.
@blobsmith, please manually review for this scenario when if condition fails and share with us what happened in that case.
Thanks for your contribution and patience!
Comment #12
olivierg commented@er.pushpinderrana thanks for your review.
It is an unused function, I removed it.
Comment #13
gbisht commented@blobsmith coder sniffer is still showing some points which need to be fixed.
http://pareview.sh/pareview/httpgitdrupalorgsandboxogilbert2288159git
Comment #14
gisleReview of the 7.x-1.x branch:
These two errors should not stop anyone from doing a real, manual review.
Comment #15
ethant1) PAReview errors mentioned above still exist
2) Line 50 MediaPreziStreamWrapper.inc - don't mix single and double quotes
3) Functionally fine, works as expected.
I don't see any show stoppers - promoting to Reviewed and Tested.
Comment #16
olivierg commented1) Done
2) Done
3) Thanks @EthanT for review
Comment #17
klausiThanks 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).
The project looks good to me after a manual review.
Thanks for your contribution, blobsmith!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #18
klausiOne more thing: The Git commits are not connected to your user account. You need to specify an email address. See https://www.drupal.org/node/1022156 and https://www.drupal.org/node/1051722
Comment #19
olivierg commentedThanks @klausi,
I changed it.