3 ms·
Perhaps this comment comes from a position of ignorance, but what's all this about "risk"? Complying with the GPL is simple. If I understand correctly, VMWare w
by Karunamon 12y ago
Perhaps this comment comes from a position of ignorance, but what's all this about "risk"? Complying with the GPL is simple. If I understand correctly, VMWare wouldn't have been in trouble here if they'd have just put a link in their docs to the effect of "ESX distributes Busybox, the source for which can be downloaded here (link)".
And even if you screw up and forget the link, the lawyers don't descend on you like buzzards - you get tapped on the shoulder and asked to fix it, which is a pretty simple matter too. The lawyers don't come out unless you stall and act in bad faith like VMWare has done.
- danieldk 12y agoIf I understand correctly, VMWare wouldn't have been in trouble here if they'd have just put a link in their docs to the effect of "ESX distributes Busybox, the source for which can be downloaded here (link)". This is about more than Busybox. Their 'vmkernel' proprietary code seems to rely heavily on code from the Linux kernel, up to the point where it may be a derived work: http://sfconservancy.org/linux-compliance/linux-vs-vmkernel_en.png http://sfconservancy.org/linux-compliance/linux-vs-vmkernel_... In other words, their hypervisor could violate the GPL. Of course, that does not change the point. If you want to benefit from GPL-licensed code, you also have to play by the rules. If the rules are never enforced, companies will systematically violate the license, as we've seen with many Android OEMs.
- joshyeager 12y agoThis chain of comments illustrates the reason that companies think the GPL is risky. Even in a highly-technical OSS-friendly community like HN, there are many different interpretations of what the GPL's restrictions actually mean. That uncertainty plus the viral nature of the GPL means that there's no way to know for sure that you won't be forced to open your whole codebase at some point in the future.
- deleted 12y ago[deleted]
- rwmj 12y agoSuppose I grabbed a copy of the sources of NT, and then started modifying it and released a product based on that, without getting licensing from Microsoft. Do you think people would be "oh, this is why using Windows is risky .. there are many different interpretations of what the MSFT license means"? Of course not.
- Karunamon 12y agoThere's a difference between "not having a license" (in which case copyright applies, in which case you lose, simple), and having a license who's terms are ambiguous and not fully legally tested.
- Karunamon 12y agoOkay, thanks for that. I hadn't read too much of the details on this yet. That said, I wonder how this will end up? I lean towards VMWare just putting their big boy pants on and releasing the VMKernel source. Speaking purely subjectively, they don't have any "competitive advantage" to defend anyways.
- johnward 12y agoThe risk that I was speaking of specifically comes into play when you use GPL code along side other proprietary code. Potentially exposing the need to release your proprietary code to comply with the license.