This drama actually has nothing to do with the GPL. The theme authors are complying fully with the GPL, and there is nothing legally or morally wrong with distributing a plugin containing separately-licensed code or assets. The exact same issues could arise even if Wordpress was released under the BSD/X11/Expat/etc licenses.
The problem is that Wordpress is trying to maintain a very high level of control over their community. One of the tools WP has is the ability to ban theme authors they don't like (i.e. those who sell themes on third-party sites) from attending official events.
Then WP throws in a few words about the GPL as a smokescreen to deflect anger at someone else.
Below Dan Grossman said the Automattic released WordPress itself under the GPL license. It sounds like they did so because they wanted to, but they could have released it under any license they wanted. That would make WordPress the source.
Alternatively Automattic may be forced to release WordPress under GPL due to being a derived work of other code. This may or may not be true. Based on their behavior it does not seem to be a contributing factor either way.
It's a common lie that someone might be forced to open-source their code because they accidentally copied some GPL'd code. This is not true. In a typical case of copyright infringement, the infringer must stop distributing the copied code and possibly pay damages. The GPL merely offers a additional choice, it doesn't force anything.
BSD is not viral. If you incorporate BSD code in your code, then you're free to licence the result under any license you choose. However, if you include GPL code in your code, the result must be under GPL or any other license that is compatible (AGPL for example). In that sense, the GPL is viral - it does not only cover the code that's licensed, but also "infects" other code.
> BSD is not viral. If you incorporate BSD code in your
> code, then you're free to licence the result under any
> license you choose.
No, you're not. You are not permitted to change the license of someone else's code. Their code remains under the BSD license, and you have to comply with it when you distribute the combined work (e.g. keeping copyright notices intact). > Copyright (c) 2013 Felix Gilcher
>
> MIT License
>
> Permission is hereby granted, free of charge, to any person obtaining
> a copy of this software and associated documentation files (the
> "Software"), to deal in the Software without restriction, including
> without limitation the rights to use, copy, modify, merge, publish,
> distribute, sublicense, and/or sell copies of the Software, and to
> permit persons to whom the Software is furnished to do so, subject to
> the following conditions:
>
> The above copyright notice and this permission notice shall be
> included in all copies or substantial portions of the Software.
>
> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
> NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
> LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
> OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
> WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The important part is: > to deal in the Software without restriction, including
> without limitation the rights to use, copy, modify, merge, publish,
> distribute, sublicense, and/or sell copies of the Software, and to
> permit persons to whom the Software is furnished to do so, subject to
> the following conditions:
All I need to do is retain the copyright notice, but only if I use substantial portions. So as long as I retain the notice, stating that some specified part of the code is licensed under MIT, I'm in the clear. The permission to sub-licence is explicitly granted, no further restriction is placed on the combined work. I don't have to provide the source code either. The end result can be whatever I choose, the license does not spread to the combined work. WTFPL is even more liberal: > DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
> Version 2, December 2004
>
> Copyright (C) 2004 Sam Hocevar <sam@hocevar.net>
>
> Everyone is permitted to copy and distribute verbatim or modified
> copies of this license document, and changing it is allowed as long
> as the name is changed.
>
> DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
> TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
> 0. You just DO WHAT THE FUCK YOU WANT TO.
No restrictions at all - effectively placing the code in the public domain, but a valid copyright waiver in jurisdictions where code cannot be placed in the public domain (e.g. in Germany, where copyrights cannot be waived)Otherwise, we are saying that Linus was doing something wrong to license his work under the GPL...
Please stop attacking people for applying GPL to their own work by their own choice. You are NEVER forced to use someone else's work in violation of their license. If you want to use their work, you must comply with their license. If you can't comply with the license, find an alternative or build your own. Then you will be able to license it as you wish. End of story.
> The GPL is not designed to be "viral".
It is designed so that if one chooses to create a work that makes use of another GPLed work, that the license "spreads" to the resulting combined work. It is in that sense that some people call it "viral" though, unlike most viral infections, choosing to incorporate a GPLed work into a larger work is done so willingly, even if sometimes those making the choice don't fully understand the ramifications. For example, as Torvalds notes [0] it's sometimes a gray area; kernel modules may or may not be considered derived works.As you correctly note, it's the author's choice to adopt the license for a new project or to combined works licensed under the GPL into an existing project. That it is a choice doesn't preclude an analysis of the license's effect on any given work.
[0] http://lkml.indiana.edu/hypermail/linux/kernel/0312.0/0670.h...
> It is designed so that if one chooses to create a work
> that makes use of another GPLed work, that the license
> "spreads" to the resulting combined work.
This is true for all popular software licenses under current US copyright law.If you _dont_ license your code under the GPL or some similar license which explicitly allows others to build on your code, copyright prohibits anyone from doing so.
You can't, in general, "create a work that makes use of" somebody else's song, or movie, or novel. Because copyright says you need their permission, and there's not a culture of songwriters, filmmakers, or authors; who explicitly grant the freedom to use their work without asking. I find it difficult to understand people who intentionally use negative language like "viral" about the GPL. It's remarkable there so much high quality software available where the authors have said "here, you can use it inspite of the fact that it's copyrighted to us, the only condition we require is that you offer that freedom to everybody else if you build something new using our copyrighted work."
If I have a project licensed under the X11 license, and I copy some BSD-licensed code into it, then that code is still the property of the original owner, and it needs to remain under the BSD license. If I simply copied it and stripped out the copyright notices, then I would be committing copyright infringement.
Envato allows you to list WordPress themes and plugins for sale in their marketplace, ThemeForest. They make these products available under a split license: the PHP code that interfaces with WordPress is made available under the GPL. CSS, JavaScript and binary assets are made available under a commercial license.
WordPress does not argue that the above scenario is illegal, only that if you split-license works like that, you're not welcome to present at conferences that use their name.
What if I made NotGPLPress that had API compatibility with WP's theme API, but was otherwise my implementation and released under a BSD license. That seems to be the exact same battle Google and Oracle just fought over Java, with Google essentially winning the APIs are not copyrightable battle. At that point couldn't every theme author just say that their theme is built for NotGPLPress and license it however they want? It seems odd that the existence or non-existence of another implementation should affect an author's licensing obligations.
Of course, the bigger problem seems to be that (some) theme authors want to be "part of the Wordpress community", presumably largely for professional and monetary reasons, while ignoring that "the Wordpress community" is strongly reliant on (and fundamentally beholden too) Automatic, and they can (and do) place expectations on the behaviours of participants in "the community", and they can (and now are) requiring that participants at events they run comply with those expectations. If you want to be "part of a community" which is reliant on one company, you probably need to play by their rules, even if you can whip out your rules-lawyer hat and claim "but those rules aren't strict interpretations of 'the law'".
That might make them really mad. If they are going to blacklist on not licensing images as GPL, what do you think they are going to do to you? ;)
The question whether conforming to a given API (which is what wordpress themes really do) constitutes a derivative work has so far only been answered "no" (and honestly, you better hope it stays that way).
GPL explicitly states that non-derivative works are not covered.
That said, basically, wordpress takes a legal position that is pretty bad, IMHO.
People copying the GPL code into their own code? Great, i'm with you, it's GPL'd, assuming
1. it's copyrightable code.
2. it's not the only way to make it compatible, since if it's the only way to make it compatible, that's so far been considered fair use.
As the ninth circuit said, anything else would grant a de-facto monopoly on functional uses.
IMHO, you really don't want the legal reality to become what wordpress is trying to enforce.
While your explanation makes that clear (and thanks for that), there's a big difference between "our preferences should become law", and "our preferences are not supported by law, but people who don't agree with them don't get invited to speak at conferences we run". Democrats are free to run conferences without being required to allow republicans to present there and vice versa, why is that different for Wordpress's conferences?
I think your choice of the word "enforce" is probably a bit of an overreach for what Wordpress are trying to do.
(for what it's worth, I don't agree with what Wordpress are doing, it seems petty and small minded to me, but I do think they have every right to be petty and small minded about conferences they organize if they choose to be…)
Except that is ridiculous. What if you start a LLC and license your code through the LLC? How is WP going to know the developer of that split-licensed code? Does this mean everyone selling themes needs to start hiding behind legal entities?
What WordPress are doing is ensuring that if you want to build a reputation at a Wordpress conference, then you need to abide by what they think are important principles. If you want to be "Joe Smith, WordPress theme superstar" at their conference, you need to GPL your themes non-php assets. If you want to sell themes at ThemeForest as "Anonymous Foo Corp LLC" with commercially licensed non-php assets, that's fine too, but Anonymous Foo Corp doesn't get invited to speak at WordPress conferences, and if Joe Smith springs "Hey, I'm Anonymous Foo Corp on ThemeForest, go buy my shit" on the audience during a presentation at a WordPress conference, it'd be spectacularly poor form, and he should expect to be called out on it and never invited back.
(and the fact that the blog post got written shows that at least one theme author does want to build his reputation by speaking at their conference, but isn't prepared to meet their "rules". wordPress, rightly or wrongly, have decided you can't do that any more.)
For example, the law says that you have to have a license to make a derivative work, and it is this particular law that is "the source of the GPL virus" in this situation. But whether or not you are making a derivative work does not have much to do with what bits of technology you use. Of course, the questions are related because choices of technology can make the question about whether you are creating a derivative work more believable on one side than the other. But if you making technology choices in the hope and on the sole basis that it has some impact on whether or not you are creating a derivative work, you are practicing cargo cult law, just the same as if you erase the experimental results table from your paper and hope it changes the gravitational constant. You're reasoning in the wrong direction.
Just as random aside, this is the same kind of thinking that led to the predominance of magnet links instead of torrent files. There are some technical reasons to prefer one over the other, but some people seem to believe there is a legal distinction when there is not. The magnet link is just as legal or illegal as the torrent file it replaces. The question is whether one is engaged in contributory copyright infringement, not whether one does it with URLs or not.