With two add-on modules for Spam (Gotcha and Spam Tokens), do we now qualify for using a "package = spam" in the .info file? This will put them into a separate fieldset in the modules admin list.

CommentFileSizeAuthor
spampkg.txt328 bytesnancydru

Comments

jeremy’s picture

Version: 5.x-1.x-dev » 5.x-3.x-dev
Status: Needs review » Fixed

The 3.x version of the spam module is designed as a package, which indeed is named "spam". While this version is not yet stable (or even usable), marking this issue as fixed in 3.x.

nancydru’s picture

Version: 5.x-3.x-dev » 5.x-1.x-dev

Is V3 (what happened to V2) being worked on? Since the other modules rely on Spam, it would be nice to get a preview.

jeremy’s picture

The first version of the spam module was created before Drupal's CVS system supported advanced featuring. Version 2 was created under a BSD license, and then when I finally moved it back into Drupal's CVS under the GPL I didn't bother to figure out how to assign a 2.x version number to it, so within the code it was referred to as V2 but in CVS it was referred to as V1. Version 3 is the current development branch, available from CVS as V3. It's very much a work in progress, not yet able to filter spam and under active development. Expect it to remain a very moving target for a while -- I'll roll an -alpha release when it's actually more or less functional, followed by a series of -beta releases as it starts to stabilize.

nancydru’s picture

Hmm... I don't see a V3 yet. Guess I have to wait for the roll up to get scheduled.

jeremy’s picture

Version: 5.x-1.x-dev » 5.x-3.x-dev

Fixing issue version, to avoid confusion as to which version addresses this packaging request.

jeremy’s picture

It's available via CVS. You can also browse the code online.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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