Mollom should be grouped together with related modules on the modules page

Ugh. That package name is poor. It's also too limited for Mollom, since Mollom provides more than spam protection.

If the package name was "Moderation", then we could consider it.

anything is better than "Other".

That's not necessarily true. Many modules simply cannot be categorized. And the original intention of packages definitely was not to enforce a package name for all modules.

It also does not really make sense to have a package containing only one module. Which apparently is going to be the case on almost all sites installing the Mollom module, since you do not need or want any other content moderation modules if you use Mollom.

So, all in all, I'm

+1 for a proper package name; I'm a fan of sophisticated package names and dislike the usually huge can of worms in "Other".

-1 because Mollom will likely be the only module in the Moderation package on many sites.

More leaning towards +1, since a more broad package name like "Moderation" increases the chance for having another module (not related to checking spam/profanity/CAPTCHAs/etc) in that category.

Lastly, this is Dries' call. Attaching a patch for the suggested package name.

Quoting @davereid:

We need a unified and automatic way of adding taxonomy to .info files via the packaging system - not doing it directly in info files by abusing an existing method

The quote is from IRC. The topic needs to be resolved in Drupal core. I know there is at least one open issue against Drupal core for this, but can't find it right now. Might have been moved to Project project.

http://drupal.org/node/542202 is pretty concise regarding the usage of package, although it seems to have been blurred by the addition of the second paragraph and the wiki page.

All of this was never intended with the "package" declaration in .info files. What we're currently seeing is an attempt to abuse a package system that was never designed for categorization. Needless to say, that fails, big time.