Slashdot Mirror


Kiss Technology Counters MPlayer GPL Arguments

Snaller writes "Recently, MPlayer claimed that KISS Technology were violating the GPL by using parts of their MPlayer movie playback code in proprietary software. Now The Danish National Radio has interviewed the managing director of Kiss Technology, Peter Wilmar Christensen. He denies all claims of wrongdoing and suggests that if the pieces of code are the same, perhaps they were leaked from Kiss Technology and were then used by the Mplayer group. He also adds that the GPL is a weak license which has never been tested in court. Gabucino from the Mplayer team is furious, and accuses the director of outright lying."

54 of 634 comments (clear)

  1. GPL == strong by BlurredWeasel · · Score: 5, Insightful

    The reason GPL has never been tested in court is that there haven't been any solid violations of the licence and the fact that it is so clear (the GPL that is...). The only grey area is 'derivative work' which most certainly includes blatently ripping off a chunk of code.

    1. Re:GPL == strong by alexborges · · Score: 2, Insightful

      Danish Law != USA Law
      (EU Law?)

      So go figure.

      --
      NO SIG
    2. Re:GPL == strong by D-Cypell · · Score: 3, Insightful

      Im not so sure.

      I think the main reason that the GPL has never been tested in courst is because violations are very difficult to prove.

      You can be sure that this isnt the only case of GPL code existing in commercial products, but the nature of closed source prevents us from being able to easly spot a GPL violation.

      If I come around to your house and steal your television, you have no right to break into my house to see if I have it.

      Its the SCO thing in reverse, SCO refuse to open out their code to prove the violation, KISS will obviously be reluctant to open theirs to disprove it.

      It would be nice to live in a world where the hard work of voluteer developers was respected via the license they choose to license their work under, wouldnt it?

      Unfortunatly, BSD/Apache style licenses are looking like more a viable option.

      Sure, where there is a clear violation, the offender should be dealt with in court and made to pay whatever penalty is decided, it finding the offenders that is the trick. :o(

    3. Re:GPL == strong by D-Cypell · · Score: 2, Insightful

      Reminds me of the Lindows/Windows debate.

      That's a trademark issue, and is an entirely different can of worms. It's also still pending


      It is a different issue from a legal perspective, yes. However it still provides a useful analogy.

      If I steal some GPL code and include it as is, it is easy to determine my violation if you have access to my source code.

      If I steal some GPL code, change all the variable names, add a few extra 'helper' methods. Move some code around etc etc it then becomes more more difficult to prove that I violated the GPL in the first place.

      There is already an argument that two developers may potential come up with identical code to a given problem, but the chance of this is quite remote, but the more minor changes are applied to the original code the harder it becomes to prove that it just wasnt a case of two different developers with the same way of thinking.

      Similarly, calling a product Windows (if you are not microsoft) is a clear trademark violation. Change a letter to make Lindows, is it still a violation of just a similar name? What about Lendox etc... eventually you change all the letters and there is no link at all... where is the line drawn...

      So yes, different types of legal issues but conceptually the same thing.

      I appreciate I am making an unpopular point here, but I am a realist, and this seems to be a problem to me.
    4. Re:GPL == strong by An+Onerous+Coward · · Score: 2, Insightful

      Technically, you don't need to give the modifications back to the original copyright holders. The GPL only requires that you give the source and modifications to anyone who receives the code from you (or make it clear that the source is available upon request).

      --

      You want the truthiness? You can't handle the truthiness!

    5. Re:GPL == strong by Ogerman · · Score: 2, Insightful

      Unfortunatly, BSD/Apache style licenses are looking like more a viable option.

      BSD-style licenses are ok for some things but very wrong for others. As a consultant who develops and supports free software business applications, there is an enormous advantage for me if other people who use my work and improve it must contribute the changes back. I've put an enormous amount of work into the foundation of my software and I don't want people freeloading off my efforts by selling proprietary derivatives with just a little bit of extra polish. GPL ensures my work stays free and that others play fair in the open source "code economy."

      If I were the mplayer developers, I too would be quite outraged. If KISS is in violation, they owe back to the community any improvements that they have made or else they must license mplayer under a commercial license and thereby support the project in doing so. Those are quite fair rules to play by. Open Source Software == efficient development model and != free lunch.

  2. Interesting by olliej_nz · · Score: 3, Insightful

    The only way we could know for sure would be to see the CVS/[insert source archive system here] logs to see whether they were developed all at once by KISS (implying they stole) or whether it built up over time...

    --
    To be or not to be.-Shakespeare
    To do is to be.-Nietzsche
    To be is to do.-Sartre
    Do be do be do.-Sinatra
    1. Re:Interesting by Neon+Spiral+Injector · · Score: 5, Insightful

      You mean, whether Kiss implimented MPlayer's unique, never seen in the outside world, never used in a video file, subtitle format called MPsub, all at once, or over time?

    2. Re:Interesting by Cpt_Kirks · · Score: 2, Insightful

      In the same, unique file format?

      About as likely as dumping a glass of water in the ocean, waiting a month, then scooping out the exact same water molecules, on the other side of the world. Possible, but highly fscking unlikely.

  3. Bad tactic by downix · · Score: 3, Insightful

    He just got a bunch of easily riled up geeks that love the GPL pissed off at him.

    Expect mailbombing, DDOS attacks, and outright criticism. Then expect to start hearing from legal advisors that know what they are talking about.

    --
    Karma Whoring for Fun and Profit.
    1. Re:Bad tactic by placeclicker · · Score: 2, Insightful

      Or, more likely, those DDoS attacks would make the OSS community look childish, and thus help KISS's case.

      --

      Browse at -1, because trolls are often the most creative part of /.
    2. Re:Bad tactic by xlyz · · Score: 3, Insightful


      DON'T DON'T DON'T DDOS or mailbomb

      there is a much better action you can take: stop buying their products!!!

      this will really hurt them

  4. see you in court then by Anonymous Coward · · Score: 1, Insightful


    if the GPL is strong , there should be no problem seeing him in court right ?

    1. Re:see you in court then by epiphani · · Score: 2, Insightful

      im there. you're paying, right?

      --
      .
    2. Re:see you in court then by broeman · · Score: 2, Insightful

      In Denmark (I expect that the company has a clausule on wanting every dispute settled in a Danish court) you can get a free process, if the prosecutor (sorry about my bad English) has an income lower than 220,000 DKK. Hopefully the mplayer-guys are "poor" (European Standards, you know), but I think a non-profit-organisation says it all?

      --

      (yes this can be compared with sex)
  5. Never let it be said... by Anonymous Coward · · Score: 5, Insightful

    Well, never let it be said that Americans are the only people to behave in shitty corporate self-interested ways.

    Such dishonesty is painfully pathological.

    1. Re:Never let it be said... by kyhwana · · Score: 2, Insightful

      They don't need to distribute apple binary codecs anymore anyway, since libavcodec/ffshow can decode SQV1/3 natively, so no need for external binary libraries.

      --
      My email addy? should be easy enough.
  6. GPL@Court by SignificantBit · · Score: 5, Insightful

    ... i'm really eager to see what is going to happen when the GPL goes to court.
    To me, it's seems that with wider commercialization of GPLed technology, it becomes more important to have solid foundation to stop once and for all corporate greed and FUD.

    1. Re:GPL@Court by 0x0d0a · · Score: 2, Insightful

      GPL@Court ... i'm really eager to see what is going to happen when the GPL goes to court.

      It appears that the revolution will come...in Hungary. :-)

    2. Re:GPL@Court by antiMStroll · · Score: 2, Insightful
      .... it becomes more important to have solid foundation to stop once and for all corporate greed ....

      That'll happen the day after all human greed stops. A more likely scenario is greedy corporations who adhere to the GPL, finding the license to their advantage, attacking greedy companies that don't. Which is a good thing.

  7. Dates? by phorm · · Score: 4, Insightful

    The arguement of "who stole whose code" shouldn't be too hard to settle. There are archives of old versions, logs of when certain sections/features were added. Compare the allegedly stolen Mplayer code with the Kiss release date, and then tell Kiss to kiss our GNU/Asses.

    As for the GPL being were and unverified in court, perhaps they'd like to be our guinea pig? Of course, without GPL they'd still be in violation of copyright and up for large monentary damages.

    1. Re:Dates? by arkanes · · Score: 4, Insightful
      Using the MPSub file format does not neccesarily imply that the code used to read it is taken from the MPlayer source. I haven't read the entire MPlayer website yet, but the sscanf() patterns they match don't convince me either - parsers for the same formats would neccesarily have similiar if not identical patterns. The other strings results are more suspicious, but I would call this reason for further investigation, not the 100% proof that the MPlayer people seem to be claiming it as.

      The guy who wrote it might very have used the Mplayer code as inspiration (not suprising, if they're using the MPSub format), without direct copying. That'd explain things like the otherwise extreme coincidence of string names and order (once you've seen those you'll tend to put them in same order when you do it yourself).

  8. Christensen doesn't make Kiss look much better by ThisIsAnExampleAccou · · Score: 5, Insightful
    So, if Gabucino is correct, Kiss Technology stole code from MPlayer. And if Peter Wilmar Christensen is correct, someone working for Kiss Technology leaked the information to the competition, possibly for money.

    Neither scenario paints a pretty picture of Kiss Technology. Are they a publically traded company?

  9. Around and round we go! by Ghoser777 · · Score: 4, Insightful

    Wow, either that's a bad translation, or Peter talked himself in circles like 8 times. I guess he wanted to make it clear that they don't use MPlayer directly... as if that really mattered. Instead of answering a question with an answer, he kept saying they were looking into it and investigating. Now that's okay for a one or two line answer, but he kept saying it over and over and over again. It really sounded like he had no idea what to say but decided to say it over and over again.

    Over all, a fun read!

    Matt Fahrenbacher

    --
    James Tiberius Kirk: "Spock, the women on your planet are logical. No other planet in the galaxy can make that claim."
  10. GPL Defense Fund? by _bug_ · · Score: 4, Insightful

    Is there any such thing as a GPL defense fund? A lot of open source software is being developed by people who probably don't have the extra money to pay the legal fees needed to pursue action against GPL violators. Hence the GPL remains untested in court (although IBM may help fix that soon).

    It'd be nice if any leftovers from the US$10 million that IBM and Intel are putting up would be dumped over into a general GPL defense fund.

  11. Re:Untested? Bah. by Anonymous Coward · · Score: 3, Insightful

    We have confirmed what we already knew, that when using code licensed under the GPL then we have to publish any derivative work. This means that the legal foundation is very thin

    Does that make any sense whatsoever? "If you want to publish something based on our code, then you have to abide by our terms" seems completely reasonable to me.

  12. Re:Untested? Bah. by Curtman · · Score: 5, Insightful

    And once again someone (KISS, not parent poster) needs to understand that if the GPL isn't valid, they have absolutely no rights to use code copyrighted by the various authors of the Mplayer code.

    Could someone who understands the language take a look at the pre-translated version of:

    We doesn't use MPlayer, we use our own player, a player like we know from Real Player, Microsoft Media Player is the application used to display movies. It is a fundamental thing for our player, because it's what we are known for, being able to play a wide range of different formats.

    And tell us weather thats actually what this guy said, or if he actually knows what any of this is about? What the hell is he saying? Is he claiming they are using Windows Media player on Linux? Or just that they have a program that functions similar to Real or WMP?

  13. Liars and thieves don't like to be called on it... by Spoing · · Score: 4, Insightful
    A little more behind the scenes negotiations before making this an even bigger issue might have been prudent.

    Yes, Kiss stole from Mplayer. Calling them on it early and harshly, though, might have been the wrong tactic as it forces Kiss to defend an unethical position or to admit they are thieves.

    Now, it's an issue of ego and anger where it could have been a largely uninvolved and low key licence dispute.

    Case in point: Anyone remember Marion Barry, former Washington DC mayor? He was caught buying crack cocaine -- and ended up a hero to many people because he fought back from an ethically undefendable position where he had already lost everything. Barry is still involved in DC politics.

    Kiss currently can cause Mplayer and other projects trouble, and since Kiss also -- potentially -- has nothing additional to loose there is little reason for them not to be defiant and to basically say "No, you're wrong" to Mplayer.

    The only thing that will change this is if the dammage of caving in is less than the dammage of fighting this.

    Any ideas?

    --
    A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  14. Re:Don't pass judgement yet. by jdhutchins · · Score: 2, Insightful

    Mudflinging with no proof from both sides? The MPlayer guys have provided some evidence, as well as how they got the evidence and how you can find it yourself. The evidence seems pretty compelling. Not to doubt the MPlayer guys, but it's always a wise idea to hear your opponents arguments. If you don't hear your opponents arguments, you may overlook a large hole in yours.

    However, there haven't been any arguments from KISS other than "We didnt' do it, we swear, and by the way, if we did it anyways, GPL sucks"

    And if GPL is so weak, why do they distribute the rest of the sources used in their stuff?

  15. Re:Not To Play Devil's Advocate by bruns · · Score: 5, Insightful

    But why they were even looking to see how KISS's stuff worked is a bit curious.

    Because, when you develop open source software, and suddenly some closed source company suddenly 'develops' software for their set top boxes that has very similar features to your open source software, you should check using simple tools (like strings) to see if anything matches. Its not hard to look for certain strings, and you certainly not violating any laws by doing it.

    You aren't reverse engineering the software.

    Open Source developers have every right to protect their projects.

    What, you don't think Microsoft, and every other closed source software developer does this to products which are very similar to theirs?

    How else are you supposed to discover when someone steals your work?

    --
    Brielle
  16. Re:Looks like the server is melting already... by Alan+Cox · · Score: 5, Insightful

    One of the first things I'd say reading this is that his reaction looks a lot like several other vendors I dealt with whose CEO simply could not believe that either their employees or their subcontractors would steal code.

    Some of the confusion also comes from the speaker. If the translation is accurate the speaker asks

    "As he said, there are no big economical options for dragging the case to court. Instead they hope that the Open Source community will put so much pressure on Kiss Techonology that they will be forced to release all its software."

    The speaker doesn't say anything about software stolen by employees or contractors, or software in dispute, just about "all software". So the reply is that KISS won't release their player app - which the company guy clearly doesn't think contains mplayer code so he doesn't have to release.

    At that point he's already denied stealing any code, but confirmed he is having the matter checked.

    Now it may be that code was stolen and he doesn't know about it. It may be it was stolen and he systematically was involved. I find the latter hard to believe - if it had been done by someone smart and with foreplanning they would a) have an instant cover story b) done the hiding job a lot better.

    So the way I read this it says
    "We havent copied anything but we will check"
    "We wont be releasing all our code, including our proprietary stuff containing only our code"
    "We do release all the open source stuff"
    "We have fixed minor errors in the past"
    "You are picking on the wrong people"

    Put that way it's not quite the same as the mplayer view. Lets just see how the evidence pans out. If the KISS guys find someone stole code then we will see how they handle it. If the mplayer guys are right it won't be too long before the KISS folks will be apologising.

    Alan

    BTW: Larg e scale commercial copyright violation in parts of the EU (Denmark I believe included) is a violation of criminal not just civil law.

  17. How come companies like Kiss cant'be punished by L by Confused · · Score: 3, Insightful

    > How come companies like Kiss cant'be
    > punished by Law?

    Because the GPL is a rather weak weapon to make their life miserable. They just have to fix the problem or publish the source to their customers and the case collapses. This approach may be very sensible in a civilised society but not a good tool to annoy your neighbour.

  18. Re:License Review by pavon · · Score: 2, Insightful

    No I don't see a difference.

    The codecs various were made available under various licences. MPlayer is redistributing them in violation of those licences.

    MPlayer released it's code under a licence. Kiss is redistributing it in violation of the licence.

    What is the difference? The fact that the codecs did not require money in exchange for a licence does not change the fact that you have no right to use them except as specified in the licence. The exact same holds for the mplayer source.

  19. Basically by dtfinch · · Score: 2, Insightful

    They're claiming that after all this time they haven't taken the 10-20 minutes to download the mplayer source and compare it to theirs, and would like to hurl a few offensive comments towards the mplayer developers and the rest of the open source community before investigating if the claims are valid.

    Notice how he states that they're not violating the GPL, then proceeds to bash the GPL as if they were. Unless they found something incriminating and went "Of F**K, we violated the GPL," it makes no sense for them to argue that the GPL is weak.

    1. Re:Basically by sde1000 · · Score: 2, Insightful

      "I didn't get your message. And furthermore, you were out when I tried to reply."

  20. Re:Don't pass judgement yet. by GustavoT · · Score: 2, Insightful

    And if GPL is so weak, why do they distribute the rest of the sources used in their stuff?

    This simply cannot be iterated enough. It's just plain silly to say something like that.

    It's called HYPOCRISY.

    --
    Gus
  21. Re:what he's really saying by ScottSpeaks! · · Score: 3, Insightful

    The mutually incompatible responses (accusing MPlayer of being the derivative work, whilst questioning the enforceability of the GPL) are a standard legal defence tactic. You present every possible counter-argument you can think of, and depending on what the "facts" turn out to be, you've already gone on record defending yourself against them. It's actually a wise move when you're not sure whether you can establish the facts in court or not. Credible or not (it sounds a bit like Bart Simpson's "I didn't do it, and nobody saw me do it"), it's what our legal system encourages.

  22. Re:Copyrights on compiled databases by IshanCaspian · · Score: 2, Insightful

    Think of it this way. You can't put 10 poems in order, publish the book, thereby gaining ownership of the poems, and then sue someone whenever you see the poem reprinted somewhere else. That's all that decision means. This, however, is different.

    Imagine, if you will, that you're sitting in a classroom, and it's time to hand in your term papers....you then notice that the kid sitting next to you has EXACTLY the same title page and table of contents from the term paper you turned in last year...wouldn't it be worth checking to see if there are any other similarities?

    --

    But there is another kind of evil that we must fear most... and that is the indifference of good men.
  23. Pardon ? by Alan+Cox · · Score: 3, Insightful

    That sounds more to me like they understand the license and don't intend to violate it. They think its bad commercial business but the market will sort out whether their proprietary player is better than open source.

    The Linux community have dealt with KISS before, and KISS are providing the linux kernel sources and busybox. People are building NFS support into their players and other fun stuff.

    Reactionary readings of stuff, especially translated stuff that has also been through the radio system and journalists (who like a good story so tend to turn things up 8)) is never a good idea.

  24. Well this blows it for Kiss players, for me by PCM2 · · Score: 5, Insightful
    Hmm. Well, this is all starting to sound very unfortunate. I was really, seriously thinking of buying one of these KiSS DVD players. But ...

    ... and here is the important thing ...

    ...KiSS needs to know that I will not be supporting (buying) they products if they are violating the GPL. It seems to me that a large part of their market is going to be geeks like us. A DVD player that plays MPEG-4 is still rather a niche market, in the U.S. and Europe at least. If they want to corner the market that's going to be interested in these products -- us -- then they need to respect our ethics and our community.

    If we continue to buy these players while this issue remains unresolved, we are just shooting ourselves in the foot.

    On the other hand, this guy sounds like a typical suit, who doesn't really know how his product gets made and whose main job is to pump it. Somebody else posted that he was once heard bragging about the "2 million lines of code" that went into his product. That's exactly the type of dumb, meaningless puffery you can expect from somebody who really doesn't understand what he's selling at a fundamental level.

    He has said that KiSS is looking into the problem. If they discover that their firmware contains open source code in violation of its license, then KiSS should immediately issue a firmware update that removes that code, for good or ill as far as product performance goes. (I'm assuming here that they aren't going to relent on their stance that they cannot, under any circumstances, open their code.)

    If they find that they really didn't use MPlayer's code, then I guess what they need to do is show their source code to a representative of MPlayer under strict NDA, such that the MPlayer people can be convinced. Would that solve MPlayer's problem, or would they be unwilling to sign an NDA for this purpose?

    Still, this whole "we can't open the code" thing is a little silly. KiSS should at least be considering the possibility of opening their source code at this juncture. They're already beginning to face competition in the form of MPEG-4 enabled DVD players from Korea, Taiwan etc. These things are going to beat them on price, guaranteed. Meanwhile, domestic companies like Linksys have announced similar products for the U.S. market, and I can't see how Sony or Panasonic can be too far behind. Any of the established consumer electronics companies is easily going to shut these guys out of the retail channel for good, just on brand recognition alone.

    If they open their source, they open up the possibility of "hacked" variants of their player, sure. But what's to lose?

    • Nobody says they have to support a hacked version of their firmware, or even support the player at all once the end user flashes a hacked version.
    • By opening their source, they gain extra goodwill and patronage from their core market (geeks)
    • Closed source isn't going to prevent anyone from emulating their features. We're already seeing it happen. Who cares how 1337 they are when $50 Korean hardware does the same thing?
    • It's unlikely that their firmware is going to be binary compatible with another manufacturer's hardware. In other words, you couldn't download a KiSS firmware and run it on a Taiwanese player unless it was hardware compatible, and I assume the hardware design could still be protected by various intellectual property laws. So open KiSS firmware helps to sell closed KiSS hardware.
    • What the hell? Open the source, use all the MPlayer code you want, save on R&D!
    Right now, I really could not in good conscience buy a KiSS product. If they opened their source tomorrow, I'd probably be jonesing for one even twice as hard as before.
    --
    Breakfast served all day!
    1. Re:Well this blows it for Kiss players, for me by Aldric · · Score: 3, Insightful

      I was just thinking something similar. Why the hell don't they just use all the GPL code they want and publish any changes they make? In fact, make it as easy as possible to modify the player. The Linux community would love it and buy it over all other players. I can't imagine there's much of a market for MP4 players outside the geek community.

  25. Who is going to buy Kiss' product. by bstadil · · Score: 2, Insightful
    Interesting point, but Kiss is a small piss ant company and no OEM is going to touch them with this hanging over their head.

    SCO has killed it's business by doing what they are doing, but the are banking on the lawsuit or Pump and Dump stock scheme.

    Kiss do not have that option, They can Company Name their behind goodbye, that's all.

    --
    Help fight continental drift.
  26. Who cares? by nsample · · Score: 3, Insightful

    I don't intend to troll, but really, *who cares*? What's the big issue here? Mindshare? Proper credit? Counting ego coup? (Don't spout some "GPL violation" BS, we all *get* that rationale... but there has to be something more to make this news.)

    So, here's my thinking: If the code in question is really as simple and trivial as claimed by the MPlayer folks, then why bother facing this Danish DVD group? Don't we expect that trivial code would be written in a nearly identical fashion independently? (I haven't seen the code, just going by what the MPlayer folks have stated about subtitling and the complexity.) And why bother? Is this a zealotry issue... trying to uphold the RMS/FSF flag for its own sake? Or is there something more?

    What we've got here is a relatively obscure company (perhaps) taking a relatively small section of admittedly trivial code for their application. If this isn't shaping up to be a legal challenge for the GPL, then it's a waste of time! No good can come of this. My momma always said to "pick your battles", and I don't see the upside of this one...

    Fighting every fight for its own sake, or even teh sake of the GPL, is plain stupid and inefficient.

    Crap. It sounds like I turned into a flamebait at the end here. *sigh* God forbid Slashdot function as something other than a mental echo-chamber once in a while. We shall see how many steps to "-1".

  27. Re:Good Luck by scheme · · Score: 2, Insightful
    In what sense are they breaking licenses? They are doing things _very_ similar to Wine regarding the usage of Windows DLLs. And Wine has commercial spinoffs so apparantly, there is no problem in using Microsoft's DLLs.

    They are breaking licenses in the same sense that they accuse KISS of breaking licenses. In particular, if you go to their downloads page, you'll notice that they offer downloads of modified dlls for various codecs including wmv, quicktime and realplayer. Likewise they distribute arial fonts. Most of these things can't be distributed without permission from Microsoft, RealNetworks, Apple, etc.

    --
    "When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
  28. But the GPL *HAS* been tested in court, and won. by hacker · · Score: 4, Insightful

    Anyone recall the MySQL vs. NuSphere case? A few reminders:

    GPL enforcement goes to court for first time in MySQL case
    Affidavit of Eben Moglen on Progress Software vs. MySQL AB Preliminary Injunction Hearing
    FAQ on MySQL vs. NuSphere Dispute

    This was over 2-3 years ago. But again, the GPL itself, will not be "tested" in court, because violations and violators are easy to find, and prove. Once you violate the GPL, everything else above and beyond that, are U.S. Copyright violations (and in some cases, Lanham Act violations).

    Most companies settle out of court, because the cost of public embarrassment would be much more damaging to them. I personally know, because I've got 4 active GPL investigations of my own going on three projects I actively contribute to (and one I am the primary maintainer of), and one company backed WAY down, once they realized the huge financial and public penalty for not complying with our license.

    No company wants to take the GPL to court, mostly because if it gets that far, the developers/FSF/community have already done their homework, and can prove, beyond a reasonable doubt, a violation. Penalties range from $30k/USD to $150k/USD per violation once the GPL itself is violated and rights to continue using it are stripped. For a site that provides "free downloads" of a product that might contain violating code, that can get quite expensive.

  29. Re:If You Don't Accept the Terms of the GPL... by ajs318 · · Score: 3, Insightful

    It is not, never has been and never could be illegal to give permission for someone to use your copyrighted work. Some might think it slightly unusual to grant permission on such a wide basis just out of the goodness of one's heart, but that is a matter for individual copyright holders.

    What might be open to question is the revocability of such permission if the licensee breaches the conditions of the licence. However, the licence can only be breached by committing a deliberate act, and it would be next to impossible to prove that KISS had inadvertently breached it.

    My guess is that if someone were to misappropriate GPL'ed software, the courts would rule that the copyright in the modified version belongs to the original copyright holders, who would then have the right to distribute that modified source code under the GPL. Ignore the GPL for a moment - we need to look at cases where someone has unlawfully distributed modified versions of "ordinary" copyrighted software {without the GPL} to determine what would be likely to happen.

    If permission once granted is revocable, then plain old copyright law applies, exactly as though KISS were selling modified versions of Windows without permission from Microsoft. And if permission once granted is not revocable, then every EULA is invalid. That's why nobody wants to test the GPL in court. Either way, it jeopardises the whole concept of payware.

    --
    Je fume. Tu fumes. Nous fûmes!
  30. Weak? Not tested in court? by Cytlid · · Score: 3, Insightful

    Oh, so all these proprietary commercial licenses are null and void until they've been tried in court? I can ignore any EULAs because they haven't been tried in court? Great!

    --
    FLR
  31. Invalid GPL ? by rickms · · Score: 4, Insightful

    Here's one thing I don't understand,as IANAL. Say the courts struck down the GPL as invalid, why is it SCO and KISS believe that, it instantly makes the source code public domain? Having the GPL invalidated pretty much invalidates thier right to use the code at all doesn't it?

    --
    Making something out of nothing : MD5 ("") = d41d8cd98f00b204e9800998ecf8427e
  32. The reason the GPL has never been tested in court by hayden · · Score: 5, Insightful
    It being hard to show that GPL code was used is only a reason up until it is found. Then companies, like KISS, that get busted start banging on about how the GPL has never been tested in court. This lasts until they get actual legal advice and then it goes something like this.

    If you lose the court case and the GPL is upheld then you have to either withdraw the product and/or release all of the source code.

    If you win the courte case and the GPL is found to be unenforcable then standard copyright takes over. In which case you've distributed copyrighted code without a valid licence and you'll get sued for damages. This outcome is the less likely of the two and would be challanged by every software company in the world (as it would probably make pretty much all software licences uneforcable).

    So if you challenge the GPL in court you have the possible outcomes of loosing or loosing worse. Not a really appealing set of options that.

    --
    Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
  33. A more likely scenario... by BiggerIsBetter · · Score: 4, Insightful

    I'll hazard a guess here:

    The Manageing Director has no clue about this, and is going on what his developers told him.

    Developers saw MPlayer as an easy solution to their problem and figured they wouldn't get caught, but were wrong, and are now desparately covering their arses.

    --
    Forget thrust, drag, lift and weight. Airplanes fly because of money.
  34. Re:Looks like the server is melting already... by 0x0d0a · · Score: 2, Insightful

    One of the first things I'd say reading this is that his reaction looks a lot like several other vendors I dealt with whose CEO simply could not believe that either their employees or their subcontractors would steal code.

    Pretty much what I thought. He probably isn't intentionally lying, even if KISS is infringing (as seems likely). He naturally kicks into do-my-job-and-don't-admit-liability-mode.

    If the mplayer guys are right it won't be too long before the KISS folks will be apologising.

    I don't know. I'd like to think that is the case, but KISS is in a really lousy position. They can't settle with all the people that have contributed code to MPlayer. They will be open to civil cases against them for the earlier violations. This sort of thing is a real black mark to your company name to have all over the news. Finally, they're looking at the expense of auditing their code and possibly the loss of chunks of their code. I suspect that they are probably not legally able to GPL their code as a whole, as they may have licenses from other folks. Not good.

    This really drives home the poor current legal situation with code.

    Code is, increasingly, a commodity. It gets produced as cheaply as possible -- India, overseas, by companies willing to infringe --whatever. You have companies, little subcontractors, who are *never* going to get sued, or if they do, bob back up again. They have a phenomenal set of reasons to infringe copyrights. You have a lot of programmers, who, even if they *are* well-meaning, may not have proper legal knowledge on how far one can legally go. Having a company lawyer sitting in an office somewhere is not enough -- techies are woefully uneducated on IP issues, and *need* to know what they're talking about. I've seen so much bad information posted on Slashdot that it's really amazing.

    Frankly, if I were designing a software engineering curriculum these days, I'd include at least one class on code-related IP issues in law.

  35. Licenses by Ashcrow · · Score: 2, Insightful

    He also adds that the GPL is a weak license which has never been tested in court.

    And I take it their software licenses have been tested in court?

  36. Re:Liars and thieves don't like to be called on it by soccerisgod · · Score: 2, Insightful

    A little more behind the scenes negotiations before making this an even bigger issue might have been prudent.

    NO. It HAS to hurt.

    If it doesn't hurt, companies will have no reason not to use GPL code in their proprietary products. The price to pay for the violation of the GPL, the risk HAS GOT to be high. They have to see that this will burn their greedy fingers, so the MPlayer people did the only right thing. Such behaviour simply cannot be tolerated.

    --
    If a train station is a place where a train stops, what's a workstation?
  37. Re:KISS supports Vorbis, DivX by danro · · Score: 2, Insightful

    I kind of wish that someone like ESR or Perensomeone respected by the folks involved, could step in and lend a cooling touch, maybe mediate a bit.

    What, pray tell, makes you see ESR as someone who would quiet things down?
    The man is always where the fighting is thickest... a regular stormtrooper of FOSS, and the last person you'll want involved if you wish a quiet peaceful solution.
    If you want some general PR-mayhem on the other hand...

    --

    "First lesson," Jon said. "Stick them with the pointy end."