Slashdot Mirror


id and Valve May Be Violating GPL

frooge writes "With the recent release of iD's catalog on Steam, it appears DOSBox is being used to run the old DOS games for greater compatibility. According to a post on the Halflife2.net forums, however, this distribution does not contain a copy of the GPL license that DOSBox is distributed under, which violates the license. According to the DOSBox developers, they were not notified that it was being used for this release."

16 of 399 comments (clear)

  1. Could you vultures wait? by Time+Doctor · · Score: 5, Insightful

    It hasn't even been a working week even before the people who gave us great things like the GPL'd quake 1/2/3 source got jumped on for slighting you trolls.

    --
    Check out ioquake3.org for a great, free, First-Person Shooter engine!
    1. Re:Could you vultures wait? by TheRaven64 · · Score: 4, Insightful

      I don't really know why ID are being blamed for this, since Valve is the distributor. Unlike ID, who gave us GPL'd Doom, Quake, etc, Valve gave us DRM'd Half Life, and deserve no sympathy when they get caught infringing copyright.

      --
      I am TheRaven on Soylent News
    2. Re:Could you vultures wait? by tuffy · · Score: 3, Insightful

      If any of us started distributing Id's copyrighted materials in violation of their license, I'm sure it'd take less than a week for their legal team to put an end to it.

      And I'm sure they wouldn't be very nice about it, either.

      --

      Ita erat quando hic adveni.

  2. Re:Does this mean by porkThreeWays · · Score: 5, Insightful

    This sort of thing isn't always on purpose. Some people think "open source" means they can use the code however they please. Programmers aren't always license experts. It seems so simple to us because we are around these terms on slashdot constantly, but there have been times where I made assumptions about close source code licenses that could have gotten me into the same trouble. The legal department doesn't review every single decision in an organization and its possible legal implications. It could have been a few guys that just didn't understand the GPL and it was missed because it wasn't the largest project in the company. Not defending them, but not everyone understands "open source" isn't the same as public domain.

    --
    If an officer ever threatens to taze you, say you have a pacemaker.
  3. Re:call me a noob... by Anonymous Coward · · Score: 3, Insightful

    > Now I may be wrong on which license DB uses
    It uses GLP v. 2.

    > it would mean that both DOSBox and the game shipping along with it would be required to release source code.

    No. They have not embedded DOSBox into their own code, so the GPL "virus" do not touch their code and do not apply to the games. They are however required to distribute (or offer to distribute) the source code for DOSBox.

    --
    MiniMax

  4. Re:Does this mean by Daniel+Phillips · · Score: 5, Insightful

    This sort of thing isn't always on purpose. Some people think "open source" means they can use the code however they please. John Carmack understands perfectly what the GPL is all about, and surely nobody needs to be reminded what a huge contributer he is to open source and open standards. Certainly an oversight and public humiliation is not in order.
    --
    Have you got your LWN subscription yet?
  5. Re:Developers not notified... so what! by babbling · · Score: 3, Insightful

    Yes, and so the fact that they hadn't contacted the developers in this case was relevant since otherwise they could've been using dosbox under another license that the developers OK'ed.

  6. Re:Does this mean by bluephone · · Score: 5, Insightful

    You're right, and I'm 100% certain that John did all the packaging of the old games himself, by hand, using DEBUG on an 8086 and monochrome screen.

    In reality, this was a business deal between id and Valve, and id probably handed over the playable binaries, and Value handed them to a small group to prepare for distribution and installation over Steam. So rather than blaming id, or claiming Valve did this with evil intent, let us combine two very powerful pieces of wisdom, "Never ascribe to malice that which is adequately explained by incompetence," and Occam's razor. It is most easily assumed that when Valve handed off the data to be packaged, the worked had the best of intentions by using DOSbox, but was inadequately informed about it's proper use and redistribution.

    --
    jX [ Make everything as simple as possible, but no simpler. - Einstein ]
  7. Transparently divisive rubbish. by Ed+Black · · Score: 5, Insightful

    Small oversight by (on id's part) a hugely prolific developer of GPL'd software. Easily corrected and pushed out to clients straight away.

    Attacking John Carmack for this precipitately is basically irrational. It also stinks of divisive trolling.

    The man's licensed (a great deal of) his own software under the GPL, for goodness' sake.

    1. Re:Transparently divisive rubbish. by ShinmaWa · · Score: 3, Insightful

      You are correct, but that's a whole different point than the GPs. The GP said that if you violate the GPL, your bridges are burned forever and ever, amen. You can't make it right, you can't fix it. One simple mistake and you are done forever.

      However, there's absolutely NOTHING the GPL that says that at all. The GPL is pretty straightforward, really: If you abide by our terms, you can distribute. If you don't abide, you have no right to distribute. Valve/ID are now abiding by the terms**, so they can distribute. Case closed.

      Because of their Steam technology, they were even able to retroactively distribute the copy of the GPL to everyone they had already distributed the software to. That makes them fully compliant with every distribution they've done. Case beaten like a dead horse.

      ** (This is assuming that Valve/ID will honor requests for the source code, of which I've not heard a yea or nay on.)

      --
      The /. Effect: Thousands of users simultaneously accessing a site to not read its content.
  8. Re:Does this mean by Dhalka226 · · Score: 4, Insightful

    It seems so simple to us because we are around these terms on slashdot constantly

    It's not simple at all. Start a discussion here about under what circumstances you do or do not need to distribute source and you'll still get a 20 post long thread with people going back and forth about who's right and who's wrong, debating what the words used in the license mean, etc.

    And people here should be some of the "experts" on the license.

  9. Re:Does this mean by GalionTheElf · · Score: 5, Insightful

    Can't believe this hasn't been pointed out yet but neither iD nor Valve are exactly garage enterprises. These are pretty big companies and you know, I find it really hard to believe that this never went past a lawyer. Programmers don't have to know anything at all about licenses and stuff like that because that's what the rest of the company is for.

    --
    I'm going over here and I don't know why!
  10. Re:Outdated Article by LWATCDR · · Score: 5, Insightful

    "I can't see how it could be an oversight. "
    A better question would be why would they do it intently?
    Id has often released their old game engines under the GPL.
    1. They had noting to gain by not including the license files.
    2. They fixed it as soon as they found they had left out the files.
    3. They did no harm to anyone.

    So why must you try to see evil when all the evidence points to a simple human error?

    This is why GPL zealots get on my nerves. They are all for copyleft, they hate closes source licenses, they hate software patents, and they hate DRM. But if someone fails to cross every t and dot every i when distributing GPL code then they are are plotting villains.

    They made a minor error and they fixed the error all before it even showed up on Slashdot.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  11. Re:Avoiding The Viral GPL by Macthorpe · · Score: 3, Insightful

    It does if you want to be listened to. Talking bollocks because everyone else is talking bollocks only ensures that they'll treat you like they do everyone else.

    Talking sense when everyone else around you has none is more likely to get you somewhere.

    --
    "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  12. Re:Avoiding The Viral GPL by BitZtream · · Score: 5, Insightful

    And this sort of thing is the reason companies are afraid of GPL. Back in reality, silly things like this are ignored because someone notices the mistake, fixes the problem, the authors of the original software are fine with it because it was a silly mistake that MADE NO DIFFERENCE TO ANYONE OTHER THAN PEOPLE PRETENDING TO BE LAWYERS. On the other hand, now big companies that could help make GPL'd software more common to the everyday user are now more afraid of using it. Why should they, its cheaper to pay for commercial software than to deal with all the bad press that can come from an honest mistake made by a bunch of raving GPL fanboys. Yes, I'm more than slightly annoyed with this kind of license bullshit.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  13. Re:Does this mean by Raenex · · Score: 3, Insightful

    That you can see the source code. Nothing more, nothing less. This is the literal definition, and the one most normal people (as well as MS) subscribe to. Microsoft makes it a point to use the term "Shared Source". There is no "literal definition" for such an ill-defined term. You can accept OSI's definition, since they have done all the marketing of that term and it has a lot of mindshare, or you can accept that people interpret it differently, in which case nearly anything goes, including public domain.

    That it means the same thing as "Free Software" -- i.e., licensed in such a way to preserve freedom -- except that it may or may not be copyleft. This is the OSI definition. Now that is complete bullshit. The OSI definition of open source does not "preserve freedom". It fully supports licenses that let derived versions become closed source -- like the BSD license.

    In neither case does it mean "public domain," Your 0/3. Public domain qualifies as "open source" as defined by the OSI. The OSI meaning of open source is an umbrella one, that includes the GPL, BSD, public domain, etc.