Josh The Geek [joshthegeek]

Hello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review the code, pointing out what it needs to be changed.

• The points reported in this review are not in order of importance / relevance.
• Most of the times I report the code that present an issue. In such cases, the same error can be present in other parts of the code; the fact I don't report the same issue more than once doesn't mean the same issue is not present in different places.
• Not all the reported points are application blockers; some of the points I report are simple suggestions to who applies for a CVS account. For a list of what is considered a blocker for the application approval, see CVS applications review, what to expect. Keep in mind the list is still under construction, and can be changed to adapt it to what has been found out during code review, or to make the list clearer to who applies for a CVS account.

1. The module doesn't implement hook_uninstall(), or doesn't implement it to remove the Drupal variables it defines.
2. Hook implementation comments should be like the following one:

   /**
    * Implements hook_menu().
    */
   

   As reported in Documenting hook implementations:

   If the implementation of a hook is rather standard and does not require more explanation than the hook reference provides, a shorthand documentation form may be used in place of the full function documentation block described above:

   /**
    * Implements hook_help().
    */
   function blog_help($section) {
     // ...
   }
   

   This generates a link to the hook reference, reminds the developer that this is a hook implementation, and avoids having to document parameters and return values that are the same for every implementation of the hook. Optionally, you can add more information in a separate paragraph to describe the particular quirks of your hook implementation.

   In the case of hooks that have variables in the names, such as hook_form_FORM_ID_alter(), a slightly expanded syntax should be used:

   /**
    * Implements hook_form_FORM_ID_alter() for node_type_form().
    */
   function mymodule_form_node_type_form_alter(&$form, &$form_state) {
     // ...
   }
   

   This generates a link to the hook reference, as well as to the particular form that is being altered. Again, optionally you can add more information in a separate paragraph to describe the particular quirks of your hook implementation.

3. The proposed module duplicates the work done from an existing project, which is what we try to avoid. It's not clear to me why the same functionality could not be incorporated into Admin Menu, then. Did you open a feature request for the existing project?

Josh,

Perhaps your best path is to try to take over maintainership of Administration Menu Dropdown if your module closely replicates it's functionality, and it appears to be abandoned.

see http://drupal.org/node/251466.

There is also an issue to actually merge that functionality directly into admin_menu:

http://drupal.org/node/226012

To review your code:

1. Please remove the .svn directory and other hidden files.
2. Please remove the following from your .info file:
   

   version = "6.x-1.1"
   core = "6.x"
   datestamp = "1284319175"

3. Please add @file docblocks to your .install and .module files. http://drupal.org/node/1354#files
4. Typo:
   

   /**
    * Implementats hook_init().
    */
   

Alright. At this point, your module looks good on it's own merits. However, as a duplicate, it makes sense to wait on this application to see if there is a response from the Admin Dropdown module maintainer.

If not, we will approve you as a co-maintainer, and you should be able to release your code as the D6 port. Please bump this in two weeks - things tend to get lost in this issue queue.

I'm the creator and my free time hasn't allowed me as much time with Drupal module maintenance as I would like. I'm glad to hear someone has found it useful enough to keep up maintenance. Per Josh's request, I'm giving him CVS access.

I am approving the CVS account as maintainer of Administration Menu Dropdown.

Thank you for your contribution! I am going to update your account.

These 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 more contributors chatting on the IRC #drupal-contribute channel. 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.

I thank all the dedicated reviewers as well.