Proposals

Code review of existing contributed modules is frequently cited as a means to improving the quality of existing contributed modules. However, the task of performing a code review falls somewhere between documentation, writing and reviewing patches, reviewing CVS applications, and creating new modules.

This is a proposal to elevate the visibility of module review, and make it easier for newcomers to perform module reviews.

Modules are grouped on the module administration page (admin/modules in Drupal 7) by package, which is defined, optionally, in our module's .info file. Package, then, is the most visible way in which modules are categorized. This wiki page documents package names chosen by module maintainers, please edit it!

In the Doxygen formatting conventions doc, it says that files should be documented with the @file directive and gives the following example:

Note the @file line in particular.

Hi,
I need a table for #127, so it will go here :)
This table is now fully complete :)

<

table>

This page is for tracking the findings of GHOP #136 in coder_format of the coder module.

http://drupal.org/node/140218 now makes this possible: http://drupal.org/node/146172

So let's do it. :-)

Core still needs to be factored out to separate page include files. If you're interested in helping out, grab a module below. Please follow the guidelines listed in the documentation page above. If you feel the documentation page should be changed, comment on the book page so we can keep that all together in one place.

A starting list of functions in node, user, and system: http://groups.drupal.org/node/5239. Note, however, that some of this (especially node) may be touched by the actions patch.