IT won't be good for the OSS ecosystem to have thousands of devs all the sudden stop contributing at their day jobs when the code is replaced.
IT won't be good for the OSS ecosystem to have thousands of devs all the sudden stop contributing at their day jobs when the code is replaced.
[citation needed]. I'm very irritated by this FUD "Just think of the jobs!" line of thinking.
Companies are aware of the "license risk" surrounding GPL today. They know what they can and can't do -- services like BlackDuck exist mainly to assess this "license risk".
Any sizable company using GPL is doing so because it helps their bottom line, not because they have their fingers crossed praying that it won't get enforced.
Reading that, I am instantly wondering if you are currently infringing someones copyright and are now working hard to hide the crime?
There is alternatives of course. Are your product a prototype that never got shipped to a customer? Are the product at the moment gpl'ed, witch corresponding source code provided to the customer, and you want to move away to closed source in the future? I know any of the three scenarios could be the situation you are describing.
There is a reason why almost every AAA game now days comes with a long list of licensed works in their credits. The competition is just that impossible to fight if they decide to write their own xml parser, their own font types, their own everything. This will happen to any aspect of the computer industry that has enough competition, so the question about using third-party licensed software, be that of any license, is a simple question about competition.
In fact, I worry that they will feel emboldened when they see how long they can violate the terms without repercussion.
Many CTOs of large enterprises have, let's say, a less nuanced view of the GPL. Their concern is that "just complying" would mean the complete and total revelation of all of their code, all of their trade secrets, and thus all of their competitive advantage. They believe, wrongly, that there are no other ways to come into compliance than to do something they believe would kill their business. Cases like this are accelerants on those flames of Fear, Uncertainty, and Doubt.
If EMC wins the lawsuit, I'd seriously consider never releasing open source code again, and I'm sure many developers would feel similarly. There are many jobs that exist only because of open source. The damage done by EMC winning this lawsuit would be substantial. And for companies who pay for their employees to develop GPL code, you think they're going to be happy if competing companies start absorbing their code into proprietary systems?
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.
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_...
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.
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.
The Conservancy has good people and provides valuable services to the F/OSS community. I trust they've weighed these considerations before deciding to act.
Its not clear how much money, nor clear what damages occurred. How does this usually play out?
It may or may not be; I think its usually seen as a gratuitous license, but I've seen some argument that it is a contract, and which it is may vary by jurisdiction.
> I thought civil suits could only result in money for damages.
This is inaccurate.
> For instance, its not possible to make VMware do anything; just to fine them.
Civil suits can result in orders for specific performance of duties under a contract, they can result in money damages, and they can result in permanent injunctions and other measures that mandate or constrain behavior of the parties. Money damages are the most common thing in civil suits, but not the only possible outcome. (And, of course, the possible outcomes and what the rules are for them all vary by jurisdiction.)
(IANAL) The GPL is a license, which is similar to but different than a contract. It says "you may use my IP under these circumstances (and I can't sue you even if I change my mind)". If one "violates" a license, one is simply using IP without permission. Incorporating GPL'd code contrary to its terms (and with no alternative license from the IP owners) is no different than copying a chapter or three from a book and releasing it as your own.
"license" is an overlapping category to "contract". Some licenses are also contracts, some licenses are gratuitous. Anything that gives the receiver permission to do something that the issuer has the exclusive right to control (such as, in the GPL, the right to do things which are exclusive to the copyright holder under copyright law) is a license, whether something is a contract depends on whether there is offer, acceptance, mutual consideration, etc.
http://sfconservancy.org/linux-compliance/vmware-lawsuit-faq...
Contacts and attempts to resolve this amicably with VMware have been going on since 2012.