Project page: http://drupal.org/sandbox/vikramaditya234/1447884
GIT: git.drupal.org:sandbox/vikramaditya234/1447884.git
Drupal version: 6.x
Overview
This module provides the functionality for the user to provide their online status. This is similar to what you set in gmail.
Features
1. User can select one from available statuses.
2. Other users will be listed in separate block, where the users will be listed and can be searched and their status known
Requirements
No dependency on any other module and tested on PHP 5.3.
Known problems
No known issue as of now
Links to Documentation
Simple usage, README.txt is provided in the module
Credits
Drupal family
Similar projects
None that I could find
Comments
Comment #1
patrickd commentedWelcome!
Please read about the workflow in the app-queue.
Please take a moment to make your project page follow tips for a great project page.
You are working in wrong named branch in git (probably you were confused about branches <> tags). 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.
(At least this has to be done before switching back to needs review)
We do really need more hands in the application queue and highly recommend to get a review bonus so we will(/can) come back to your application sooner.
regards
Comment #2
musikpirat commentedYou are still not working in a correct branch, you have to stick strictly to the naming conventions. :) I'd suggest to move to 6.x-1.x.
It is also recommended to keep .js and .css files in subdirectories
Comment #3
patrickd commentedit's not a requirement to work in a custom named branch (you can name them as you want as long we can figure out what version it's for)
the thing is that you can't create dev-releases with a wrong named branch
Comment #4
patrickd commented@musicpirat
assign issues to your self to either state that your doing a deep review and you want to make sure that someone else doesn't do the work twice or if your planning to take care of this issue in its complete livecycle
Comment #5
musikpirat commentedOk. Thaught that would be a mandatory to indicate, that I have a look at the issue. :)
Comment #6
musikpirat commentedThink my attempts to help in the review process double the work for you. :(
Comment #7
patrickd commentednever mind!, maybe you should have a look at older issues to get a feeling how everything works here ;)
Comment #8
vikramaditya234 commentedAdmin panel image
Comment #9
vikramaditya234 commentedI have added a new branch 6.x-1.x-beta, but could do exactly what is mentioned in the http://drupal.org/node/1127732 as the release identification section is not present my page edit. Hope this works, else please guide me through.
Comment #10
Miszel commented1) Since you decided decide to work in 6.x-1.x-dev branch, please amend your issue summary to inform reviewers about it:
git clone --branch 6.x-1.x-beta http://git.drupal.org/sandbox/vikramaditya234/1447884.git user_status
I would however suggest renaming the branch to 6.x-1.x to be able to create dev-releases
2) You README.txt should contain more information. After installation and after enabling those two blocks, I don't know what I am supposed to do. More information on how to use and configure the module would also be very useful. Make sure your README.txt follows the recommendation: http://drupal.org/node/447604
3) Please put more information on your project page. Guidelines can be found here: http://drupal.org/node/997024
4) The automated review (http://ventral.org/pareview/httpgitdrupalorgsandboxvikramaditya234144788...) shows one error, please correct it.
5) After enabling user status option block is not showing my status. I don't know why. Please see attached screen-shoot.
6) I don't think you should be putting putting drupal_ad_js into a template file. You could add it to your module instead, perhaps in the hook_block ???
Comment #11
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
Comment #11.0
klausiAdded more information on the issue