Slashdot Mirror


Survey Says GPLv3 Is Shunned

willdavid writes in to note a survey of open source developers conducted by Evans Data that indicates a real rift in the community over GPLv3. The survey was based on in-depth interviews with 380 open source developers and no estimated margin of error was given. "Just 6 percent of developers working with open-source software have adopted the new GNU General Public License version 3... Also, two-thirds say they will not adopt GPLv3 anytime in the next year, and 43 percent say they will never implement the new license. Almost twice as many would be less likely to join a project that uses GPLv3 than would be likely to join... [Evans Data's CEO said] 'Developers are confused and divided about [the restrictions GPLv3 imposes], with fairly equal numbers agreeing with the restrictions, disagreeing with them, or thinking they will be unenforceable.'"

14 of 382 comments (clear)

  1. Remember! by heinousjay · · Score: 5, Insightful

    Those restrictions are for your freedom. It is important to take freedom away to protect it. Truly allowing freedom would allow freedom to be taken away, and we can't allow that, so we've taken away some freedom to allow true freedom to flourish.

    I can't imagine why anyone wouldn't understand that perfectly.

    And I'm sure I'll get modded down, but before you do that, read through my first paragraph carefully and tell me what I've said differently than the GNU people.

    --
    Slashdot - where whining about luck is the new way to make the world you want.
    1. Re:Remember! by cromar · · Score: 4, Insightful

      GPL protects the freedom of the code, not the freedom of the developer. Big difference! If you want developer freedom, use the BSD license or some such. Different tools for different problems :)

    2. Re:Remember! by Bogtha · · Score: 4, Insightful

      I'm not sure if you are being sarcastic or not, but if you are, then please be aware that taking freedoms away to protect other freedoms is the basis of all law. You aren't free to hit me because you've had that freedom taken away from you.

      Unless you are an anarchist, you really have no basis for criticising the GPL in this regard, because you agree with this logic applied to different areas.

      --
      Bogtha Bogtha Bogtha
    3. Re:Remember! by A+beautiful+mind · · Score: 2, Insightful

      Ultimately, the GPL has begun the process that all legalese follows - it is now becoming too complicated to understand without paying a lawyer a very large sum of money. Given the target audience and the goals, this is not a good thing.
      Your beef is with the legal system, specifically legalese. It is the way to enter into official, legally binding agreements. Without the GPL using legalese, it would be worthless for it's goals. If you want to know what the GPL is about, be sure to read the documents on FSF's site that detail the intentions ("spirit") of the license.

      If you need legal certainty that the GPL is what it appears to be and FSF's interpretation and execution of codifying their intentions into legalese is correct, then you of course need to consult a lawyer. It is the legal system's fault normal people need a legal interpreter in order to conduct official business.
      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    4. Re:Remember! by synthespian · · Score: 2, Insightful

      Freedom is a category that relates to people.
      Freedom can never relate to an inanimate object, such as code.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  2. Oh dear! by mmcuh · · Score: 4, Insightful

    Oh dear! Another rift in the community, etc. Really, how many articles of this type have been posted to Slashdot in the last few weeks?

    And the statement "Just 6 percent of developers working with open-source software have adopted the new GNU General Public License version 3" is obviously false, since the vast majority of GPL-licensed software have copyright notices that say that the software is available "under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version" - which includes GPL version 3.

    What is this "Evans Data Corporation"? It would be interesting to see any other press releases they have written.

  3. No Margin of Error by DragonWriter · · Score: 2, Insightful

    The survey was based on in-depth interviews with 380 open source developers and no estimated margin of error was given.


    No doubt because it wasn't a random sample in the first place, so a "margin of error", which reflects the sampling error, would be meaningless.
  4. Re:Slow adoption is to be expected by JesseMcDonald · · Score: 2, Insightful

    Unless the committers transfer copyrights to a central body like in the case of the gnu tools and FSF, it is hard to move to another license if not bordering on impossible.

    Unless, of course, all the commits were "GPLv2 or later", in which case the project was effectively already under the GPLv3 from the moment it was released.

    --
    "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
  5. Re:Slow adoption is to be expected by fotbr · · Score: 3, Insightful

    Not necessarily. GPL version 3 only provisions do not apply to it, unless it is changed to be licensed under GPL 3 (only, or "or later").

  6. Gee duh. by heli_flyer · · Score: 2, Insightful

    The basic problem with this article is that it confuses Open Source with Free Software. They probably polled BSD, MSPL, Mozilla, etc developers and asked if they were planning to switch to the GPLv3, and as would be expected, most said "no". To me, it's just the obvious restated as something insightful.

  7. Re:Slow adoption is to be expected by fotbr · · Score: 2, Insightful

    They SHOULD all be counted as GPL2, because until they are explicitly moved to GPL3, they are not GPL3.

  8. Re:Slow adoption is to be expected by DragonWriter · · Score: 3, Insightful

    My point was that all these projects can be counted as GPLv3 projects, or is it that important that I formally fork such a project to be counted in the numbers?


    Well, yes, if it is not currently licensed with the restrictions in the GPLv3 (but merely allows other people to relicense their own redistribution that way), it is inaccurate to describe it as a GPLv3 project. I mean, by your argument, every project under a GPLv3-compatible license (or, presumably, in the public domain like SQLite) should be counted as a GPLv3 project because someone could conceivably redistribute a derivative of it under the GPLv3 at some point in the future.

  9. Re:Please undertand the GPL first by Grishnakh · · Score: 2, Insightful

    The GPL is all about preventing commercial use. If you bothered to think about the license(s) after reading, you would realize that.

    You're misinterpreting the words "preventing commercial use".

    What you really mean is "steal someone else's code, make a few modifications, and sell it as your own." That's basically stealing, because you've added no real value.

    What I mean by "commercial use" is "a company is allowed to use GPL code and incorporate it into their own product, as long as they release the changes to customers. That way they don't have to reinvent the wheel."

    If you're Linksys, for example, it's cheaper and easier to use Linux as the base OS on your router, rather than writing your own OS from scratch. But part of the bargain is that you have to share the modifications you make with your customers. This doesn't mean you have to provide your customers with schematics to the device, or even the source code to proprietary software that runs on top of Linux, but the portion that you borrowed from someone else (Linux), you have to provide the changes.

    However, if you're CrapSoft Inc., and want to make a special version of Linux to sell to the government for a juicy contract, but you want to keep your changes secret so the customer is dependent on you, that's not allowed. Do you honestly see a problem with that? If so, I suggest you get to work writing BSD-licensed workalikes to all GPL software, because you have no right to tell other software developers under what terms they're allowed to share and distribute their code.

  10. Waiting for GPL V4 by asscroft · · Score: 2, Insightful

    It doesn't seem fair to attack Microsoft with GPL V3 without also going after Google. Google gets to use GPL software without ever having to release source because they're not selling software, they're selling services. If Microsoft did that GPL V4 would come out faster than you can say Free Software.

    --
    because I have been enjoined by this Holy Office to abandon the false opinion which maintains that the Sun is the centre