Received: by 10.229.82.80 with SMTP id a16mr891977qcl.24.1234913385149;
        Tue, 17 Feb 2009 15:29:45 -0800 (PST)
Return-Path: <if.webs...@gmail.com>
Received: from mail-gx0-f177.google.com (mail-gx0-f177.google.com [209.85.217.177])
        by mx.google.com with ESMTP id 15si1859892gxk.4.2009.02.17.15.29.44;
        Tue, 17 Feb 2009 15:29:44 -0800 (PST)
Received-SPF: pass (google.com: domain of if.webs...@gmail.com designates 209.85.217.177 as permitted sender) client-ip=209.85.217.177;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of if.webs...@gmail.com designates 209.85.217.177 as permitted sender) smtp.mail=if.webs...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by mail-gx0-f177.google.com with SMTP id 25so4042684gxk.22
        for <sk2-gpl-dev@googlegroups.com>; Tue, 17 Feb 2009 15:29:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=6IutApmy5PYRpsbUGPVGwRLDWI8YRpJausVEFpuqDss=;
        b=JVdRTB72XY3RDZ6arL9YIYTccZZKyfXFcBnvJTMaFsYdaadveVNrD3m48bo5VDs5Zv
         EAV4MySN08wi/ZYueLCVmTkvTNQDUHN2ZEJF5etOiydamzeWZoY2wYVjV+FxWLUClDT5
         nIOQFbkUUeAC7qyrDHi/6BCg63xtt0QQ5610o=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=b2FVswWKR0lkvbS+YzC+wQX6WzKt3AWSBh/xMP01xAIsWnYRqA1DlQEgRWnwULdAEw
         TiPwHz4xuQP43Ug3qtbJQuyomRaDN/YiH8+LarKQ6B8whgJIPZ+UXlrJQ7MFmbj3N7/x
         5xfmzCcH0qAubK/5C+aWY20aOU7/MQTVWPjVE=
MIME-Version: 1.0
Received: by 10.100.144.11 with SMTP id r11mr521287and.24.1234913384046; Tue, 
	17 Feb 2009 15:29:44 -0800 (PST)
In-Reply-To: <87064494-FC26-4F37-A5FE-1736D6258F87@striderweb.com>
References: <87064494-FC26-4F37-A5FE-1736D6258F87@striderweb.com>
Date: Tue, 17 Feb 2009 17:29:44 -0600
Message-ID: <674b4a3b0902171529m214657e7we58942f88dd2f...@mail.gmail.com>
Subject: Re: [SK2 Dev] Spam Karma 2.4-alpha
From: Austin Matzko <if.webs...@gmail.com>
To: sk2-gpl-dev@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Tue, Feb 17, 2009 at 4:44 PM, Stephen Rider
<wp-hack...@striderweb.com> wrote:
> 1.  Nice integration, but in terms of interface, I think it's better
> to go with:
>
>        Run selected entries through [all Spam Karma plugins] (Apply)
>
> rather than
>
>        (Run selected entries) through [all Spam Karma plugins]
>
> () = button and [] = dropdown

That does make more sense.  I just copied the existing markup and
wasn't happy about it.

> 2. If you're not, you might all want to pay attention to the "Auto
> Update Plugins" thread on the wp-hackers list.  Working on
> standardizing a location for plugin-related data that (such as sub-
> plugins).  In the case of Spam Karma, I think the standard SK plugins
> would go where they are right now, but it would also search the
> "secondary" location for third-party plugins.

I don't see great harm to doing this, but I don't understand why it's
necessary.  Why can't 3rd-party SK plugins just be regular WordPress
plugins?  If a 3rd-party SK plugin is a WordPress plugin, it can be
installed using the WP plugin installer.  If it's just a file to be
put in the proposed plugin data directory, then people have to fire up
their FTP client, adding unnecessary difficulty.

I think all we need to do is add an action hook at the point when we
load SK plugins, and 3rd-party plugins can attach a callback to that
to instantiate their classes.

> 3. I think we should remove the RBL plugin from core SK, and add the
> Akismet SK plugin

Is there another RBL site we could use to replace blbl.org, the one in
the RBL plugin?

I think adding SK plugins is great, so long as it's okay with their
authors and their licenses.  Do we know how the Akismet one is
licensed?

Austin