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
Unless I'm missing something, this ended in a settlement, not an in court win backed up by a judge.
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.
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."
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.
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.
80. (1) Subject to subsection (2), the act of reproducing all or any substantial part of (a) a musical work embodied in a sound recording, (b) a performer's performance of a musical work embodied in a sound recording, or(br> (c) a sound recording in which a musical work, or a performer's performance of a musical work, is embodied onto an audio recording medium for the private use of the person who makes the copy does not constitute an infringement of the copyright in the musical work, the performer's performance or the sound recording.
So, any copying I do, for my own personal use, is ok. This includes downloading music. This seemingly does not include uploading music. See here for more.
The fact that ISP can't get subscriber information from ISP's for file sharers might not make it legal, but it sure does make it easy to get away with.
"A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis