Slashdot Mirror


German Court Convicts Skype For Breaching GPL

terber writes "A German court has once again upheld the GPLv2 and convicted Skype (based in Luxembourg) of violating the GPL by selling the Linux-based VoIP phone 'SMCWSKP 100' without proper source code access. (Original is in German, link is a Google translation.) Skype later added a flyer to the phones' packaging giving a URL where the sources could be obtained; but the court found this insufficient and in breach of GPL section 3. The plaintiff was once again Netfilter developer Harald Welte, who runs gpl-violations.org. The decision is available in German at www.ifross.de (Google translation here)."

62 of 309 comments (clear)

  1. Damn by Anonymous Coward · · Score: 4, Funny

    What a bunch of GPL Nazis.

    1. Re:Damn by MontyApollo · · Score: 2, Funny

      >>What a bunch of GPL Nazis.

      Sorry, I laughed.

    2. Re:Damn by s_p_oneil · · Score: 2

      Yes, and that lesson is to use BSD.

    3. Re:Damn by ravenshrike · · Score: 4, Interesting

      Let me get this straight. It's a net based phone application, which you need access to the internet to be able to use anyway, but yet an url where you can find the source code for the relevant part of the app isn't sufficient? Can someone help explain the insanity here, or am I not seeing something blindingly obvious?

    4. Re:Damn by Anonymous Coward · · Score: 3, Informative

      Section 6:

      "You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

      a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange."

      The thing is that Skype sold a physical produt (a phone), and according to the wording of the GPL the code needs to be distributed on a durable physical medium with this product.

  2. Correct terminology by Akaihiryuu · · Score: 5, Informative

    Noone would be convicted of "breaching the GPL". The GPL is not an EULA. If you violate the terms of the GPL, you are (re)distributing without a license permitting you to do so (since the GPL, which you violated, is the only thing that gives you permission to do so), which is a copyright violation, not a GPL violation. I wish articles would get the specifics right.

    1. Re:Correct terminology by ikegami · · Score: 3, Insightful

      You said the GPL was violated in a post trying to explain why it's Copyright and not the GPL that was violated.

    2. Re:Correct terminology by Mr.+Underbridge · · Score: 4, Funny

      Noone would be convicted of "breaching the GPL". The GPL is not an EULA. If you violate the terms of the GPL, you are (re)distributing without a license permitting you to do so (since the GPL, which you violated, is the only thing that gives you permission to do so), which is a copyright violation, not a GPL violation. I wish articles would get the specifics right.

      You win today's "Pedant of the day award." Look for your certificate in the mail.

    3. Re:Correct terminology by Akaihiryuu · · Score: 4, Insightful

      You *can* violate the terms of the GPL, if you do you lose your rights to distribute (since it is what gives you the rights). However you would not be convicted of doing so. Instead, you would be convicted of distributing without a license in violation of copyright (since you had no license to distribute). It's a technicality I know, but I wish more people would understand the specifics.

    4. Re:Correct terminology by blhack · · Score: 3, Funny

      you get runner up for using the word "pedant".

      but you don't get a certificate. We're kindof assholes like that.

      --
      NewslilySocial News. No lolcats allowed.
    5. Re:Correct terminology by timster · · Score: 5, Insightful

      This is far from pedantry. Using terms suggesting that someone would be convicted or held liable for a "GPL violation" suggests that a court must uphold the GPL as valid for such a lawsuit to be successful. This makes people believe (erroneously) that the GPL is a questionable document that needs to be tested in court.

      On the contrary, a standard legal action against someone not in compliance with the terms of the GPL would be a simple copyright infringement case; the onus is on the defendant to show that they had a valid license (and met its terms).

      --
      I have seen the future, and it is inconvenient.
    6. Re:Correct terminology by mrchaotica · · Score: 5, Insightful

      Hey, we're having a legal discussion here -- pedantry is necessary!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    7. Re:Correct terminology by Linker3000 · · Score: 2, Insightful

      No, if you are having a legal discussion, stupidly large fees are usually necessary.

      --
      AT&ROFLMAO
    8. Re:Correct terminology by AKAImBatman · · Score: 5, Insightful

      Using terms suggesting that someone would be convicted or held liable for a "GPL violation" suggests that a court must uphold the GPL as valid for such a lawsuit to be successful.

      The court must "test" the GPL if the defendant claims that he accepted the terms. At that point the judge will attempt to decide whether the defendant did indeed keep up his half of the bargain, potentially restricting the power of the GPL agreement where local laws say otherwise.

      This makes people believe (erroneously) that the GPL is a questionable document that needs to be tested in court.

      The GPL is a fairly air-tight design, but there's nothing erroneous about its need for court testing. A judge can (and will!) strike various parts of the agreement if he finds them to be in conflict with either the law or the intent of the agreement. As a result, it's difficult to legally "prove" that a given type of agreement will hold up in court unless either that same agreement or a similar agreement is tested. The GPL has had sufficient legal testing to show that it will hold up in court.

      If I'm not mistaken, your confusion stems from section 5 of the GPL, which explicitly provides for the fact that no proof of an agreement takes place. According to the GPL, you don't have to accept it to use the software. It falls back on standard copyright law in that case. Thus when an infringer is identified, he faces a double-edged sword. Does he claim that he did not accept the GPL, in which case he's on the hook for copyright infringement? Or does he claim that he did indeed accept the terms of the GPL, in which case he's on the hook for (I'll phrase this carefully just to annoy the "contract vs. license" folks out there :P) "breach of the terms and conditions of the contract"?

      The GPL is an interesting experiment in using a legal loophole as the foundation for a distribution agreement. This case provides further evidence that the concept works as well in practice as it does in legal theory.
    9. Re:Correct terminology by gad_zuki! · · Score: 2, Interesting

      >which is a copyright violation

      Right, we need to protect copyright at all costs! Maybe insert some DRM to protect us from evil capitalists!!

      I wonder how many slashdotters would agree that the idea to limit copyright to 12 years or so means that linux will be put in the public domain for anyone to do whatever they want, and to hell with the gpl.

      Not trying to troll, but its funny to see people quote copyright law line and verse when it serves them.

    10. Re:Correct terminology by cpt+kangarooski · · Score: 2, Insightful

      It sounds fine to me (though 12 years is a bit long for software -- it might be better to have a shorter term for it, and a longer term for other kinds of works). Linux is not that important in the grand scheme of things. If getting sane copyright laws meant that people could ignore the GPL for a 12 year old version of Linux (but not for any changes that had been introduced since then) I would very happy. Incidentally, how many people do you think are interested in running or making closed forks from Linux as it existed in 1995?

      --
      -- 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.
    11. Re:Correct terminology by Eivind · · Score: 2

      True. The GPL was not followed. But here's the thing: It's not forbidden to ignore the GPL. Its not law, afterall.

      It's not that complicated.

      Normally, Copyrigth law says that you aren't allowed redistributing or copying creative works that someone else created.

      The GPL says, in effect: "We give you permission to do those things anyway, if you follow these rules ...."

      So, if you break those rules, you *don't* have permission, which means if you still copy, you're in violation of copyrigth law.

      This is why the GPL is not an contract. (or an EULA, and why programs such as OpenOffice that insist on "I agree" on installation are braindead)

      It doesn't matter if you "agreed" to it or not. Copyrigth-law says you need permission. GPL says you get it if you follow the rules.

  3. Conflict and Chaos in the Hive Mind! by goldspider · · Score: 4, Funny

    Court upholding GPL - Good!
    Conviction for copyright violation - Bad!

    What's a loyal drone to believe anymore??

    --
    "Ask not what your country can do for you." --John F. Kennedy
    1. Re:Conflict and Chaos in the Hive Mind! by mrchaotica · · Score: 4, Informative

      The GPL is permissive, and thus turns the usual function of copyright on it's head.

      In other words, usually when people violate copyright it's through an act that increases the spread of the information, and prosecuting them for it would restict that spread. In contrast, when people violate copyright by failing to abide by the GPL, they themselves are restricting the spread of the information and prosecuting them restores it.

      If one (e.g., a "loyal drone") consistently believes that spreading information is good and restricting it is bad, there is no contradiction.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Conflict and Chaos in the Hive Mind! by goldspider · · Score: 2, Funny

      Are we talking beer, speech, or herpes?

      --
      "Ask not what your country can do for you." --John F. Kennedy
    3. Re:Conflict and Chaos in the Hive Mind! by Hatta · · Score: 2, Insightful

      GPL is permissive... But it prevents you from distributing something with out making the source available...

      The GPL is permissive the same way the 13th amendment is permissive. Both prevent you from taking away the rights of others.

      What I don't get is why is putting the source on the internet not good enough?

      Not everyone has access to the internet. Had they included a written offer to send the source code by post for a reasonable shipping charge they'd probably have been fine.

      --
      Give me Classic Slashdot or give me death!
    4. Re:Conflict and Chaos in the Hive Mind! by FooBarWidget · · Score: 2, Informative

      "The GPL is permissive the same way the 13th amendment is permissive. Both prevent you from taking away the rights of others."

      No, because under copyright law, you never had that right in the first place. The GPL gives you *more* rights than you had, it just doesn't give you the right to not give the same rights to others.

  4. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 4, Funny

    Why not!

    In any case you have completely misrepresented peoples positions and conflated different groups.

    Don't look now but I think your strawman is on fire.

  5. Re:Slashdot Hypocrisy by Anonymous Coward · · Score: 4, Funny

    Yes we can. And do. You see, RIAA/MPAA are evil. The OSS guys are good. Haven't you seen Star Wars?

  6. Re:Slashdot Hypocrisy by mrchaotica · · Score: 4, Insightful

    What do you mean? Opposing the RIAA means supporting the user's freedom. Enforcing the GPL also means supporting the user's freedom. There is no contradiction.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  7. Misleading or incomplete summary. by argent · · Score: 5, Informative

    The actual problem is that they did not include the text of the GPL with the phone. The summary here in Slashdot didn't mention that, and had me wondering what the problem with the provided URL was.

  8. Re:Slashdot Hypocrisy by langelgjm · · Score: 4, Insightful

    Now we will see the same people who oppose RIAA/MPAA copyrights cheering the copyright action that enforces open source. Don't you see that you can't have it both ways?

    In a perfect world, we wouldn't need the GPL, but we don't live in a perfect world. The GPL attempts to use the (imperfect) legal tools that do exist (read: copyright law) to accomplish its goal of access to source. The spirit behind it has little to do with copyright.

    --
    "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
  9. Re:Slashdot Hypocrisy by Volante3192 · · Score: 2, Insightful

    Umm, I think you'd find many people on /. would gladly let groups like the RIAA and MPAA hold onto copyrights if they didn't exert such a stranglehold on them and for so long.

    What we're opposed to are the draconian enforcement and perpetual lengthening of copyright expiration.

    So...no. I don't see where your argument has solid ground to stand on.

  10. Just out of curiosity by WindBourne · · Score: 3, Insightful

    Are you talking about American courts or German Courts. Because each country interprets the GPL, and copyrights, in very different fashion. Heck, in china, they ignore you until for some minor reason, you piss them off. Then you are shot. I think that is one of the VERY few countries that do that (for that reason).

    --
    I prefer the "u" in honour as it seems to be missing these days.
  11. Source Code by jshriverWVU · · Score: 4, Informative
    If anyone is looking for the source code it's here

    Can also check out this link for more info here

  12. Re:Slashdot Hypocrisy by mrchaotica · · Score: 3, Insightful

    Like it are not, all those extensions that benefit the (MP|RI)AA also end up benefiting the open source world as well

    I assume you're talking about the benefit of copyleft (i.e., enforcing the sharing) versus plain permissive (e.g. Public Domain). The thing is, plain permissive really isn't all that much worse than copyleft. In contrast, (from the RIAA's perspective) public domain is very much worse than proprietary. So, having a longer copyleft term doesn't benefit the Free Software community nearly as much as having a longer copyright term benefits the RIAA.

    Besides, old music remains valuable to society. For the most part, old code doesn't.

    For both of those reasons, it is unnecessary for Free Software to have long copyright, and thus most Free Software advocates oppose copyright extensions. The fact that the RIAA et al. abuse copyright only confirms that position more.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  13. Server Error? by EmbeddedJanitor · · Score: 3, Funny

    My German is a bit rusty, but I'm pretty sure that "Server Error" is not a very good translation.

    --
    Engineering is the art of compromise.
  14. Holy Larva Batman! by fishthegeek · · Score: 2, Funny

    the case that also the program at the same place is offered for the Download: "If distribution OF executable or object code is larva by off ring ACCESS ton of CoPy from A designated place, then off ring equivalent ACCESS ton of CoPy the SOURCE code from the same place COUNTs as distribution OF the SOURCE code, even though third parties of acres emergency compelled tons of CoPy the SOURCE along with the object code." In all other cases of the software selling it is not sufficient to make the SOURCE code available only on-line one.

    It's a wonder why Microsoft hates the GPL, Balmer is afraid of GRUB(s)
    --
    load "$",8,1
  15. Re:Beginning of the end for open source? by FunWithKnives · · Score: 4, Insightful

    You are mistaken. The only way that Open Source will die is if this type of thing doesn't happen. People like Harald are doing their best to uphold Open Source, as well as Free Software. If you want to allow corporations to fuck everyone else over and take without giving back, then you should really be looking at one of the BSD licenses.

    "Holy shit, someone's actually enforcing GPL v2! Open Source is going to die!" is, excuse my language, but fucking retarded. Find something else to blow up about. I hear the sky is falling.

    --
    "We may face a scorched and lifeless earth, but they're accountable to their shareholders first."
  16. Re:Not Really by dada21 · · Score: 2, Insightful

    I don't believe that copyright drives innovation -- innovation usually means providing a new direction or addition to a previous product that someone else likely designed, which was "innovated" from a previous product that another designed. New ideas based on old ideas, etc.

    What drives innovation is a desire to capture a particular market share for a demand, in effect providing a new supply stream for an existing demand, or hoping to create demand due to a new supply stream for a new product or feature.

    In my opinion, it is the combination of features, at a given price, backed by a given support structure, with promises to function at a given level of operation, that matter most. In this case, it isn't copyright that provides for a "winner" in that market of supply and demand, it is the person who releases the best combination of features+price+support+quality to a market that desires it, that wins, if that person markets the product properly.

    Copyright merely restricts competition from doing better than the originator of that particular product or service, and does the market a disservice by reducing the opportunity for other producers to do something one step better.

  17. Re:You are all wrong by vux984 · · Score: 2, Informative

    What you may not do, is to distribute them for your gains.

    'for your gains' is not a required condition.

  18. The interesting part by jeti · · Score: 4, Interesting

    After a previous conviction, a sheet was included
    with the phone that contained URLs to the GPL-
    license and to the source code . The articles do
    not make any statement on whether the source code
    contained all modifications, but they do not claim
    otherwise.

    The court decided that providing only an URL to the
    license was not enough and that the whole license
    should have been included in printed form.

    So far, so good. Now the interesting part is that
    according to the judge, providing a link to the
    source code is only acceptable for software that
    is provided on the internet. For software that comes
    preinstalled, the source must also be delivered with
    the device.

    This decision seems extremely strange to me. It is
    not what I read in the GPL v2. Here is the relevant
    part:

    3. You may copy and distribute the Program (or a work based on it,
    under Section 2) in object code or executable form under the terms of
    Sections 1 and 2 above provided that you also do one of the
    following:

            a) ...
            b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your cost
    of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,
            c) ...

    1. Re:The interesting part by Todd+Knarr · · Score: 4, Insightful

      I think the judge looked at the paragraph a bit further on in that section where it talks about providing access to the source as a download from a server, and noted that that case is explicitly allowed only when the software itself is also distributed as a download. That led him to the conclusion that clause B that you quote, when it talks of "medium customarily used for software interchange", means exactly what it says: an actual copy on some storage medium, logic being that if it allowed downloads from servers then it wouldn't have been neccesary later to explicitly allow downloads from servers. Combine that with failing to include the license text when the license says plainly in section 1 that you must include a copy of it's text and the judge's decision doesn't seem unreasonable.

      And I know the issue of downloads of source has been discussed, and IIRC the FSF's position is that it's not acceptable on it's own. Network servers can be taken down, files on them can be removed, some recipients may not have Internet access but none of those cases lifts the obligation to provide source code. The only way a distributor can guarantee he'll always be able to meet that obligation is to be prepared to provide source on a physical medium. The case of providing downloadable source for downloadable software was actually viewed as falling under 3a, not 3b, that is source code being provided along with the software itself, which makes a world of difference in the distributor's obligations.

    2. Re:The interesting part by obeythefist · · Score: 2, Interesting

      Kicking a company in the nuts for violating the GPL is well and good, but when they are actively trying to make amends, isn't it bad for the FOSS community and PR in general to keep on kicking anyway?

      Using the same mechanism as the RIAA to uphold freedom is good.
      Using the same sore-winner attitude as the RIAA and punishing people for the heck of it is bad.

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
  19. Re:You are all wrong by L0rdJedi · · Score: 2, Informative

    The only thing Skype did wrong, which the summary doesn't mention but someone else did, is that they didn't include a copy of the GPL with the phone.

    The court said including a website address to where the source could be downloaded wasn't good enough. I'd like to know why that wasn't good enough. Is it only because the text of the GPL wasn't included?

    This doesn't look like a win for the GPL. This looks like a major pain in the ass. I didn't even know that distributing a copy of the GPL was a requirement. I've never read it fully, but I guess I just assumed that as long as you make the source code available, everything is fine.

  20. Umm I think they misread one part by Kjella · · Score: 2, Informative

    Zwar wurde dem Gerät später ein Beiblatt beigelegt, das auf die verwendete GPL-Software verwies und eine URL enthielt, wo die Quelltexte abrufbar sind - doch dies genügte dem Gericht im vorliegenden Fall nicht. Diese Möglichkeit sehe die GPL nur für Software vor, die über das Internet geliefert wird.

    Rough translation (but better than google):
    "Later a note was included with the device, which said it used GPL software and a URL where the source code is available - but this was not enough for the court. The GPL only permits this for software that is delivered over the Internet."

    Doesn't that get covered by 6 b) 2):
    "6. Conveying Non-Source Forms.

    You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
    (...)
    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (...) or (2) access to copy the Corresponding Source from a network server at no charge."

    Or maybe it didn't come as a permanent offer, in which case they might be talking about 6 d):
    "d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. (...)"

    --
    Live today, because you never know what tomorrow brings
  21. Re:Only if copying is not fair use by ThePiMan2003 · · Score: 3, Informative

    Thats actually just fine under the GPL, but when you hand that executable to someone else, thats when the GPL is invoked. If you grab some code change it and just use it for yourself you do not need to do anything, but when you distibute it, by putting it on phones you sell, or putting the binary up for download somewhere you must also include the source.

  22. Re:You are all wrong by ericrost · · Score: 2, Informative

    Yes, the GPL says specifically that you must include a copy of the GPL to make sure the user knows his rights.

    Section 1:
    "You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you .... and give any other recipients of the Program a copy of this License along with the Program."

  23. Re:Only if copying is not fair use by Bogtha · · Score: 4, Informative

    There's a minority opinion in US circles that suggests that copying an executable, in order to use it, constitutes fair use.

    It's not fair use, because copies of software that are made for the purpose of using it are not covered by copyright in the first place. The law is explicit about this:

    Notwithstanding the provisions of section 106, it is not an infringement for the owner of a copy of a computer program to make or authorize the making of another copy or adaptation of that computer program provided: (1) that such a new copy or adaptation is created as an essential step in the utilization of the computer program in conjunction with a machine and that it is used in no other manner

    In short: It's not fair use (that's a different set of exemptions), but it is legal.

    --
    Bogtha Bogtha Bogtha
  24. Re:Slashdot Hypocrisy by Orange+Crush · · Score: 2, Insightful

    Have you ever stop to consider when software covered under the GPL will actually become public domain and no longer be bound by the terms of the GPL?

    Assuming Linus lives to at least 70 (born in 1969), the Linux kernel will not be released into the public domain for another 101 years or so. And that's only the parts he wrote. I think it's safe to say that the FOSS community will not be harmed by the release of what will then probably be an ancient and rather quaint bit of software from the turn of the last century.

  25. Re:Beginning of the end for open source? by 91degrees · · Score: 2, Insightful

    Skype's business doesn't require secret proprietry code It's a service, and they givwe the client software away. They could rewrite from scratch at greater expense, and there may be a valid business reason to do so, but it's not goin to resuolt ina major impact for open source.

    Countless businesses use GPL software for all sorts of reasons - whether internally or for bespoke systems. Skype deciding not to isn't going to harm the cause. On the other hand, Skype getting away with not following the terms honourably will harm the free software movement - or at least the FSF's free software movement.

  26. No conviction by hellfire · · Score: 2, Insightful

    Okay, it is Germany, and I'm going to use the definitions based under American law, but I'm 99% sure the same holds true in Germany.

    A conviction is for criminal court. Copywrite law falls under civil law. No one from Skype is going to jail and no one is going to pay a huge fine to the government. However, the organization that won this case could potentially get a tidy sum.

    Let's just pile onto the inaccuracies of the summary for this article. Let's hear it for inflamatory, add-pumping summaries!

    --

    "All great wisdom is contained in .signature files"

  27. Hooray for Harald! by PingXao · · Score: 2, Interesting

    This guy is waging a one-man show against GPL violators. Oh, the EFF is involved to some extent, but their effort is not Harald's. Harald, by the way, is the lead on the ipfilters project, something many /.'ers have probably heard of.

    He is swamped with submissions from folks claiming this company or that is in violation of the GPL. I submitted one myself about a year and a half ago. Nothing ever came of it. Not because the company is innocent, but because Harald has very few resources to go after the perpetrators of GPL license abuse. When a company gets reported he has to physically buy the item - most violators seem to be in the embedded Linux area - and verify the GPL violations before putting the lawyer(s) on them. He has scored some notable successes.

    But he is basically pissing into the wind. For every successful case he pursues there are 10 more that go unpunished. The real people who should be up in arms against commercial violators of the GPL are the authors who hold the copyright on the code being misused.

    Sadly, most of them can't be bothered and the violations go on. This will be the end of the GPL: developers who do not care to enforce their rights. Not v3 or v4, or Linus or Stallman or tiny paragraphs in section 1. At some point there will be a case where an evildoer will use the defense that since the copyright holder didn't pursue company X 5 years ago they should be prevented from trying to do it now. And poof! The copyright will vanish or be declared null and void and with it the GPL distribution license that goes along with it.

    Hooray for Harald! Watch out for the backspray, Harald.

    1. Re:Hooray for Harald! by Microlith · · Score: 2, Insightful

      Copyrights do not expire due to lack of enforcement, only trademarks.

      The case could easily be made that the violation was deliberately and intentionally obscured to make discovery difficult, and then the penalties could be even greater.

    2. Re:Hooray for Harald! by Kjella · · Score: 5, Informative

      At some point there will be a case where an evildoer will use the defense that since the copyright holder didn't pursue company X 5 years ago they should be prevented from trying to do it now. And poof! The copyright will vanish or be declared null and void and with it the GPL distribution license that goes along with it.

      Wow, did you drink some SCO FUD? Copyrights are never nullified because of lack of enforcement, and I dare you to find an example. Not enforcing them may limit your ability to collect damages, but at any time you can send an injunction to make them stop.

      What's needed is enforcement of copyright law:
      506. Criminal offenses
      (a) Criminal Infringement.
      (1) In general. Any person who willfully infringes a copyright shall be punished as provided under section 2319 of title 18, if the infringement was committed
      (A) for purposes of commercial advantage or private financial gain;

      2319. Criminal infringement of a copyright
      (a) Any person who violates section 506 (a) (relating to criminal offenses) of title 17 shall be punished as provided in subsections (b), (c), and (d) and such penalties shall be in addition to any other provisions of title 17 or any other law.
      (b) Any person who commits an offense under section 506 (a)(1)(A) of title 17
      (1) shall be imprisoned not more than 5 years, or fined in the amount set forth in this title, or both, if the offense consists of the reproduction or distribution, including by electronic means, during any 180-day period, of at least 10 copies or phonorecords, of 1 or more copyrighted works, which have a total retail value of more than $2,500;
      (2) shall be imprisoned not more than 10 years, or fined in the amount set forth in this title, or both, if the offense is a second or subsequent offense under paragraph (1); and
      (3) shall be imprisoned not more than 1 year, or fined in the amount set forth in this title, or both, in any other case.

      If you're using a substantial amount of GPL'd code beyond the rouge developer taking code, that should be enough to know you're willfully infringing. Being a for-profit company should be enough to prove "for commercial advantage". At which point they should be strung up on criminal charges and sent to jail like with SOX regulations. That's how it should be, note there's no minimum amount to make (3) go into effect and send them away for a year, even at a $0 "retail value" as long as you can prove *they* earned money on it.

      --
      Live today, because you never know what tomorrow brings
  28. Re:Slashdot Hypocrisy by sumdumass · · Score: 4, Insightful

    I think your point is missing reality a little. We have a few things to keep straight.

    First and probably the most important is that not everyone who dislikes the **AAs voice their opinion for the GPL and vice versa. This means that you will see people vocal about one and not the other and when putting it all together, you see the static noise level to be about the same but totally neglect the fact that it is coming from different sources.

    Second, And probably just as important, Most of the anti **IA people I speak to are in the position because of the what and how RIAA and the MPAA are handling things not because of their right to handle them. When they run threats of legal action in order to extort a settlement from the people who would seem to have the most difficulty defending from it, something is wrong. It would seem that if protecting against copy right infringement would be important, it would be important to go after everyone doing it and not just the people who stand a chance of having a successful defense.

    I don't know of the GPL people going after widowed grandmothers who don't even own a computer and make them spend hundred if not thousands of dollars to prove that. I don't know of any GPL people falsely accusing people of infringement by infecting their computer and snooping around. I don't know of GPL people going around and writing virus and jamming networks with infect material in order to extract revenge on people and ruin their computer install because you used a legal service to do something legal.

    If and when they start doing stuff like this and everything else the **IAs are doing, I will be just as vocal against them as some are for the **IAs. As it is, I don't usually comment in the RIAAs or whatever unless it is something really bad. So don't confuse the noise level on both as being from the same people or for the same reasons, they aren't.

  29. Re:Slashdot Hypocrisy by Greyfox · · Score: 2, Insightful
    Nope, we'd cheer for an individual artist who won such a copyright case, too. The RIAA/MPAA are a bunch of ticks who live off the blood of those artists while infecting society in general with lyme disease. We like artists and programmers and copyright. We don't like ticks or lyme disease. Or Hillary Rosen, may her vagina be clogged with brillo pads. She creeps us out. We're pretty sure she's an automaton.

    We also (And I think I speak for everyone of favor of copyrights 'round here) would like to see copyrights for something made today expire sometime in our lifetime. The original copyright term was just about right. That shit was never meant to last forever. Sure that'd mean that the original windows and linux source would be going to the public domain right about now, but that's just more incentive to innovate on the part of the folks who wrote that stuff.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  30. Re:Stop this rubbish by Anonymous Coward · · Score: 2, Funny

    Someone ist sehr crankisch.

  31. Support your local GPL enforcer! by Anonymous Coward · · Score: 2, Informative

    Seriously, looking at http://gpl-violations.org/support.html everyone can see that Harald is asking for help in maintaining the site - and the site badly needs it.

    So, instead of talking about the GPL on /. why not help running gpl-violations.org?

  32. Hm, no a german court did _not_ "upheld" the GPL by angel'o'sphere · · Score: 2, Interesting

    I started reading the threats but stopped after the first few *5* rated articles ;D

    What me rely wonders is this wording A German court has once again upheld the GPLv2 .

    No! A german court did not upheld the GPL. No court is interested in the GPL. the court honoured copyright law. The authors of the code in question are the copyright owners. The company distributing the code is not a copyright owner. The license is completely irrelevant.

    Notpicking mode on:
    A license could be void if it contained illegal terms, like: you agree to hand over your first born son, and his first born son and also his up to the 17th generation to follow to (insert your name here) ...
    In this case the license would be void. Not copyright! You still had no right whatsoever to distribute the code / IP of the legal owners.

    The court did not uphold the GPL. It only decided that Skype violated the GPL and in doing so violated copyright law If you violate a BSD or MIT license you violate copyright law as well.

    To uphold a license you would need to challenge the legal-ness of the license. So instead of suing Skype for breaking copyright law you would need to sue the author over using an illegal license. However there is no real applicable law here. You could construct a case probably by having a license that also encourages murder and rape ... like: by using this software you also a accept that the nazis did not committed a holocaust. In germany claiming in public that "the nazis did not commit the holocaust" is a legal offense. So having a license including legal offenses you had a license that would be void or tangible. But still you could not distribute the code of the copyright holder ... because your act of distribution has nothing to do with the license but only with copyright.

    angel'o'sphere

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  33. Re:Only if copying is not fair use by MooUK · · Score: 2, Informative

    On top of that, the GPL itself specifically states that running the program is outside the license and is always permitted.

  34. Re:Definitions... by DragonWriter · · Score: 2, Informative

    So, you can copyright source code, no problem. I know there is a bit of confusion about the meaning of the term "derivative work" and here's an example.

    Let's say I have a trivial program, say, "Hello World" or something like that. What exactly is the copyrighted bit here? Is it the source - that is, the exact language representation used - say, C++ or Pascal or Assembly?

    Certainly.

    Or is it the instructions generated by that source?

    Provided that you (the copyright holder) generate them (by running the compiler/linker/etc.), certainly, they are included as part of the original copyrighted work (or perhaps another copyrighted work, the distinction is probably unimportant in most cases, though for copyright time limits it may be important if the source is recompiled differently at a later time.)

    How many different source code versions of "hello world" can compile into the same executable?

    An infinitely large number. But copyrights aren't patents, so if someone else happens to generate the same executable from their own independently developed source that I developed from my copyrighted source, we could both have copyright on our own soure, and each have a independent copyright to the identical executable.

    The reason I'm not sure it's the "instructions generated by that source" is because that means that the copyright can extend to things that do not yet exist.

    Copyrights do extend to things that don't exist at the time the original work is created; all derivative works, for instance, by definition do not exist when the original work is created, yet are covered by copyright.

    Let's say I have a copyrighted bit of code. Then let's say that some guy comes along 3 years later and writes, for a brand-new architecture that didn't exist when I obtained my copyright, in a different language, some library that performs the functionality of my code and compiles it. Now let's say someone compiles my code on the new machine and the compiled version of my library is the same as the "independently developed" code (which is possible in certain cases).

    So here's the question - did the guy developing for the new architecture violate my original copyright or not?

    No, because while identical, the code is not in fact derived from your original expression. This is where copyrights differ from patents (aside from the kind of things they apply to), because the latter covers even independent inventions, while copyright only protects copies, not coincidences.

    It's quite important, because if you can only copyright source code and not the binaries - then that is an interesting situation. If the copyright really applies to the compiled binaries that's another interesting situation. It seems, however, that the current take is that it applies to both things simultaneously.

    It applies to both, but not to independently developed works, however similar (though proving that a work is independently developed may be a challenge if the similarities are so strong as to make coincidence seem unlikely.)

    Another odd situation - what happens if I reverse-compile a copyrighted program and then distribute the reverse compilation. I generated a new, different work than the original source code and a different "work" than the compiled binary. Or did I?

    You did create a new, different work. However, it is a derivative work, and thus probably violates copyright unless some special exception applies.

    Is that different than me going to a museum and sketching The Scream?

    No, not really.

    The only conclusion I can make at this point is that the artificial constructs of copyright need some work.

    Given your admitted ignorance of copyright,

  35. Skype was NOT convicted by voltheir · · Score: 3, Informative

    RTFM
    They convicted SMC, who makes a Skype phone, of the GPL violation because they didn't include the source code with the phone. NOT skype

    how can every slashdot mod and user be completely wrong?

  36. Re:Slashdot Downloads. by cpt+kangarooski · · Score: 2, Informative

    There isn't one. When you make a copy of a copyrighted web page in order to browse it, as you necessarily must, if only into RAM, you had better either have a license (either express or implied), or an applicable exception, or else you're infringing. So say the courts.

    --
    -- 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.
  37. Re:GPL blah blah blah by HatofPig · · Score: 2, Interesting

    You have read about the OpenMoko Neo 1973 open-platform cell-phone, right? The developer version (sans-wifi) is available now, and the consumer-ready version will ship in October. It's linux-based, and 100% open-source (both hardward and software) for a price comparable to the iPhone.

    --
    Silicon & Charybdis McLuhan Kildall Papert Kay
  38. Re:Does GPL copyright expires? by gd2shoe · · Score: 3, Insightful

    Of course it does. The only thing that makes the GPL enforceable is copyright; when the copyright expires, it passes into the public domain just like everything else.

    I take that partly back. It more completely passes into the public domain that a vast majority of software, because the source is easily available (copyright expiration wont make companies release the source).

    It will (of course) be many years before any software copyrights expire (here in the States at least).

    --
    I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
  39. Re:Skype is good? by hughk · · Score: 2, Informative

    Skype is hard to firewall. This means that if you can get to the internet with your PC, you can normally access Skype. I'm sure that hotels would like to stop it to force into using their expensive telephones. Mobiles aren't always an option when you are travelling overseas due to extortionate roaming rates. Skype has saved me a fortune on international calls.

    --
    See my journal, I write things there