triomidwest.blogg.se

1. Mullenweg wordpress wixmullenweg code#
2. Mullenweg wordpress wixmullenweg license#
3. Mullenweg wordpress wixmullenweg professional#
4. Mullenweg wordpress wixmullenweg windows#

but you could be riding a dangerous line.

Mullenweg wordpress wixmullenweg code#

If it's linked, then you also need to post the source code to the Wix mobile app.ĭepends on how it is linked. The question is if the distributed Wix mobile app linked to the GPL code. When one uses terms like "stolen", it is irresponsible to not be explicit about the details. Matt Mullenweg seems to be aware of this repo and yet he insists that there is some additional and unidentified code that is not publicly available. The source for the entire version of their editor is available on GitHub. Wix seems to be in compliance with the GPL. I would call that a pretty explicit case of attribution. Unattributed - The repo is named "wix/WordPress-Editor-Android". Stolen - incorrect and inflammatory verb use. The end result of this was that Apple's customers suffered with a sub par product and the Samba project suffered with fewer people contributing to it. This ended up with developers who would have been working on patches and changes for Samba, instead working on their own closed-source implementation that, quite frankly, was nowhere near as good or as mature as Samba. For a number of years, SMB compatibility and functionality took a huge step backwards on OS X, all because the Samba project started to use GPL v3. Now that no corporation can touch any GPL v3 licensed code, we now have fragmentation and less developers working on open source code bases.Īpple, for example, have had to implement their own SMB stack as smbx, instead of using Samba.

Mullenweg wordpress wixmullenweg professional#

This was good, it meant that we had professional developers who were paid to work on these projects and the changes they made were contributed back upstream. While Apple (as an example) were using GPL v2 licensed code, they were actively contributing patches and changes back to the relevant projects. I feel that the viral licensing clauses in GPL v3 will ultimately hinder the further development of software.

Mullenweg wordpress wixmullenweg windows#

Now, Windows provides an interesting case as it has two types of Dynamic Linking - one which operates identical to the Shared Objects on Linux/Unix, and another that makes a dependency on the associ Focusing on memory space is a misnomer that will not get you very far. Shared Objects (*.so) (dynamic linking) on Linux do not necessarily share the *same* memory space when loaded for use by a program - especially with the Automatic Random Address Loading that has been happening of late to increase security. If, at no point, do the two pieces of code combine into one thing - then it's not a derivative work - just two programs which coexist and copyright does not apply to that. Because once the code shares a memory-space, it becomes part of the same greater whole - and THAT is legally a derivate work. >Whether the memory space is shared is nothing to do with the legal text of the GPL.Īctually it absolutely IS what matters - which is EXACTLY why THAT is where the GPL draws the line - because it's where the LAW and Court Precedent has drawn the line.

Mullenweg wordpress wixmullenweg license#

"If we do, we'll make sure to follow the license you've put on the code very carefully." "Thank you for the offer to use them," Mullenweg responded. Wix had also argued they're giving back to the open source community by listing 224 public projects on their GitHub page. " Mullenweg responded "It appears you and Tal might share a misunderstanding of how the GPL works," ultimately adding "software licensing can be tricky and many people make honest mistakes." "The claim is that the Wix mobile apps distribute GPL code and aren't themselves GPL, so they violate the license," Mullenweg wrote.Ībrahami argued that "Everything we improved there or modified, we submitted back as open source," adding "we will release the app you saw as well.

"Wow, dude I did not even know we were fighting," Wix CEO Avishai Abrahami posted on the company's blog Saturday - responding to Wordpress creator Matt Mullenweg, who on Friday accused Wix of stealing their code.