Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I'm the lead developer for Akismet.com, and I'd like for there to be an official Akismet Drupal module. Since this project has been unmaintained for so long, and it already has the Akismet namespace, could I please get ownership in order to release an Akismet module compatible with the newer Drupal versions?
Comments
Comment #2
colanTo prevent duplication of work, it would make more sense to move this issue from Akismet (which is dead) to AntiSpam, which is actively being used. I don't think it makes sense to split these up again when we already have a framework in place that supports multiple services (including Akismet).
Once you get access, I'd recommend starting with committing the patch from #2379263: AKISMET service is not working with current 7.x DEV along with the other RTBC issues before starting a Drupal 8 branch.
Comment #3
colanWe should probably change the title too.
Comment #4
Everett Zufelt CreditAttribution: Everett Zufelt at Myplanet commented@cfinke
, are you interested in the plan that Colan has described above?
Comment #5
cfinke CreditAttribution: cfinke commentedI considered posting this under the AntiSpam module, but I chose Akismet mostly because of the name and because my efforts would have to be focused on improving Akismet support, not integrating other anti-spam services. Given that the only other two services integrated into the Antispam module have shut down since the module's last update, I suppose that would make AntiSpam a defacto Akismet module anyway.
If you think that focusing all attention on the AntiSpam module makes the most sense, I would be happy to take over maintenance of it.
Comment #6
Everett Zufelt CreditAttribution: Everett Zufelt at Myplanet commented@Colan, do you have any thoughts about the best path forward?
Comment #7
colanI like the idea of maintaining a framework via AntiSpam that can work with multiple service providers. Even if Akismet is the only one operating now, being able to add new ones if they become available would be nice. Basically, having a pluggable system acting as an abstraction layer would be useful just like we've done with Search API and Solr. (Solr is no longer its own module, it works on top of the API.)
However, @cfinke, if you'd rather not maintain somewhat of an abstraction layer (or allow others to contribute patches to that effect), then I suppose it doesn't really matter which module you go with.
I'm just trying to minimize duplicated effort wherever possible.
Comment #8
cfinke CreditAttribution: cfinke commentedI'd be fine maintaining AntiSpam as a base abstraction layer that other modules can hook into, with Akismet as the bundled default.
Comment #9
colanGreat. Thank you!
Comment #10
Everett Zufelt CreditAttribution: Everett Zufelt at Myplanet commented@cfinke, I would agree that it is in the best interest to maintain the abstraction. I've added you as a maintainer. Please let me know if you have any questions.
Comment #11
Everett Zufelt CreditAttribution: Everett Zufelt at Myplanet commentedComment #12
cfinke CreditAttribution: cfinke commentedComment #13
eaton CreditAttribution: eaton at Lullabot commentedI'm late to the party, but +1 to this. I haven't had time to maintain this integration module for a long time, great to see it in good hands!
Comment #14
DamienMcKennaAs another awol comaintainer I'm excited to see newcomers - thanks cfinke (and Everett, and colan)!