Drupal Contrib CVS applications

The Drupal< site runs a repository and project issue system to allow the distribution are various third party contributed modules.

To gain access< potential new users are required to submit applications that include links to examples of their intended contributions. If the applicant fails to provide a link then it can not be progressed and usually (9 times out of 10) results in an automatic decline.

So what's this post for? Well, as part of the CVS applications process, the applicant's work is reviewed for some basic requirements. The most important requirement is that the author of the code shows both an awareness and understanding of security issues in their code. The review looks at other points too, like the ability for themers to easily alter the produced HTML so making the module suitable for a wider audience.

This series of articles (or blog if you like) is written by the primary Drupal CVS reviewer. In the past, such reviews have taken place between the CVS team and the applicant. However, the same mistakes are made over and over and this information may well be of use to others either thinking of applying for a Drupal Contrib CVS account or just by others who would like some insight into Drupal coding best practices and security related information. And so this series came into being to highlight some of the many reasons people fail (often at the first attempt) to acquire a Drupal Contrib CVS account.