Bug 491790 - Review Request: mediawiki-SpamBlacklist - An extension to provide a Spam Blacklist management system
Review Request: mediawiki-SpamBlacklist - An extension to provide a Spam Blac...
Product: Fedora
Classification: Fedora
Component: Package Review (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-03-24 00:06 EDT by John Guthrie
Modified: 2010-02-08 19:26 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-02-08 19:26:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Guthrie 2009-03-24 00:06:02 EDT
Spec URL: http://www.guthrie.info/RPMS/f10/mediawiki-SpamBlacklist.spec
SRPM URL: http://www.guthrie.info/RPMS/f10/mediawiki-SpamBlacklist-0-0.3.20090318svn.fc10.src.rpm
SpamBlacklist is a simple edit filter extension. When someone tries to save the
page, it checks the text against a potentially very large list of "bad"
hostnames. If there is a match, it displays an error message to the user and
refuses to save the page.

The list of bad URLs can be drawn from multiple sources, including a URL that
contains a list of bad URL regexes, a file that contains a list of bad URL
regexes, or a database location.  The last option will allow you to
manage a local blacklist from a wiki page.  By default, it used the blacklist
at http://meta.wikimedia.org/wiki/Spam_blacklist.

Whitelisting is supported as well.

Note from the author regarding stability:
 This extension has not been widely tested outside Wikimedia. Although it has
 been in production on Wikimedia websites since December 2004, it should be
 considered experimental. Its design is simple, with little input validation,
 so unexpected behaviour due to incorrect regular expression input or
 non-standard configuration is entirely possible.
Just to repeat, this is an *EXPERIMENTAL* extension.
Comment 1 John Guthrie 2009-03-24 00:28:12 EDT
I should make a note regarding the value that I put in for the license field.

I have set the license field to "Freely distributable without restrictions" on the basis of the following URLs:


I am also using the README file that is contained in the package as part of the basis for this value of the License tag.

I have also sent an email to the author to get a better clarification as well.
Comment 2 Jason Tibbitts 2009-07-08 22:40:07 EDT
Did you receive clarification from the author?

Many of these mediawiki plugins suffer from terribly confusing licensing status.  
This one seems especially bad as the only thing we can really go on, the README file, says:

This extension and this documentation was written by Tim Starling and is 
ambiguously licensed.

I would argue that without clarification, there is no way this can go into Fedora.  It doesn't even seem that we have redistribution rights.  I guess I'll block FE-Legal.
Comment 3 Tom "spot" Callaway 2009-07-14 16:42:45 EDT
I'm inclined to agree with Tibbs's assessment. There are two points to be made here:

1. There is no license on this code (and it is code, not content). Without a license, the code is non-free.

2. "Freely distributable without restrictions" is not an acceptable license for Fedora code.

You should get specific licensing terms from the copyright holder (aka, the author). Without that, this cannot move forward. His individual views on free software aside, the way that copyright law works is that the only right we are given simply by having access to his software is the right to use. We do not have the right to copy, modify, or redistribute. We need him to explicitly grant us (and anyone who gets the code from us) those rights.
Comment 4 John Guthrie 2009-07-26 13:12:28 EDT
Alas, I have not received any kind of response from the author as yet.  I will try to contact him again.  If I still don't get a response, then we'll probably have to close the review request.
Comment 5 Tom "spot" Callaway 2009-11-30 20:03:40 EST
Just following up on this one, did you get any kind of response from the upstream author?
Comment 6 Jason Tibbitts 2010-02-08 19:26:32 EST
I'm going ahead and closing this given the AWOL status of the submitter.  Should anyone wish to resubmit, please address the legal issue first.

Note You need to log in before you can comment on or make changes to this bug.