WordPress Creator GPL Says WP Template Must Be GPL'd

An anonymous reader writes "Matt Mullenweg (the creator of open source blog software WordPress), after review by various legal experts, is sticking to his guns that themes and plugins that 'extend' WordPress violate the GPL if they are not themselves distributed under the GPL. Matt has gone so far as to post this on Twitter. According to Matt, the premium template called Thesis should be under the GPL and the owner is not happy about it. WordPress is willing to sue the maker of Thesis theme for not following GPL licensing. The webmasters and Thesis owners are also confused with new development. Mark Jaquith wrote an excellent technical analysis of why WordPress themes inherit the GPL. This is why even if Thesis hadn't copy-and-pasted large swathes of code from WordPress (and GPL plugins) its PHP would still need to be under the GPL."

Comments

It comes form scope creep

[Sycraft-fu]

The idea of the GPL, at least the original idea, seemed to be that if you modified the code of a project and distributed that modified version, you also had to distribute the code. Ok, fair enough and easy enough to understand. So Linksys could go and use Linux on their routers, and they have to release the mods to Linux they make, but not any of the software they run on it.

However then you get things like this. A theme for something they now say has to be GPL. Not a new version of the software, a theme that adds in to it. Ummm ok. What about plugins, do those also have to be opened up? This leads to other worries, will GPL authors try and say if you use a GPL'd software to create something (like a picture with GIMP) that too has to be opened up?

That is some of the "viral" nature MS was bitching about. You GPL something and then you want to say everything it touches has to be GPL'd too.

I think people get a little miffed when they find that using GPL software got them more than they bargained for.

Re:And this folks...

[ehrichweiss]

Even better, why don't Thesis just make a "templating engine" to handle the WP code that can then be released under GPL and then release the rest of the CSS, images, etc. under their own license? I can think of a couple of ways this could be accomplished and it would protect Thesis entirely.

From the WP "analysis" on one of the links in the summary...

****
"My JS/CSS/Images are 100% original. Do they have to be GPL?

No, they don't. If they aren't based on GPL'd JavaScript, CSS, or images, you are not forced to make them GPL. What you could do is offer a theme under a split license. The PHP would be under the GPL, but other static resources could be under some other license."
****

That said, I'm a bit concerned about how this "it's a part of WP" will be interpreted because doesn't that then mean that commercial apps like Zend Studio, etc. are ALSO required to comply with the GPL since they ostensibly hook into the various GPL'ed libraries, etc. ??

I mean I'm all for GPL but if everything that so much as touches GPL'ed software falls under that license, we're going to find fewer and fewer people willing to create commercial apps for GPL OS'es, etc..and while I may not use it, we definitely don't need to go shooting ourselves in the foot at this stage of the game.

Re:I don't buy it.

[guruevi]

Yes you can, the GPL only talks about distribution. The thing is the moron copied and pasted WP source code and then went ahead and charged for it. Besides that, PHP include and require makes the files part of it's own program and then compiles it - it becomes a single program. If you don't like that, use exec or system. It would be the same as releasing a GPL program written in C++ but then not releasing the header files under the GPL.