The GPLv2 Goes To Court
Jason Baker writes Despite its importance, the GPLv2 has been the subject of very few court decisions, and virtually all of the most important terms of the GPLv2 have not been interpreted by courts. This lack of court decisions is about to change due to the five interrelated cases arising from a dispute between Versata Software, Inc. and Ameriprise Financial, Inc.. These cases are dealing with four important terms in the GPLv2: 1) What are the remedies for breach of the terms of the GPLv2? 2) What is a "distribution" under the GPLv2 that triggers the obligations under the GPLv2? 3) Does the GPLv2 include a patent license? 4) What type of integration between proprietary code and GPLv2 licensed code will result in creating a "derivative work" and subject such proprietary code to the terms of the GPLv2?
This would have been the perfect story to get covered there....
RMS only commissioned the license. He did not create it. The lawyer that actually drafted the license would likely be a much better "witness" assuming that such things would even be considered in this case.
Amicus briefs are likely the only means of being seen or heard in a case like this.
A Pirate and a Puritan look the same on a balance sheet.
...4) What type of integration between proprietary code and GPLv2 licensed code will result in creating a "derivative work" and subject such proprietary code to the terms of the GPLv2?
It upsets me that this question will be answered by those who [probably] know nothing about software and code. Why won't they ask those who created this GPL? Wouldn't they surely know better?
Versata is essentially a "vulture" company that buys software companies that are down to life-support levels to extract the last bits of value (continuing support contracts, etc.). If you ever see them knocking on your door, find another job ASAP because your company (and your job) is a gonner. Interestingly, one thing that companies do as part of the due diligence when acquiring other companies is determine if there is any open source in the products in order to identify potential liabilities. Btw, companies looking for a buyout often go through a phase to clear out potential open source infringements, so that's a sign if it wasn't clearly spelt out..
I'm guessing that in this case Infosys, a contractor for Ameriprise, probably got paid to develop some software and made it in the form of a library to be used in other contracts. Having outsourced to India before, I was pretty sure that was going on (that and liberal use of open source). After all, rapid development doesn't happen magically.
I wonder if it is possible to create a communication language that has the reproducibility and stability of a programming language. There is hardly even any point in writing out legal rights or documents when everytime it is read it can be interpreted differently. It seems that the law has taken the stance that, since reinterpreting it every time is a hassle and inconsistent, we will just use the interpretation of whoever read it first. But since we have no accurate way of storing legal ideas, how do you interpret the interpretation accurately?
Troll is not a replacement for I disagree.
No, no, no. What they should have done is submitted it to Slashdot and read the posts to find out what the GPL means and what they should do.
I hope you're right. I also hope that the significant amount of published literature discussing the nature of the license can count for enough public comment to deflate arguments that the violator didn't know of any other interpretations of the license beyond their own.
Do not look into laser with remaining eye.
From the Article:
"3. Does the GPLv2 include a patent license?"
No. And THAT is why we have the GPLv3, to head off patent problems (among other things)
RMS only commissioned the license. He did not create it. The lawyer that actually drafted the license would likely be a much better "witness" assuming that such things would even be considered in this case.
Even so, what the lawyers who created the license intended doesn't matter. Or what he was told that the license should achieve, doesn't matter either. The text of the license matters.
software patents are not legal in most parts of the world. so, why should I careas world citizen?
Because if the U.S. legislature and courts make software engineering impractical, your country will end up with a lot of skilled U.S. citizens applying for work visas.
This one is easy - if there's a breach then the license is void and Copyright is the effective law. Code was copied without permission, which becomes a copyright violation, and remedies are already established for that.
GPL is entirely based on the teeth of copyright - almost every OSI license is. If you hate imaginary property then you might question your use of licenses that depend on it.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
RTFA. The whole point of why this one is interesting is that the upstream here--Ximpleware--is suing and claiming damages.