[D6] Greetings

For starters there's a license.txt file that shouldn't be there as Drupal adds it for you. Also in your greetings.info file your 5th line, where you put the version info, it is also automatically added by Drupal. You should follow proper naming convention when it comes to your functions which you can read about here and remove all old CVS $Id tags. Code sniffer found some problems as well which you can see here

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.

Hello venkatadapa, a few notes:

greetings.module
Line 62: t() is used for translating strings, so passing it an empty string is irrelevant.

The word "occasion" is mispelled throughout the module in different ways. It's good to keep the spelling consistant and accurate, especially if used in function and variable names so that there isn't confusion for people who use it and/or want to contribute to the project.

You should try to remove the php logic from greetings-block.tpl.php.

No major problems though.

----
Top Shelf Modules - Enterprise modules from the community for the community.

In your .info file, what are pongals? I'm not sure what's going on in greetings_nodeapi() - that will be executed on any node's 'delete revision' op, not just greetings nodes.

Thanks for your contribution, venkatadapa!

I updated your account to let you 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:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and get 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.

----
Top Shelf Modules - Crafted, Curated, Contributed.