Currently we have a D5 and a D6 version "published" in above node.
I got an first e-mail: We are sorry to inform you that your CVS account request has been declined due to: you are referring to an existing module.
Indeed I am referring to an existing module. The current maintainer doesn't want to maintain the new module and wants it to be a separate module. He will make a reference to this module because it extends the features of Domain Access. This situation is not mentioned in http://drupal.org/cvs-application/requirements, to which you are referring.
Other Domain Access modules, with extended features, do have their own maintainers, that's why I am requesting to become a maintainer for this module and not a co-maintainer.
Your second e-mail states: I would like to fix bugs I find as I go or add new features to existing modules. The correct way to leave feedback for a module is to use the patch issue/queue system.
I did read this sentence and we did use the issue/queue system. See node/255771 - mentioned already above - issue date May 7, 2008. Several people have the same problem as you can read from this issue, but the current maintainer doesn't want to solve it , also not after receiving the solution of the problem.
I understand the Drupal community doesn't want to have explode the number of modules and maintainers. To become a maintainer is not my first choice, but if the current maintainer doesn't want to solve a common problem (for a subset of users?) what should I do then?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | domain_redirect.zip | 14.41 KB | promes |
Comments
Comment #1
avpadernoSee the part saying .
The point is that CVS applications made with the purpose of creating a project that is a duplicate of another existing project are rejected. Whenever you want to create a module because the existing one is buggy, or because it is no longer maintained, or it is too difficult to use for you, the application is rejected.
Comment #2
promesThe module is attached.
Comment #3
avpadernoThere have not been replies from the OP, who has not uploaded the code for the review. I am marking this report as .
Comment #4
promesI am sorry I didn't set the status to "Needs review". I overlooked this.
Comment #6
avpadernoI am sorry; I have not seen the attachment, and the status of this report has not been changed as it should be.
Comment #7
avpadernoComment #9
avpadernoAs per comment #1, I am setting this report as .
Comment #10
avpaderno