michael.kluz [michaelkluz]

Hello, and thank you for submitting a CVS application.

Before your module or theme is reviewed, I would like to present this checklist which covers 90% of the types of errors that reviewers are forced to reject an application for. Please make sure the items on the checklist are all taken care of prior to setting your application back to 'Needs review'.

1. Please run your module through the Coder module code review. This will pick up a lot of coding standards, function misuse, security, and internationalization issues. See http://drupal.org/project/coder
2. Please make sure all non-binary files have an @file documentation block as per http://drupal.org/node/1354#files
3. Please make sure that your code commenting complies with the Drupal Doxygen guidelines as shown at http://drupal.org/node/1354 . This ensures that the API module and external sites like drupalcontrib.com can properly parse your code's documentation.
4. Please make sure that the proper CVS $Id$ tags are added to all files as per http://drupal.org/handbook/cvs/faq. This requirement will be going away once we move from CVS to Git next year.
5. Please make sure all your text strings are wrapped in t(). This makes them translateable. See http://api.drupal.org/api/drupal/includes--common.inc/function/t/6
6. Remove any commented out code.
7. Make sure your module or theme is ready to be released in it's submitted form. Modules that don't work, or aren't ready to be used are immediately rejected.
8. Please don't include a 'version' line in your .info file. This is always added to the .info file by the Drupal.org CVS packaging script.

Once you have double checked all the above items, please set your application status to 'needs review'. If you made any changes to the code, please make sure to upload the updated module as well.

Hi. Please read all the following and the links provided as this is very important information about your CVS Application:

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications

• The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
• Or if your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.

As per previous comment, I am setting this issue to won't fix.
Since new users can now create full projects, applications have a different purpose and they are handled on a different issue queue. See Apply for permission to opt into security advisory coverage for more information.