Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Saturday December 27 2014, @07:10PM   Printer-friendly
from the anything-is-better-than-nothing dept.

Two stories appeared recently, The problem with license trends in Bruce Byfield's Blog on Linux Magazine's site, and the other on ZDNet, titled The Fall of the GPL and the rise of permissive licenses which both point out some worrying trends in open source licensing.

The first point both articles make is that there is an increasingly cavalier choice of open software licenses selected by projects. Many projects seem to choose a license at random or simply adopt what ever license was in vogue on the platform where they started development. Aaron Williamson, senior staff counsel at the Software Freedom Law Center, discovered that 85.1 percent of GitHub programs had no license at all.

Byfield spends much of his article explaining just how hard it is to actually obtain any reliable statistics. So many software sites simply fail to mention licenses in their repository directories, that one is reduced to google searching for license names, which often shows nothing at all. There are few ways to gather any statistics other than brute force download or researching project by project. Byfield's point is that nobody has done this in a believable way.

The trend seems clear that those who do choose a license are increasingly choosing MIT/BSD virtually un-restricted licensing for new projects as opposed to any versions of the GPL. From the ZDnet article:

(Apache/BSD/MIT) ... collectively are employed by 42 percent. They represent, in fact, three of the five most popular licenses in use today." These permissive licenses has been gaining ground at GPL's expense. The two biggest gainers, the Apache and MIT licenses, were up 27 percent, while the GPLv2, Linux's license, has declined by 24 percent.

It could be that those NOT choosing a license are simply tired of the whole argument, realize they will never be in a position to enforce any license anyway, and simply cast their code to the wind and trust to the mantra of "prior art". You would think that the generation that grew up with Groklaw and the SCO wars would actually care about this issue. One would think that watching Apple take BSD from open source to closed source while hurling sue-balls left and right would have served as a warning.

Or it could be a realization that the restrictions imposed by the GPL and other "copyleft" licenses are, in their own way, almost as burdensome as some commercial licenses. Or maybe it is the subtle differences in the GPL, GPLv2, GPLV3, LGPL, LGVLv2, LGPLv3, Affero-v1, Affero-v2, (ad infinitum) are so confusing that even a comparison chart of license features is confusing and bewildering to many who just want to cut code.

Are those of us in the software industry just making a mess for the future with all these licenses? Have we thrown up our collective hands in despair? Has the GPL-style copyleft license outlived its usefulness?

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by metamonkey on Monday December 29 2014, @05:40PM

    by metamonkey (3174) on Monday December 29 2014, @05:40PM (#129991)

    The only things I'd consider releasing under a non-GPLed license are some libraries, simply because I think I'd be more likely to get improvements from the community by using a more permissive license like MIT.

    If I write a material design button library for Android 5, I'd like to share it, but I just don't think people would want to go through the record-keeping required by the LGPL. They're making a commercial app, they just want a damn button library, and they don't want to think about the implications of "infecting" their app with the GPL. Nor with making available the source for the portions of the library they used. It's just a lot of bookkeeping to get some pretty buttons. Instead, I think I'd be more likely to get contributions by using the MIT license. They'll use my buttons, wrap them up in their closed-source app, I don't care, and then probably share any improvements they made back. But if I LGPL it...I just don't think anybody would use it. I'd rather have wide adoption with non-guaranteed returns than low adoption with guaranteed returns.

    Completely different for a full-fledged project. That gets GPLed. But a library? MIT.

    --
    Okay 3, 2, 1, let's jam.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2