Jump to:

Problem

The Mollom module needs to be ready for Drupal 8 at the beginning of its release (a moving target, for sure).

Proposed Resolution

The module will need to be rewritten using the base user stories and test cases and guidance. The approach of a simple 'going through change requests' is too massive and does not take into account the fact that some portions of the module will need to be re-thought.

Changes

Minor - in general we are aiming for parity of API, functionality, and interface with the initial release. Larger changes to functionality, etc. will be made in subsequent releases but the aim for 8.x-1.0 is to simply provide Mollom functionality for Drupal 8. Some minor changes may include

Finally moving statistics display to JavaScript

Flag as inappropriate dialog implementation will be more native if possible

Will begin looking at shift to entities only rather than forms (but will not make this change in 8.x-1.0).

Timeline

Along with Drupal 8 release ;-)

Original report by @Gaelan

It's not that far off. :) I'm going to take a stab at this. We'll see if that goes anywhere.

I've started to take a stab at this as well. I don't expect I'll have something that runs without erroring out for another month or so. My initial approach is to just modernize the existing without rethinking the whole thing. I would expect a full re-think will become an obvious next step once done with the exercise of a straight port.

Hi there,
The start has been postponed for a few more weeks at this point. Would love to use this space to discuss high-level ideas, though, and we could move them into separate tickets for work once I get a basic structure built on the d8 branch.

Please follow the 8.x-1.x branch to find out what the updates are. As soon as we are happy with a stable 1:1 port of the 7.x-2.x branch to 8.x-1.x we'll start posting issues here again. Big architectural changes, as ashta mentions should still happen here.

We welcome patches for sure, so please let us know if you are interested in collaborating!

The branch is being worked on. I'm sorry to not be able to give you a date when it will be ready yet but we are working hard whenever we can schedule some time. We also welcome help from contributers, so feel free to give patches or suggestions.

The module should already install, but it is lacking active spam protection still.

As an FYI - I've been plugging away at this from the core requirements point of view. As I find smaller tasks (or not so small tasks as the case may be) that still need doing I'm adding them as d.o. issues and linking them to this parent issue. If you want to take one on - feel free to assign it to yourself and take stab at it. The core spam blocking will be available shortly - however tests have not yet been written.