I am proposing to take over as maintainer of this project. The current maintainer seems to disappeared, leaving this project orphaned. The purpose of this support request is to ask the current maintainer to declare their intentions. Either step forward and maintain the project or hand it on to the next person.

The procedure is that, if after two weeks, the current maintainer has not replied I will raise an issue to transfer the project. If the current maintainer definitely wants to orphan the project they should post a message here saying as much. This will speed the transfer process. I'll also attempt to contact them by other means. :)

Comments

ultraBoy’s picture

ultraBoy commented

Thanks for contacting me.

I suggest starting with your patches. If they are ready, we can test and commit them. After *several* patches you'll get permissions to module's folder in CVS. Ok?

liam mcdermott’s picture

liam mcdermott commented

To be honest I'm not worried about having CVS access, just want to get my code into version control. Since many of the bugs in the queue have been waiting some time, a patch has been waiting 25 weeks, and the project hasn't changed since March I came to the conclusion it was not being maintained.

Sorry, that might sound a little rude, but the reasons for coming to those conclusions are understandable. :)

czarphanguye’s picture

czarphanguye commented

"I am proposing to take over as maintainer of this project. "

"I've completely rewritten this module to clean up the code and fix [...]"

Sounds as if you already started a new branch of this module... I'm going to apply the patches at http://drupal.org/node/164287 yet fear that the current maintainer is just to MIA. Perhaps "Signature Module 2" should be created so that our patched module are n't conflicting with update_status and when/if the core sig module is updated cause additional issues with the changes due to *.install updates

P.S. Liam, Thanks for taking the time to address these module issues. <3

liam mcdermott’s picture

liam mcdermott commented

czarphanguye: thanks for the encouragement, if you get on well with that patch would you mind marking the bug 'Patch (ready to be committed)' ? Thanks. :)

The .install file will update your existing signature install without having to do anything but run update.php

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

@ultraBoy (or @zertox) - your response is quite reasonable, but based upon the lack of activity in CVS and the issue queue we have to wonder is if you really want to maintain the module?

manoloka’s picture

manoloka commented

I am wondering?

Lean have you taken over?

liam mcdermott’s picture

liam mcdermott commented

Lean have you taken over?

You mean 'Liam'? :)

No, the only way forward was to fork the project. The newer version of this module is Signatures for Forums, and comes with lots of new goodies.

manoloka’s picture

manoloka commented

Ups :-) Yes I meant Liam

Does "Signatures for Forums" works for any node or only for forums?

Edited --> Sorry I didn't go there and read the description, I've done it now and I know that YES it works for any node.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Issue summary: View changes
Status: Active » Closed (works as designed)

Closing out all 6 year old issues at this point.