Schmooz allows every user the ability to start their own conversation on a webpages.
Basic Overview (http://www.youschmooz.com/)
=========================================================
Schmooz started out with one simple goal: to organize the hundreds of comments that were posted on a single webpage. With this in mind, it has shaped itself into an innovative new way of online communication. Designed by Dhruvil Patel and developed by the WebPlanex Team, Schmooz is here to change the way people communicate on websites.
Want to have your own separate conversation on a webpage? We let you do that.
Want to favourite a stream of comments so you can view it later? We let you do that as well.
Want to mention a friend on Twitter directly from a comment? Yes, you read that right.
We hope you enjoy our service and we welcome questions and feedback at feedback@youschmooz.com
=========================================================
Features
=========================================================
Organized Commenting
Schmooz allows every user the ability to start their own conversation. Instead of one continuous stream of comments, users can distinguish between different conversations and reply in the ones they want to participate in.
View multiple Conversations
Not only do users have the ability to take part in more than one conversation, they can view two conversations on a webpage at the same time, making reading and replying to comments super efficient.
Instantly See What's Trending
Usernames of the people that have started a conversation are displayed in a box. The size of the username increases as more people post replies within that conversation. Now you can easily and intuitively see which conversation is trending on each page.
Mention friends on Twitter directly from a comment
Addicted to Twitter? We can relate. Thats why we made it possible for you to mention someone on Twitter directly through your comments or replies. You can also mention people that are signed up to Schmooz.
Type "@@" followed by someone's Twitter handle to mention them through Twitter.
OR
Type "@" followed by their Schmooz handle to mention them through Schmooz.
Favorite Conversations
See something funny, important or memorable that you want to remember for later? Just click the star to save the comment and all its replies as a favorite so you can check it out anytime from your Dashboard.
Colour coded Comments
Colour coded comments help distinguish the replies from comments and keep track of the conversation. As a website that uses Schmooz, moderators will have the option to pick any choice of colours to match your website's colour scheme.
You can see live demo here.
=========================================================
A link to project page:
http://drupal.org/sandbox/Youschmooz/1937952.git
Setting up repository for the first time
git clone --branch master Youschmooz@git.drupal.org:sandbox/Youschmooz/1937952.git youschmooz
cd youschmooz| Comment | File | Size | Author |
|---|---|---|---|
| #3 | drupal-schmooz.zip | 24.15 KB | Youschmooz |
| drupal-schmooz.zip | 24.15 KB | Youschmooz |
Comments
Comment #1
trof commentedCreate link on your sandbox project and Git.
I found your project in the Git - file ... looks like Joomla component. Could you please redo this as Drupal component so I can take closer look at the code?
It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
Review of the master branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
Source: http://ventral.org/pareview - PAReview.sh online service
Remove LICENSE.txt, it will be added by drupal.org packaging automatically.
Comment #2
arun ak commentedHi,
In your git branch files are not represent a drupal module.
A drupal module must need:
1) modulename.info
2) modulename.module
files.
Refer this : http://drupal.org/node/416986
Comment #3
Youschmooz commentedHello,
Sorry, my mistake i committed wrong code. Please review now.
Thanks
Comment #4
PA robot commentedLink to the project page and git clone command are missing in the issue summary, please add them.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #5
Youschmooz commentedHello,
Youschmooz (http://www.youschmooz.com/)
Project Page (http://drupalcode.org/sandbox/Youschmooz/1937952.git)
Thanks
Comment #6
Youschmooz commentedComment #7
balintcsaba commentedHi Youschmooz,
Is funny how you talk to a robot :)
That was an automatic message by the drupal.org system, you forgot to add to your application issue description the link to your project page and the git access.
You will find the example on of my previous projects description at Taxonomy Publisher Filter and Cache Flush.
Also please read the Apply for full projects to avoid such kind of mistake in the future what will slow down your application process.
Comment #8
Youschmooz commentedComment #9
kscheirerThe correct link is https://drupal.org/sandbox/Youschmooz/1989684 and http://drupalcode.org/sandbox/Youschmooz/1989684.git.
The project page describes the Schmooz service, instead it should describe what the module does (integrate with your service).
You need a branch that contains your code, either 7.x-1.x or 6.x-1.x. delete the master and youschmooz branches.
Remove LICENSE.txt, ",,.php", and cvsignore, and youschmooz.info. Drupal's packaging script will include a license file for you.
Is the name of your module youschmooz or schmooz? Pick one and all filenames/functions should use it.
Delete schmooz_update_7000() and schmooz_update_7001(). The former is empty, and the latter doesn't work. If you want something to happen when the module is installed use hook_install(). That is also the correct place to install your schema, not in an update hook. If you do decide to delete "post comments" permission from 2 roles, be aware that other roles may still have that permission, and you should let the administrator know what you're doing with a drupal_set_message().
In schmooz_element_post_render() it looks like you're trying to implement a SSO, consider using another module for this or make it configurable for the admin. I'm concerned that you're exposing user data.
Make sure curl is present before using it. Or use a hook_requirements() to let the admin know there is a problem.
Last but not least, please follow Drupal coding standards, https://drupal.org/coding-standards. Please fix problems found by automated review at http://ventral.org/pareview/httpgitdrupalorgsandboxyouschmooz1989684git.
----
Top Shelf Modules - Enterprise modules from the community for the community.
Comment #10
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #10.0
PA robot commentedAdded project link and Git access