LS,
Step 1. of dealing with abandoned projects
I noticed this project started in august 2005. I also noticed that
This is the issue queue for a security.module that was never released in the wild.
as VeryMisunderstood stated in #429050: Security issue: Redhat servers have been attacked after installing Drupal.
I've some idea's about this module (no code ready yet) and I'm willing to take over maintainership. Since Uwe hasn't filled in a IRC-nick I contacted him today about this issue also through his PM.
Also start of step 2: (wait 2 weeks)
Best,
VinceW
-=[ Your Information Matters ]=-
Comments
Comment #1
VinceW commentedHello.
I have tried to contact the developer for the module Security both through the Drupal contact form and through posting an issue to the project page. Both attempts have been unsuccessful. The module is located at http://drupal.org/project/security.
I posted a request to take over maintainership at http://drupal.org/node/507278, which is moved to the webmasters queue now.
Uwe Herman, the initial maintainer opened an issue (Add a "Security" project at http://drupal.org/node/12646) in de webmasters que where he is refering to his initial (2004) thoughts on a security module. Those thoughts are still valid IMO, but have to be worked out. I've been working out some things and I would like to know if I'll be granted maintainership of this module before continuing.
I don't have a CVS account (yet), but have a request (17-jul-2009) pending for a Drupal/Ubercart module I've been working on. Would be nice if both applications could be granted.
Best,
VinceW
-=[ Your Information Matters ]=-
Comment #2
VinceW commentedJust a small adaption of the title, because after moving it to webmasters queue it wasn't clear enough in a glance
Best,
VinceW
Comment #3
avpadernoComment #4
vm commentedmoving to CVS as its been over 2 weeks and looks like all requirements have been met to make this OP a co maintainer
Comment #5
avpadernoIsn't this a task for the webmasters?
Comment #6
dave reidProject ownership transfers belong in the webmaster queue. Please stop moving these issues.
Comment #7
avpadernoI notice that there is a report open about a security problem (#48959: Security problem); it's not clear if the OP did what suggested him, and if he reported the problem to the correct place. Maybe this needs a little investigation, before to proceed with this.
Comment #8
dave reid@KiamLaLuno That looks like someone tried to report a security issue about Drupal, and not anything related to the security.module.
Comment #9
avpadernoThat makes sense; the OP has been confused by the name of the project, and used the project issue queue to report a Drupal security problem.
Comment #10
avpadernoI transfered the ownership to VinceW; the previous maintainer has still access to the project repository.
Comment #11
dave reidI also added a note on the project page that the module's issue queue is not the place to report security hole issues with a link to the security documentation.
Comment #12
avpadernoI added the warning also in the report guidelines; I think that this could avoid somebody else reports a Drupal security issue on the project issue queue.
Comment #13
dave reidI forgot about the issue report guidelines. Thanks Kiam!
Comment #14
VinceW commentedTnx all for the time looking into my request and for the transfer.
I realize the confusion which people can have. I'll do my best to handle this in a conscious way. If I'm making any errors, mistakes, or whatever, please do contact me about them.
Best,
VinceW