Improve module description text and link

Thanks Chris. This makes sense to me.

Hrm, there aren't any other modules that could provide spam or profanity filters? If so, using an ambiguous title like that may be a problem. I kinda disagree about not using 'Mollom' as the title.

1. The proposed change is too tailored for a specific distribution, in which most users won't ever consider or install a different module for this kind of functionality.
2. The proposed wording is too limited with regard to Mollom's current and upcoming features.
3. We need to keep "Mollom" in the title. We can optionally append descriptive terms; e.g., "Mollom content moderation".
4. The direction of the revised description makes sense, but I think the wording can be improved.

The current title, which is just 'Mollom' is not very descriptive. Most end-users might not know what Mollom is. The proposed title is better with end-users in mind. What is the rationale for keeping 'Mollom' in the title?

If we insist on keeping Mollom in the title, maybe we can go with 'Mollom spam and profanity filters' instead of 'Spam and profanity filters'? Just a thought.

Revised proposal attached.

What is the rationale for keeping 'Mollom' in the title?

We're simply not there yet. Removing module names from the administration UI might work for certain Drupal distributions that are intended for a certain audience, in which site administrators won't even attempt to download and install other/third-party modules, so the distribution can tweak the entire administration UI in a way that assumes there can only be one module for a particular functionality.

However, regular Drupal users do install Spam module + CAPTCHA module + Mollom module + others at the same time. To try them, and to perhaps keep them. Removing the project/module name means that you have multiple links that state Spam protection, Spam prevention, Spam and profanity filtering, etc.

To some extent, regular Drupal users also expect modules to expose themselves with their module name, because the users know that they are working with a modular system.

I think there are two competing things here:

(a) many sites are built and handed over to clients - clear menu items help if you do not hand over a complete manual too, so people know what Mollom is
(b) Mollom does not yet have the name recognition like Google Analytics does for example, so people recognize what it is just by its name

I think the new proposed patch is a good middle ground to try and support those running multiple modules as well as those who just get their site.

+++ mollom.module	29 Jan 2011 23:17:41 -0000
@@ -191,8 +191,8 @@ function mollom_menu() {
+    'description' => 'Manage automated moderation of user-submitted content.',

Not sure whether we want to replace "Manage" with "Configure" though.

Powered by Dreditor.

#8: mollom-HEAD.description.6.patch queued for re-testing.

I like it. The description uses the word content redundantly, so it sounds awkward, but I don't have a better suggestion. Certainly an improvement.

Title will look a bit unusual (just look at a screenshot with the other admin items), given other modules rarely use so long titles. The description is supposed to elaborate. But otherwise looks good. Can we somehow shorten the title?

"Mollom spam protection and automated content moderation" sounds like this blocks spam of type Mollom.

Maybe "Mollom: Spam and profanity filtering"

Personally, I am down with this as of #15. It's as clear and concise as I can think of right now. Marking rtbc.

Wow, lot's of activity for a small patch. :-)

I'm happy with #15 - it is an improvement over the current so I committed it to HEAD.

I don't think we need to backport the changes.

Thanks!

Sorry, but I'm not happy with this. The link title is too long/wordy. It looks like this change wasn't actually tested and visually reviewed:

Let's keep the conversation going then -- maybe we can come up with something better. I'll give it some thought too.

Looks like needs works then as per @Dries.

Attached patch simplifies and shortens to "Mollom content moderation", which resolves the issue.

I think this is ready to fly.

Works for me. Feel free to commit.

Committed to 7.x. Not sure if this needs to be committed to other branches -- 6.x, 7.x working branches or 8.x. Moving to 'to be ported' so we can double check what needs to happen.

Committed a cumulative backport to 6.x-1.x.

Note: The last patch was committed to 7.x-rest only, not to master (7.x-1.x). I've committed it to master, too.