Michigan Diagnostic Software Case Big Win for GPL
Pig Hogger writes "Many people claim that the validity of the GNU Public License has not been tested in court in the US. Well, it just had been, in Michigan, in a case that validated open-source car diagnostic software against the pretension of automakers who want to keep it secret. But don't take my word for it; read the story on GROKLAW." It's actually the Society of Automotive Engineers involved here; DrewTech (the developers in this case) nicely donated half of their settlement money to the SAE.
But remember, the GPL itself is not specifically "tested", per se, because GPL software developers assert them rights granted to them via copyright on an individual basis. This makes it a sometimes long and arduous process to assert rights and/or prove infringement, but hopefully more precedent will help.
s p
r yos-pearpc.html
0 0501.html 0 0503.html 0 0504.html 0 0507.html
l e&id=348
1 78 y os.php
g _id=11116974
g _id=11125509
Since the provisions of the GPL have been upheld in a case in Germany as well, maybe PearPC will be able to more easily defend itself against CherryOS, which has blatantly taken GPL code, without release of source code or attribution, from PearPC and several other GPL projects:
eWeek has a general overview of the situation:
http://www.eweek.com/article2/0,1759,1775386,00.a
Below is a comprehensive collection of evidence, which runs the gamut from CherryOS including original PearPC graphics, extremely unique strings and error messages, debug code from PearPC, the same unique MAC address as PearPC's default network adapter, shared specific functionality, including bugs, and so on:
http://www.ht-technology.com/cherryos-pearpc/cher
http://www.drunkenblog.com/drunkenblog-archives/0
http://www.drunkenblog.com/drunkenblog-archives/0
http://www.drunkenblog.com/drunkenblog-archives/0
http://www.drunkenblog.com/drunkenblog-archives/0
http://starport.dnsalias.net/index.php?show=artic
http://forums.pearpc.net/viewtopic.php?p=16178#16
http://www.tliquest.net/ryan/cherryos/
http://dhost.info/kourge/en/projects/frauds/cherr
Additionally, PearPC project authors are already asserting their rights under the GPL:
http://sourceforge.net/mailarchive/message.php?ms
And a general compilation of some of the evidence so far against CherryOS:
http://sourceforge.net/mailarchive/message.php?ms
I wondered what he was doing these days. Is Mimi still his secretary?
Don't blame Durga. I voted for Centauri.
Unless I'm missing something, this ended in a settlement, not an in court win backed up by a judge.
Wouldn't simply compelling the defendant to release the code with the appropriate acknowledgements be more in line with the community spirit of the GPL? A monetary settlement seems unnecessarily punitive.
"Ask not what your country can do for you." --John F. Kennedy
I wondered why it had gone extremely slow... by the way, the article poster has got it wrong. It's not a victory per se for the GPL as it never went to the finish, the two parties settled instead. However, it is possibly good news for those of us frustrated at companies tying up international standards with submarine patents and other IP trickeries... Microsoft watch out.
Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
Well, the donated half the profits back to SAE (the defendant). Presumably the rest was for court costs/legal fees. If you read TFA, the lawyer for the plaintiff basically states this--the goal was not to win money, but to improve SAE's processes. There was no intent even from the plaintiff to punish.
And how would you propose to deter other companies from stealing GPL code, if their only risk was a little egg on their face and a slap on the wrist?
How would you offset the costs of determining if some code has been stolen, as well as the lawyer/court fees in order to prove it before a judge?
Freediag is stagnant because people have lost interest. If they want to implement new protocols within the 0BD II standard they should pick up Freediag and continue the development. Freediag is almost completely finished the portability portion of it's development. It compiles under most operating systems.
I guess Yay! for GPL being upheld in court. Yay! For independent an DIY auto repair folks. However, bummer for a project that really needs some new blood.
What could possibly go wrong?
a.) The GPL and Linux are not one and the same.
b.) This case did not involve Linux in any way.
c.) It's not even the case that this is a legal victory for GPL. The existance of GPL was found persuasive by this particular defendent in reaching a settlement. It's not a precedent for "more prey."
AFAIK, copyright law does not provide for compelling someone to do anything... other than to pay damages and stop violating the author's copyright.
Besides that, why shouldn't the author's seek monetary damages??? It costs them money to go to court and to force the violator to quit infringing on their rights.
What is in the community spirit of the GPL is something that will help ensure that future violations do not occur. Playing hardball will help that happen. Being "nice" about it will not.
If you don't believe me, ask the RIAA.
Yes, the code was written under the GPL, yes the SAE did then take that code and start selling it as if they had written it and without the GPL, but it seems that the entire process was over whether the SAE owns their own regulations after the government steps in and turns them into Law.
The answer, as it was in the prior case cited, was "no".
It seems that the license of the software involved wasn't related to the case at all, other than as a "starting point" for the case to begin. If the code had been BSD-licensed, they wouldn't have been suing the SAE first. If nothing else, it simply indicates that you can issue a DMCA takedown notice for GPL'd code someone else is using without obeying the GPL license.
If I have been able to see further than others, it is because I bought a pair of binoculars.
"Infringed upon", then, you "pedantic twat".
Without the threat of punitive damages, why would someone pay any attention to the GPL?
History is so yesterday!
As I read this, it's a copyright case only. One side (SAE) claimed rights to code that the other side (DrewTech) had released via GPL. It could have been something proprietary, and SAE would still have lost the case from what I understand.
It's like saying "Axemurderer convicted of killing author of GPL-released code" is a big win for the GPL. It wasn't part of the case, near as I can tell.
William of Ockham had no beard. The most likely explanation is that it was chewed off by squirrels every morning.
You say "stolen" as if the "victim" of the "crime" is deprived of property.
Code can't be "stolen".
Er....no. Sorry, this is the hippie "file sharing is perfectly OK" bullshit that drives me nuts.
You claim taking my code does not deprive me of property. Not so. If I own it, I have the right to license or charge for it. By taking it, you deprive me of the oppoerunity to sell it to you. I have now been deprived the income I would have made from that sale.
So, you claim "Well, I wouldn't have PAID for it, so no harm done." Sorry, still wrong. Assuming that the code in question is something I charge money for, then in taking it you have stolen something of value--the value that others are willing to pay for it. The thief who breaks into a store cannot claim "well, I wouldn't have ever bought that jewelry, so no harm done.
Ah, but code is infinitily copyable--by taking it, I'm not depriving someone else of their ability to use it. With due respect, this is irrelevant. The issue is whether you are using/taking someone else's property without permission. By the "no one is deprived" argument, radio stations would never need to pay license fees to music artists--by playing a song off a CD they own, they're not depriving anyone else of the ability to play the song...
But we're talking about the GPL here; doesn't "stop violating the author's copyright" == "compelled to release code and acknowledge authors"?
"Ask not what your country can do for you." --John F. Kennedy
"If nothing else, it simply indicates that you can issue a DMCA takedown notice for GPL'd code someone else is using without obeying the GPL license."
Somehow, the thought of using the DCMA to defend the GPL just seems highly ironic, as well as downright unclean.
TLR
A man no more knows his destiny than a tea leaf knows the history of the East India Company
There are more than 300,000 pages referring to "gnu public license", and that is just in Google. That is just with quotes, too! One of the links points to a good wikipedia article, as well.
Don't blame Durga. I voted for Centauri.
I think the most interesting point in the article is that the developers won a $75K settlement and then turned right around and donated half of it back to the people from whom they won it. Now that's a class act!
I'm not good in groups. It's difficult to work in a group when you're omnipotent. - Q
Or the plot for "Batman 6".
Don't blame Durga. I voted for Centauri.
By taking it, you deprive me of the oppoerunity to sell it to you. I have now been deprived the income I would have made from that sale.
Iow, you want the government to give you an equal opportunity to make all of the potential sales you can over somebody else's right to do what they want with their purchased property, their computer. Not only are you for affirmative action (ie equal opportunity) but also for taking away real, personal rights over physical property away in favor of virtual, potential rights over information. So in essence you are a neo-liberal libertarian.
Is it still OK to violate RIAA and MPAA copyrights?
"Ask not what your country can do for you." --John F. Kennedy
The infringer could also stop distributing modified versions.
how to invest, a novice's guide
No, stopping distributing copies or derivatives of GPLed works, and possibly destroying extant unlawfully made articles, would suffice.
-- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
Making brash statements like that will get you into trouble, mon ami. Especially in places like this one.
Results 1 - 10 of about 453,000 for GNU Public Licence. (0.33 seconds)
"God of Rock, thank you for this chance to kick ass. "
Eric Grimm, lawyer for DrewTech: "..the only real ruling that has been made in the case is a discovery ruling by Magistrate Judge Paul Komives, permitting DrewTech to take the deposition of a third-party witness."
It's certianly a win for the GPL: the judge refused to grant summary judgement, and the settlement clearly showed that they were afraid of the GPL.
But it is not a judge ruling "yes, this license is valid and binding". Indeed, it's not a judge ruling anything.
No. That is more than would be required of the defendant to stop violating the copyright. To stop violating the copyright, he can simply stop distributing the material. Releasing his own code (which he has based on GPLed code) might be an option the defendant would have, but it is not something he can be forced to do.
If somebody distributes a binary program with no source, how is anyone supposed to tell if they just linked to a library versus incorporated the original GPL'd source into theirs? If all you have is the executable machine code, I'm not sure you could tell the difference.
Similarly, allowing library linkage to be a valid way to bypass the GPL would just result in everybody putting existing GPL sources into a "library structure" and linking in. Congrats, you'd have a way to completely de-tooth the GPL.
Using a library is just an organizational technique that keeps an individual source file from becoming too large. You can pre-compile a library to keep your compile times down. The net effect is that you're bolting the library onto your project, and you're deriving benefit from that linkage. If you don't want the GPL baggage, don't expect to get any free benefit from GPL'd works, either. You're perfectly welcome to develop the code yourself. Nobody requires you to use GPL'd code.
Point 6a describes other ways of complying with the LGPL, which also don't have to involve GPL'ing your work, or giving people source code, or whatever.
Village idiot in some extremely smart villages.
"Ah, but code is infinitily copyable--by taking it, I'm not depriving someone else of their ability to use it. With due respect, this is irrelevant. The issue is whether you are using/taking someone else's property without permission."
You are confusing terms, though. You are using the word "stolen" which implies that you no longer have said item. "Unauthorized copying" more accurately describes the offense, not "stealing". Your examples show that you are confused as to the differences as well.
Making unauthorized copies is illegal. Some people also believe it is immoral. Using the term "stealing" to describe it is simply denying reality.
Also remember that the purpose of copyrights is NOT for the authors, but for the public. Copyright IS NOT a "right" of itself, but an artificial one given by the public for the public's benefit. That doesn't mean that people can decide for themselves to break that trust, but it does mean that you are dealing with something that is in an entirely different ballpark than stealing.
Engineering and the Ultimate
This case mentions that any work incorporated into law by reference can not maintain its copyright. It's happened before (the building code case mentioned) where an existing work became law, so the original authors could not charge others or claim infringement for printing (what was previously) their material. Now shouldn't the same logic apply to patents? If someone patents some algorithm that is incorporated into MPEG, and MPEG is legislated as the standard for HDTV, shouldn't that invalidate any patent claims over the algorithm the same way copyright is over-ridden? Or is this another way patents are different from copyrights?
I have now been deprived the income I would have made from that sale.
You wrongly assume that a developer interested in the functionality you are selling would buy it rather then code it themselves.
Just like in the music world; if people MUST pay to listen to something and thats the ONLY way to hear it, alot of people would just opt not to hear it. How is that a lost sale?
No, it does not.
Copyright law for infringing or derivative works only allows for the original author to affect distribution of the infringing work, or demand damages. Specifically, you can force someone to stop distributing a piece that infringes on your own, but you cannot claim ownership of their work, nor force them to continue distribution against their will.
The GPL, specifically, is a list of terms and conditions upon which you are allowed to distribute programs made from GPLed source code. Should you violate these, you are infringing upon the copyrights of the code's authors. Ergo, the authors can then sue for damages and/or an injunction against distribution.
However, it is unlikely that a judge will enforce the GPL terms (by compelling to release source) rather than sticking to straight-up copyright infringement/license violation. This is where monetary damages are most effective - by offering to reduce the punitive damages of a suit in exchange for the release of source code, the company can be 'encouraged' to comply. Furthermore, a successful punitive damages suit discourages other companies from allowing GPL violations to proceed to legal action - allowing the FSF to get them in compliance by simple nastygrams instead of expensive lawsuits.
In short - yes, monetary damages are damned well neccessary.
Do radio stations pay license fees to music artists? I didn't think they did. (We sure as hell didn't in college radio.)
Pax -- Ob
"Many people claim that the validity of the GNU Public License has not been tested in court in the US. "
...
Many people are not lawyer and are have no clue what the GPL is all about and what its real power are. Most people dont even know what law are in effect in the US.
The Best worldwide Law Teachers and Freedom Lawyer drafted the GPL , once the acusee get a simple explanation from a judge as to the possible effect of a penalty one might occurs from losing such a case they ALL settle.
It dont mather that they ALL settle because "Many people" said its untested in court.
And its going to be like this until there is actually one dumb enough to go all the way and loose.
"Journalist" and "reporter" used to ask question to the one who lost like I dont know : "why did you setlle ?"
That would be news worthy. I dont pay people for the fun of it , I guess they dont either
"radio stations would never need to pay license fees to music artists--by playing a song off a CD they own, they're not depriving anyone else of the ability to play the song"
Circular reasoning.
You might say that you have rights to your intellectual property. Other people disagree. Fortunately (for you), for now, the courts agree with you. Don't confuse that with a natural right.
I don't agree that depriving you of a potential sale is, in any way, theft. Would I be stealing from you if I told your potential customers that your software didn't work, and that they shouldn't buy it? Should I go to jail if I did that?
Why yes, I AM a rocket scientist!
"The GNU has grown [strong] teeth!" is more appropriate. When the GPL came out linux didn't even exist.
You make a good point. With a static link (as I was assuming,) the two pieces are bound together. With a dynamic link, you could distribute your proprietary code and have the end-user obtain the GPL library and do the final linkage. I would expect that you could distribute the dynamicaly-linked library along with the proprietary code, as long as the two pieces are distinct and separate. Hell, you could perform a sort of dynamic link using a shell script, and that structure doesn't propagate the GPL between programs.
If they settle, it's not a win, it's a settlement. Does not set a very useful precedent, however correct the settlement appears to be.
Until it is tried, adjudicated, and upheld, the original statement stands. At best, the GPL has been tested, but not proven.
Get your facts straight. This headline is deceptive and wrong.
http://drteknikal.blogspot.com/
...to stipulate ejecting the individual SAE members who decided that stealing the code was a good idea, and the individual SAE members who counterclaimed against the GPL software.
such people should be punished, not rewarded for their idiocy. ejecting them from the SAE would be an appropriate punishment imo.
imo that is the best way to "improve the SAE". not contributing money so they can continue more of the same.
Why does every groklaw article that shows up here rub me the wrong way ... even when I always seem to be on their ideological side of the fence.
Now there is a case in Michigan, which just settled, where the GPL not only stood its ground, it came off victorious, and this time it was very much a part of the case.
IANAL (and neither is groklaw) but how can a settlement be considered a test of the GPL or even a victory? Unless their intent is to spin the result which doesn't do anyone any good. So why are they trying to do it?
Speak truth to power.
From the article:
you had the SAE, the standards body which publishes the standards, which essentially tried to claim copyright on the software and intended to charge DrewTech thousands per year to use the very software DrewTech employees had written and released under the GPL. [emphasis mine]
Nothing says greed like charging someone else for the right to use his own work.
The problem with the patent system is not that it rewards the inventor - that's fine - but that it also allows a lazy but devious patent applicant to make a profit at the expense of those who actually implement the design in question. Nothing could be closer to communism, in spite of what Microsoft and others might say.
In fact, if one really thinks about it, patents are probably the most anti-capitalist, anti-freedom, anti-progress part of our Constitution. They are the equivalent of economic terrorism - patent liability can strike any business, anywhere, with devastating effect.
Ok, I know it's kind of trollish to equate patents with terrorism, but at least it provides a way of explaining the situation to the average, non-technical person. They'll at least understand the appeal to terrorism (**GASP!! THE HORROR!!**).
The society for a thought-free internet welcomes you.
What morons would donate half their settlement back to the company that gave it to them, even if they do get it as a tax write off?
If you need the tax writeoff, you can donate it somewhere else. The SAE, being part of the automotive conglomerate, tried to fuck these developers, they got busted, and the developers just rolled over and LET THE SAE fuck them.
Some charitable good will, to say "oh, we caught you this time, now you'd better be more careful stealing other people's shit"???
Here I thought code people were generally the smarter of the bunch... *wtf*
"Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
Now that people are using copyright law to protect ownership of GPL source code, people can no longer in the next breath defend copyright infringement on P2P networks.
If you use intellectual property and copyright law to defend the GPL and go after infringers, then there is nothing wrong with the RIAA protecting its intellectual property using copyright law and going after infringers.
It's not a lost sale if people don't hear it. It is a lost sale when they download it and do hear it, regardless of the bullshit "I wouldn't have bought it anyway" argument. You might not have bought it, but you still listened to it anyway.
kurzweil_freak
5th Kyu Genbukan Ninpo/KJJR student
Be the darkness that allows the light to shine.
We've covered this! Were you not paying attention?
/. groupmind takes that are contradictory, but this isn't one of them. Start scouring the board for a better one.
We like freedom of information. The GPL improves it, traditional copyright restricts it.
There are lots of positions the
Actually in this case "deprivation of property" was present. This wasn't a simple case of some kid sharing his copy of of the black album. SAE was trying to assert ownership over code that someone else had written and then CHARGE THEM THOUSANDS OF DOLLARS FOR IT.
This bears much more resemblance to the SCO case than to any swap kiddie.
A Pirate and a Puritan look the same on a balance sheet.
You don't see a contradiction here?
1.) Copyright infringement on P2P networks is okay. It's not theft.
2.) Copyright infringement of GPL source code is not okay. It's theft.
Just repeating that the GPL improves freedom isn't really saying anything other than RMS propaganda. There are real issues here revolving around the usage restrictions of intellectual property. If the discussion is to ever go anywhere, there needs to be a rational starting point.
But remember, the GPL itself is not specifically "tested", per se, because GPL software developers assert them rights granted to them via copyright on an individual basis.
Also: As I read it GPL wasn't strictly at issue here. The core issue was whether a standards organization can claim IP rights over the standard itself when that standard is embodied as code. Once that issue was clearly articulated both parties seemed to take the enforcability of the terms of the GPL as a given.
What is important here is that it was the terms of the GPL that allwed Drew Technologies to haul the SAE into court, claim damages from them, and get them to settle WITH a payment of damages.
The SAE had posted Drew Tech's code, claiming they owned the copyright because it was derivitive of the standard and demanding a "subscription fee" from both Drew Tech and from all other users of Drew Tech's GPLed code.
The GPL violation was the hook Drew Tech chose to file a takedown demand, drag the SAE into court, and demand damages for violation of THEIR copyrights - like any other GPL software provider. B-)
Even in the absense of an actual decision, this case shows that licensing your code under the GPL doesn't jepoardize your ability to haul offenders into court and claim (and get settlements for) damages for violating your license terms.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
[...] this case shows that licensing your code under the GPL doesn't jepoardize your ability to haul offenders into court and claim (and get settlements for) damages for violating your license terms.
In fact it may enhance this ability, by lowering the threshod for claiming damages.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
I thought that one of the important things to come out of the case was this:
:-) ])
The doctrine is now enshrined in 17 U.S.C. 102(b). The relevant section says:
(b) In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.
A lot of people think that their ideas, procedures, processes, etc... are (or can be) protected by copyright. The answer here is - no. They can not be protected by copyright. These are protected by patents.
Tangibles => copyrights
Intanigbles => patents
(I don't know about anyone else, but I do get a lot of questions on this when friends/relatives/and other stranger persons ask me about copyrights. And no, IANAL! I just like to read about the law. [Surprised my own lawyer by how much I knew about the law.
Someone put a black hole in my pocket and now I'm broke.
really - whether this was a settlement or a judgement, it really has nothing to do with "testing" the GPL.
1. some people (Drew) wrote some software that complied to (implemented) a standard.
2. the standard is copyrighted by someone else, the SAE (the issue of whether they can copyright or charge royalties on something that's part of the law I think is a side issue).
3. SAE tried to claim ownership of the copyright of the software, claiming it was a "deriviative work" of the standard.
4. they were unsuccessful in doing so, the core reason being because copyright only covers a particular composition of text, not the "ideas, procedures, processes, methods of operation, concepts, principles, or discoveries," that may be described, explained, illustrated, or embodied" within it. if I write a book explaining how to turn lead into gold, you can't copy the sentences and paragraphs I wrote. but you can certainly write your own book explaining the same procedure. this is a long-standing principle, and no new legal ground was broken here - no precedents.
5. Drew was confirmed as the legal copyright owners of their software, not the SAE, which was what the case was about.
6. Drew (had) happened to release the code under the GPL. This is an expression of how they wish to excercise their copyrights. But nothing about the GPL was tested or decided. Only that Drew owns the copyright, which allows them to release it under GPL, and SAE cannot prevent them from doing that because SAE does not own the copyright because it is not a derivative of SAE's copyrighted work.
the validity and terms of the GPL never entered into it. talk about a "victory for the GPL" is nonsense.
Suppose we take the proposition: The 28 year limit on copyright was the last form of the law that should be recognized - the Supreme court was wrong in ruling that the phrase in the Constitution "for a limited time" meant anything up to 1 day short of eternity.
then:
1a.) Copyright infringment of works under 28 years old on P2P networks is not OK.
1b.) It's not necessarily theft either, but its not OK.
2a.) Copyright infringment of works over 28 years old on P2P networks is OK.
2b.) (Corrolary derived from another proposition below) - If it should be legal, then it's definitely not theft, (as no form of theft should be legal).
2c.) (Corrolary derived from another proposition below) - If it is theft, then that trumps the 28 year expiration rule and violates one of our first premises, (as no form of theft should have an expiration date, after which it stops being theft).
2d.) If it is theft, then that also trumps the current life +70 rule (by analogy with 2c.))
3a.) Copyright infringment of GPL code is not OK, simply because it's under all under 28 years old.
3b.) It's not necessarily theft, but again it's not OK.
I don't actually support taking just that point as the whole basis for copyright law, and yet I can come up with related arguements from other premises that lead to other such conclusions - you are aware that you stated four propositions with just two numbers there, aren't you? Leaves you wide open.
We could start with the premise that the 56 year version of the law was valid, although now that some forms of copyright violation are criminal, the changes in requiring registration in that law look like they make it a case of taking without compensation from the taxpayers to me (but IANAL). We could start from a later version, although ex-post-facto arguements are being ignored there (again in my NAL opinion). We could start from a given fair use definition, and come to one conclusion or another. Personally, I favor a fair use definition that recognizes both time and space shifting rights, and some forms of hardware agnosticism.
Who is John Cabal?
You claim taking my code does not deprive me of property.
NO - listen to what people are saying. They're saying that "copying" and "taking" are two different things. "taking" implies a transfer of a single object - wrong for TWO reaons - one being that a person got the fruits of your labor without your permission, and another, totally unrelated reason, being that you had you've been deprived of your property unfairly. So "taking" implies the dual problem of freeloading AND deprivation of your property. What happens when someone copies is just one half of that picture.
If deprivation does not occur, then "taking" also does not occur. The words were invented long before the technology to make quick instant perfect copies of things was available. So the distinction didn't matter before. Now it does, and the cartels are using the old connotations of the terms to their advantage - trying to make people associate file copying with that feeling of having been deprived of property that is associated with theft.
Does this condone the behavior of the copyright violators swapping files - no, actually. I agree that that's wrong. I just disagree that it should be prosecuted as theft. It's not. It's a brand new kind of crime, one that is mild but has large consequences when done in bulk. And if the law and the cartels insist upon prosecuting it as a larger crime than it is, then nobody will ever respect them, take the problem seriously, and stop doing it. They mock the law because they know it's wrong. And they're right.
Copyright violation is not theft, any more so than jaywalking is murder. Don't punish a minor crime with a major crime's sentencing.
Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.
That's the General Public License.
"A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
I see this as a major screw-up for SAE. They should have had these ideas patented rather than copyrighted. Had they done so, the case would have been addressed in a completely different way.
Of course I haven't read the software source in question, nor the works from which the software was to have been a derivative work... though if I understand it correctly, the software isn't a derivative work from software but from some form of published standard... a protocol or format. This, more or less, falls under the realm of patents if I am not mistaken.
Is this a real test of the GPL? Did the judge issue a ruling that the GPL holds precedence over SAE's claims? From what I read in TFA, SAE agreed to drop the case against DrewTech. This would imply that the judge didn't issue a ruling -- hence an out-of-court settlement.
While this case did gain a judge's audience, I am unclear about how, if the case was dropped, this is a documentable win for the GPL. I'd like it to be, but is it really?
It doesn't lower any threshold, this case was settled and therefore sets no precedent.
I see you still don't 'get' it regarding the GPL. So let one of those freaks you refer to attempt to enlighten you.
When those GPL'd libraries are linked in, staticly or dynamicly at runtime, you are still making use of code that bears a GPL license. If your code that wants to use that GPL licensed code as part of its functionality isn't GPL also, then the linking is, and properly so, a violation of the GPL and illegal by copyright law.
There is no 'slightly pregnant' here. If you want to use GPL'd code, then your code must be likewise GPL'd or under an approved similar license. End of discussion.
Gawd I wish some dummy would actually let this get to where the judge renders his/her opinion for public record and let the precedent actually be set instead of saveing a few on attorneys fees with a settlement when they realise that tweaking the GPL tigers tail is going to get them eaten.
You're right about one thing, these decisions really are quite obvious. Oh, and go learn how to spell license too. There are in fact several ways, but yours is not among them in my dictionary.
--
Cheers, gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.34% setiathome rank, not too shabby for a WV hillbilly
Yes.
Sure, but does any of the pages contain a hint that a "GNU Public Licence" actually exists?
I know what the GNU General Public License is. Follow the link in my sig, and you'll see that I've used it myself for years. The article, however, talks about a "GNU Public License".
It doesn't lower any threshold, this case was settled and therefore sets no precedent.
I didn't say that the CASE may lower a threshold. I said that USING the GPL may lower a threshold.
When part of your payment is intangible fallout from your open source distribution it may take less action by the infringer (or an action he's more likely to take) to produce damages a court would recognize than it would, say, in the case of a proprietary program.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
was copyright instituted as a privilege in the first place?
Instead of just making a few conjectures based on guesses and a narrow perspective on the topic, I suggest you make some research on your own. That way, you'll bring something to the table.
The question isn't what use there is for novels. The question is what use is there for copyright. Historically, ever since Baldesar Castiglione and before, books had been re-typeset, distributed, translated and been entirely free game for anyone willing to make a quick buck. This often resulted in a bastardization of the work in question, questions about who was the original author and how the work should be presented to the world.
Books were more labour-intensive back then. The typesetting, printing, binding, as well as the production of paper all involved a relatively much higher investment. I have always seen copyright as the right to choose how the child of one's mind will be seen, as the blame w.r.t. corrupted derivatives will surely fall on the author. What is just as sure is that economic forces will favour those who do shoddy work to underbid the original author.
Copyright is about the rights of one person to distribute his own work in the manner he sees fit. Traditionally, it has served a vital role in ensuring a clarity in the common European discourse on academic topics. The economic implications were originally merely secondary, yet as the lowest tend to rule where a common understanding and ideal is lacking, it is nowadays seen as the main reason for copyright.
This is why I can but be ambivalent on the matter of copyright today. Seeing how the recording industry treats those that wish to be artists, how the publishing industry uses college text books as cash cows, and how the movie and advertisement industries have joined forces to warp common sense to promote lifestyles and the associated spending habits, I cannot endorse what copyright has become. Yet doing away with it altogether would open up the gates for the same sort of injustices that originally produced the necessity for it -- on a much larger scale, and at an infinitely greater pace.
Unfortunately, this is an area of discussion that cannot be open, as there are far too many economic interests involved. That in itself is a sign the copyright laws have failed, as the artistic concerns and the concept of credit where credit is due are only secondary in the debate.
And whoosh, there goes the joke.
The "GNU public license" does not exist, references on google are mistakes.
GPL
The problem was that SAE claimed ownership of the software as a derivitive work (even though they didn't write it).
Also, and this is the killer part here, SAE tried to distribute the software in violation of the terms of the GPL, including not redistributing the source code, claiming to own the software under a propritary license arrangement, and violating section 7 of the GPL, which dumps the GPL license altogether and prohibits distribution of the software under any means what so ever.
In essense, this really is a test of section 7 of the GPL, and by doing what SAE did on their website, they violated this portion of the GPL and hence it turned into a simple unauthorized distribution of copyrighted material subject to normal copyright penalties.
The rest is muddled into arguments over actual ownership of the copyright, but that was quite clear in this case, and even if it turned out that SAE would "own" the software via derivitive works theory, they still wouldn't be able to distribute the software, and were in willful violation of the copyright laws. Had this been the case, the GPL would have been a much bigger factor, but instead the court ruled that software can't be considered a derivitive work based only on figures and standards from another document.
Too bad this only applies in the state of Michigan, as this sort of ruling does have national significance. It is legal precedence, however, and can be used to bolster an argument in other courts in the USA for similar cases.
Please explain how its a bullshit arguement. Its not possible that someone would put effort into downloading but not be willing to pay for it?
Just because someone isn't willing to buy doesn't mean they aren't willing to use it for free. Hence, its not a lost sale.
"However if you are going to distribute the GPL code, you must follow the licience, that is, any GPL or derivative code you distribute or copy must be licienced with compatibility to GPL."
I don't like that they do it, or did it, but isn't that how nvidia got around the GPL vs. binary drivers?
They did not actually distribute any GPLed code. So, losing the right to distribute GPL code that they did not distribute in any case was not a problem. Am I remembering this correctly?
all the best,
drew
FreeMusicPush If you want to see more Free Music made, listen to Free
"My point is, using code is not the same as making a derivative of it, and thus the GPL does not (and should not) prevent me from using GPL libraries in non-GPL code."
So your point is that in the case libraries licensed "Copyright 2005 Foo Nanki, all rights reserved" you are free to link to them and not pay or whatever and everything is cool as it relates to copyright law? If not, please explain the difference as you see it.
all the best,
drew
FreeMusicPush If you want to see more Free Music made, listen to Free
Comment removed based on user account deletion
By taking it, you deprive me of the oppoerunity to sell it to you.
There are many people who want to sell me things, and many ways I can deprive them of the opportunity to do so. Most of those ways are legal, but even the ones which aren't legal are still not always theft.
For example, sneaking into a movie theater deprives them the chance to sell me a ticket, but isn't theft. It's trespassing. Calling it theft sounds idiotic, as if you can only concieve of one word for all possible crimes. "Help, police, there's a thief! He lit my house on fire!!"
The issue is whether you are using/taking someone else's property without permission.
If you think that's the issue, then say "using/taking" and not "stealing", and don't complain when people don't want to use "stealing".
It's like if there is a debate about abortion of human fetuses, and one side says "We shouldn't allow the murder of babies". It's completely correct for their opponents to dispute the use of those words- because accepting them would mean acquising to defeat. If the "pro-life" guys can trick the "pro-choice" debater into saying "Somtimes it should be legal to murder an unborn baby", they've won the PR battle.
The wrongness of abortion / copyright-infringement is a separate question from the wrongness of murder / theft. By attempting to use the latter severe terms for the former, separate actions, you attempt to prevent having a rational debate at all.
"Copyright infringment is theft" is just as dishonest a bumper-sticker sentiment as "abortion is murder"
Do radio stations pay license fees to music artists? I didn't think they did.
Yes, but it's done in bulk. The station pays a single lump fee to the music publishing association, which then splits it up amoung all the musicians according to their popularity percentage. (So your little indie-rock jam tapes can pay the billboard top 40)
Asking the DJs to write down each song played might be fairer, but its a whole lot of work. Probably whoever owned your transmitter handled that fee already, and you DJs never even had to be told of it.
Sig: Playgirl editor Michele Zipp was recently fired for being Republican.
In related news, Republican Michele Zipp was recently fired for being a pornographer.
(And in light of that, it's more plausible that she was fired from Playgirl for being a gargantuan hypocrite, a characteristic inherent in any Republican smut-peddler)
Suppose we take the proposition:
You are expending far too much intellectual energy on someone who's proven herself not to be worth it. The only productive effect of a post there can be denying bonch the "last word", but since she won't care what it says (or even really read it), that could've been accomplished much more easily with 2 lines of quasi-witticisms.
To answer you, it's a bullshit argument because on one hand you're saying that (insert noun here) has no value or worth, and then turning right around to say it's worth using. Sure, it's possible that someone would put effort into downloading it but not be willing to pay for it; I would call that person a hypocrit and an asshole. But that's just me, obviously there's a whole world of people out there who don't give a fuck about anyone but themselves. Bravo.
I would think that with as many people on /. bitching about corporations, lawmakers, and scientists, saying "just because you CAN, have you stopped to think if you SHOULD?" that they would have the balls to apply that to themselves. Then again, this is teh slashdot...
kurzweil_freak
5th Kyu Genbukan Ninpo/KJJR student
Be the darkness that allows the light to shine.
You're a real piece of work. I've read all your anonymous posts in this article. It really isn't any different than before which is the disappointing part. It must suck not having enough influence to make the waves you'd really like to.
Tell us, what will you do with the power you so richly desire once you get it.. if you get it? Strike down all those that mocked you on pissy little blogs like slashdot? You can do better than that.Go after the ones that are really laughing at you from up above. Aim higher and test your mettle.
Speak truth to power.
I'm still waiting for the case (in the USA) where an independent developer goes after some company that took his GPL code and is then forced (by court ruling) to open up their whole app or stop using the code. Then Ballmer, SCO, et al can shut up.
When you look at the state of the world, how can you not become a radical, liberal anarchist?
It depends on the company. Some want to be known for their code, some want it all to be of a proprietary nature. For the latter: Let them fear the GPL. If they can't understand it (which usually means they're unwilling to read it), then they shouldn't touch it, and instead they should be spending their own time/money creating their own code from scratch or using code of licenses they prefer.
A strawman of my own: I don't think we'd want a situation where they used GPL code, their code was forced open, and then it was later found that more code they'd used without authorization got comingled with other GPL-based projects. Not every use of OSS should be encouraged.
Copyrights, Patents, Trademarks: temporary loans from the Public Domain, not real property ("intellectual" or otherwise)
Self-Addressed Envelope?
First, let me say that this is far from any area of expertise I may have.
"Now in essence there are two methods of including it in a program: distinction or inclusion."
I am not sure what you are trying to say here.
"Now if my code is distinct from the other code, I could distribute it without the GPL code. Even if it does not work without those, I own the copyright to the code, and so I can do what I want with it."
Yes, and you could also distribute it without the Foo code too. Right? However, would you lose your rights to distribute the gpl code in question if you did this?
"If I mix my distinct code with the library with the GPL licence needed to run it, there is no conflict. Both are seperate entities. Dependence does not make derivative. The owner of the GPL code has no grounds for complaint.
If however I created the same mix with the Foo library, then I am distributing copyrighted works without a licience and it is infingement (or theft or piracy or murder depending on how silly we wish to be with the argument)."
Let's take these two together. If you are correct re the gpl and the "all rights reserved" cases. It would simply mean that the gpl would need to be reworded to fix the issue. Imagine a line starting at public domain and ending at "all rights reserved" - the gpl falls somewhere on that line. It would just need to move a little further towards the "all rights reserved" end and the issue could be resolved in favour of the gpl rights holders' wishes. (gpl license designers wishes?)
For instance, suppose some text like the following was added to the end of hte gpl license:
"You may not distribute this code if you also distribute code which links to this code and that code is not licensed under this license."
Would that do it in your mind?"
all the best,
drew
FreeMusicPush If you want to see more Free Music made, listen to Free
Comment removed based on user account deletion
Not at all. Copyright law is supposed to promote the "progress of the useful arts and sciences"[1]. Better, it is supposed to increase the amount of art produced (benefiting the people) by making it possible for artists to make a living off their works (benefiting the artists). It can hurt the people if it is made longer than it needs to be to get the artists to create.
No where in here do publishers matter. If every time something is created, everyone gets it free through p2p, then people can't make a living off creating art in the way they're used to. That may or may not be a bad thing, but it is a fundamental change. Perhaps we would switch from having a creative class to a distributed system where everyone creates?
This post written under Gentoo-linux with an SCO IP license.
[1] US constitution, I.8.8
This post written under Gentoo-linux with an SCO IP license.
you are still making use of code that bears a GPL license.
Irrelevant. "Making use" of GPL code has no relation to the GPL license. In fact, that license specifically says that people can use the supplied program without even agreeing to the license. The GPL only covers copying, modified copying, and distribution.
There is no 'slightly pregnant' here
Yes there is. This area is highly ambiguous, although it has nothing really do to with the GPL itself, and everything to do with the copyright law that gives the GPL its teeth.
Is "linking" to a program or piece of data an act of copyright infringement? Well, copyright law covers "reproduction" and "distribution", and by linking to an external library (or website) my program (or web page) neither reproduces nor distributes... so it doesn't infringe copyright in the straightfoward sense. There may be ways to stretch it to fit though, such as by arguing that the function name or URL used to accomplish the link was itself an item protected by copyright, and thus making the link was reproducing a small amount of protected material- but that's a tenuous reach.
Nonetheless, some plaintiffs have attempted to get linking interpreted as a means of copyright violation, but they haven't really suceeded yet.
As has been said before, the linking to a GPL library will violate the GPL if and only if linking to a copyrighted library is found to be a violation of copyright.