The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.
I have been programming for 36 years now, first for ICL (now Fujitsu), then as part of various R & D projects as diverse as operating systems, automated test and 3-D visualization, and more recently as a consultant.
I have developed several web sites for customers based on Drupal. In this process, I have had to write modules to implement functionality required in particular cases, and have also needed to patch existing modules to fix bugs.
Having used Drupal quite a bit, it is only right to give back to the community, contributing modules which may be helpful to a wider group of users. The first piece of code I would like to submit has already been posted as a diff file at http://drupal.org/node/487212 and has received encouraging comments. I have now packaged it as a standalone module.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | fs_stats-6.x-1.0.tar_.gz | 1.56 KB | linuxxguy |
Comments
Comment #1
linuxxguy commentedComment #2
linuxxguy commentedComment #3
avpadernoHello, 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.
As per requirements, the motivation message should be expanded to contain more features of the proposed project. For themes, it should include also a screenshot of the theme, and (when possible) a link to a working demo site using the proposed theme; for modules, it should include also a comparison with the existing solutions.
As you attached the code as patch for an existing module, what would happen if the current maintainer would accept the patch? The same code would be present in two different modules.
This is my personal consideration, not something written in the application requirements.
Comment #4
avpadernoComment #5
avpadernoPlease read the following links as this is very important information about CVS applications.
Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for these applications. Please read Migrating from CVS Applications to (Git) Full Project Applications and Applying for permission to opt into security advisory coverage on how this affects and benefits you and the application process. In short, every user has now the permissions necessary to create new projects, but they need to apply for opt into security advisory coverage. Without applying, the projects will have a warning on projects that says: