Livechatoo module provide a livechatoo.com service into drupal block.
Code was checked with drupalcs on http://pareview.sh/pareview/httpgitdrupalorgsandboxraweez2416789git

Usage

1. Set Livechatoo block to any region.
2. Set Livechatoo account name "demo" for test use.
3. Save configuration.

Project

https://www.drupal.org/sandbox/raweez/2416789

Git

git clone --branch 7.x-1.x http://git.drupal.org/sandbox/raweez/2416789.git livechatoo

Drupal version

7.x

Comments

PA robot’s picture

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.

yuriy.kostin’s picture

Hi Matej,
My suggestions follow:

yuriy.kostin’s picture

Status: Needs review » Needs work
matej.lehotsky’s picture

Hi,
thanks for review! I changed module to use Drupal Behaviors in js.

matej.lehotsky’s picture

Status: Needs work » Needs review
darol100’s picture

Status: Needs review » Needs work

@raweez

There is still a lot complains on the Pareview.sh.*

Manual Review

Individual user account
Yes: Follows the 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 the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
Yes: Follows the 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

No hook_help, you should consider adding the hook_help even if display the same information as the README.txt. *

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.

klausi’s picture

Status: Needs work » Needs review

Those issues by pareview.sh should definitely be fixed, but are not major application blockers. Anything else that you found or should this be RTBC instead?

darol100’s picture

Status: Needs review » Reviewed & tested by the community

Not seeing any blocking issues to this module.

avpaderno’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for your contribution!

I updated your account so you can promote 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!

Thank you, 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.

Thank you to the dedicated reviewer(s) as well.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.