Comments on: How the GPL works, or not http://gpoul.strain.at/2009/07/06/how-the-gpl-works-or-not/ The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies, or opinions. Mon, 25 Jan 2010 22:27:45 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: gpoul http://gpoul.strain.at/2009/07/06/how-the-gpl-works-or-not/comment-page-1/#comment-770 gpoul Mon, 13 Jul 2009 17:18:40 +0000 http://gpoul.strain.at/?p=694#comment-770 you might want to read example 4.0 in this document: <a href="http://www.law.washington.edu/lct/swp/Law/derivative.html" rel="nofollow">http://www.law.washington.edu/lct/swp/Law/derivative.html</a> - very interesting... Looks like I was "assuming" that things work as they're handled with linux kernel modules where there are binary-only modules in existence and nobody ever sued anyone. I realize that assuming things is always worse than asking a lawyer, though. :-) you might want to read example 4.0 in this document: http://www.law.washington.edu/lct/swp/Law/derivative.html – very interesting…

Looks like I was “assuming” that things work as they’re handled with linux kernel modules where there are binary-only modules in existence and nobody ever sued anyone.

I realize that assuming things is always worse than asking a lawyer, though. :-)

]]> By: gpoul http://gpoul.strain.at/2009/07/06/how-the-gpl-works-or-not/comment-page-1/#comment-769 gpoul Mon, 13 Jul 2009 17:03:17 +0000 http://gpoul.strain.at/?p=694#comment-769 @earl: yes, there is confusion, at least for me. Not that I'd not write a WordPress module if I need one, because I still believe that something based on an API can not be a derivative work, but that is my interpretation alone and if I have the choice I'll go with something that has another license. I'm also not the only one. Looks like <a href="http://foolswisdom.com/commercial-wordpress-themes-gpl2/" rel="nofollow">others have this confusion too</a> and understand the issues even less than I do. :-/ @earl: yes, there is confusion, at least for me. Not that I’d not write a WordPress module if I need one, because I still believe that something based on an API can not be a derivative work, but that is my interpretation alone and if I have the choice I’ll go with something that has another license.

I’m also not the only one. Looks like others have this confusion too and understand the issues even less than I do. :-/

]]> By: earl http://gpoul.strain.at/2009/07/06/how-the-gpl-works-or-not/comment-page-1/#comment-768 earl Mon, 13 Jul 2009 13:51:51 +0000 http://gpoul.strain.at/?p=694#comment-768 @gpoul: is there any confusion whether wordpress modules have to be GPL'ed or not? @gpoul: is there any confusion whether wordpress modules have to be GPL’ed or not?

]]> By: gpoul http://gpoul.strain.at/2009/07/06/how-the-gpl-works-or-not/comment-page-1/#comment-754 gpoul Wed, 08 Jul 2009 06:29:41 +0000 http://gpoul.strain.at/?p=694#comment-754 @Kariem: My main concern was that anything using a specific proprietary API will be "determined by [Program]" and "designed only to be combined with [Program]". Just think about eclipse plug-ins and things like that. Although if the main problem in this case is "They are derivative of WordPress because every part of them is determined by the content of the WordPress functions they call." that's not such a huge deal as most plug-ins or kernel modules programmed to a specific API, while being designed to work with a specific program will not be detremined by the content of [Program] functions they call as there would be no value in doing something like that. - That might be the distinguishing factor for this case. It would be interesting to see a case made for Wordpress modules. I guess that would clear up confusion... or not ;-) @Kariem: My main concern was that anything using a specific proprietary API will be “determined by [Program]” and “designed only to be combined with [Program]“.

Just think about eclipse plug-ins and things like that.

Although if the main problem in this case is “They are derivative of WordPress because every part of them is determined by the content of the WordPress functions they call.” that’s not such a huge deal as most plug-ins or kernel modules programmed to a specific API, while being designed to work with a specific program will not be detremined by the content of [Program] functions they call as there would be no value in doing something like that. – That might be the distinguishing factor for this case.

It would be interesting to see a case made for Wordpress modules. I guess that would clear up confusion… or not ;-)

]]> By: Kariem http://gpoul.strain.at/2009/07/06/how-the-gpl-works-or-not/comment-page-1/#comment-753 Kariem Tue, 07 Jul 2009 23:23:04 +0000 http://gpoul.strain.at/?p=694#comment-753 The main points are at the end of the quoted paragraph: they are "determined by [WordPress]" and "designed only to be combined with WordPress". Without WordPress they could not be used for anything else. The statement refers only to the PHP elements in WordPress themes. All other components (styles, images, layout, transformation code) are not considered derivative of WordPress and can be used in a lot of different contexts. But the problem you are referring to in general is very true: it is important to think about how your code uses other modules and vice versa. Just calling an API covered by the GPL does not necessarily mean your code has to be licensed under the GPL, but there is indeed some gray area. Kariem The main points are at the end of the quoted paragraph: they are “determined by [WordPress]” and “designed only to be combined with WordPress”. Without WordPress they could not be used for anything else.

The statement refers only to the PHP elements in WordPress themes. All other components (styles, images, layout, transformation code) are not considered derivative of WordPress and can be used in a lot of different contexts.

But the problem you are referring to in general is very true: it is important to think about how your code uses other modules and vice versa. Just calling an API covered by the GPL does not necessarily mean your code has to be licensed under the GPL, but there is indeed some gray area.

Kariem

]]>