Slashdot Mirror


German Court Finds Fantec Responsible For GPL Violation On Third-Party Code

ectoman writes "Are firms responsible for GPL violations on code they receive from third parties? A German court thinks so. The Regional Court of Hamburg recently ruled that Fantec, a European media player maker, failed to distribute 'complete corresponding source code' for firmware found in some of its products. Fantec claims its third-party firmware supplier provided the company with appropriate source code, which Fantext made available online. But a hackathon organized by the Free Software Foundation Europe discovered that this source code was incomplete, and programmer Harald Welte filed suit. He won. Mark Radcliffe, an IP expert and senior partner at DLA Piper who specializes in open source licensing issues, has analyzed the case—and argued that it underscores the need for companies to implement internal GPL compliance processes. 'Fantec is a reminder that companies should adopt a formal FOSS use policy which should be integrated into the software development process,' he writes. 'These standards should include an understanding of the FOSS management processes of such third-party suppliers. The development of a network of trusted third-party suppliers is critical part of any FOSS compliance strategy.'"

228 comments

  1. Premptive STFU to GPL haters by Anonymous Coward · · Score: 5, Insightful

    So they got caught violating an oss license? (TBH they were just being lazy by relying on their supplier's word. You've got to know and own the product you sell.)

    Imagine how much shit they'd be in if they'd been caught violating copyright on a piece of closed source software. Ask anyone who's dealt with the BSA to comment on how friendly and fair they are.

    1. Re:Premptive STFU to GPL haters by datajack · · Score: 2

      I was going to say pretty much the same thing. I would imagine that Fantec are now looking to sue whoever supplied those components to them.

    2. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 0

      They wouldn't have been in shit because the proprietary firmware wouldn't have had such licensing issues. You've invented a scenario that would not have existed. This is purely a GPL issue despite the deflection attempt.

    3. Re:Premptive STFU to GPL haters by Desler · · Score: 0, Troll

      But copyrights are bad and copyright infringement is okay, right? Oh wait this was over copyrights on GPL code so we have a double standard. My bad, I seem to have lost my head.

    4. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 5, Insightful

      Actually at the core of the issue here is not really the GPL. At the core is that they got the code from another company and relied on that company adhering to the license.

      Basically the ruling says that when you got the code from a third party, you cannot rely on the third party acting correctly when determining whether your use of the code complies with the license. If the third party violated the license (in this case, by not providing the complete source code), it doesn't protect you from the responsibility of checking the correct licensing yourself when redistributing the code.

      That it was about GPL code is only tangential to the issue (although it's almost certainly the reason why it ended up on Slashdot).

      Basically the scheme is the following: A gives code to B under a given license. B then gives the code to C in a way that violates A's license. C relies on B having followed A's license and figures out that redistribution in a certain way would not violate A's license. However since B's analysis rests on the false assumption that B complied, it turns out that C's redistribution of the code also violates A's license. But with a closer inspection, C could have found out that B didn't comply. The court ruling now says that C is responsible for violating the license.

      Here A is whoever owns the copyright for the code in question, B is Fantec's firmware supplier, C is Fantec, the license is the GPL, and the violation is not distributing the complete corresponding source code.

    5. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 2, Insightful

      While I agree with what you're saying and I think the decision is correct, the problem is that when companies read articles such as this, all they see is, "If we use open source, we could get sued and screwed for something a third party did."

      It makes the use of GPL licensed software appear unpredictably dangerous. And there's no getting around that.

    6. Re:Premptive STFU to GPL haters by suutar · · Score: 1

      would it be any less of a double standard if corporations got a pass on copying code while decrying music copying?

    7. Re:Premptive STFU to GPL haters by Desler · · Score: 1

      Where did I say they should? Oh right, nowhere.

    8. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 2, Informative

      How did this get modded insightful?

      Yes, they should follow the license for all code they use.
      No, this would not have been an issue if they had used code under BSD.
      Yes, if I had a company that was producing code based on OSS, I'd be making sure I was using BSD licensed (or one of the other more liberal licenses).

      It's a simple matter of risk, BSD licensed code is less risky for companies to use. That's not good or bad, it just is.

    9. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 0

      GPL isn't about sharing, it's about forcing others to share.

    10. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 1

      They wouldn't have been in shit because the proprietary firmware wouldn't have had such licensing issues.

      The licensing issue was that Fantec's firmware supplier gave Fantec firmware using third-party code, but in a way that violated the license of the third-party code. Fantec redistributed the code as it received it from the supplier (as part of its devices, possibly also as firmware updates), which therefore was also in violation of the license.

      Now, please tell me why you think that could never happen with proprietary firmware. You don't really think proprietary code cannot violate licenses of any third-party code it uses, do you?

    11. Re:Premptive STFU to GPL haters by hairyfeet · · Score: 2, Interesting

      It probably wouldn't have cost them as much as most likely it would have been settled out of court without the need for lawyers and court fees, the BSA just wants to get paid after all and will negotiate,whereas with the GPL there is NO negotiation nor compromise because like it or not that is the way RMS designed the license.

      What I personally don't get when it comes to these cases is...why? Why would you bother taking the risk of using GPL code when you aren't a FOSS company and risk possible lawsuits like this? If you don't want to be a FOSS company there is BSD and there is plenty of proprietary solutions so there is really no damned point in taking the risk when your company isn't a FOSS based company. After all BSD is good enough for fricking Apple and the PS4 so its not like its not got plenty of support, so seriously they should get an extra 40% tacked on to the verdict as a "You're a dumbass" penalty for wasting all that money when there was no damned need to take the risk.

      Does this make GPL bad? Nope, but one would have to be blind not to see you really need to base a company around FOSS if you are gonna be using it as it doesn't play nice with proprietary, again by design, but as long as your business makes its money by using one of what I call the "blessed three" models by which pretty much all GPL businesses are based, selling support/services, selling hardware (like this company) or holding out the tin cup? Then there is no problem with you handing out the source and thus no issues with GPL. Its when these companies try to mix GPL and proprietary that it bites them in the ass.

      So the moral of the story is thus...if you are gonna use GPL make sure its no problem for your company to abide by the terms, otherwise choose something else. These cases show that stealing GPL code will end up costing you no different than if you stole proprietary code because as far as the courts are concerned its one and the same. Just because its "free as in beer" doesn't mean its "free as in do what you will", that is what the BSD license is for.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    12. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 0

      TBH they were just being lazy by relying on their supplier's word.

      what's the point of using a supplier if you essentially have to
      redo all their work?

    13. Re:Premptive STFU to GPL haters by MozeeToby · · Score: 1

      In some businesses being forced to open your code could be much more damaging that even the largest copyright settlements.

    14. Re:Premptive STFU to GPL haters by suutar · · Score: 1

      I didn't mean to imply that you said they should get a pass; you didn't. It just seemed to me that your statement carried an assumption that the alternative was not itself a double standard, which seemed odd.

    15. Re:Premptive STFU to GPL haters by aristotle-dude · · Score: 0

      GPL isn't about sharing, it's about forcing others to share.

      Right, the GPL is like socialism where the state owns everything and forces everyone to share in the labour whereas BSD is like communism where the community can share or not share freely because there is no "state" and people share when it benefits everyone in the group to do so.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    16. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 0

      Actually at the core of the issue here is not really the GPL. At the core is that they got the code from another company and relied on that company adhering to the license.

      Basically the ruling says that when you got the code from a third party, you cannot rely on the third party acting correctly when determining whether your use of the code complies with the license. If the third party violated the license (in this case, by not providing the complete source code), it doesn't protect you from the responsibility of checking the correct licensing yourself when redistributing the code.

      There doesn't seem to be anything surprising here - the same applies in most liability law, in that you can usually be sued for a liability even if it was your supplier's fault. (An example I can give which shows this is the same outside of IP law is: lets say your next door neighbor gets a contractor in to do some building work; the contractor damages your house in the process. Usually you would have to sue your neighbor, not the contractor (at least, this is the case in the UK)).

      Usually, if you get sued and it was your supplier's fault; you then need to sue your supplier to get your money back.

      Or did people somehow think that you're not going to get hammered for copyright infringement if you publish some music/art under the belief that your supplier had given you a licence to it and it later turned out they weren't the copyright holder?

    17. Re:Premptive STFU to GPL haters by citizenr · · Score: 1

      Good luck suing small Chinese factories :)

      --
      Who logs in to gdm? Not I, said the duck.
    18. Re:Premptive STFU to GPL haters by shentino · · Score: 1

      It also gives GPL fanatics an incentive to sneak GPLed code into stuff they supply other developers, then tipping off the original licensor.

    19. Re:Premptive STFU to GPL haters by citizenr · · Score: 1

      What I personally don't get when it comes to these cases is...why? Why would you bother taking the risk of using GPL code when you aren't a FOSS company and risk possible lawsuits like this? If you don't want to be a FOSS company there is BSD and there is plenty of proprietary solutions so there is really no damned point in taking the risk when your company isn't a FOSS based company.

      They are not in electronics manufacturing business, they are in relabeling Chinese crap business. They dont care about licenses shmihences until you poke them with a very sharp stick. Chinese also dont care about licenses and WOULD provide all the source code (they already do to their own Chinese partners) if that was the requirement.

      --
      Who logs in to gdm? Not I, said the duck.
    20. Re:Premptive STFU to GPL haters by gnasher719 · · Score: 1

      Yes, they should follow the license for all code they use.
      No, this would not have been an issue if they had used code under BSD.

      The problem is that Fantec received code from a third party. If the third party told them correctly what license applied, and Fantec acted accordingly, they would have been fine. If the license had been BSD but the third party lied and Fantec acted accordingly, they would have been fine most likely. If the license was GPL (as it was in this case) or proprietary, the supplier lied, and Fantec acted on the false information (which they did), obviously there was trouble.

      But the problem isn't GPL; the problem is not being told which license applied and acting wrongly because of that false information.

    21. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 0

      Agreed. This really has nothing to do with the GPL. If it had been proprietary code that had been stolen, it would have been at least as bad. If your contractors don't respect copyright, you're in trouble. Better to add terms to your contract saying they will indemnify you in the event that they give you copyright-violating code.

    22. Re: Premptive STFU to GPL haters by turbidostato · · Score: 1

      Yes with BSD you would have end up in exactly the same case: you still need to comply on third party code licensing terms. What, but trolling, makes you think otherwise?

    23. Re:Premptive STFU to GPL haters by Microlith · · Score: 1

      It probably wouldn't have cost them as much as most likely it would have been settled out of court without the need for lawyers and court fees, the BSA just wants to get paid after all and will negotiate,whereas with the GPL there is NO negotiation nor compromise because like it or not that is the way RMS designed the license.

      Nonsense. With the BSA it would have cost thousands in licensing fees as they dug into the entire company. The vast majority of GPL-related incidents are resolved out of court.

      What I personally don't get when it comes to these cases is...why?

      Why? Why do people enforce the license their software was released under? Gee, I have no idea. Maybe it has something to do with the fact that people like to have the terms under which their software was made available respected, like any other license?

      Why would you bother taking the risk of using GPL code when you aren't a FOSS company and risk possible lawsuits like this?

      Because the software is useful and the likelihood of suits like this is low?

      If you don't want to be a FOSS company there is BSD

      There might be BSD for whatever solution you're looking at.

      there is plenty of proprietary solutions

      There might be a proprietary solution, at significantly increased costs.

      BSD is good enough for fricking Apple and the PS4 so its not like its not got plenty of support

      BSD is almost exclusively the user-space command line tools and some minor aspects of the platform's behavior. They also have resources to throw around. And while it has support, it doesn't have nearly the support that Linux has.

      one would have to be blind not to see you really need to base a company around FOSS if you are gonna be using it as it doesn't play nice with proprietary, again by design

      Oh hairyfeet, lying again. Are you going to delve into the mad conspiracy theory that Torvalds et. al. are secretly integrating code into the kernel to cause proprietary userspace apps to misbehave?

      Its when these companies try to mix GPL and proprietary that it bites them in the ass.

      No, it's when companies don't pay attention to the licenses the software they get from ODMs and violate the terms that they get bit in the ass. But please, deliberately misrepresent the situation more.

      if you are gonna use GPL make sure its no problem for your company to abide by the terms, otherwise choose something else

      And it is very, very easy to comply with the GPL.

      These cases show that stealing GPL code will end up costing you no different than if you stole proprietary code

      Precisely!

      So the irony here is that your takeaway is "don't use GPL code" when the real lesson here is "pay attention to the license and abide by the terms." Now shall we see you lie through your teeth some more?

    24. Re:Premptive STFU to GPL haters by lister+king+of+smeg · · Score: 2

      GPL isn't about sharing, it's about forcing others to share.

      no it is about reciprocal sharing. i share with you as long as you agree to share not take.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    25. Re:Premptive STFU to GPL haters by Solandri · · Score: 1

      Basically the scheme is the following: A gives code to B under a given license. B then gives the code to C in a way that violates A's license. C relies on B having followed A's license and figures out that redistribution in a certain way would not violate A's license. However since B's analysis rests on the false assumption that B complied, it turns out that C's redistribution of the code also violates A's license. But with a closer inspection, C could have found out that B didn't comply. The court ruling now says that C is responsible for violating the license.

      That's how it's supposed to work. The next step is for C to sue B for breach of contract and/or damages suffered due to failure to comply with A's license, and (assuming B did their due diligence and put in a reasonable effort to make sure the code complied with A's license) for the court to find in C's favor and make B pay.

    26. Re:Premptive STFU to GPL haters by sjames · · Score: 1

      Sure it would. Do you actually think there would be no complaints had the supplier copied someone else's proprietary firmware and just hexedited the identifying strings?

    27. Re:Premptive STFU to GPL haters by sjames · · Score: 3, Interesting

      Why would you take the risk of using proprietary code? Most proprietary vendors have lawyers on retainer and tend to be less forgiving of violations.

      If you read TFA you'll see that this is not their first time violating the GPL on the plaintiff's code. The first time, they were allowed to correct the error and sign an agreement that they wouldn't let it happen again. There was a monetary penalty attached to further violations. They did, in fact, violate the licence on the same software AGAIN. They were offered the opportunity to correct the error, pay the agreed upon penalty and call it good, but they refused. Then and only then did they get sued.

      How often do you get one for free when violating a proprietary license?

      The fact is, most of the time GPL authors will be satisfied if you simply correct the error that they point out. Particularly if it looks like it was simply an error.

    28. Re:Premptive STFU to GPL haters by Anonymous Coward · · Score: 1

      How does using proprietary solutions prevent you from getting sued when/if a supplier/employee copies source code without payment?

    29. Re:Premptive STFU to GPL haters by amorsen · · Score: 2

      Using code at all is unpredictably dangerous. In most cases, it is impossible for someone to prove that a particular piece of software does not incorporate any unlicensed third party code. Software patents make it all even murkier. Such is life with "intellectual property".

      If you compile the software yourself from source, you have at least some chance at finding violations yourself. On the other hand, if you get handed a binary blob to redistribute, you better have a very trustworthy supplier.

      --
      Finally! A year of moderation! Ready for 2019?
    30. Re:Premptive STFU to GPL haters by tlhIngan · · Score: 1

      While I agree with what you're saying and I think the decision is correct, the problem is that when companies read articles such as this, all they see is, "If we use open source, we could get sued and screwed for something a third party did."

      It makes the use of GPL licensed software appear unpredictably dangerous. And there's no getting around that.

      To be honest, businesses should be putting open source under the same scrutiny they have for commercially licensed software as well.

      Some actually have, imposing actual processes on the use of open-source code and auditing the code base to ensure proper adherence.

      Any company dabbling should have a policy. One example would be that every OSS used - be it in a final code drop to the customer, or used for internal tools, must be approved by legal who can tell if using it will conflict with other licenses currently in use. Some things may be preapproved for external distribution (e.g., Linux kernel), others may be approved for internal use (build tools). Everything else must have approval to be used.

      Sure it's "not as fun" because now if you want to use $COOL_NEW_SOFTWARE you need to submit requests to legal to review it and approve it, but it's the only way to stay "safe". And yes, I know legal teams that explicitly ban GPLv3 from their approval list - or rather, if it's GPLv3, unless you can make a really compelling case, it won't be approved (so you can use GCC, for example, which is GPLv3, but not other GPLv3 stuff).

      Far too many companies have been getting away with the "it's free, we can do anything we want" mentality when they really should be imposing the same policies they have for commercial code.

      Hell, half the products might accidentally be violating the GPL or the commercial license because someone linked a GPL'd library with commercially licensed code.

    31. Re:Premptive STFU to GPL haters by amorsen · · Score: 1

      It probably wouldn't have cost them as much as most likely it would have been settled out of court without the need for lawyers and court fees, the BSA just wants to get paid after all and will negotiate,whereas with the GPL there is NO negotiation nor compromise because like it or not that is the way RMS designed the license.

      The vast majority of GPL violations get handled out of court. Anecdotal evidence seems to suggest that the payment in most cases is zero.

      Most actual court cases around GPL software seem to be brought by Harald Welte, and he in particular settles almost all cases outside court.

      --
      Finally! A year of moderation! Ready for 2019?
    32. Re:Premptive STFU to GPL haters by tibit · · Score: 1

      There is zero risk if you comply with terms of the license. Is that so hard to understand?

      --
      A successful API design takes a mixture of software design and pedagogy.
    33. Re:Premptive STFU to GPL haters by Darinbob · · Score: 1

      Also the issue that this ruling will have no weight in other countries. It may not even be used consistently in other German states.

    34. Re:Premptive STFU to GPL haters by angel'o'sphere · · Score: 1

      This ruling holds in all countries that signed the "Bern convention".

      Going to court already was braindead stupid. The ruling is nothing else than repeating the wording of the law. The law clearly states in a case of copyright infringement/violation the holder of the rights can sue anyone in the chain of the act of violation.

      Anyone in the EU doing business with software should know that. You don't need to be a lawyer for that as basic copyright law is tought in every university during your computer sciense education.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    35. Re:Premptive STFU to GPL haters by angel'o'sphere · · Score: 1

      Because there is no real risk.

      The original GPLed software has no 'monitary value' as it is not sold for money. So there is no damage.

      The only damage in this case are the court costs, which are likely minimal as the court costs are based on the software value/damage (which is close to zero).

      The reason is how german law in this case works, you can not simply sue for arbitrary damage and a brain dead jury grants it. You have to prove that you had said damage which you only can in this case by comparing it with lost sales or your usual income you make with the software, which is zero.

      So the case was made for the principle (right full so) to remind the culprit that he can not rely on false warranties of his supplier.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    36. Re:Premptive STFU to GPL haters by tibit · · Score: 2

      What does it mean to be a FOSS company? The way you use it, it's pretty much meaningless. It's a smoke screen. You're trying to make an argument, but you seem yourself a bit puzzled as to what argument you're after.

      GPL is a comparatively simple license, and compliance is fairly easy. If someone claims that it's hard, they IMHO admit to being dense. I still don't get it why would someone need to label themselves "a FOSS company" in order to, you know, comply with the terms of just one one of the multitude of software licenses they have to deal with. GPL is not special in the sense that if you have any complex product that leverages other third party products, you'll be dealing with a bucketload of licenses. Often most of those licenses were never tested in court, have never been scrutinized by anyone but the lawyer(s) who originally wrote them, and in the end seem to be a much bigger pain in the ass than GPL would ever be.

      I posit that in spite of perhaps unwanted freedom that GPL forces upon you and your customers, GPL wins you a lot of free third-party expertise as to what it takes to comply in various locales, and case law to back it up. Last time I checked, some of this legal expertise is billed $500/hour. Any other popular OSS license would give similar benefits. Shrink wrap licenses and one-off licenses (products from small software shops) are potentially much more risky since you don't have a big body of knowledge telling you really what the potential pitfalls are. Even shrink-wrap licenses for popular products like MS Windows have multiple variants and are subject to constant revisions, so their benefits of scale are diminished compared to fairly constant GPL.

      --
      A successful API design takes a mixture of software design and pedagogy.
    37. Re: Premptive STFU to GPL haters by Anonymous Coward · · Score: 1

      Ever read the terms of the BSD license?

      It doesn't take long, I'll wait...

      .
      .
      .
      .
      .

      yes, that's right, the only requirement is that you properly credit the author. The steps they took would have more then fulfilled the terms of the BSD license.

    38. Re:Premptive STFU to GPL haters by thesupraman · · Score: 2

      Do you ever sold a car? a microwave? a cellphone? a watch?

      All of them contain software, I damn well hope you obtained all the sourcecode for their software
      and had it fully checked for all license compliance, as otherwise you are responsible in exactly
      the same way. The people who SOLD the non-complant software ORIGINALLY should be
      responsible, however thats not whats being done here.

      THAT is why this is bad, for everyone.
      In fact the GPL doesnt even require you to sell it, is lending your car to someone distribution?
      There are certainly those who would argue it is on the side of the GPL, hope you got those software
      audits done!

      THAT is why the GPL over extends in this case.

      Why was the software supplier not the target? Not 'big time' enough?

    39. Re:Premptive STFU to GPL haters by icebraining · · Score: 1

      Copyright is violence. The GPL is self-defense. There's no double standard, even if they use similar means.

    40. Re:Premptive STFU to GPL haters by Microlith · · Score: 1

      Wow check out the FOSSies above you, if you dare say ANYTHING other than "Gee isn't GPL great? why it sure is Skip and RMS' farts cure global warning" they literally foam at the mouth like rabid dogs...too bad they can't seem to parse a sentence or understand basic language.

      I see that you can't stand being corrected or having the (deliberate?) flaws in your argument pointed out to you.

      Because GPL and proprietary don't play nice with each other, again that is by design

      Despite the fact that the LGPL exists? Despite the fact that there is a lot of proprietary running on GPL platforms? Despite the fact that your point rings completely hollow?

      as it was designed to further RMS political agenda

      Of course it was. You act like he's not allowed to have one.

      just look at how TiVo was named in GPL V3 because by following the license to the letter they still pissed off RMS because they didn't follow his agenda.

      Yes, DRM and one-sided lock down is shitty. Unless you're the one with the keys.

      what everyone here seems incapable of grasping is that not every company wants to be a FOSS company

      Err, how is "everyone here incapable of grasping" this? Oh right, you're attacking a stereotype and ignoring valid counter-arguments because you've already arrived at a conclusion.

      its pretty damned obvious since this was NOT THEIR FIRST OFFENSE that this company does NOT want to be a FOSS company so...why?

      Because the reality is that their suppliers find it easy to use GPL code because a lot of the work is done for them, and this company has failed, repeatedly, to ensure compliance with the license. The GPL isn't the relevant aspect here (but of course, that doesn't matter to you.)

      Why do these coders keep risking the companies they work for by taking GPL code when there is no need?

      Why do companies fail to ensure compliance with licenses? Because they're incompetent. Again, this has nothing to do with the GPL, as has been repeatedly pointed out to you.

      Have you had fun attacking the stereotypes in your mind today?

    41. Re: Premptive STFU to GPL haters by Anonymous Coward · · Score: 0

      You try sticking the BSD license on some code you don't know where came from, and see how that works out in court...

      No, the BSD license will not protect you in this case.

    42. Re:Premptive STFU to GPL haters by david_thornley · · Score: 1

      On the off-chance that you actually believe that....

      The GPL does not restrict your rights. Anything you could do without permission (like give an existing copy of software to somebody else) you can do regardless of F/OS license. It allows you to do certain things that would be otherwise illegal provided you follow certain rules. It specifically says you don't need to agree to the license for normal use.

      "Distribution", in this case, isn't just giving a copy of something to another. It's a matter of creating new copies (forbidden by copyright law unless you have a license) and then getting them distributed. A bookstore doesn't have to have a license from a copyright holder to buy a box of books and sell them, but the publisher does need a license or the copyright.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    43. Re: Premptive STFU to GPL haters by Anonymous Coward · · Score: 0

      noone's talking about that. What's being discussed is that if they had used BSD code, rather then GPL code, it wouldn't be an issue.

    44. Re:Premptive STFU to GPL haters by RockDoctor · · Score: 1

      You've got to know and own the product you sell.

      Ideally you would know your product that well. In practice often you don't. For example, our software line at work is protected by use of hardware dongles ; in theory we should know the detailed ins and outs of that product, but in practice we don't. It's a tool that we use, but we really don't care how it works in detail ; it's not our core business ; we're not interested in it ; if it stops working, we go and find a different supplier of a comparable product.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    45. Re:Premptive STFU to GPL haters by hairyfeet · · Score: 1

      A FOSS company is one whose products and/or services are primarily based around FOSS software, everyone from non profits like the Document Foundation to Red Hat would be considered a FOSS company. why its a BAD IDEA for a company that is NOT a FOSS company to use FOSS in their products is plainly illustrated in TFA and also by TiVo.

      As for the "unwanted freedom" as you put it, way to choose words for maximum propaganda value BTW, nice touch, I don't care if FOSS offers me blackjack and hookers if it doesn't fit my use case it would be fucking stupid to use it, now wouldn't it? I work primarily with home users and SMBs, 2 places where FOSS OSes suck a big hairy nut thanks to 1.- Shitty driver model breaking drivers so that hardware that works in foo doesn't work in foo + 1, 2.- Shitty half baked software that doesn't come even close to the proprietary solutions, see pretty much every bookkeeping software on Linux VS Quicken and Quickbooks, and 3.- Nothing that comes even close to the length of support that MSFT offers without paying tens of thousands of dollars, for an example show me ANY Linux OS that gives you 10 years of updates WITHOUT having to do the upgrade deathmarch and deal with #1 that doesn't cost several thousand dollars, see Red Hat and their $300 a year just to get updates.

      So while many "true believers" such as yourself think FOSS is the answer to everything in reality? Its actually only good for a few niches and the low adoption numbers reflect that. Its good for servers, its good for embedded, oh and before you mention Android which is the rallying cry of the FOSS crowd let me cut you off at the pass, android is a proprietary spinoff of an embedded Linux product, its 100% controlled by Google which is why handset makers can lock down the OS with impunity, because Google uses the "TiVo trick" by making sure ONLY GPL V2 is allowed.

      But since I'm not a programmer free lawyers mean jack and squat, and as a user and retailer I've found FOSS software leaves a LOT to be desired, so much so in fact that thanks to all the headaches FOSS software brings with it (Google "Linux busted shitter problem" to see a deeper explanation) it is actually cheaper for me to use proprietary than to use FOSS because of the better support and frankly just better written software.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    46. Re:Premptive STFU to GPL haters by hairyfeet · · Score: 1

      Hey nice straw man you built there, be a shame if i threw this match by it...WHOOSH! Comparing LGPL to vanilla GPL is like saying "Well if you can do it with BSD you MUST be able to do it with GPL, since they are all FOSS licenses, right?" even RMS has come out against LGPL because it doesn't promote his agenda like the GPL does, so comparing the two is pointless, other than the name they really have little in common.

      And I think its funny as hell that the so called "enlightened" FOSSie faction can ONLY throw insults, know why that is? Because otherwise all you get is the same old excuses, which just FYI they have been used so many times there is a joke site that lists them and the one I linked to I think is VERY apropos as most of the FOSSie faction are notorious for using circcular logic. Oh and last time I showed up with a link from TM Repo one FOSSie had the brass balls to compare a joke site to Stormfront, which just shows that FOSSie is a good choice of name, like Moonie one can't question their beliefs.

      --
      ACs don't waste your time replying, your posts are never seen by me.
  2. Bigger Issue by mdielmann · · Score: 1

    This isn't going to make it easier to convince companies to adopt the GPL. It's not necessarily accurate, since Fantec clearly didn't exercise due diligence with their third-party software, but that's what a lot of upper management is going to hear.

    --
    Sure I'm paranoid, but am I paranoid enough?
    1. Re:Bigger Issue by Anonymous Coward · · Score: 0

      so what? The point is that the GPL is being enforced _in court_, that's a boon to FOSS developers everywhere, all we need is a few more test-cases like this.

    2. Re:Bigger Issue by fuzzyfuzzyfungus · · Score: 4, Insightful

      This isn't going to make it easier to convince companies to adopt the GPL. It's not necessarily accurate, since Fantec clearly didn't exercise due diligence with their third-party software, but that's what a lot of upper management is going to hear.

      I don't doubt the theoretical potential for this to be FUDed; but it isn't as though Fantec would have been any better off if their shoddy firmware contractor had been out of compliance with code under any other licence... Somehow, the fact that you can get your ass handed to you for violating software licenses seems to be Super Scary when it's OSS; but just part of doing business when it's proprietary; but it's the same principle at work either way.

    3. Re:Bigger Issue by gmack · · Score: 4, Informative

      They didn't adopt the GPL they borrowed code that was GPL so they had to do less work rather than spend tends of thousands of dollars doing the work themselves. It's not the first time I've heard of a company thinking their added code totaling a fraction of a percent of the project is somehow worth more than the rest. It's also not the firs time I've seen willful ignorance on behalf of a device maker.

      I few years back I was sourcing some kit for an ISP and discovered the ADSL modems were based on Linux + BusyBox. I asked the manufacturer if I could have the source so we could try some local modifications only to be told "the chipset maker doesn't supply that" and I would have to talk to them (in China) about it. I argued the point but they refused to accept that they had a legal obligation. Fortunately about a year later they entered into a settlement with the gpl-violations.org but by then I was no longer working for that ISP.

    4. Re:Bigger Issue by serviscope_minor · · Score: 2

      This isn't going to make it easier to convince companies to adopt the GPL.

      That's their problem, to be honest. And it's good for me if they wish to make themselves less competetive by giving into FUD.

      The thing is the same issue applies equally to GPL code and proprietary code. If a third party had used someone else's proprietary code, they'd be in an even bigger heap of shit, but no one would be saying that it is going to hinder the uptake of proprietary code.

      Basically the rule is you need to do due dilligince to make sure your suppliers aren't supplying you with dodgy crap.

      --
      SJW n. One who posts facts.
    5. Re:Bigger Issue by Anonymous Coward · · Score: 0

      Are you conflating two distinct meanings of the word "free" intentionally, or accidentally?

    6. Re:Bigger Issue by mdielmann · · Score: 1

      This isn't going to make it easier to convince companies to adopt the GPL. It's not necessarily accurate, since Fantec clearly didn't exercise due diligence with their third-party software, but that's what a lot of upper management is going to hear.

      I don't doubt the theoretical potential for this to be FUDed; but it isn't as though Fantec would have been any better off if their shoddy firmware contractor had been out of compliance with code under any other licence... Somehow, the fact that you can get your ass handed to you for violating software licenses seems to be Super Scary when it's OSS; but just part of doing business when it's proprietary; but it's the same principle at work either way.

      If the Fantec product had been proprietary, they wouldn't have been under violation, and they couldn't have verified if there was a licensing issue with any firmware provided by their supplier, which would have been noted in any good contract. The supplier, if anyone would have been on the hook for license violations (assuming the firmware had any code they didn't own), and Fantec may have gotten an injunction against sales of their product (at least until new, complaint firmware was in place)

      Face it, there are a lot of new and different things you have to be aware of when going down the OSS road. These things are no worse than the traditional methods, just different And that different can land you in court and cost you piles of cash of varying sizes. The two options are like riding a horse versus driving a horse-drawn wagon. Superficially, they are a lot alike, even use the same engine, but there are key features that are different, and need to be taken into account.

      --
      Sure I'm paranoid, but am I paranoid enough?
    7. Re:Bigger Issue by Anonymous Coward · · Score: 0

      This isn't going to make it easier to convince companies to adopt the GPL.

      That ship has long since sailed. Linux is being used on a gazillion different devices and nobody cares about Fartec or whoever.

    8. Re:Bigger Issue by shentino · · Score: 1

      What if your supplier is a GPL fanatic who planted the violation on purpose for the express reason of forcing you to cough up your own code?

    9. Re:Bigger Issue by fuzzyfuzzyfungus · · Score: 1

      If the firmware had been proprietary and in-house (either their house or the contractor's) they wouldn't have been in violation; but 3rd-party proprietary components would have played out in almost exactly the same way.

    10. Re:Bigger Issue by FireFury03 · · Score: 1

      If the Fantec product had been proprietary, they wouldn't have been under violation, and they couldn't have verified if there was a licensing issue with any firmware provided by their supplier, which would have been noted in any good contract.

      No more so than they could with GPLed software.

      Their supplier provided them with a product which incorporated third party code. The supplier assured them that the third party licence was being adhered to. This turned out to be incorrect, and Fantec got hauled up for breaking the licence. In this case the third party code was GPLed, but lets suppose that it came from Microsoft under one of their licences - if the licence hadn't been adhered to they still could've been hauled up to court.

      The licence is pretty irrelevant here; all that is relevant is that the supplier used third party code and didn't comply with the licence, which in turn caused Fantec to fail to comply with the licence. Fantec's next step is going to be to sue their supplier and recover their costs.

      Of course, whatever licence you use, the idea that your licensing responsibilities evaporate as soon as your supplier screws up would be insane - that kind of system would simply lead to shell limited companies being set up as the "suppliers" which could be dissolved as soon as there is a claim against them, absolving the real company of any responsibility. So really, nothing to see here, the law operates as expected.

      Face it, there are a lot of new and different things you have to be aware of when going down the OSS road. These things are no worse than the traditional methods, just different And that different can land you in court and cost you piles of cash of varying sizes. The two options are like riding a horse versus driving a horse-drawn wagon.

      None of this is "new and different" - any third party code is a risk, whatever the licence. The only safe way is to write all your own code - most people consider that to be unrealistically expensive and therefore decide to take the risk with third party code. Third party code means due-dilligence in order to mitigate the risk of infringing a licence.

    11. Re:Bigger Issue by Anonymous Coward · · Score: 0

      You say no and pay for the copyright violation instead. Then you sue that fanatic to reimburse you the cost of that. Yes, it's going to be a bit more painful than this sounds, but not as big as an issue as you suggest.

    12. Re:Bigger Issue by Anonymous Coward · · Score: 0

      There's all sorts of fraud that a supplier could commit, one of them is to fraudulently relicense GPL code to you as non-GPL.

      This isn't really a GPL problem, you would not be liable to release your code in that instance, having never accepted the GPL. Instead you would be left without usable code, and a lawsuit with your supplier. This is the same thing as if a supplier took your money and didn't deliver.

      I suppose with GPLv3 it's more ambiguous, but I expect the part that involve distribution without copying (facilitation I think GPLv3 calls it) won't stick in court.

    13. Re:Bigger Issue by Anonymous Coward · · Score: 0

      Wrong.

    14. Re:Bigger Issue by serviscope_minor · · Score: 1

      What if your supplier is a crook who uses unlicensed code for the express reason of making more money by not paying?

      What if, what if?

      You did have a contract, right?

      --
      SJW n. One who posts facts.
    15. Re:Bigger Issue by tibit · · Score: 1

      That's their problem, to be honest. And it's good for me if they wish to make themselves less competetive by giving into FUD.

      You've taken the words out of my mouth. I was just going to say that re-use of de-facto industry standard GPL code in most cases brings huge financial savings. If my competitor doesn't want to leverage that, it's their loss. Same goes for re-use of open communications protocols. Bitch all you want about "dinosaurs" like, say, X.25, but that thing is by now patent free and comes with an extensive machine readable conformance test suite, and is a free download. There is way more if you care to dig in the ITU-T's treasure trove. Same goes for IETF RFCs. A lot of other communications protocols, especially industrial ones, are only "open" in marketing speak. They end up costing thousands of USD just to get the pdfs, and usually a couple thousand more to get the conformance test suites. And you need to license the patents. At least there's a couple that have learned from ITU's approach, and keep their stuff at least free to download like ethernet powerlink or ethercat...

      --
      A successful API design takes a mixture of software design and pedagogy.
    16. Re:Bigger Issue by Darinbob · · Score: 1

      The whole point of GPL and other open source is indeed to save you money so that you don't reinvent the wheel. There is nothing wrong whatsoever with using open source to save yourself extra work. You never need to "adopt" GPL principles to use GPL code.

    17. Re:Bigger Issue by Anonymous Coward · · Score: 0

      Good. Companies which don't understand the GPL should not use it, and should not be "convinced" to do so. That is exactly what leads to things like this happening.

    18. Re:Bigger Issue by mdielmann · · Score: 1

      This isn't going to make it easier to convince companies to adopt the GPL.

      That ship has long since sailed. Linux is being used on a gazillion different devices and nobody cares about Fartec or whoever.

      Using a GPL'd piece of software doesn't mean you've adopted GPL - it as often as not means you're using the most inexpensive product on the market, and all they know about GPL is that it's the title of the license they clicked "I Accept" to without reading (if they read that much). My mom uses OO.o because she can't be bothered to pay $100 to write up fairly standard documents. I use LibreOffice because I dislike Microsoft's desire to capture markets using closed standards (and not OO.o because I updated my system after setting up my mom's). The number of people who use Linux, for example, is likely far greater than the number or people who develop GPL software, as should be expected. This is certainly true if you include Android, which is a legitimate option.

      I don't mean to marginalize those who adopt GPL'd software for purely financial reasons. I personally can't think of a better statement of support for GPL'd software in general and Linux in particular than millions of people have decided that it is the superior product with no bias given by their personal philosophy.

      --
      Sure I'm paranoid, but am I paranoid enough?
    19. Re:Bigger Issue by gmack · · Score: 2

      The whole point of GPL is that it's a bargain, you get the code and you share the improvements if you distribute the result. That bargain is not being met if they refuse to release the source code and that's my whole point. We have companies who think the device driver they add is somehow worth more than the rest of the project and so they shouldn't have to follow the rules.

    20. Re:Bigger Issue by icebraining · · Score: 1

      If you distribute any third-party code, you need to do that anyway. It's not the GPL, it's copyright.

    21. Re:Bigger Issue by icebraining · · Score: 2

      No, that's not the point of the GPL. The point of the GPL is to uphold the four software Freedoms, has defined by rms in the Free Software concept.

      The GPL may be useful for saving money, but that's just an helpful side effect, not the main purpose.

      And you may not need to adopt its principles, but you certainly need to adopt its requirements.

    22. Re:Bigger Issue by msobkow · · Score: 1

      Whether that's true is entirely in the mind of the developer or project lead who initiates a project.

      I've no interest in saving anyone from reinventing the wheel with my work. I just want to share what I've spent many years working on, hopefully see it used, and ensure that any enhancements/changes to it are published instead of being held in a proprietary state.

      I don't believe what I've worked on all these years is any way related to a common wheel. It's not quite like anything else I've seen elsewhere, though others have used different techniques to achieve similar results.

      --
      I do not fail; I succeed at finding out what does not work.
    23. Re:Bigger Issue by Anonymous Coward · · Score: 0

      If the Fantec product had been proprietary, they wouldn't have been under violation

      Windows is proprietary. Are you claiming that all those pirate sites aren't in violation? Because they are doing the same thing as this company was found guilty of: Distributing works under copyright without the appropriate license to do so.

    24. Re:Bigger Issue by Anonymous Coward · · Score: 0

      You take the copyright law option.

      The GPL specifically states that it is not a contract, and you are not required to agree to anything. Thus, you cannot be forced to cough up your own code. Instead, you'll be forced to cease and desist distributing the product in question, until the code in question has been replaced with something you do have a license to, and paying a large fine.

      Just like any other copyright law suit.

      The nice thing about GPL violations is that you are usually given the OPTION of simply adhering to the license, and we'll pretend nothing happened. This is not a requirement though, if you are sued for GPL violations, you may not be given this option. They might insist on cease and desist plus a fine.

    25. Re:Bigger Issue by OdinOdin_ · · Score: 1

      > GPL principles

      What is this, you mean complying with GPL licenses when you produce a derivative work ? This is a legal obligation not a choice.

      > open source is indeed to save you money so that you don't reinvent the wheel

      The GPL way is that when you choose this path (to leverage other peoples open source work), then you provide the same openess that you consumed to all those downstream who you redistribute all or part of your changes.

      Note the use of the word redistribute, this is key to the additional requirements the GPL consumer has imposed on them, if you keep your modifications private.

      The grey areas here are around what counts as redistribution and what counts as a derivative work. Some stances on these areas are that redistribution is any copy created of software and supplied (so includes firmware, downloadable parts of a website, but does not includes server side parts of a website or code executed as a some kind of trade secret process). The derivative works includes any substantial part of the software that can not be removed without disrupting function, or substituted for an alternative implementation. Keeping the GPL parts as a DSO/DLL can assist this his process, providing you can demonstrate it is substitutable.

  3. Err - what? by queazocotal · · Score: 4, Insightful

    'A german court thinks so'?
    Under very few legal codes is it OK to distribute something that you do not have the appropriate copyright/licence.
    Even if you don't investigate properly to find out if you do or don't, that doesn't get you off the hook.
    It may alter the penalties, but the fundamental legality isn't really in question, pretty much anywhere.

    Raising 'GPL' is a red-herring here - 'Oh - I diddn't realise that machine had an unlicenced copy of windows on it' - is exactly the same case.

    1. Re:Err - what? by Nerdfest · · Score: 2

      I seem to recall a German court doing the same thing with MP3 licencing and Microsoft about 10 years ago. They licenced it from someone who did not have the rights, and MS got fined, not the supplier. At least they're consistent.

    2. Re:Err - what? by Anonymous Coward · · Score: 0

      There was one case in Germany where a GPL-violating company tried to defend itself by saying "The GPL has no legal consequences." The answer of the judge was simply "Are you sure? If you take up the position that the GPL is not in effect, then you're practically admitting a willful violation of copyright."
      The company's advocate reconsidered his strategy.

    3. Re:Err - what? by Bogtha · · Score: 1

      Under very few legal codes is it OK to distribute something that you do not have the appropriate copyright/licence.

      Distribution is fine. It's copying that is restricted by copyright.

      For example, I can go and buy a game in a box from a shop. I then give you that game. I'm distributing the game, but I am not copying it. Copyright doesn't stop me because copyright is for copying, not distribution.

      Why does that matter? Well consider this: what happens when I buy a machine with GPL software preinstalled on it by the vendor? I have the right to ask for the source code, right? Well what happens when I sell that machine to somebody else? I never had to agree to the GPL because I never made any copies of the software. I'm not obligated to follow the terms of the GPL. Does the person I sold the machine to have any right to ask me for source code? Why?

      --
      Bogtha Bogtha Bogtha
    4. Re:Err - what? by amorsen · · Score: 1

      Does the person I sold the machine to have any right to ask me for source code? Why?

      It gets tricky. Generally you are only allowed to pass on the entire software or none at all, not to modify it by only providing parts. Either the source code came with the software, in which case it could be argued that you have to transfer both binaries and source code in order to comply with copyright, or it came with a written offer. In the latter case the person you sold it to can just go directly to whoever made the written offer.

      Notice that the recipient never actually has the right to ask for source code. They do not own the copyright, so they cannot enforce the license. All they can do is alert the copyright holder(s) of the license violation and hope that the copyright holder(s) care.

      Even if you manage to circumvent the GPL this way, it is rather inefficient. You have to redownload the software every time you put it on a new machine, otherwise you're copying it. If you make scripts to do it for you, you are likely to end up modifying the software, which triggers copyright.

      --
      Finally! A year of moderation! Ready for 2019?
    5. Re:Err - what? by Bogtha · · Score: 1

      Generally you are only allowed to pass on the entire software or none at all, not to modify it by only providing parts.

      In the scenario I described, I'm not modifying anything.

      Either the source code came with the software, in which case it could be argued that you have to transfer both binaries and source code in order to comply with copyright

      Why would I be compelled to transfer source code to anybody? The only thing that would require me to do so is the GPL. I don't have to agree to the terms of the GPL because I'm not making any copies of the software.

      The GPL is a license that allows you to do things that would otherwise be covered by copyright in exchange for you agreeing to do certain other things. In this scenario, I'm not doing anything that is covered by copyright. There's no reason for me to agree to the GPL.

      In the latter case the person you sold it to can just go directly to whoever made the written offer.

      They can't. The organisation I bought the machine from is only compelled by the GPL to provide source code to the person they distributed the binaries to, i.e. me.

      All they can do is alert the copyright holder(s) of the license violation and hope that the copyright holder(s) care.

      What license violation? The vendor is complying with the terms of the license by providing source to me if I ask for it, and I don't have to agree to the license, so I'm not violating it.

      Even if you manage to circumvent the GPL this way, it is rather inefficient. You have to redownload the software every time you put it on a new machine, otherwise you're copying it. If you make scripts to do it for you, you are likely to end up modifying the software, which triggers copyright.

      I think you might have misread my comment. Why are you talking about redownloading the software to put it on a new machine? I am buying the machine with the software preinstalled. I'm not downloading or installing anything.

      If modification takes place, it will be the vendor I am buying from that does the modification, and that vendor is only compelled to provide source code to me.

      --
      Bogtha Bogtha Bogtha
    6. Re:Err - what? by amorsen · · Score: 1

      Why would I be compelled to transfer source code to anybody? The only thing that would require me to do so is the GPL. I don't have to agree to the terms of the GPL because I'm not making any copies of the software.

      If the vendor picked the option of giving you the source code along with the binaries, they can be argued to both be part of one piece of software. You have to transfer the entirety of the software to avoid copyright triggering. Otherwise you are modifying, and that is a copyright "event". You cannot keep some of the software (the source code) and transfer the rest.

      However, that is not the interesting case, as you are implying that the vendor picked the option of providing a written offer instead of source code.

      They can't. The organisation I bought the machine from is only compelled by the GPL to provide source code to the person they distributed the binaries to, i.e. me.

      This is not true. The GPL requires that the offer is made to "any third party".

      I think you might have misread my comment. Why are you talking about redownloading the software to put it on a new machine? I am buying the machine with the software preinstalled. I'm not downloading or installing anything.

      Because you can get around the GPL once that way. It is not really a hole worth being concerned about.

      --
      Finally! A year of moderation! Ready for 2019?
    7. Re:Err - what? by Bogtha · · Score: 1

      If the vendor picked the option of giving you the source code along with the binaries they can be argued to both be part of one piece of software.

      No, that's not the case, and the GPL isn't written that way. The source and binary forms are treated individually and where distribution together is mentioned, the GPL describes the source form as accompanying the binary form, not being a part of it. If one thing accompanies another, they are by definition distinct from one another.

      They can't. The organisation I bought the machine from is only compelled by the GPL to provide source code to the person they distributed the binaries to, i.e. me.

      This is not true. The GPL requires that the offer is made to "any third party".

      Not really. You are quoting "any third party", so I assume you are talking about GPLv2. Here's the relevant section from that license:

      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:

      [...]

      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,

      When the vendor distributes the machine to me, they are compelled to provide the written offer to me. I am not compelled to give this written offer to anybody I might sell the machine to.

      I think you might have misread my comment. Why are you talking about redownloading the software to put it on a new machine? I am buying the machine with the software preinstalled. I'm not downloading or installing anything.

      Because you can get around the GPL once that way. It is not really a hole worth being concerned about.

      Once? People can buy machines in bulk. Are you missing the relevance to the story here? Consider what happens if a company like Fantec contract an external organisation to install GPLed software on their components before reselling them.

      --
      Bogtha Bogtha Bogtha
  4. FOSS license compliance is difficult for many by drdread66 · · Score: 4, Insightful

    A previous employer of mine really really really wanted to offer FOSS support & products as part of their lineup. In the end, the lawyers won, as they couldn't craft a policy that would allow anyone other than a lawyer to make the decisions. This was mostly for GPLv2 and v3, but they got the dev managers completely wound up about all the license types. Mostly this resulted in the company punting on the FOSS idea.

    It's not terribly surprising that some small outfit decided to outsource the responsibility, assuming they were in a similar "analysis paralysis" situation. Too bad they did not understand the intent of the licenses and just "do the right thing."

    1. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      Sounds like they had a bad lawyer.

    2. Re:FOSS license compliance is difficult for many by HornWumpus · · Score: 4, Insightful

      Compliance is easy. Never even look at GPL code. If it's not under BSD, don't touch it.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    3. Re:FOSS license compliance is difficult for many by qbast · · Score: 4, Insightful

      But they magically understand proprietary licenses? And somehow fact that every proprietary license is different and may contain different pitfalls is not a problem?

    4. Re:FOSS license compliance is difficult for many by serviscope_minor · · Score: 1

      Compliance is easy. Never even look at GPL code. If it's not under BSD, don't touch it.

      I'll stick with my Linux instances, running GCC compiled code thanks very much. If you want to make your job harder and more expensive, feel free and I'll try to poach your customers.

      --
      SJW n. One who posts facts.
    5. Re:FOSS license compliance is difficult for many by MtHuurne · · Score: 2

      The outsourcing is what got them into trouble in the first place. They got both a binary and sources from their supplier and assumed that those two matched, without verifying that by doing the build themselves.

    6. Re:FOSS license compliance is difficult for many by suutar · · Score: 1

      no, but proprietary licenses are already in a "lawyer must make decision" state and everyone's used to it.

    7. Re:FOSS license compliance is difficult for many by HornWumpus · · Score: 0

      Good luck with that.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    8. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      A previous employer of mine really really really wanted to offer FOSS support & products as part of their lineup.

      So instead they went into solaris support and are getting sued by Oracle for not following their license?

      Doesn't matter what the license is if you are incapable of following instructions.

    9. Re:FOSS license compliance is difficult for many by gnasher719 · · Score: 1

      Compliance is easy. Never even look at GPL code. If it's not under BSD, don't touch it.

      That is completely idiotic in this context. The problem wasn't that the company used GPL code and didn't comply with the license. The problem is that they bought code from another company, they believed that they had all the copyrights, and the company that sold the code cheated on them.

      That can happen with proprietary code as well, as Microsoft found out when a company sold them lots of video code that they had originally written for Apple, and to which Apple had the copyrights.

    10. Re:FOSS license compliance is difficult for many by HornWumpus · · Score: 1

      No. They bought code from another company, knowing it was GPL. The source the other company supplied was incomplete.

      Had they bought code, knowing it was BSD this would never have been an issue.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    11. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      Linux doesn't even have a stable implementation of a COW FS that supports proper volumes and snap-shots. Good luck "saving" money and offering a sub-par service.

    12. Re:FOSS license compliance is difficult for many by Krishnoid · · Score: 2

      I remember reading that that the GNU GPL is a license, not a contract, and that most proprietary software is accompanied by both. My vague understanding is that lawyers aren't familiar enough working with the GNU GPL's 'bare license' situation.

    13. Re:FOSS license compliance is difficult for many by bill_mcgonigle · · Score: 1

      Ssshhhh!! The lawyers concluded that more lawyers would be required. Looks like it backfired on them.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    14. Re:FOSS license compliance is difficult for many by MtHuurne · · Score: 1

      Had they bought code, knowing it was BSD this would never have been an issue.

      But how do you know what is in the code if you don't examine it? It could still contain GPL-ed code, or code copied from a competitor by an industrial spy.

    15. Re:FOSS license compliance is difficult for many by MobyDisk · · Score: 2

      It is not a common practice to have lawyers involved in software tool decisions. Having worked as a software engineer and consultant for companies ranging from 3 employees to Fortune 500s. None of them ever had lawyers review software licenses.

      At my most recent job at a Fortune 500, I reported 2 cases where we were completely ignoring licenses: one was a click-through that said I agree to allow the company logo to be used in their marketing. Naturally, I have no such authority and putting that in a click-through makes no sense. The other simply said "All Rights Reserved" which was nonsense because it was an SDK, with a royalty-free redistributable. Clearly someone threw that text into the install without thinking.

      When I suggested that the legal department make some guidelines, everyone ran and hid because no one wants lawyers involved in their lives any more than is necessary.

    16. Re:FOSS license compliance is difficult for many by phantomfive · · Score: 1

      It's not that easy. You have to make sure that the BSD code is not taken from a GPL project, which is essentially what happened in this case (although it was proprietary code taken from a GPL project). You have to audit the code to make sure the person who gave it to you is telling the truth (even if they are honest, they might not realize where code was given to them).

      --
      "First they came for the slanderers and i said nothing."
    17. Re:FOSS license compliance is difficult for many by gnasher719 · · Score: 1

      I remember reading that that the GNU GPL is a license, not a contract, and that most proprietary software is accompanied by both. My vague understanding is that lawyers aren't familiar enough working with the GNU GPL's 'bare license' situation.

      That's very unlikely. Legally, it is quite trivial: GPL allows you to do certain things. So you check: Is your use allowed either by copyright law, or by the GPL. If yes, then you're fine. If not, don't use it.

      The GPL says roughly "you may do X if you do Y". Because it's no contract, it means if you do X without doing Y then you have copyright infringement. Without the GPL license, doing X would be copyright infringement, whether you do Y or not. If it was a contract, the copyright holder could force you to do Y if you do X, or could sue you for copyright infringement. Since it is no contract, they can't force you to do Y; they can only sue for copyright infringement.

    18. Re:FOSS license compliance is difficult for many by HornWumpus · · Score: 1

      In the real world it works the opposite.

      The BSD code is quite legally incorporated into a GPL project.

      Later a GPL zealot finds the code in a commercial project and runs around like a chicken with it's head cut-off. Later still it's explained to them what happened and they disappear, never to apologize. Rinse, repeat.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    19. Re:FOSS license compliance is difficult for many by Microlith · · Score: 1

      Later a GPL zealot finds the code in a commercial project and runs around like a chicken with it's head cut-off. Later still it's explained to them what happened and they disappear, never to apologize. Rinse, repeat.

      If this happens so often you'd have an actual, concrete example of this happening, right?

    20. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      Linux doesn't even have a stable implementation of a COW FS that supports proper volumes and snap-shots.

      Which you need on a 20 euro media playing gadget... because?

    21. Re:FOSS license compliance is difficult for many by whoever57 · · Score: 1

      No. They bought code from another company, knowing it was GPL. The source the other company supplied was incomplete.

      And had Fantec dealt with the issue properly when it was first brought to their attention, this would not have gone to court.

      Fantec had the opportunity to do the right thing but decided instead to risk the court ruling against them.

      --
      The real "Libtards" are the Libertarians!
    22. Re:FOSS license compliance is difficult for many by sjames · · Score: 1

      If you think FOSS licensing is confusing, try a proprietary license where even just using the software internally can lead to liability and they're not going to let you go if you say you're sorry and won't do it again.

    23. Re:FOSS license compliance is difficult for many by sjames · · Score: 1

      Or if they had appropriately specified a deliverable in source form that they then ran make on to produce the binary firmware.

      So you're saying that if they had told the same 3rd party that delivered mis-matched source and binary for some reason to stick to BSD they would have magically become competent and not included any GPL or proprietary code anyway?

    24. Re:FOSS license compliance is difficult for many by Belial6 · · Score: 1

      Don't forget to hire a sooth sayer to vet all of your code, as the foundation of this case is that Fantec did not check what license the code was under. If they had, they wouldn't have been in violation.

    25. Re:FOSS license compliance is difficult for many by HornWumpus · · Score: 1

      There are good number in the /. archives.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    26. Re:FOSS license compliance is difficult for many by tibit · · Score: 1

      Agreed. After all you can be getting an implementation that was poached by a contractor from GPL sources, for example. Suppose you are making telecom gear and subcontract out the ISDN PRI stuff. It's nothing but very basic due diligence to make sure it didn't get copy-pasted from libpri or the other open source implementation I forget now.

      --
      A successful API design takes a mixture of software design and pedagogy.
    27. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      I work at an SAP division in the United States, where we have a software license compliance office within engineering, partnered with the legal department. All open source software, whether for internal use or distribution to our customers, must be submitted for review.

    28. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      BSD has its supporters, GPL has zealots. Righto.

    29. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      So good a number that you didn't even bother to find the one instance you have ever seen?

    30. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      Compliance is easy. Never even look at BSD code. If it's not under WFTPL , don't touch it.

    31. Re:FOSS license compliance is difficult for many by Microlith · · Score: 1

      Hey look, there it is again:

      The data is out there, go look for yourself!

      This has to be a logical fallacy of some sort. "I can't be arsed to back up my claim, so go find proof of my claim for me." I see it used in so many context, virtually always by someone who has no actual evidence for it.

    32. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      Such as?

    33. Re:FOSS license compliance is difficult for many by Anonymous Coward · · Score: 0

      This is bullshit. If it isn't, then your legal team is incompetent and you should fire them.

      FOSS is easy to understand. You have essentially two licenses: BSD do whatever you want with it, just make sure to stick the license somewhere visible.
      If it's GPL, use it and post your changes somewhere where your customers can find it.
      If your changes are so valuable that you don't want to share them, then they're valuable enough to warrant a clean-room implementation.

      There are other licenses, but they're usually simple variations of the above two.
      The bit about not understanding them is a red herring. Proprietary licenses are a lot more complex, and companies use them every day.

  5. This is why they hate us by Anonymous Coward · · Score: 2, Insightful

    Shit like this. No wonder everything's going BSD.

    Did anyone try to work things out with the company?

    All stuff like this does is make people afraid of open source.

    And why does it seem that all these troublemakers are from Germany?

    1. Re:This is why they hate us by jedidiah · · Score: 4, Insightful

      > Shit like this. No wonder everything's going BSD.

      You wish.

      While it sound like a silly juvenile retort, it really is the case.

      Why would anyone with a pathological need to "win in the market" or "be associated with the cool brand" bother with BSD to begin with?

      > Did anyone try to work things out with the company?

      No. People just like to litigate for fun. They like to waste the money.

      Don't be such an idiot. If anything gets in front of a judge it's because one or both sides refused to compromise. The FSF has a long history of quickly dispensing these things by allowing the offending party to come into compliance.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:This is why they hate us by Inzkeeper · · Score: 2

      Yes, Fantec was approached in an effort to work it out.
      Their initial reaction was to deny everything.
      When confronted with undeniable proof, they simply blamed a contractor and said that they were not responsible.
      ...at least, that's what the articles I read reported.
      At that point, what options are left?

    3. Re:This is why they hate us by Anonymous Coward · · Score: 0

      BSD gives more freedom to a developer or a company, but not to users you idiot.

    4. Re:This is why they hate us by citizenr · · Score: 1

      Shit like this. No wonder everything's going BSD.

      so insightful, all those millions and millions of BSD based smartphones.

      --
      Who logs in to gdm? Not I, said the duck.
    5. Re:This is why they hate us by timmyf2371 · · Score: 1

      Yep, I have one. So do the millions of other iPhone users.

      --

      Backup not found: (A)bort (R)etry (P)anic
    6. Re:This is why they hate us by FireFury03 · · Score: 2

      Ooooo, someone's a little butthurt, yeah? BSD offers more freedom and is a license that wasn't cooked up by a bearded, fat-ass Jew who likes to eat his own toejam.

      Why do you actually care? If you don't want to comply with the GPL then don't use GPLed code - your choice.

      As a developer I actually *don't care* if you use my code - my code is written to do a job I need it to do, and rather than keeping it all to myself I release it in case its useful to other people. I usually use GPL under the premise that any improvements someone makes to the code will be made available to other people - they're benefitting from my code, why shouldn't other people benefit from their improvements too? If you don't like the terms under which I release my code, you're free to not use it - go find some code that does the same job under a licence that suits you better; or write your own; or even negotiate a different licence with me. But instead, what Fantec did was get some code they found useful and ignored the licensing terms - that's not cool and companies who ignore the licence and refuse to come into compliance after they've been asked to really do deserve to be sued. No one forced them into breaking the licence, there was nothing stopping them saying "we don't like that licence, lets write our own code instead of using someone else's work".

    7. Re:This is why they hate us by Microlith · · Score: 1

      a bearded, fat-ass Jew who likes to eat his own toejam.

      I see that Stormfront and its sociopathic, nerd-focused sister sites are starting to make themselves apparent on Slashdot.

    8. Re:This is why they hate us by Anonymous Coward · · Score: 0

      It gives more freedom to everyone who has the code. It's called copy-centre (as opposed to copyleft/copyright) for a reason.

    9. Re:This is why they hate us by sjames · · Score: 1

      Did you even try to read TFA?

      If you had, you'd know that this is the second time they have violated the license on that code and that the first time they were allowed to simoply correct the error and sign an agreement not to do it again with a penalty to be paid if they did. You would also know that they DID do it again and were offered an out of court settlement where they (again) correct their error and pay the agreed upon penalty. You would finally know that they refused that offer and then (and only then) were sued.

      if you had bothered to read TFA, that is.

    10. Re:This is why they hate us by citizenr · · Score: 1

      So your example against GPL is most IP hostile company on the planet? Seems legit.

      --
      Who logs in to gdm? Not I, said the duck.
    11. Re:This is why they hate us by Anonymous Coward · · Score: 0

      What a stupid appalling comment, it totally invalidates itself.

    12. Re:This is why they hate us by Anonymous Coward · · Score: 0

      Ah right, iPhone, that totem of user freedom.

    13. Re:This is why they hate us by aristotle-dude · · Score: 1

      BSD gives more freedom to a developer or a company, but not to users you idiot.

      Users don't code you idiot. Typical end users have no interest in having the code. They would rather pay for software that hire someone else to make changes.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
    14. Re:This is why they hate us by Anonymous Coward · · Score: 0

      Spare me your pious bullshit, Microtroll. I've been here since 1998, but I always comment anonymously when dealing with GNUtards because I know this territory well.

    15. Re:This is why they hate us by chilvence · · Score: 1

      End user here. I love having the code. You fucking programmers get bored and go do something else, leaving everyone who needs to use your software up shit creek. At least if there is code in the wild, there is still hope!

    16. Re:This is why they hate us by Tripkipke · · Score: 1

      You realize that there's loads of GPL software in your precious iphone?

    17. Re:This is why they hate us by Microlith · · Score: 1

      Because you'd be remembered as someone incapable of anything but spitting out slurs? Unable to present a level of commentary exceeding that of a homophobic 14 year old on XBox Live?

    18. Re:This is why they hate us by aristotle-dude · · Score: 1

      End user here. I love having the code. You fucking programmers get bored and go do something else, leaving everyone who needs to use your software up shit creek. At least if there is code in the wild, there is still hope!

      You are not an end user. If you can code then you are a developer who happens to use other people's software. End users "use" the software. When it stops serving their need they find something else.

      --
      Jesus was a compassionate social conservative who called individuals to sin no more.
  6. LOOK !! PIGS ON THE WING !! by Anonymous Coward · · Score: 1

    You know that I care !!
    What happens to you !!
    And I know that you care !!
    For me too !!

    Need shelter from GPL !!
    Don't do it !!
    It's a trap !!

  7. Is this what they really want? by Anonymous Coward · · Score: 0

    So, because some people decide that they want this code for some silly reason, more companies will just dump gpl outright to limit their exposure to stuff like this?

    1. Re:Is this what they really want? by queazocotal · · Score: 4, Insightful

      This isn't a GPL thing.
      This is a general IP thing.

      If you are not - as a buisness selling software (even if in embedded hardware) requiring your suppliers to state that all software used is compliant with relevant licences, with appropriate penalty clauses or indemnification if they are not - then your lawyers don't deserve to be employed.

      Exactly the same happens if you ship unlicenced windows on your systems.

    2. Re:Is this what they really want? by qbast · · Score: 1

      Hopefully yes. Having dozen more companies simply grabbing bits of GPL stuff and closing it because nobody dares to do anything is a loss. If you are still in 'OMG an actualy company looked at my code and wants to sell it! I am so honored!' phase, then by all means choose BSD for all your stuff.

    3. Re:Is this what they really want? by Anonymous Coward · · Score: 0

      Exactly the same happens if you ship unlicenced windows on your systems.

      Except Microsoft doesn't give you the option to publish the source and avoid a lawsuit.

    4. Re:Is this what they really want? by queazocotal · · Score: 1

      They provide you the means of complying with the licence though - it's just that it involves actual cash, rather than required actions.

  8. More of a "better chance you get caught" by nedlohs · · Score: 1

    A third-party firmware supplier could also supply you something that included copyrighted code under some other license (doesn't have to be a free software/open source one) without meeting the requirements of the license. And you would distribute that infringing on the copyright.

    Of course if the source code isn't supplied it's harder for the copyright holder to find out.

  9. Yes, when asked to comply the company lied. German by raymorris · · Score: 4, Informative

    It appears that when asked to comply with the license by posting the code they actually used, the company lied and said they weren't using iptables.
    Contrast that to when I pointed out to Plesk that they were violating the Apache license. They very quickly apologized and posted the code, putting an end to the issue. All they needed to do is post the code that they compiled in order to come into compliance.

    The court opinion is six pages, Im guessing three of those are boilerplate. Are there any fluent speakers of German who can read through it and tell us the facts as expressed by the court?

  10. Re:Premptive STFU to GPL white knighters by mwvdlee · · Score: 4, Insightful

    They published code, it got used, they're dealing with it.
    What's the problem (apart from them not dealing with it in the way you'd prefer)?

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  11. A Case for mediation by Martin+S. · · Score: 1

    It looks like there is an attempt to make an example of this company when perhaps mediation would have been a more suitable approach give they attempted to comply but failed procedurally rather than pursued a policy of wilfully evasion.

    1. Re:A Case for mediation by Todd+Knarr · · Score: 1

      Probably. This isn't the first time this has happened. They aren't the first company to fail to audit code their suppliers provided. At some point you have to stop and say "OK, by this point everybody ought to know what they need to do. It's been in the news enough that nobody can claim it's not well-known. So from here on out, no more excuses. No more passing the buck. You know what you need to do, do it or accept the consequences.". If you don't, the failures won't be addressed.

  12. Not just due diligence, lying and covering up by raymorris · · Score: 4, Informative

    Not only did they not exercise due diligence to start with, it appears that when asked to comply with the license by posting the code they actually used, the company lied and said they weren't using iptables. Had they simply said "oops, sorry about that, here's the code we compiled" it would have been resolved with just a few minutes of time.

    That second scenario is what Plesk did. I pointed out they weren't in compliance and as an Apache copyright holder I insisted that they comply.
    They immediately posted the Apache code they were using, ending the matter. The only effect on them is that now a couple of Slashdot readers know that they did the right thing.

    I think that's the big takeaway - when you mess up, don't lie and initiate a cover-up, just fix it and move on.

    1. Re:Not just due diligence, lying and covering up by mdielmann · · Score: 1

      Not only did they not exercise due diligence to start with, it appears that when asked to comply with the license by posting the code they actually used, the company lied and said they weren't using iptables...I think that's the big takeaway - when you mess up, don't lie and initiate a cover-up, just fix it and move on.

      I missed that part, and yes, trying to cover it up only hurts. I still expect a fair number of management employees to walk away with the soundbite that GPL equals lawsuits.

      --
      Sure I'm paranoid, but am I paranoid enough?
    2. Re: Not just due diligence, lying and covering up by turbidostato · · Score: 1

      Then other companies with more clever management will take advantage of it and will outperform them. Isn't that free market in action?

    3. Re:Not just due diligence, lying and covering up by sjames · · Score: 1

      To make matters worse, this is the second time they violated the GPL on the same code. The first time they were allowed to fix it and sign an agreement not to do it again with an agreed upon penalty for non-compliance.

    4. Re:Not just due diligence, lying and covering up by amorsen · · Score: 2

      I missed that part, and yes, trying to cover it up only hurts. I still expect a fair number of management employees to walk away with the soundbite that GPL equals lawsuits.

      Hopefully the management employees will also notice that the average number of GPL violation cases going to court is below 1 per year, and that most of the settlements are really, really cheap.

      Hopefully they will not notice that there are very few developers of GPL'd software who are willing to defend it in court, and therefore the GPL can be ignored on most code if you are sufficiently brave.

      --
      Finally! A year of moderation! Ready for 2019?
    5. Re:Not just due diligence, lying and covering up by thesupraman · · Score: 1

      No, thqats not what happened at all.

      When asked it seems they did obtain and provide the source code that they believe was
      required - and as supplied y their supplier. \
      It appears however that more was wanted, and the argument is about how far the GPL extends.
      From a bit of digging it looks like the actual items in questions were not IPTABLES at all, however
      were the code they used to create IPTABLES configurations - REALLY? that seems a pretty damn
      long stretch, calling that art of IPTABLES, dont you think?

      The GPL people are not doing themselves favours when it comes to being adoption friendly - we see
      this time and time again where they are as clear as mud as to what 'counts' right up until they want
      to drag you in to court, at which time it becomes a crapshoot (and they have little to lose) as the
      judges often have little technical understanding.

      and this is software freedom?

  13. FOSS Policy is pretty simple by Anonymous Coward · · Score: 0

    Many companies simply have a list of open source licenses that are permissible. Apache, MIT, BSD, etc... and GPL in any form is often barred from us

    1. Re:FOSS Policy is pretty simple by hermitdev · · Score: 1

      Same here. MIT, BSD, Boost and LGPL are acceptable for software we sell. GPL is acceptable for anything internal only. On one project that was external, I had to get lawyer's approval for a small library whose license amounted to "Provided as-is, no warranty. Use however you want, I don't care." Lawyer's response was, "Wow. I wish all licenses were this simple. Approved."

    2. Re:FOSS Policy is pretty simple by Anonymous Coward · · Score: 0

      I can see that companies could find the GPL (v2, v3 and Affero) unacceptable but I don't see why they should refuse the LGPL (v2 or v3).

  14. GPL go away by optikradio · · Score: 1, Troll

    One day, we will be free from tyranny of GPL. One day.

    1. Re:GPL go away by Anonymous Coward · · Score: 0

      One day, we will be free from tyranny of GPL. One day.

      It's the day when copyright gets abolished.

  15. Re:Premptive STFU to GPL white knighters by VortexCortex · · Score: 3, Interesting

    You publish your code. It might get used. Deal with it.

    Ah, then by that logic, we can ignore all copyright laws. Eureka!

    To be perfectly clear: I would rather a world where labor to create a work is done and paid for once, and the infinite monopoly granted to any who refuse to work without assurance of pay would be applied to content creation as it is in all other labor fields. Yes, I would rather a world where no copyrights existed at all; Where to get more money you would have to do more work instead of sell more copies which are infinitely reproducible and thus valueless:
    Econ101: infinite supply == zero price; // regardless of cost to create.

    Not monetizing copies but the work which yields their infinite supply instead is actually how the open source model of software production operates. As a car mechanic or home builder or burger joint would: I do an estimate, agree on a price for the new work (code | feature | installation | maintenance | etc.), then do the work once and get paid once for it, then seek more projects to do more work to get paid further. Instead of the insanity of selling ice to Eskimos -- or 1's and 0's to folks with computers -- I get paid proportional to my work.

    Conversely, since copyright does exist, I am not free to utilize any other available configuration of 1's and 0's already created and thus in infinite supply. In response to the ridiculous state of copyright whereby I am disadvantaged by my sane work practice and since I do not foolishly work for free then gamble my livelihood in the closed source copyright futures market -- A market where the work can go underpaid or unpaid if the market value didn't match the demand leading to job insecurity, and whereby the publisher middle men can drain the consumers of orders of magnitude more wealth than the cost to create the work (see how that works? The workers are disadvantaged, yes?); In response for being held to these ridiculous laws in order to make a living in society I choose to assert that my end users have all the rights and capabilities granted to any others who would monetize my work. Unable to rid the world of all copyrights, I expect businesses to obey them as I must. I merely expect that the business community enriched with unbounded advantages provided by GPL'd code not disadvantage me by disallowing my future work upon projects such code makes possible.

    Now, perhaps you are feckless enough to assume I can simply ignore copyrights if I want. Perhaps you assume a person can have security in their future while their small business breaks copyright laws at will, and allows others to close off future job opportunities by not releasing source code as the contract under which the work was performed would require. Perhaps you would say: "Just deal with bad actors making a less of a viable future for you." Perhaps you would say the blame lies with me for publishing my code in the first place, and ignore all the other compliant businesses which my work bolsters all of at once and I thus thrive upon. Perhaps you would think we allow ever more egregious infringement of the open source copyrights to proliferate while allowing the brutal punishing of end users for minor copyright infringements against proprietary licensors. Perhaps you would say, that I "might get used. Deal with it.", and then ignore that dealing with it is exactly what is being done in TFA...

  16. Any third-party code? by Todd+Knarr · · Score: 1

    Shouldn't any company including any third-party code in their products already have a process in place to make sure that code's all properly licensed and they're in compliance? This isn't about GPL or FOSS code. If one of your suppliers includes proprietary code in the firmware they supply to you that isn't properly licensed or you aren't following the license terms don't you have the same problem?

    1. Re:Any third-party code? by robmv · · Score: 1

      Exactly, forget about the GPL license in this case, the suppliers could have embedded malware on the product and never notice it. Fantec apparently didn't built the source they received. If I pay someone to do something for me I at least pay someone (an employee) to test if the package I recevied meet the contract I have with that supplier. If I requested source code for everything, that person must validate that

  17. Re:Premptive STFU to GPL white knighters by AlecC · · Score: 4, Insightful

    So you would make speculative IP creation impossible. Before you created any IP, you would have to establish contact with all possible customers and agree, and contract, a price for the IP you would create. This was the way the system used to work in the 18th century: Dr Johnson had to line up a number of sponsors before he produced his dictionary. The same applied for music: Bach needed a sponsor for his cantatas etc. The invention of copyright then produced an explosion of publishing: because people could retain the IP of their putative great works, they could publish speculatively (possibly with funding from a publisher), and if indeed it turned out they were great works, they would be repaid for their efforts,

    Your proposal would, I think, destroy the literature and magazine industries. Yes, magazines have subscribers. But why should I subscribe if I can get a copy as soon as the magazine is published? How can the editor of a magazine get enough readers to contract for something that they will receive free once the first user has received it? How can the writer who /thinks/ he has a great book make a profit from it when the first review copy can be Torrented for free? Why create any new work of literature? Music is slightly different: a live performance is different from a recording, and some groups distribute recordings for free in order to get fans at their concerts. But, in the days of the Kindle etc., an e-copy of a book is approximately as good as a hard copy.

    Literature and music are not the same things as burgers and car repairs. The invention of copyright had a massive positive effect on human culture. Very little of the music you listen to and the books and magazines you read would exist without it. Of course, I am not saying that the existing system is perfect - very far from it. Its application to programs and code is very defective. But in throwing the whole thing out, you are losing the good as well as the bad.

    --
    Consciousness is an illusion caused by an excess of self consciousness.
  18. Re:Premptive STFU to GPL white knighters by aristotle-dude · · Score: 1

    You publish your code. It might get used. Deal with it.

    Ah, then by that logic, we can ignore all copyright laws. Eureka!

    I have a question for you. Why is it that you can take literary works and sample from them without violating copyright but GPL'ed code is viral? If they are both based on copyright, why can't you take small samples of code and incorporate it into non-gpl'ed code? Isn't that hypocritical of you? Why is is that you create a derived work from a literary work and by just rewriting it, you have to pay no royalties and yet GPL advocates want the original author to be able to "steal" all of the derived works even it it almost completely refactored into a new codebase? Why is it that you can sample sounds from a song to create a derived work without paying royalties? Why is is that you can create a parody without paying royalties?

    What makes GPL'ed code so special? Is it based on copyright or not? In my opinion, if you publish code on a webpage inlined with the text of an article, it cannot be GPL'ed because the reader never had the opportunity to agree before reading the code and it cannot be unseen. In that case, the author is trying to retroactively license it after effectively releasing it in the public domain.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  19. Just no. by Anonymous Coward · · Score: 0

    When a whore makes her cunt publically available on the town square, it has already been violated by herself. She does not prove anything if someone equally sick sticks it in her. They are all just a sick bunch of fucks that should be dealt with in the loony bin.

  20. just write your own damn code by slashmydots · · Score: 1

    3rd party code is a fucking disaster no matter where you get it, who wrote it, or who sold it to you. When my company needed a supplemental CRM utility, I wrote it. It works perfectly and is still on version 1.0.0. Our current CRM software is so poorly laid out and coded that they people responsible would get a D if they're lucky in my 2-year technical college advanced programming course. I got the only perfect 105% score in that class in the college's history. What's the difference? In labor hours, it cost my company about $200 for me to write it. The main CRM cost about $45,000.

    1. Re:just write your own damn code by Anonymous Coward · · Score: 0

      still your earn jack shit, hehehe
      captcha: submit

  21. Re:Yes, when asked to comply the company lied. Ger by Kjella · · Score: 1

    The court opinion is six pages, Im guessing three of those are boilerplate. Are there any fluent speakers of German who can read through it and tell us the facts as expressed by the court?

    The court didn't really go into much of anything, in short it concluded that the source was incomplete which means no rights were granted by the GPLv2 which means their distribution was a copyright violation. That they didn't know about it seems entirely irrelevant to the ruling. In fact it's so totally absent that going by this ruling you might think that if your copyright is violated, you can sue every mirror and every one of them would be guilty, no matter how much good faith belief they might have it's legally distributed.

    --
    Live today, because you never know what tomorrow brings
  22. Or... by Stormy+Dragon · · Score: 1

    'Fantec is a reminder that companies should adopt a formal FOSS use policy which should be integrated into the software development process,' he writes. 'These standards should include an understanding of the FOSS management processes of such third-party suppliers. The development of a network of trusted third-party suppliers is critical part of any FOSS compliance strategy.'

    Or, they could just say "that's too much hassle, let's stop being involved in FOSS development".

    1. Re:Or... by icebraining · · Score: 1

      If they're not distributing the source, good riddance. Let them pay to build their own proprietary implementations.

  23. Re:Premptive STFU to GPL white knighters by sjames · · Score: 1

    If the sample is quite small, you probably could, regardless of the licence, but there would be some legal risks. Just like any other sort of work. For example, pick a popular novel, copy the 1st chapter and write a different story from there. Let's see if you survive the court battle. OTOH, lift a single line and you may be OK. Actually, with just one line, you're much more likely to be OK with GPL software than with a popular novel.

    The GPL violations that get people in trouble tend to be a lot more copying than any known interpretation of fair use would allow.

  24. WTF makes you think anyone said no fair use? by raymorris · · Score: 2

    > Why is it that you can take literary works and sample from them without violating copyright but GPL'ed code is viral?
    > If they are both based on copyright, why can't you take small samples of code and incorporate it into non-gpl'ed code?

    You can. Who said otherwise? Just as you can quote a few sentences from a book, you can copy a few lines from a GPL work.
    You can't copy-paste several pages from a typical book, under normal circumstances, and you can't copy-paste several pages from a GPL work without complying with the license.

    It may be a mistake to get into a discussion involving fair use on Slashdot since quite a few people here seem to think it means you
    can take whatever you want, from anyone you want, and do with it whatever you please. As it sounds like you know, fair use has a
    very specific definition. Generally, it means you can use a small sample of a work in a way that does not compete with the original
    work, such as quoting a book in a review. I've never heard anyone say you can't quote code in a code review.

    > Why is is that you create a derived work from a literary work and by just rewriting it, you have to pay no royalties and yet GPL
    > advocates want the original author to be able to "steal" all of the derived works even it it almost completely refactored into a new codebase?

    I'm not sure what you're on about here either, but you can't refactor a book either. You can write a new book on the same topic.
    You can't re-arrange the paragraphs by cut and paste, add a few words, and call it your own. Same with software. Maybe this
    will make it clear:

    It's illegal to shoot someone.
    is it illegal to shoot someone and give them a Coke?
    is it illegal to shoot someone and smile at them?

    It's illegal to take my code and distribute it without following the license.
    is it illegal to take my code and distribute it without following the license and also add your own code?
    is it illegal to take my code and distribute it without following the license and also change my code a little bit?

    Adding some of your own code to mine is the same as adding a Coke to the shooting. How would that make it okay?

    Following the GPL is nothing more than posting your changes, or giving them to your customers. Is that SO hard?
    You insist on selling my work, but can't post your own?

  25. I don't understand the confusion by mark-t · · Score: 1
    If they were given the code that was under the GPL under conditions that diverged from the GPL, then they are only in violation of the GPL if they further distribute it under different conditions from the GPL.

    One analogy that I'm particularly fond of in this matter is that if you receive a counterfeit bill and you somehow become aware that it is counterfeit, if you still try to spend it knowing that it is counterfeit, you are actually breaking the law. If you don't know that it's counterfeit, you aren't breaking the law, but you still don't have any legitimate right to try to use it as if it were genuine.

    Since this company evidently now knows (or should know) it is in violation of the GPL, they now have a choice... either comply with the terms of the GPL when they distribute the works, or simply cease distributing it completely. Anyone who already received illegitimate copies of the work before they were aware that it was supposed to be GPL'd have no more real recourse than people who might have come into possession of counterfeit currency when there was no knowledge of its counterfeit nature at the time of transfer.

  26. Not GPL but contact law by Anonymous Coward · · Score: 0

    The GPL is irrelevant. The company used used the software in its media platers had contractual obligations that it failed to full-fill. That these contractual obligations arose from a GPL license is neither here nor there. Despite what idiots think, GPL is NOT a special case in law, or a law of its own. GPL falls within standard legal frameworks.

    Of course Fantec lost with their "Not our problem, mate, someone else did the software- go hassle them". How the hell is that a legal argument. Fantec were the ones using and 'selling' software, so it was Fantec that had to meet their 'contractual' obligations with those responsible for creating the software- in this case following the rules of the GPL license.

    No court has ruled any GPL license to be invalid in the simple sense. It is the meta restrictions many open-source morons THINK open source licenses place on users that would almost certainly fail in court. Courts are not about upholding some nebulous philosophy. They will, however, respect that which falls under straightforward contract law.

    PS the conclusion of this article is garbage. All companies should be expected to honour any contractual terms they previously commit themselves to, without 'special' policies (or people, or departments) that exist merely to serve one very special form of one very small subset of possible contracts/licenses a company may involve itself with. Open source licenses should be straightforward so compliance is also straightforward.

  27. Thank you, that's unfortunate by raymorris · · Score: 1

    Thank you. I was hoping the court commented on the fact that they continued to infringe after having been notified, when (mostly) rectifying the infringement would have been simple.

  28. Compliance Really is Easy by Anonymous Coward · · Score: 0

    If you redistribute GPL code, just post it on your website (including changes that you have made). Why is this so cumbersome to comply with?

    The real issue is about the freedom of the code, not to be locked up in a binary blurb which becomes obsolete or makes the device obsolete. Our $15,000 3D printer had Redhat in it. When the company went bankrupt, there was no support. If I was not able to run e2fsck from a shell, we would have owned a $15,000 paperweight.

    The same can not be said for the many Palm Pilots, Windows CE devices (iPaq), or even old Macintoshes that I have thrown out.

  29. Re:Premptive STFU to GPL white knighters by ae1294 · · Score: 3, Insightful

    I agree that the idea of copyright is a good one. I hope most here understand that people who create something like music or software deserve a chance to make a profit before everyone can just download it for free and give nothing back in return. Open source works because there are enough people willing to give back something whether it's a bug report or a few lines of code. Everyone is better off if the software isn't really the thing that is being sold. Now sometimes the software is the thing that is being sold and those who create it 'closed source' deserve to make some money IF people want to use it. In my opinion the problem with copyright isn't the idea, it's a solid and workable method to encourage people and business to create new things. The problem like most problems is that the populace wasn't paying attention and what was a good idea was twisted into a terrible monster just as patents have been. I'm not saying its our fucking fault but I am saying we collectively need to fucking put in some effort to fix it. I have no idea if that's really possible anymore since government has become just as much a monster as copyright and patents, more so even.

    Anyway copyright should be limited, No more than 10 years I'd say. If you can't make your money back in that time frame than you fucked up. Patents I think should be something like 5 years or maybe 7. I don't know but I think a sold per-reviewed study could look at all the various industries and pick apart their profit reports and find the sweet spot for both copyright and patents. We have to wash away the greed and absurdness of both these good idea's gone bad. I can't image anyone who really thinks logically that someone should be able to live the rest of their life because they wrote one song 20 years ago. It just doesn't make any fucking sense. There is nothing magic about making music, movies or software. The only difference is once you have made them you have an unlimited supply of them which some people think means it should be worthless and free but if that was the case than no one would bother putting in the time. Sure you'd have some people doing it as a hobby but that isn't the same as doing it as a business and polishing whatever it might be over and over again because you don't have a day job taken up all your time.

    I think the US got copyright right way back when but we all closed our eyes for a moment and greed twisted it into something we all hate and despise. The only other thing I have to add is those caught using something that is copyrighted for personal use shouldn't be bankrupted for it. They should have to pay for the product plus a fine of a grand or three. Now people making bootleg copies should face much hasher penalties and corporations that knowingly screw over others should get their asses handed to them since it's going to be rare to catch them in the act.

    I'd like to see these problems fixed because I think it would lead to a new renaissance of creativity. Which was the whole point of these laws to begin with.

  30. A policy for GPL code, yeah right.. by nnull · · Score: 1

    "Mark Radcliffe, an IP expert and senior partner at DLA Piper who specializes in open source licensing issues, has analyzed the case—and argued that it underscores the need for companies to implement internal GPL compliance processes. 'Fantec is a reminder that companies should adopt a formal FOSS use policy which should be integrated into the software development process,'"

    Yeah, because that's gonna work!
    No, what's actually going to happen at businesses, they're going to implement a policy of "NO GPL" in their policy. Why? Because it's easier. This is why it's hard for businesses to accept GPL based code. When it now requires I hire a lawyer and consultant to actually figure out if I'm in "compliance", because I may obviously not have all the legal knowledge to figure it all out myself, I'm just not going to bother. Basically this has made the situation even worse and businesses are just going to look at GPL based code as a time bomb waiting to go off on them and refuse to deal with it. I'd rather hire another programmer to rewrite the piece of software I need, as it will be cheaper for me in the long run.

    1. Re:A policy for GPL code, yeah right.. by icebraining · · Score: 1

      Good. Let them spend their money reimplementing the wheel, it gives us Free Software developers a leg up. The company I work for has already replaced dozens of SAP installations thanks to community shared code.

  31. Ignorance of the code by msobkow · · Score: 1

    Being ignorant about what the code you're building a product from is no one's fault but the vendor's. I agree 100% with the ruling.

    Too many people like to try to play the "I didn't know" card. You're responsible for knowing what you're distributing, especially when you're charging for a product.

    I recently worked for a company that had to completely rework a piece of their product line because one developer decided he liked a GPL'd library better than a more-free-for-commercial-use library. It cost them a good three months of development time to rewrite the code with the rejected library.

    The developer in question thought free is free; he never read the details of the license, nor asked any of his coworkers about licensing issues. He wasn't fired or anything, but he was reprimanded.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:Ignorance of the code by Todd+Knarr · · Score: 1

      I recently worked for a company that had to completely rework a piece of their product line because one developer decided he liked a GPL'd library better than a more-free-for-commercial-use library.

      And this is why when I'm deciding what third-party libraries we can use in software, the first question is "What's the intended use of this software?". Some licenses are perfectly acceptable if it's internal-use-only or developer tools that wouldn't be for software we're distributing to others.

  32. Free is no longer free by davidwr · · Score: 1

    Free (open) is no longer free (as in beer) if compliance costs are high.

    This alone will drive companies to import only closed-source or BSD-style licenses where they are not obligated to provide the source and as such are less likely to be sued by someone who stumbles upon a violation that they themselves overlooked.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  33. Re:Yes, when asked to comply the company lied. Ger by Anonymous Coward · · Score: 0

    did they lie or did they not understand what an iptable was? Remember they outsourced to a third party so they may not have understood what the magic black box of code they were given did.

  34. So using GPL licensed code by viperidaenz · · Score: 1

    Is a risk for a company to do. Even after posting all the code they have online for free access, they get sued.

    If it was all proprietary, no one would be in court now. Lawyers wouldn't be getting rich.

    1. Re:So using GPL licensed code by Microlith · · Score: 2

      I see the liars are out in force today.

      Is a risk for a company to do.

      As much of a risk as any copyright violation is.

      Even after posting all the code they have online for free access, they get sued.

      Are you illiterate? They got in trouble precisely because they failed to comply with the license by blindly posting something that didn't actually work i.e. it was missing code.

      If it was all proprietary, no one would be in court now.

      Or they would be in court for violating someone else's license.

    2. Re:So using GPL licensed code by viperidaenz · · Score: 1

      It was what they were given. They didn't write the code. Who says they even know how to compile it themselves?

      They're distributing something they paid someone else to write for them.

      The third party they contract violated the GPL license. Fantec is distributing the binary with the source code they were supplied with. If they didn't alter anything, how are they violating anything?

    3. Re:So using GPL licensed code by icebraining · · Score: 1

      If they can't ensure the source is valid, they need to specify that in the contract with their provider, so that they can know demand a reimbursement from the costs of this action. Ignorance is not an excuse in many legal wrongs, and copyright infringement is no exception, otherwise all those people writing "NO COPYRIGHT INTENDED" on Youtube wouldn't be liable either.

    4. Re:So using GPL licensed code by Microlith · · Score: 1

      It was what they were given. They didn't write the code. Who says they even know how to compile it themselves?

      Then what are they doing in business? If they're making and selling media players, they should have someone on hand to manage the software, right? No? Then they're a worthless entity whose lawyers should all be fired for incompetence.

      They're distributing something they paid someone else to write for them.

      A fool's errand.

      The third party they contract violated the GPL license.

      Yes, they did as well. Chinese ODMs do constantly and it's shit.

      Fantec is distributing the binary with the source code they were supplied with.

      Thus they are not innocent, but also in violation due to a lack of due diligence.

      If they didn't alter anything, how are they violating anything?

      For one, if they didn't alter anything then why do they bother to exist? No value add, no reason to exist. Second, they are still redistributing which puts them under the terms of the GPL.

    5. Re:So using GPL licensed code by viperidaenz · · Score: 1

      So if I upload some GPL code to sourceforge, skip out a few files and let people download the binary, everyone who downloaded it can sue sourceforge?

    6. Re:So using GPL licensed code by Tripkipke · · Score: 1

      Nope, you are the one distributing, they just provide a platform for you to distribute your code

    7. Re:So using GPL licensed code by viperidaenz · · Score: 1

      Yeah right, and Mega Upload wasn't distributing anything either, just providing a platform for other to do so. Look how that turned out.

  35. Re:Premptive STFU to GPL white knighters by tibit · · Score: 1

    Stop with the bullshit, AC. You think there was no asking involved? Get a grip.

    --
    A successful API design takes a mixture of software design and pedagogy.
  36. Re:Premptive STFU to GPL white knighters by HaZardman27 · · Score: 3, Informative

    Nope, sorry. The fsfe.org article suggests that attempts were made to resolve the issue with no success prior to Welte seeking legal action. FANTEC made their own bed, and now they get to lie in it.

    --
    Apparently wizard is not a legitimate career path, so I chose programmer instead.
  37. Re:Premptive STFU to GPL white knighters by Anonymous Coward · · Score: 0

    Thanks for the clarification. That was not the picture I first got. :-)

  38. The second time they violated for the same, eh by raymorris · · Score: 1

    Interesting. That was in 2010, it seems, from this link:
    http://lawandlifesiliconvalley.com/blog/

  39. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 2

    We all know that a world without copyright would not work.

    Or more precisely: would be a poor world in terms of art and sciense and technology.

    Perhaps you have a car, the software in the car costed perhaps about 100 million dollars to be crafted.

    Do you really think anyone is able to pay so much money if he can not leverage it on sales of at least a million cars?

    How much does a our days movie production cost? A few hundret millions at least. Without copyright no one would be able to make money from a movie, except those who "pirate" it. So bottom line only hobbyists would make movies. They would need a second job to earn their living.

    Sure, you could imagine a world where people watching youtube videas click the like button later and pay a dollar. But is that not comunism which you equally hate?

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  40. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    Good post. In the "United States of Money" people pay a dollar for a burger, which they only can eat ONCE.

    But a dollar for a song is to much, which they can listen too for ever.

    Most people against copyright are those who never ever invented/crafted/made anything themselves.

    OTOH if you payed me 500 million and you had the super cool software idea. I would craft it for you, no problem.

    But for 100k? Certainly not, for that price I can work for anyone ...

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  41. Re:Premptive STFU to GPL white knighters by dylan_- · · Score: 1

    This was the way the system used to work in the 18th century: Dr Johnson had to line up a number of sponsors before he produced his dictionary.

    This is completely wrong. The Statute of Anne was introduced in 1710, when Johnson was less than one year old. And Johnson was contracted to write the dictionary by a group of London book-sellers who approached *him* for the task.

    --
    Igor Presnyakov stole my hat
  42. And it is similarly problematic for non GPL code. by Anonymous Coward · · Score: 0

    Got code from MSDN? Check if you're legally allowed to include it. One guy was convicted for using stuff from the description given in his MSDN documentation.

    If it had been BSD licensed code, it would have been equally illegal: it had no attribution on the code and no inclusion of the license terms as required by any of the BSD versions.

  43. Then you're a retard. by Anonymous Coward · · Score: 0

    The GPL compliance is pretty damn easy.

    GPL your stuff and you don't care.

    That isn't what's NEEDED, but it's the very very simplest option.

    And since you can't actually comprehend that, then you're a retard.

    PS if you have so much of a problem with licenses, you must be running with pencil and paper: all software is licensed and if you don't have a lawyer explaining the rights that you have to even use the software, given that you don't understand the GPL, rather indicates that you're a damned pirate and completely illegitimately ripping off other people's work.

  44. Re:Premptive STFU to GPL white knighters by icebraining · · Score: 2

    I earn a living writing copyrighted works (software), and I'm still against copyright. And it has nothing to do with not wanting to "pay a dollar for a song" - I'm more than happy to do so (as long as it doesn't feed the RIAA).

  45. Re:Premptive STFU to GPL white knighters by icebraining · · Score: 1

    There's plenty of good films being made outside of the hugely inflated machines of Hollywood. For example, Amour, winner of last year's Palme d'Or, had a budget of less than $9 million. Pulp Fiction had an even smaller budget ($8.5M).

    Movies take millions of dollars because it all goes into their pockets (it's called Hollywood accounting - look it up). If we cut the government monopoly and forced them to compete, budgets would adjust without hurting quality significantly. Maybe you wouldn't have Avatar, but I'm sure we can live without it.

  46. warned in 2010; were shipping entire Linux OS by raymorris · · Score: 1

    They had code to configure iptables, sure. Which they shipped with iptables and the rest of Linux. You realize their device needed needed an OS to boot, right?

    In 2010, when they were caught before, they signed a letter agreeing they understood that they needed to include an offer for the complete source, as they compiled it. Not some other version of Linux, the version they were using. That's really not complicated - if you ship GPL software, include an offer to provide the source you used.

  47. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    I hope most here understand that people who create something like music or software deserve a chance to make a profit before everyone can just download it for free and give nothing back in return.

    They do have a chance; if they fail, though, that is on them. I view government-enforced monopolies that encourage censorship and cause people to lose real property rights to be a disease.

    --
    Filthy, filthy copyrapists!
  48. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    We all know that a world without copyright would not work.

    How do you know any such thing? Do you have any objective evidence that that is true at all, or are you merely speculating what a world without copyright would be like? No, asking random questions and telling other people to come up with viable business models does not prove anything.

    Also, even if that is true, I still view copyright and its ilk as a disease similar to 'solutions' such as the TSA; even if they work (and I do not believe they do), they require me to give up freedoms in order to make them work, and that, for me, means they're not good solutions at all.

    --
    Filthy, filthy copyrapists!
  49. Re:Premptive STFU to GPL white knighters by Anonymous Coward · · Score: 0

    Most people against copyright are those who never ever invented/crafted/made anything themselves.

    Nice ad hominem.

  50. Fantec or Fantext? by wonkey_monkey · · Score: 1

    Fantec claims its third-party firmware supplier provided the company with appropriate source code, which Fantext made available online.

    In the same sentence, even.

    Odd that Firefox would red-underline the word "online." Also odd that it red-underlines "Firefox."

    --
    systemd is Roko's Basilisk.
  51. Re:Yes, when asked to comply the company lied. Ger by Anonymous Coward · · Score: 0

    When faced with the possibility of going to court, you spend the necessary time to evaluate your case.
    Even if they didn't know what an iptable was, I find it hard to believe that they didn't investigate it quickly after getting the threat.

    Anyway, it's all academic. The court doesn't care if they knew or not, they just care if they were in violation of the license.
    Well, perhaps knowledge and intent could count when deciding the damages.

  52. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    How do you know any such thing? Do you have any objective evidence that that is true at all, or are you merely speculating what a world without copyright would be like?
    There are plenty of history books and alas plenty of evidence ...

    they require me to give up freedoms in order to make them work ...
    Which freedom do you give up if there is a copyright?

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  53. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    It does not matter about "how much money" we talk.

    The point is the guy investing his time should have a chance to live from his time, aka earn at least enough money.

    Without copyright he can't ...

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  54. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    So you have a contract that forces you to give up your copyright and give it to your employer?

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  55. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    There are plenty of history books and alas plenty of evidence ...

    But there is no actual scientific, objective evidence (that I know of) that copyright in this day and age is beneficial. Even if you can point to past societies (or even a few current societies) that didn't have copyright, chances are they were/are vastly different than our current society, so you can't actually prove much at all by using them as examples.

    Which freedom do you give up if there is a copyright?

    Really? What happens if a website is hosting copyrighted material without permission and someone in power decides they don't like it? Censorship ensues.

    But that's just one freedom that is lost. I cannot use my own resources (money, materials, etc.) to replicate copyrighted material without first begging for someone else's permission; this, to me, is an infringement of physical ('real') property rights.

    --
    Filthy, filthy copyrapists!
  56. Re:Premptive STFU to GPL white knighters by Anonymous Coward · · Score: 0

    I earn a living writing copyrighted works (software), and I'm still against copyright.

    To be honest that doesn't mean much unless you are financially at risk if the software does not generate revenue. If you are paid an hourly rate or a salary you are not at risk. You can move to a new company where are new group of people who are at risk will go into debt paying you.

  57. Re:Premptive STFU to GPL white knighters by icebraining · · Score: 1

    The unemployment rate in my country for my age bracket is 38%. The idea I can "just" move to a new a company is not realistic.

  58. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    It is not an infringement on your physical / real properties rights. Just because you own 100 acres of land you can not replicate that with your money/materials.
    You have to buy it from someone else (or invade a country and steal it).
    You have a shiny house and want to build a new one? You need permission of the authorities to do that on your ground you actually own. Oh, if you don't own enough ground it falls back to above.
    You want to replicate a car? Well it might not be covered by copy right but by patents and other IP laws. Well, yes they are similar anoying as copyright is.
    Nevertheless you imagine you had particular rights (or options / possibilities ) in the material world, and not having them in the IP world you feel you got robbed of those rights.
    Fact is: you have no such rights or options in the material world. Nevertheless you feel robbed.
    Why do you need the permission to replicate some copyrighted material? What exactly do you want to do with that permission or that material? What is so hard to simply invent something similar with your own brain? Wow ... now we get close to the point. You can not write / imagine a story worth making a movy of. But you are able to "take" a story and make a movie of? And you want to do that without paying the author of the story?
    Well if you where in the movie business you would always pay authors for their stories.
    You simply "imagine yourself" being "deprived" of "rights" (priviledges) or "options" you would not have in the real world anyway.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  59. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    It is not an infringement on your physical / real properties rights.

    Of course it is.

    Fact is: you have no such rights or options in the material world. Nevertheless you feel robbed.

    And I think many laws need to be changed. What of it? You pointlessly listed all those examples and assumed I agreed with all those restrictions (and you could easily find differences between many of those and copyright infringement if you thought about them for two yoctoseconds), but that's not necessarily the case.

    Wow ... now we get close to the point.

    No, your pointless ad hominems aren't even close to the point. I feel it is arrogant for you to assume that no 'creators' want copyright abolished and that everyone who does want copyright and its ilk abolished must not be an innovator.

    You simply "imagine yourself" being "deprived" of "rights" (priviledges) or "options" you would not have in the real world anyway.

    I have no idea what your point is. I'm already well aware that there are laws and rules that aren't to my liking, so why go through the trouble of stating the obvious? Obviously, I think these things need to be changed.

    --
    Filthy, filthy copyrapists!
  60. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    Then try changing them.

    And also work on recreating how business and life works.

    To abolish all those laws and still have a life worth living we need to live in a "Star Trek" world.

    Where energy is free, people get housing food and cloth for free and only those who want do work and everyone can use / reuse / adapt everything.

    As long as the world is driven by money, and the need to work and make money it will be very difficult to get rid of IP laws and other property laws.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  61. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    To abolish all those laws and still have a life worth living we need to live in a "Star Trek" world.

    Simply incorrect. And I already mentioned that there are obvious differences between many of the examples you gave and copyright infringement.

    As long as the world is driven by money, and the need to work and make money it will be very difficult to get rid of IP laws and other property laws.

    No one is suggesting we get rid of property law entirely. The only thing suggested was that we get rid of government-enforced monopolies that impose artificial scarcity, encourage censorship, and infringe upon real property rights.

    As long as the world is driven by money, people need to come up with their own business models and not use government thugs to enforce artificial scarcity.

    --
    Filthy, filthy copyrapists!
  62. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    Sigh, then describe some of those business models ...

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  63. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    Crowdfunding, for one. But it is not up to me to find business models for these people. That's partly what the 'free market' is about. I'm not going to hand people business models just because they can't find one themselves; that's up to them and only them.

    --
    Filthy, filthy copyrapists!
  64. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    Lol, so you have no idea about what you are talking.
    Good that you admitted it now.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  65. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    Actually, I do. If you want a working business model, you're going to have to find it yourself; this is typically true in a free market environment. I hear some people talk about entitlement when they speak of copyright infringement, but how entitled do you have to be to seriously expect that other people come up with business models for you? That's your job, and if you fail, it's on you.

    Good that you admitted it now.

    Just like how a minute ago you claimed that 1 + 1 = 3, right? Oh, wait... that didn't happen.

    --
    Filthy, filthy copyrapists!
  66. Re:Premptive STFU to GPL white knighters by angel'o'sphere · · Score: 1

    There are not many working business models.
    I would say 90% of the world follows the same business model, and the other 10% have 3 or 4 others.
    Business models have nothing to do with free market.
    If you think there are business models (especial in the creative sector) that work without copyright/ip laws then publish them and farm in your nobel price for economics.
    As long as you have nomsuch idea/plan your are just hot air.

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  67. Re:Premptive STFU to GPL white knighters by cheekyjohnson · · Score: 1

    Business models have nothing to do with free market.

    But government-enforced monopolies that impose artificial scarcity and infringe upon real property rights sure do; in fact, they have little to do with the free market.

    If you think there are business models (especial in the creative sector) that work without copyright/ip laws then publish them and farm in your nobel price for economics.

    I don't need to; business owners are responsible for finding them.

    As long as you have nomsuch idea/plan your are just hot air.

    This entire comment is just an eyesore.

    There is no "hot air" here. The world would remain even without copyright, even if your delusions say otherwise. Even if it were true that copyright encouraged innovation, I'm not the type of coward who sells out everyone's freedoms in exchange for something (whether that be safety or increased innovation). I'm against the TSA, copyrights, patents, free speech zones, and a host of other nonsense that governments do to infringe upon people's freedoms, and frankly, I highly doubt anything you say could change that (especially since you just keep asking me to pointlessly come up with business models for other people, for some strange reason).

    --
    Filthy, filthy copyrapists!