Comments on: Why They’re Wrong: WordPress Plugins Shouldn’t Have to be GPL

By: munroe island

munroe island — Tue, 03 Nov 2020 02:29:00 +0000

one of the best honeymoon resorts in Kerala with backwaters surrounding three sides enjoying the local fishing’s and have fresh fish fries and curry with meals delivered on a banana leaf from refreshing Munroe island lake resort.

By: download triplets of belleville

download triplets of belleville — Tue, 19 Jul 2016 18:55:50 +0000

download triplets of belleville How are You, you must see those sites property ads and friendship and mobile phones

How are You, you must see those sites property ads and friendship and mobile phones

By: Theodore R. Smith

Theodore R. Smith — Sun, 12 Apr 2015 14:07:00 +0000

Bullshit. Linus simply had that clause added as additional protection against GPL fanatics like the ones at WordPress.

By: Namdnal Siroj

Namdnal Siroj — Thu, 07 Jun 2012 10:31:36 +0000

This is the first and only argument in this discussion that seems logical (and reasonable) to me.
Derivation of WordPress would be when you extend or modify the WP-code to create a new CMS, with extended or modified functionality. Not when you use it as a tool to display or run your original work.

By: Thomas Bodetti

Thomas Bodetti — Mon, 03 Jan 2011 22:50:32 +0000

I suspect that eventually this will get hauled into court, and perhaps we will have at least some legal definition, of course that will not settle the matter forever, until that time this is mostly speculation, subject to subjective subjection.

Software is perfectly capable to playing well together is it humans that seem to not be able to get along.

By: redwall_hp

redwall_hp — Mon, 02 Nov 2009 23:41:13 +0000

"So whatever the reason is wordpress.org does not allow non-GPL plugins, it is not because that is enforced by the GPL. Rather, it is automatic's deliberate decision to do so. And that's OK. Their website, their rules."

And I'm okay with that. The problem I have is that they're so vocal about other websites not following the same rules. They pressured theme authors to make the PHP portions of their themes GPL, and they're doing the same thing with plugins. The Thesis people are standing their ground so far, and I applaud them for that.

By: Hackadelic

Hackadelic — Mon, 02 Nov 2009 19:05:18 +0000

I think you are making the assumption that providing the plugin download is "redistributing". I think that's not quite true.

Be that as it may, the GPL does not prohibit SEPARATE distribution of copylefted with non-copylefted software. The explicitly allow putting such a mix on a single DVD and distributing that DVD. Similarly you are allowed to provide GPL-ed and non-GPL-ed stuff on the same website. (For example, donwload.com has all kinds of downloads, and they don't have to fear any license liability threats.)

The only legal problem would arise if they tried to package WordPress itself with non-GPL-ed plugins, but that's something they won't do w/o checking back w/ the plugin author (who then may copyleft the plugin for the sake of inclusion).

So whatever the reason is wordpress.org does not allow non-GPL plugins, it is not because that is enforced by the GPL. Rather, it is automatic's deliberate decision to do so. And that's OK. Their website, their rules.

By: redwall_hp

redwall_hp — Tue, 11 Aug 2009 23:19:14 +0000

That's certainly one way to put it.

By: Hackadelic

Hackadelic — Tue, 11 Aug 2009 09:55:48 +0000

Why not vote about this? [polldaddy 1862941 http://answers.polldaddy.com/poll/1862941/ polldaddy]

By: Hackadelic

Hackadelic — Tue, 11 Aug 2009 09:54:38 +0000

Furthermore, often it is even the other way arround: *WP calls the plugin* (hence the term "callback"). While the plugin does call WP functions to register it's callbacks, the *main* plugin functionality is invoked by WP. So even if calling a function *would* mean deriving work in the sense of GPL (however ridiculous it might be), it is then WP which "derives" from a plugin, not less than a plugin "derives" from WP.