I am applying today because I want to take over an abandoned module called Private Message Limits.
The module was made in some context, but now it has been commited only 3 times (in the first 24 hours of its lifetime), back in july 2009, then was abandoned (never answered in the issue queue, that has only 5 questions).
The module does not work anymore with the most recent versions of Privatemsg and badly needs to be fixed.
I make extensive use of this module, I have been into Drupal for quite some time, and would like to share the current and future work on this module with the community, in a proper and decent way. This module is about security and spam prevention for the Privatemsg module.
Cheers
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | privatemsg_limits.tar_.gz | 8.75 KB | artscoop |
| #3 | privatemsg_limits.tar_.gz | 8.76 KB | artscoop |
| #1 | privatemsg_limits.tar_.gz | 8.99 KB | artscoop |
Comments
Comment #1
artscoop commentedComment #2
artscoop commentedComment #3
artscoop commentedOk, I've fixed the $Id$ tags in the info and module files, changed the module description and help.
Comment #4
artscoop commentedPHP error fixed.
Comment #5
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review your code, pointing out what needs to be changed.
The procedure to take over an abandoned project is described in http://drupal.org/node/251466.
Comment #6
frankcarey commentedI'm encouraging artscoop to submit patches to the module's issue queue first. Please see: #747886: Offering to maintain Private Message Limits
Comment #7
avpadernoConsidering that the project reported as abandoned has not been marked as abandoned, and that the current maintainer of the project replied, I am marking this application as . As reported in the requirements page, a CVS application for a project that seems abandoned should be created after there is evidence the project is really abandoned.
Comment #8
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: