24 ms·
This response still doesn't address the core issue: The Wix mobile App uses GPL code but the rest of the source code of the app has not been made public so far
by weinzierl 10y ago
This response still doesn't address the core issue:
The Wix mobile App uses GPL code but the rest of the source code of the app has not been made public so far as required by the GPL. At least they missed to add a written offer to distribute the source code. If they will publish the source if someone requests it has to be seen.
When it comes to attribution it gets more difficult.
As far as I understand the code from Wordpress is under plain vanilla GPL 2 without any supplements [1], so attribution is not required.
[1] https://github.com/wordpress-mobile/WordPress-Editor-iOS/blob/develop/LICENSE https://github.com/wordpress-mobile/WordPress-Editor-iOS/blo...
EDIT: If anything, this whole controversy shows one thing: Open source licenses (particularly the GPL) are still not widely understood.
(I assume ignorance on WIX's side).
- firasd 10y agoExactly. Regarding "everything we improved there or modified, we submitted back as open source", unfortunately the GPL doesn't let you redistribute code after modifying it while only releasing the modifications. I guess "we will release the app you saw as well" may mean that they'd open source the whole app and thus be compliant, but it's unclear. Also the fact that the company was once also known as "Wixpress" is easy to verify [1], not sure why he would contest that. [1] http://files.shareholder.com/downloads/AMDA-29IDMU/0x0xS1193125-13-387285/1576789/filing.pdf http://files.shareholder.com/downloads/AMDA-29IDMU/0x0xS1193...
- mbesto 10y agoFrom the lead developer: https://medium.com/@talkol/how-i-found-myself-accused-of-stealing-code-from-wordpress-a7350da9f9f2#.wym6nvgmv https://medium.com/@talkol/how-i-found-myself-accused-of-ste... > I know some developers are scared of using GPL, apparently for a pretty good reason. The WordPress GPL Rich Text component in question, is actually a wrapper around another Rich Text component named ZSSRichTextEditor which is licensed MIT. In retrospect it would have been easier to use it directly. https://github.com/nnhubbard/ZSSRichTextEditor https://github.com/nnhubbard/ZSSRichTextEditor https://github.com/wordpress-mobile/WordPress-Editor-iOS https://github.com/wordpress-mobile/WordPress-Editor-iOS So, Wix built a wrapper for a GPL piece of code, which was just a wrapper for a MIT piece of code. According to this tweet[0], the only thing Wix needs to do is to assign a GPL license to their code...but alas IANAL. [0] - https://twitter.com/nitrogen/status/792486850845773824 https://twitter.com/nitrogen/status/792486850845773824 EDIT - From the OP's blog: > When you embed and use GPL code, you have to release the entire thing as GPL. (That’s why it’s called a viral license.) So they need to release not just their changes to the editor, but the entire app that was distributed.
- deleted 10y ago[deleted]
- alanh 10y ago> I’ve spoken to some [WordPress] engineers… They even gave me a WordPress T-Shirt. OK, that sounds like permission to violate the GPL to me! Edited to add: My sarcasm would be dickish if either of these guys from Wix actually addressed the core issue instead of responding with nothing more substantial than “But I thought we were friends!”
- g00gler 10y agoIf he's calling the people who work on WordPress engineers he could probably plead ignorance.
- edsouza 10y agoThe WordPress-Editor-iOS GPL license should be invalid, because it includes the sources from the ZSSRichTextEditor project which is MIT licensed. Which specifically has a clause: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. edit: reading the readme.md in the WordPress-Editor-iOS project, they list the following projects that were used in the codebase: ZSSRichTextEditor (License MIT) CYRTextView (License MIT) HRColorPicker (License BSD) jQuery (License MIT) JS Beautifier (License MIT) Instead of retaining of the licenses for the projects. They removed the licenses, and replace it with the GPL license. IANAL - I think that is not how you re-license someone elses project.
- greglindahl 10y agoThe Apple iOS AppStore effectively prohibits GPLed code. So Wix is in hot water two ways. Clever of the CEO's blog post to not even mention the GPL. "Yes, we did use the WordPress open source library for a minor part of the application (that is the concept of open source right?)" -- ha ha no.
- fred256 10y agoOut of curiosity, why is GPL software prohibited on the app store?
- gruez 10y agoAFAIK it's because all app store apps have proprietary DRM by apple, and since it's built into the app, it would be violating the GPL to distribute the app without also releasing the source code for apple's DRM.
- FireBeyond 10y agoThat seems more pedantry from the FSF than anything else. You are perfectly free to distribute the source code to an app you publish to the App Store. The fact that binary compiled from said source code is digitally signed is ... neither here nor there. By that rationale, PGP signing source code would fall afoul of the same, after all, which is the bit that is compiled - the signed code, or the unsigned code?
- davexunit 10y ago>You are perfectly free to distribute the source code to an app you publish to the App Store. But the GPL states that when a user receives a binary, they may request the complete corresponding source code to that software. That doesn't mean most of the code, minus this proprietary bit that handles DRM.
- Turing_Machine 10y ago
- smallnamespace 10y agoIt's unclear under copyright law whether distributing the bundle of [code that calls GPL'd code + GPL'd code] makes the entire bundle fall under GPL [1]. It's pretty clear that if you modify some GPL'd code, you have to relicense that modified under GPL. It's not clear whether that holds when all you did was call the GPL code for a different product. There're two main possibilities here: 1. The entire bundle is a derived work; under the terms of the GPL, derived works must be copylefted under GPL. This is the FSF's position as stated on their FAQ. 2. Wix's code + the GPL library is a 'mere aggregation', as defined by the license. Their only obligation is to distribute the library itself, along with modifications, under the terms of the GPL, but not their own code. For example, Linux distributions redistribute GPL + non-GPL code together, without making everything GPL. None of these questions have really been tested in the courts. [1] http://www.epiclaw.net/2012/01/31/combining-or-linking-proprietary-software-unmodified-code-licensed-under-gplv2 http://www.epiclaw.net/2012/01/31/combining-or-linking-propr... PS: There's also a third possibility, which is that the whole thing is a derivative work, but calling the library falls under fair use.
- 1024core 10y ago> It's unclear under copyright law whether distributing the bundle of [code that calls GPL'd code + GPL'd code] makes the entire bundle fall under GPL [1]. My recollection was that GPLv3 made it so that if you included any GPL code, you had to opensource the entire. That freaked people out, so there was another GPL, LGPL meant mainly for libraries and other code that is linked into your code, so you won't have to release your code if you just linked against it. Of course, you'd have to release the modifications if you modified the LGPL'ed code to use it in your own. IANAL, etc.
- smallnamespace 10y agoYes, the LGPL explicitly says that you're allowed to link. But the converse, that linking implies a derivative work under GPL, has never been adjudicated in a US court.