Is this module still supported?
The last release from the 7.x branche is from 2010-Dec-18
And there is no a Development releases from 7.x!?

I hope the version 7.x-1.1-beta1 works reasonably...

Comments

mgifford’s picture

Title: This module is still supported??? » SpamSpan still being maintained?
Issue summary: View changes
gpk’s picture

Title: SpamSpan still being maintained? » SpamSpan appears to be unsupported
Project: SpamSpan filter » Drupal.org project ownership
Version: 7.x-1.1-beta1 »
Component: Documentation » Abandoned/unsupported projects
Status: Needs review » Active

Next step in the process.

Not sure if I have selected the right "Component" since there is no "Project ownership" component, which is what https://drupal.org/node/251466 states should be used.

Link back to project page: https://drupal.org/project/spamspan

Last commit by the maintainer https://drupal.org/commitlog/commit/1864/134361d1d29f118f03c8a085501307b... was in Dec 2010.

The only comparable/alternative project I'm aware of is Invisimail https://drupal.org/project/invisimail - but I'm not sure it's any better maintained/supported at present.

dddave’s picture

Status: Active » Postponed

Marked the module unsupported and slapped a warning on the project page.

dddave’s picture

Status: Postponed » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

peterx’s picture

Is this the right place to suggest a short term fix?

I am working on a site using a slightly updated Spamspan and could apply a few fixes. Their main fix is to switch the email address to a contact form. The Email module does something similar. If Spamspan had the Email module as a dependency, email addresses in content could use the Email module contact form.

I am making the change here. I could contribute that change and a few other fixes then drop the module back to unsupported.

The alternative would be to add a filter module to the Email module and direct people from this module to the Email filter module.

dddave’s picture

Status: Closed (fixed) » Active

The module is up for grabs. If you want it, you get it in no time.

peterx’s picture

Ok, I will take it on and promote some improvements.

dddave’s picture

Status: Active » Fixed

Module transferred to peterx. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

vitalie’s picture

Hi, I'd like to get involved as well. I've ported spamspan to D8 and fixed some further bugs on the way. See https://www.drupal.org/node/2394055.

Can I have access to Git? I've written to peterx personally, he did not reply yet.

dddave’s picture

Hi vitalie,

this has to happen in the module's queue for now. If peter doesn't respond to you in the next weeks you can reactivate the issue here but I strongly recommend trying to get in touch with him directly.

@peterx Could you please edit the project page to remove the abandoned module warning?

peterx’s picture

Vitalie added as maintainer. Note changed to mention Vitalie for D8. status changed to actively maintained. I left a link to here in case someone wants to maintain earlier versions.

vitalie’s picture

Thank you very much @peterx. I am happy to maintain version 7 as well.

peterx’s picture

Vitalie, as a maintainer, you can edit the module page and change the note about D7.

vitalie’s picture

ok, Peter, I've changed the note with respect to D7, but left it still for D6.

adamps’s picture

It's great that there are new maintainers. But I'm confused, especially by #16. As I see it, the module page https://www.drupal.org/project/spamspan seems to still indicate unsupported:

1) Note: As of 2014-05-26, this module appears to no longer be supported. If you are interested in taking this module over, or you as the module maintainer feel this message has been posted in error, please reply to #1808266: SpamSpan appears to be unsupported.

2) Maintenance status: Seeking co-maintainer(s)
Development status: Maintenance fixes only

Please can you update?

vitalie’s picture

Thanks @AdamPS. I've updated. Does it make more sense now?