GPL May Not Work In German Legal System 434
erbse2 writes "It may be that the (L)GPL can not be (fully) enforced under German jurisdiction. This is at least the conclusion professor Gerald Spindler of the jurisprudential faculty of the University of Goettingen came to when he examines the Legal questions of the open source software (It's long, it's complex and it's in German and it's written by a professor, so don't expect to understand anything, if you are not a German lawyer).
Heise News has the article in German, however, the fish may be with you.
IANAL, however, as one can put some of the legal problems aside, most of the concerns mentioned in there should provoke at least some thought by brave men around RMS."
No problem! (Score:5, Funny)
We'd not read it even when it's short, simple and in English, so how hard could it be.
Re:No problem! (Score:5, Interesting)
(from http://www.georgetown.edu/faculty/ballc/oe/pater_
For other examples of Old English text, google is your friend.
In other news (Score:5, Funny)
Re:In other news (Score:5, Informative)
Re:In other news (Score:2, Informative)
Translation (Score:5, Informative)
The Organization of German Software Industries (VSI) considers its view reinforced that using Open-Source-Software leads to jurisdictional uncertainties. On behalf of VSI, Professor Gerald Spindler of the law faculty at the University of Goettingen examined "Jurisdictional Questions of Open Source Software". In more than 100 pages he examines the situation from different perspectives: Author's Rights (Urheberrecht), Usage Rights (Verwertungsrecht), and Liability Rights (??, Haftungsrecht).
Spindler spots jurisdictional uncertainties for all parties involved: Developers may be held liable if software does not work as expected, even if they only participated marginally in the development, rather than being a lead developer. Employers could walk on thin ice if they pay employees for writing Open Source Software. And buyers of such software must be prepared that liability is limited to the criteria common for items given away for free, i.e. severe negligence only.
Although one could argue about one or the other detail of the study, it spells out many problems. The license that is probably most popular for free software, the GPL, is hardly considered to be fully enforceable in the German maze of laws. For VSI, the results are probably most welcome, in order to spread uncertainty among people interested in Open Source, who are currently watching the actions of SCO against IBM eagerly.
Re:Translation (Score:5, Interesting)
Re:Translation (Score:5, Interesting)
Why should the license be fixed? Do idiotic clauses in MS EULAs get fixed based on user feedback? Does Munich decide to buy 14,000 licenses of GPL s/w based on this sponsored study about GPL licensing? Are Germans nuts to believe such propoganda?
For your info, Germany has huge tech giants in IT - SAP, Siemens, SuSE - just to name a few. And ALL of them have stakes in Unix/Linux/OpenSource and cellphone segments.
LinuxTag's protest against SCO was direct and stinging - compare that to the farce in Utah. Advice: Don't mess with Germans - they're known to be merciless and ruthless, despite their appearances.
Re:Translation (Score:3, Funny)
So you're saying they're passive-aggressive? I'm offended.
Re:Translation (Score:3, Funny)
Let me try to keep up: if someone asks whether Martha Stewart might avoid jail time, I'll ask "Did Jeffrey Dahmer avoid jail time?"
Re:Translation (Score:4, Insightful)
Every producer of every product on Earth has some kind of liability. That's not different when producing software. Even if the EULA or the GPL claim otherwise. This problem gets worse with a software that is created by a team of volunteers in 10 countries around the world. Who is liable? Under which laws of which country?
There are a lot of other minor problems in the article. E.g. that you don't need to confirm that you agree to the GPL while installing the software. (That's similiar to unacceptable "with opening this box you agree to the EULA" when the EULA is *in* the box). You simply can't agree to sth. you haven't seen.
Btw., the article doesn't mention, how to fix the license. You'll get what you pay for
Bye egghat.
Re:Translation (Score:5, Insightful)
The only way you are allowed to distribute the application is by agreeing to the GPL. Don't like it? Don't distribute it, but that will not stop you in ANY way from being allowed to use it.
Re:Translation (Score:3, Interesting)
You don't need to agree to the GPL when installing (Score:3, Informative)
There are a lot of other minor problems in the article. E.g. that you don't need to confirm that you agree to the GPL while installing the software. (That's similiar to unacceptable "with opening this box you agree to the EULA" when the EULA is *in* the box). You simply can't agree to sth. you haven't seen.
Don't get confused - the GPL is not a license you agree to when you install it. The GPL (and brethren) ask you to agree to the terms of the license when you distribute the software - normally you woul
Re:You don't need to agree to the GPL when install (Score:3, Informative)
Every producer of every product *has* liabilities. If the software is under the GPL or the EULA doesn't matter. I should have made this clearer.
The question the article now asks is simply: Who is to blame, when something goes terribly wrong. When sth. with SAP goes terribly wrong: Sue them. When somebody distributes virus contaminated software: Sue them. But what, if the Linux kernel contains some backdoor? Blame Linus? Alan? Redhat?
And remember: The article is G
Re:You don't need to agree to the GPL when install (Score:3, Insightful)
I would say you would go after whoever maintains the kernel you were using. Could be AC, could be Linus, could be SuSE, etc. That seems like the most logical answer to that question.
The concept of copylefting for example is difficult under German law (Urherbergesetz). "You own the copyright of everything you produce" is it's basis. That's to protect the producers. Bad for copylefting.
I don't think you understand how copyle
Re:You don't need to agree to the GPL when install (Score:3, Insightful)
A contract is not valid if you don't agree to it, that is for certain. And the GPL itself says:
So, don't agree with the GPL? No problem! You are not forced to accept it in order to use a GNU/Linux system or any other GPLed software.
But bear in mind that most countries have copyright laws, and you will be in
Re:Translation (Score:5, Informative)
They conclude that under German law, the authors liability is most probably limited to intentional damage and gross negligence.
Also, they argue that clause 2 (allowing modifications) and clause 9 ("and any later version") may be problematic. The problem with clause 2 is that modifications of a program may (e.g.) tarnish the reputation of the author, and legally one cannot waive one's right to sue for that (at least in Germany). Also, apparently the author may claim that modifications violate the artistic integrity of her work. However, the analysis foresees problems mainly for works of art, rather than utility programs. Clause 9 is problematic because here the author waives rights for future usage modes that she cannot yet foresee. But licences can only apply to usage modes presently known.
The baseline of problems with the GPL seems to be that in Germany (and, I think, also in other european states), waiving or selling of basic personal rights is usually not possible.
Re:Translation (Score:5, Insightful)
That is, if you cannot apply the GPL, you MUST NOT apply it. As soon as you are without the GPL, you have source code and binaries for something that you are now not allowed to distribute without getting permission from the author, except as allowed by your country's take on fair use.
The GPL is a voluntary license, and you never HAVE to apply it if you don't want to. The fact that, in some legal systems, it may not be possible to apply it in some or all situations, simply means that you have what you are given, and you may not use it in ways that you are not allowed to by law.
The GPL doesn't apply to you unless you want it to.
Don't you think this is a problem, then? (Score:4, Insightful)
What it means is that the GPL is really brittle. Anywhere that any clause of the GPL is invalid, GPL code cannot be distributed. In this specific case, it means that e.g. Linux install parties are illegal in Germany.
Re:Translation (Score:3, Interesting)
Actually, I'm not sure that you can. At the Linux Expo last week that was attached to the "Networks for Business" show I was chatting a a guy from Belgium who sells merch to fund OpenBSD development. One of the things he mentioned was that in many European states a license is only binding if you have signed a paper copy of it. Therefore both the GPL and all those click-wrap/shrinkwrap licenses are not binding (I presume that *BSD &c licenses would similarly be
Re:Translation (Score:2, Interesting)
So this guy is saying that the 'ABSOLUTELY NO WARRANTY' part has no effect in Germany? Gee, I bet that affects way more than just GPLed stuff if true.
Thanks for the translation work, by the way.
Re:Translation (Score:5, Interesting)
If you give something away without compensation, your liability is very limited under German law, anyway. In particular, you can only be held liable in case of gross negligence or premeditation. So, for software authors who just offer their software for download, this is not a problem.
People who sell open source/free software (either written by themselves or someone else) might be held liable to a certain extent. In that, they're no different from people who sell propietary software.
Re:Translation (Score:3, Insightful)
I.e., it may come as a shock to some people from the USA, where the idea is that big corporations make the law and the common man must bend over and pull down the pants whenever some billion dollar company says so... but in Germany, and some other places in Europe, politicians still do so
Re:Translation (Score:5, Insightful)
But the same is valid for all commercial software in Germany too. EULAs have repeatedly been denied validity because of the german contract law. EULAs are a contract between you and the author of the software. But because you didn't buy the software directly from the author, but from a third party (the reseller, the company bundling the software with a computer etc.pp.), EULAs can't be enforced. All the author can impose on you is the priviledges he gains from the Author's Right (Urheberrecht).
This makes software under GPL in no way different than any commercial software you buy in Germany from a liability point of view.
Re:Translation (Score:2)
If there is no contract between the author and the end user, how can the author be liable at all for the performance of the software?
And even if there were some kind of implicit liability, what would it be for? Open source software generally doesn't promise that it will perform any function in particular, so if it destroys someone's computer or data, well, that's just too bad.
GPL allows others to provide warrantees (Score:3, Interesting)
Note that this guarantee does not transfer if the person you sell GPLed software to resells/redistributes it. You get to decide your own terms for your waranties.
SUSE could easily provide a waranty for SUSE Linux that satisfied the mini
Gross Negligence (Score:3, Insightful)
Examining the source code comes under the heading of "due diligence". If an Open Source product breaks, then the negligence is on the part of the user, not the author.
If you read the instructions that come with prop
Re:Translation (Score:3, Interesting)
There are problems wityh the liability exemption in any case. I don't suppose anyone would think that a virus writer could avoid liability for damages by making GPLing their creation, so there have to be *some* limits.
Re:Translation (Score:4, Insightful)
Developers may be held liable if software does not work as expected, even if they only participated marginally in the development
followed by:
And buyers of such software must be prepared that liability is limited to the criteria common for items given away for free, i.e. severe negligence only.
These cannot both be true i.e. it cannot be that OSS developers are liable and yet buyers cannot hold anyone liable.
I think the guy is just trying to point out as many possible legal holes as possible. This is what lawyers do. Put any contract in front of a lawyer and they'll find holes it in. If they couldn't they'd be out of a job.
Re:Translation (Score:2)
And he's talking about Open Source here?? Has Joe ServicePack ever received anything from 'the company where his money ultimately reached' (I don't use seller, vendor, OEM etc. - I know MS dodges behind these things).
So why should JoeServicePack bother at all whether his s/w is Open Source or Closed Source? Do proprietary s/w makers offer any decent su
Have read the 100 pages (Score:3, Informative)
What did it say? Basically it did ask who was liable and who was not liable? From what I gathered, their reasoning is that just because the GPL exists it cannot bypass general AGB rights. AGB rights are general business conditions. Basically AGB says that if you sell me something buggy I have a right to bitch.
Ok first sure GPL has to deal with the AGB, but what about EULA's? Granted the article does not harp on this it could
Re:Translation (Score:2)
good babel quotes (Score:5, Funny)
"Employers could go on thin ice, if they pay coworkers for the letter of open SOURCE often commodity."
"Even if one can argue perhaps over or other detail the study, then she calls many problems nevertheless with the name."
Re:good babel quotes (Score:2)
The article mentions the GPL only at the end and basicly doesn't say anything about it at all...
Actually the claims are just as bad against closed-source as well. Every EULA I have ever read had some 'no-warranty' clause somewhere in it.
Jeroen
Re:good babel quotes (Score:2)
Re:good babel quotes (Score:2)
However I have seen some EULAs and come accross systems that did have it installed and some programs display these kind of things also in their splash screens.
It is always fun to be able to tell somebody they basicly promised their first born to a software company when in an Open vs. Closed discussion
Jeroen
Re:good babel quotes (Score:4, Funny)
Don't worry, the comments below the main text clarifies it a lot:
If thus a damage to a right property third developed , CAN the user cling, if he uses scrap iron and that does not wait. And the manufacturer CAN cling, because he that produced. And/or both beside in vein etc..
finally (Score:4, Funny)
Re:finally (Score:2)
babelfish translation (Score:5, Funny)
Das machine is nicht fur gefingerpoken und mittengrabben. Ist easy
schnappen der springenwerk, blowenfusen und corkenpoppen mit
spitzensparken. Ist nicht fur gewerken by das dummkopfen. Das
rubbernecken sightseeren keepen hands in das pockets. Relaxen und vatch
das blinkenlights!!!
ehh.. I think babelfish has been on the crack pipe again
Re: babelfish is yoda (Score:2)
It's been around for quite some time.
See here [google.com] for many more references.
Translation of page 2 of the study (Score:5, Interesting)
im Auftrag des Verbandes der Softwareindustrie Deutschlands e.V. (VSI) means that the study was paid for by the German association of proprietary software makers.
Re:Translation of page 2 of the study (Score:5, Insightful)
So here you got a list with all things that might go wrong with the GPL in Germany. The same thing could be done with any contract (most contracts are dubious and open for interpretation).
You should thank the opposition (VSI) for giving their money to investigate your contract. Read it wisely and improve where necessary.
Re:Translation of page 2 of the study (Score:3, Interesting)
This study is so self-contradictory that I can hardly see any use beyond spreading FUD. For example, two major conclusions are:
Yes, a court might decide that someone who sells (as opposed to: gives away without compensa
Next study (Score:3, Interesting)
Otherwise this is merely FUD.
that doesn't make much sense (Score:5, Insightful)
This is not surprising, since the study was commissioned by the VSI, an alliance of closed source software development companies, whose members are the usual suspects: Microsoft, Sun, Autodesk, and others. I suspect that if the BSA commissioned something similar in the US, they could find a "legal expert" giving the same kind of opinion.
In any case, if this really is the legal situation in Germany (or any other nation), the logical next step is to fix the laws. There is no reason to leave any legal uncertainty around BSD or GPL-like licenses: they are clearly one valuable and valid way of licensing software, and they are an important component of a free market in software.
Re:that doesn't make much sense (Score:3, Interesting)
Re:that doesn't make much sense (Score:5, Informative)
If you buy and run product X be it linux/windows/aix/????? and it destoys youre data, sleeps with youre cat and sets fire to youre wife then though luck. Sure some special contracts exist wich rememdy this but these are little more then extremely expensive insurance policies such as you could buy from any insurance agency.
But the VSI can't really be blamed for this FUD. Suse is right there in germany stealing their contracts. Damn commies must be stopped or else what did they tear down the wall for!!!! :)
Really europe makes some extremely dence laws, netherlands introduced a .5 to 1 euro tax on dvd recordables, but opensource here is pretty hot. Well compared to the us goverment. Anything to stick it to the yanks!
Re:that doesn't make much sense (Score:3)
It's not clear to me that there is that much of a difference. The US has the DMCA and COPA, plus police confiscations of computer equipment without a trial. German courts stopped SCO's slander with a restraining order. And European antitrust efforts seem a bit more on the ball. On the other ha
Hourra! (Score:5, Funny)
I AM a German lawyer and it is the FIRST article I have understood on Slashdot!
Re:Hourra! (Score:3, Funny)
I AM a German lawyer and it is the FIRST article I have understood on Slashdot!
you insensitive clod!
Please try to post properly, this is Slashdot, you know.
shold be a problem in brazil too... (Score:5, Interesting)
Re:shold be a problem in brazil too... (Score:3, Interesting)
You publish it. You retain copyright, but you grant others a distribution licence.
If what you are saying is true, it would not be possible to publish information of any kind in Brazil. It may not be possible to put information in the public domain. This has nothing to do with the GPL.
In fact, when I was in Brazil there were a great many publications on sale, split 50/50 between porn ( Brazillian women are *so* hot) and normal stuff.... quite a lot of Linux st
WARNING: THIS STUDY IS F.U.D. !!!! (Score:5, Interesting)
He's right, kinda (Score:5, Interesting)
Just read the first few pages (Score:2, Interesting)
All other concerns are about liability which creates the same problems for proprietary software with their more than restrictive EULA.
This obviously an elaborate piece of FUD funded by a proprietary software association headed by Microsoft.
Does this impact SCO vs LinuxTag?? (Score:2)
BTW, does anyone know if the MS EULAs are enforcable in Germany? I guess any Legal System would laugh them out of court.
The responsibility for the product? (Score:5, Interesting)
The conclusion from this study IMHO is that generally software providers should compensate damages that software bugs cause, it should not only be the problem of the Open Source Community. From that point of view commercial licences are equally flawed.
Follow the money (Score:2, Interesting)
"Commissioned by the Association of the Software Industry
in Germany" -- they paid for it, they get to decide the
conclusions.
So it's FUD, in short.
German Alternatives (Score:2)
Maybe someone with knowledge in US and German law can comment on those alternatives from "Kompetenznetzwerk Universitätsverbund MultiMedia NRW"?
So what if GPL is invalid? (Score:2)
A new Linux distro that doesn't provide source? Fine. How many would buy such a thing? How many would pay money to buy a browser now?
A new h/w design / spec that builds on top of Linux, but source not provided. That could be a worry. Wonder if people would flock to buy such a h
IANAL but I'm German (Score:4, Informative)
The only problem is that justice is not a matter of laws and "being right" anymore, actually (thanks to the lawyers) its more a matter of money. And sadly money is the resource that Microsoft has in big ammounts.
How is an open-source developer liable? (Score:3, Insightful)
I'm a little unsure of the details of this (~9 years since I last read any German, so I didn't even try).
But they talk about liability and GPL software *customers*. Since when are people who donwload a GPLed project customers? If you get linux from IBM, say, then you're an IBM customer and IBM shouldn't release products without checking and testing all the code they're selling. But going from that to holding contributing developers liable is ridiculous (even if it is German law).
"This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY"
Re:How is an open-source developer liable? (Score:2)
Take in example a contract about slavery. You can write down anything in there, it's just not valid. Contracts about drugs, etc. etc.
Same goes about warrenty. In example in germany the consumer protection law forbids companies to resign themself from warrenty. (However this only applies to company - consumer contracts, in their application field). private person to private person can buy/sell things excluiding warranty, and compa
Re:How is an open-source developer liable? (Score:2)
Re:How is an open-source developer liable? (Score:2)
However the GPL _is_ a contract, like any license is a contract. However in difference to most other contracts it is not signed or accepted explicitly. Under certain conditions contracts can also be accepted implied.
The famous school example is, you offer me to sell you car for 1.000$, I say I don't know yet, give me a week to think about it. You agree. The next day I tran
Finally... (Score:2, Funny)
Laws change in each country (Score:3, Funny)
The good side is that the MS'EULA may not be legal everywhere too.
And in many years, people from Jupiter, Aldebaran or Coruscant will claim that the GPL and the EULA from MS are both non-sense according to their legal system ("what's this 'intellectual property' crap??!!" will they ask). If they have one.
(The reverse may be true: the Generous Telepathic License from Pluto is probably not legal on Earth.)
interesting point: language (Score:5, Interesting)
That may not matter for US projects put under the GPL and downloaded from US sites, where US law might apply even to German users. But it does matter for GPL'ed software re-distributed within Germany, and in particular for GPL'ed software created inside Germany (KDE?).
VSI intended this study to be a vehicle for putting down free and open source software. But the money they spent on it (it probably wasn't cheap) may actually help German free software efforts sharpening up any legal loose ends. Maybe one should get the BSA and Microsoft to invest in a similar effort in the US--it saves legal expenses for organizations like the FSF.
Re:interesting point: language (Score:2)
Talk about mixed metaphors. I hope they'll tighten them up; sharpened loose ends sound even more dangerous than ordinary loose ends
Re:interesting point: language (Score:3, Interesting)
Well, yes and no. Two parties can agree to a contract in whatever way they like, as long as both parties understand the contract. However if you use standard form contracts (i.e. contracts not individually negotiated by the parties) when doing business with consumers, there are some quite strict regulations, and one of them is that th
Too bad for Germany (Score:2)
I assume the copyrights still hold in Germany.
The study is not about the GPL at all (Score:5, Insightful)
Let us imagine for a second that this is actually a fault in the GPL. Now, what about public domain software (not GPL), such as software freely provided by computer manufacturers, or by individuals or groups. Exactly the same issues apply: writing such software can expose the programmer and company to liability, and using such software means you have to accept that no-one is liable.
Now how about commercial software. Is this any different? No, it can be criticised for exactly the same reasons.
So, it's clear that the so-called study is a misdirection. The GPL is about ownership and freedom, the study is about legal liabilities. No matter who owns the software, the legal liabilities remain shared between the author and the user, as defined by contracts and legislation.
That the study was paid for by a group representing commercial software vendors suggests that the deep pockets of interested parties lie behind it. Why Frankfurt, Germany? Because Germany is at the fore-front of the OSS revolution. (Note that my company has been distributing OSS products since 1997 and a steady 9-10% of all downloads have been from Germany, against 40-50% from the USA and 30-40% from the rest of the world).
The study is bunkum and can be dismissed easily, since taken to its logical conclusion, no-one should write software at all, and no company should use any product whatsoever if they are not able and willing to sue the person making it.
Summary starts on p. 104 (Score:5, Informative)
I don't have a lot of time, but here's my first impression. IANAL, etc., etc. The summary raises three categories of legal problems, involving (1) the copyright holder, (2) contract law, and (3) liability. Actually, it seems to me that everything boils down to the issue of liabiliy: who has to pay if the software is defective in some way. Identifying the copyright holder and clarifying the contract are all means to the end of deciding who has to pay up. Incidentally, the text occasionally mentions open source software in general, but it appears that the only license analyzed in detail is the GPL (at least in the summary).
The section about the copyright holder strikes me as a tremendous struggle with what should be an easy question. Prof. Spindler or whatever says that since so many people may have contributed to the development of GPL'd software, in so many different countries, there may be huge problems identifying the copyright holder. This is the longest and most complicated part of the summary, and I'm not into working it all through right now, especially since I don't see the problem. Isn't this a moot issue with the GPL, since there is always exactly one copyright holder, regardless of who else contributed? That is, if the distributor of GPL'd software elects to include someone else's contribution, they nevertheless distribute it under their own copyright?
There are other issues in this section: if a company pays employees to contribute to GPL'd software, they might not be able to let the company be the copyright holder, because they do it for money, and the GPL allegedly says you can only do this free of charge. (Is that right?) It also raises the problem that the GPL as a business contract (one business allows another to use software under the conditions of the GPL) may be problematic since it's only in English. And that it is difficult to know when the GPL applies to new development, since the criteria for determining whether one software is derivative of another are unclear.
The second part contains what I think is the most critical claim: That the exclusion of warranty and liability in GPL sections 11 and 12 is not valid under German law. Open source software is legally regarded as a gift, and even for gifts, German law requires certain minimal standards of consumer protection, for example against deliberate or gravely negligent defects.
And so in the third section, Prof. Spindler claims that there are liability issues related to open source software, for the aforementioned cases of deliberate or gravely negligent failures of the software. He specifically mentions that distributors may be liable for viruses distributed in the software. Also, third-party-users may have stronger liability claims if they suffer damages caused by GPL'd software. For example, if a provider uses GPL'd software that is used in turn by its customers, and the software has some kind of defect that harms the customers, then the provider itself may be limited with respect to liability claims against the software authors, but the customers might be able to make stronger claims against the provider. "Download centers" or software distributors (such as SuSE, I guess) may be liable for distributing defective open source software. And if a provider or distributor does not hire support or consultants to help them ensure that the software is not defective, they may be exposed to liability claims because they were insufficiently diligent.
As I said, this summary reflects a superficial read-through and I'd be surprised if I've really understood it all. Hope it helps, but don't sue me if my summary/translation is defective. %^)
Re:Summary starts on p. 104 (Score:3, Informative)
It may be that some projects specifically require contributors to assign copyright to a primary point, this is not usually the case. Usually, every contributor holds copyright on the code he submitted.
As a side effect, by the way, t
Other problems with GPL vs. german law (Score:5, Interesting)
As far as I understand, german "Urheberrecht" (not quite the same as copyright, more like "author's right") is basically inalienable. You can't just give away or sell your rights.
One consequence of this is that germans cannot put their software or whatever in the public domain (well, they can, but it would involve dying, and even then it takes some years). Another thing I wonder about is the FSF policy of only accepting patches when the author transfers copyright to the FSF (fun question: why is the GPL not good enough for them?). A german developer cannot meaningfully do that. How can they accept contributions from german developers?
Re:Other problems with GPL vs. german law (Score:3, Interesting)
As far as I understand, german "Urheberrecht" (not quite the same as copyright, more like "author's right") is basically inalienable. You can't just give away or sell your rights.
One consequence of this is that germans cannot put their software or whatever in the public domain
How is this a problem with the GPL?
One consequence of this is that germans cannot put their software or whatever in the public domain (well, they can, but it would involve dying, and even then it takes some years). Another t
Re:Other problems with GPL vs. german law (Score:3, Informative)
Because they want to be able to sue for copyright infringement if someone else violates the GPL. If they own the whole copyright to the whole code, it makes the lawsuit simpler and more painful for the opposition.
Standard legal procedure (Score:4, Funny)
The opinion of one lawyer is worth precisely nothing, unless he's the judge and you haven't got enough money to escalate to a higher court.
Short summary (Score:3, Insightful)
Almost the whole basis of this professors's doubt about the GPL and the LGPL are based on doubts over legal responsibilities (The German word is "Haftung") i.e. who can you sue if your OpenOffice crashes and ruins your document. He makes some vaild points (the only ones I can make out as far as I can see) about the fact that under German law you cannot disclaim legal responsibility for a product you "sell" or provide in the market. He tries to claim that anyone involved in an GPL'ed software can be made responsible for the workings of the software.
What the good professor doesn't mention, but many other people on the Heise forums do mention, is that Microsoft's EULAa suffer from this exact problem in that the EULAs try to free Microsoft from any legal culpability as to the workings of it's software.
I personally think that the GPL should be proven in court. It should be so that it can finally be taken seriously by governments and Professors who get funded by Microsoft (This was indirectly funded by Microsoft) to undermine the GPL.
Misleading summary (Score:3, Informative)
It's safe to assume that this part works worldwide: the right to create a derived work is an exclusive right of the copyright holder, and he can grant that right only if arbitrary conditions are met.
One problem is the no-warrenty clause - such clauses are invalid under some circumstances, for example when the loss if life was caused. I've seen open source software from US companies with an explicit line that use for medical application or life support is not permitted - perhaps there are similar dangers in the US.
Everything else is legalese - which type of contract is the GPL, who are the parties in the contract [does the user have a contract with all authors together, or with each author individually, i.e. thousands of seperate contracts, etc.]? Is an English contract enforcable?
One interesting point is that if someone violates the GPL, then it might be difficult to sue for damages: It may be necessary to name all coauthors for such a lawsuit. But since an individual author can ask for a restraining order, which is sufficient to enforce the GPL, this is not a critical problem.
Re:Actually, the GPL hasn't exactly worked.. (Score:5, Informative)
No, SCO is not challenging the GPL, SCO really has little to do with linux.. it is about two things, one, a contract dispute with IBM, two, ownership of derivatives (they claim that if you write code and license it to SCO for use in SysV, then SCO owns all rights to that code and you cannot take that same code and use it elsewhere).
Re:Actually, the GPL hasn't exactly worked.. (Score:5, Interesting)
Consider the following argument from IBM:
"We have copied code we think is ours into linux, however SCO then also distributed the same code under the GPL. If the code ever was questionable they have granted permission to use it at that moment. And thus set a precedent for more copying"
At that moment SCO would have to kill the GPL in order to have any case (or a substantial case) at all.
Jeroen
Re:Actually, the GPL hasn't exactly worked.. (Score:3, Interesting)
From: http://www.businessweek.com/magazine/content/03_2 7
Re:Actually, the GPL hasn't exactly worked.. (Score:2)
This, of course, means that they don't understand the GPL. Nobody can redistribute GPL'ed software unless it is free and clear of non-GPL'ed intellectual property. The purpose of that clause is exactly to stop this kind of situation, where a company like SCO "latches onto" a successful open sou
Re:Actually, the GPL hasn't exactly worked.. (Score:2)
And while that may be the intent of the GPL, who is going to stop them?
If what I've read is true - I believe that SCO are still distributing Linux from their web site (although not selling it) - and thi
Re:Actually, the GPL hasn't exactly worked.. (Score:3, Insightful)
Not only does SCO have to stop redistributing Linux, so do RedHat, Debian, SuSE, and IBM.
However, the situation hasn't arisen yet: while SCO has made a lot of noise in the PR area, they haven't yet actually demanded licensing fees or made any specific IP claims. So, so far, SCO can continue to distribute Linux, as can anybody else.
Who wou
wth? (Score:3, Insightful)
If federal officials decide that Linux merits the same export controls as Unix, experts fear that could end development of Linux by the open-source community.
What's that all about? Why wouldn't development of the export controlled sections of linux not continue to be developed in a whole bunch of non-US countries?
Comments like that one piss me off...
Re:Actually, the GPL hasn't exactly worked.. (Score:3, Insightful)
The articles that I've seen by people who signed the NDA, suggest all they saw is about 80 lines. Of course, that doesn't mean there couldn't be more than 80 lines in dispute.
I guess how many lines you count, might depend on:
(a) what you're referring to (disputed code or common code)
and (b) whether you count the things which SCO didn't (as far as I know) claim to have developed, but which IBM contributed to Linux, an
I'm still not worried. (Score:3, Funny)
And we have them.
Unless SCO produces a contract signed by Linus in 1990 granting them rights to all future derivatives, they won't even put a dent in Linux.
Re:Actually, the GPL hasn't exactly worked.. (Score:5, Interesting)
How exactly is the retail of the dodgy widget an excuse for the thief?
Re:Actually, the GPL hasn't exactly worked.. (Score:5, Insightful)
But in this case it is not without SCO's knowledge...or atleast they had the opportunity to examine the source before distributing it.
By not doing it (and thus taking a risk) they forfitted the right to complain later. SCO's argument that nobody checks before shipping is nonsense. Just because everybody takes risks does not mean that they don't have to face the consequences of their actions.
Once the first 'widget' gets through the offending company might use your apparent approval as a sign for subsequent 'theft'.
In the case of IBM vs SCO not even the theft has been proven...
Jeroen
Re:Actually, the GPL hasn't exactly worked.. (Score:5, Insightful)
Let's say SCO writes a song. I write a new verse and new vamp for the song. It's a hit. We go on tour together. SCO and I perform the song for years on tour. We sell concert cd's of the song with my verse and music included to our adoring fans. We make money. Suddenly (overtaken by an evil spirit) SCO says, "it's all mine now." Pay me! Or don't sing the song.
In the end, I think it was SCO's responsibilty to know what they were doing with the GPL.
Re:Actually, the GPL hasn't exactly worked.. (Score:3, Insightful)
As far as SCO is concerned - let's consider history of the company:
Let's assume for a moment there is SysV stuff wrongly added to Linux - purely for the purposes of debate:
1. Caldera were a public company company trading in Linux products, not even as an incidental part of the busines, but as the founding reason for the entir
Re:Actually, the GPL hasn't exactly worked.. (Score:3, Insightful)
You didn't finish your (very poor) analogy..
If you discover the subcomponent, then refuse to tell them what it is, and continue selling your 'product' - WITH FULL KNOWLEDGE, and your contract with them states that THIS IS OK, then you don't have a legal leg to stand on - it's not "theft", because you are saying that it's OK.
Re:Actually, the GPL hasn't exactly worked.. (Score:3, Insightful)
Re:Slam SCO, now GPL? (Score:5, Insightful)
Secondly, no court was involved, but a German Professor of Law wrote a study.
And thirdly, the study was commissioned by a trade association of proprietary software companies -- what do you expect? Even without suspecting the author of willful misinterpretation, you can be sure that the sponsor carefully picked somebody who shared their vision or something to that effect.
Re:Slam SCO, now GPL? (Score:3, Insightful)
On the other hand, if your corporation writes some new piece of free software which is contributed to by the public, or which incorporates pre-existing free code, you might be liable for that code which you had no control over; e.g. if there are deliberate backdoors.
No
Re:Slam SCO, now GPL? (Score:5, Informative)
In the US it is very normal that two 'grown up' parties agree to something fair reaching; such as waiving certain rights or liabilties with respect of each other.
In most of (continental) europe that is not quite so easy; and the contract or agreemnt which two parties may have with each other may simply be overclassed by national law or 'common sense' in that respect.
The national law dictates that there are certain minimal levels and that disowning it all is simply not an option.
So regardless of what the developer (dis)claims with respect to warranty; the court may well held him liable to a certain extend.
At the same time, there is also a bright side; those liabilities are generally much more limited and 'capped' than in the US; and hardly ever exceed a small multiple of the resonable sum/economic value of the good (and not what can be done with that good). And they also put very reasonable demands on the 'user'. Willy nilly risking 5 million of lost production on a bit of untested free software is not going to ring true with the judge. He expects (more) resonable caution than generally in the US.
Also note that the scope of damages is very propotional to the purchace/gains of the developer/transaction. Sor 'free' (as in gratis') software those amounts are obviously not going to be very large.
Except if there is a bit more blame; i.e. someone knowingly dropping the ball. And unlike the US, where that waiver is going to help you - it may do little or nothing in most of Europe. Whereas in the US you are fairly secure.
On the other hand - any secondary damages issues are not nearly as much of a problem in europe, and virtually unheard of. Plus bear in mind that cost recovery and legal assistance is on an entirely different level in germany compared to the US. This making the issue of frivolous lawsuits by a megacorp which cripples a small developer virtually unheard of in most of the EU.
So in short; yes - you are bit more open to exposure in Europe - but as long as you behave resonably and are not vandalizing the hight of that exposure is very limited; and proportional to your fairly direct and clear cut gains from that software. And with open source / gratis - that is not going to make you go bust.
Dw