Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 May 2016 at 20:24 UTC
Updated:
21 Dec 2016 at 17:25 UTC
Jump to comment: Most recent
Comments
Comment #2
PA robot commentedGit clone command for the sandbox is missing in the issue summary, please add it.
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 #3
translate.com commentedAdded sandbox command
Comment #4
translate.com commentedUpdated status
Comment #5
translate.com commentedUpdated status..take 2.
Comment #6
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgsandboxtranslatecom2723595git
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #7
translate.com commentedReady for review, all of the style issues the auto check found are corrected.
Comment #8
gislePlease note that before adding tags, you should read the issue tag guidelines. Do NOT use tags for adding random words. I've now removed the random words you added.
Comment #9
translate.com commentedComment #10
gislePlease note that before adding tags, you should read the issue tag guidelines. Do NOT use tags for adding random keywords. I've now removed the random tag you added.
Here is a list of all project applications currently waiting for review. Just now, your application is on very bottom on the last page, which means that its spot in the waiting list is #187.
Every time you add a tag to your application, you're moved down to the bottom of this list. In other words, doing this random tagging may result in you having to wait longer for a review by a human reviewer.
One way to bypass this waiting list is to earn a review bonus. If you want a review anytime soon, you should try that.
Comment #11
gisleI've fixed the instructions for cloning the sandbox in the issue summary for you.
Three days ago you wrote:
No, they're not. Please click on this link:
http://pareview.sh/pareview/httpsgitdrupalorgsandboxtranslatecom2723595git
Fix the style issues, add the README.md, and make sure you check this one out:
If it is not a false positive, you should fix it. If it is a false positive, point that out so that reviewers will not keep complaining about it.
Comment #12
translate.com commentedAdded a README.md file and cleaned up several more stylistic errors.
There is a warning that still comes up, which i believe is a false positive:
I believe it's a false positive because it makes reference to users being able to make changes, which they shouldn't be able to. Only admins should have access to the settings page to make any changes.
Comment #13
klausiNo, that is not a false positive. Any user that has the permission "access administration pages" is able to make changes on admin/config/regional/website_translator, but only admins with a permission to change something should be able to. For example with "administer site configuration".
Comment #14
translate.com commentedMy bad, I definitely understood that warning oppositely. Just made the change- thanks for your help!
Comment #15
sudishth commentedAutomated Review
No problem found
Manual Review
Individual user account
Yes: Follows guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows licensing requirements
README.txt/README.md
Yes: Follows guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
used with default value variable_get('variable_name',''), https://api.drupal.org/api/drupal/includes!bootstrap.inc/function/variab...
Comment #16
yogeshmpawarComment #17
sriharsha.uppuluri commentedIts good to have directory name(translate_com_website_translator) and module name(website_translator) same.
Automated Review
Please fix reported issue on https://pareview.sh/node/209
Manual Review
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 #18
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.