News for hackers. Stuff that matters.
Re:What is copyleft? by anjbe on Monday August 15, 2016 @09:25AM (#12290228)
Discussions of copyleft versus permissive licensing always seem to cover the same “freedom for users versus freedom for developers” clichés and the same tired slavery metaphors.

My dislike of copyleft is emphatically not because I want to enable proprietary software. I hate proprietary software, and don’t use it on my machines.

No, my biggest complaint about copyleft has always been that it prevents other free software from being able to use it. Copyleft licenses actively lead to incompatibility.

Remember when LibreDWG, an AutoCAD file parser, couldn’t be used in various free software CAD projects, because LibreDWG is GPLv3+ and FreeCAD, etc were GPLv2 only? http://libregraphicsworld.org/blog/entry/libredwg-drama-the-...

If FreeCAD had been under a permissive license, it would have been able to link against LibreDWG. If LibreDWG had been under a permissive license, FreeCAD would have been able to link against it. If they were both under a permissive license, they would have been able to be linked together and share code directly!

How about when NYC released open building and address data? A laudable move, one that helped several open source projects, the largest probably being OpenStreetMap. OpenStreetMap is under a copyleft license, and though they benefit from NYC’s data, due to the licensing NYC can’t make use of OpenStreetMap’s improvements without a convoluted parallel construction scheme: https://www.openstreetmap.org/user/lxbarth/diary/23588

A common response is that the onus is on NYC to release their data under a copyleft license so they can benefit. But there are often significant (even legislative!) barriers to doing that, especially in the United States where government entities are often required to release data to the public domain. How about changing that legislation? Well, if you had initiated such a legislative reform just a few years ago OSM would have been under the Creative Commons BY-SA—which is incompatible with OSM’s current license, the ODbL.

Remember how much grief has resulted from the unclear (or perhaps too clear) licensing status of ZFS on Linux?

Releasing software and data under the freest, most permissive license possible prevents such a thing from ever happening. I would rather allow a hundred Chinese featurephone vendors to lock down their crappy derivatives of my code than use my copyright to prevent a free software project from using my code in good faith.

Re:What is copyleft? by the_why_of_y on Monday August 15, 2016 @03:15PM (#12292700)
In the software case this is a real (and quite stupid) problem, and it is specific to the GPL (and AGPL) license, in particular if projects use it against the recommendations of the FSF as "version N only".

However it's not necessary to resort to permissive licensing, as there are many copyleft licenses that avoid this problem, such as LGPL, Mozilla's MPL, or Eclipse's EPL.

Re:What is copyleft? by cyphar on Monday August 15, 2016 @09:32AM (#12290282)
I view it as a personal choice for what you find important. Personally, I would prefer that my software not be used rather than it be used in a way that takes away users' freedom. You clearly think differently and are entitled to think differently.

Maybe you might consider using the MPLv2? It's a weak copyleft license that allows sub-licensing to other copyleft licenses (and inclusion into lax licensed projects without re-licensing the original project). Unfortunately, it suffers from not being strong enough to cover a "derived work" and only effectively copylefts files. But IMO that's better than nothing.

Re:What is copyleft? by anjbe on Monday August 15, 2016 @09:50AM (#12290391)
> Personally, I would prefer that my software not be used rather than it be used in a way that takes away users' freedom.

But by releasing my library under a free license that’s incompatible with someone else’s free license, I drastically restrict the ability of people to use my software.

This isn’t an academic limitation—this has a real impact in the real world. Just ask any packager who’s had to deal with “GPLv2 only” versus “GPLv3 or later” incompatibilities. Much free software cannot use the functionality provided by my free library.

I’m not talking about the right to redistribute proprietary derivatives here. I’m talking about that most fundamental of software freedoms, freedom 0: the freedom to run the program as you wish, for any purpose.

Re:What is copyleft? by cyphar on Monday August 15, 2016 @10:25AM (#12290616)
> I drastically restrict the ability of people to use my software.

There are no restrictions on usage in any free software license. There are restrictions on distribution of modified versions in the GPL. So you're only restricting the ability of developers to use some code that you've written to make a new program. Is this suboptimal? Yes. Is it necessary? Yes. Any other method of licensing would allow for proprietary forks to be made from your software. Whether you agree that is a problem or not is besides the point -- the purpose of copyleft is to make it impossible for proprietary software developers to create proprietary versions of the software. Unfortunately in reality it happens to also disadvantage some free software developers.

There are (soft) solutions to this: always use GPLvX-or-later to future-proof your licensing choices, encourage others to do the same.

> I’m talking about that most fundamental of software freedoms, freedom 0: the freedom to run the program as you wish, for any purpose.

Users are not encumbered by any of the GPL requirements. If a user just wants to use a program (or give copies to people), they will never encounter license incompatibility. Developers are the only people who have to worry about this, and I would argue "the 'freedom' to create new software under a different license" is more of a privilege than a right. Is it important? Yes. Is it as important as (or more important than) preventing proprietary forks? I don't think so.

Re:What is copyleft? by anjbe on Monday August 15, 2016 @11:16AM (#12291001)
> There are (soft) solutions to this: always use GPLvX-or-later to future-proof your licensing choices, encourage others to do the same.

How is this a “solution” to disadvantaging free software developers? LibreDWG was licensed GPLv3-or-later and it didn’t help FreeCAD one bit. If Linux had been licensed GPLv2-or-later it would not have improved the ZFS situation at all. There are many existing codebases under many free licenses out there; new software under any GPL version often cannot be incorporated in those projects, but new permissively licensed software can.

> Users are not encumbered by any of the GPL requirements. … Developers are the only people who have to worry about this…

“Users,” as you call them, are certainly indirectly encumbered. When LibreDWG provides DWG file parsing, but is licensed in such a way that FreeCAD cannot use it, users cannot use it.

And I strongly dispute the distinction that you make. The Free Software Definition doesn’t divide people into groups of “users” and “developers, who are not users.” Someone who links software against a library is just as much a user of that library as someone who runs the code indirectly through LibreOffice. When complicated licenses proliferate and decrease compatibility, it prevents free software from being incorporated with free software. That certainly violates the spirit of freedoms 2 and 3.

Re:What is copyleft? by cyphar on Monday August 15, 2016 @03:47PM (#12292903)
> LibreDWG was licensed GPLv3-or-later and it didn’t help FreeCAD one bit.

The problem is that FreeCAD isn't licensed under GPLv2-or-later. But LibreDWG's code can be used under a GPLv4 (when it comes out) license, so at least you don't have two cases of this problem.

> it would not have improved the ZFS situation at all.

Yes, because Sun intentionally created a GPL-incompatible license and Oracle continues to perpetuate that. What's really troubling is that the Sun folks take it as a point of pride that their license is GPL-incompatible and don't consider it to have been a mistake.

> When LibreDWG provides DWG file parsing, but is licensed in such a way that FreeCAD cannot use it, users cannot use it.

If we're going to play the "theoretical software that might've been written" game, then I could argue that not copylefting your software also indirectly encumbers users because the users' friends may start using a proprietary version of a free software program that is incompatible.

> The Free Software Definition doesn’t divide people into groups of “users” and “developers, who are not users."

Developers are users. And developers have the same set of freedoms as users. However, there are certain privileges that developers can also have that don't make sense to users -- those privileges are not essential freedoms under the Free Software Definition. "The right to create a fork under another license" does not appear in the Free Software Definition, no matter how you try to twist it. Developers are allowed to link software against a library under a free license, they just have to follow the license rules. Now, if they (or other developers) have made license choices that restrict them in that department it's not the fault of the license. Is it a shame when that happens? Absolutely. But talking about how lax licenses solve all of these problems (while dismissing the downsides) is just being disingenuous. We have a perfect case study of copyleft working -- the Oracle proprietarisation of OpenSolaris. Had OpenSolaris been under a lax license, Oracle would probably still own the technical talent for Solaris (and it would have become a large proprietary software machine). That didn't happen because of copyleft.

Re:What is copyleft? by aylons on Monday August 15, 2016 @10:33AM (#12290677)
> But there are often significant (even legislative!) barriers to doing that, especially in the United States where government entities are often required to release data to the public domain. How about changing that legislation?

If it is public domain, it may be incorporated at software licensed in any form, even whole proprietary.

Also, public data must be public domain, but software used by government doesn't.

Re:What is copyleft? by michaelt on Monday August 15, 2016 @11:25AM (#12291063)
I believe the poster's point was:

If the government is required to release the data as public domain; then it's integrated into OpenStreetMap which is copyleft; then a correction is made to OpenStreetMap; the correction can't be merged back into the public domain data.

Thus the copyleft project, in their attempts to stop people freeloading on their work without contributing back, have freeloaded on someone else's work without contributing back.

Re:What is copyleft? by brudgers on Monday August 15, 2016 @12:50PM (#12291616)
[IANAL]

One of the features of GPL is there is low administrative overhead in regard to legal matters when accepting contributions. The legal simplicity comes out of copyleft fully utilizing strong copyright and under GPL authors do not give up any rights.

On the other hand, placing a work in the public domain requires the author to give up their rights under copyright. Public domain is not a license. It is a legal sibling, not a child, of copyright. The result is that public domain works require legal administrative overhead in order to accept contributions...for example, an organization may find it necessary to create and maintain documentation regarding how and when each outside contributor placed their work in the public domain. Some open source licenses, such as Eclipse, also require similar record keeping.

That's not to say that GPL's reliance on the same classes of strong copyright law that the entertainment industries see as useful is necessarily unproblematic.

Re:What is copyleft? by anjbe on Monday August 15, 2016 @11:07AM (#12290914)
Sorry, but I don’t understand the purpose of this reply. The point I was making was that modifications to public domain data incorporated into OpenStreetMap cannot be used to improve the original source, because the OpenStreetMap copyright adds restrictions to the data.