News for hackers. Stuff that matters.
Re:LLVM relicensing update and call for help by still_grokking on Sunday November 21, 2021 @12:14AM (#29294361)
> Developers are scared away by lGPL.

I see GPL as a sign of quality and am attracted by projects using it. It's a promise nobody will ever take that thing away from me once I've started using it.

I'm a developer, by the way. :-)

Edit: Not to mention that some people even using GCC, Linux and Java.

Re:LLVM relicensing update and call for help by Vinnl on Sunday November 21, 2021 @04:58AM (#29295228)
People can't simply take away MIT-licensed code either - it grants you the right to use that code, and does so irrevocably.

What GPL does is make sure that code that is built on top of that will also be accessible to you, if the product it's used in is made public. But your own contributions and anything MIT-licensed it is added to will never be legally taken away from you.

Re:LLVM relicensing update and call for help by kzrdude on Sunday November 21, 2021 @08:10AM (#29296036)
With software, we don't see any frozen particular version as the main asset, but the continuity of the project is the asset. Otherwise we wouldn't de-value unmainted software so much. (The code is there, the license is clear, it could be used).

GPL makes sure the project's main strand of development stays accessible to you.

Re:LLVM relicensing update and call for help by Vinnl on Sunday November 21, 2021 @12:53PM (#29298166)
Well, unless the copyright holder of that code decide to use another licence in the future — then the snapshot that was licensed as GPL will remain available to you, but the main strand of development may not.

But yes, if this copyright is spread over many people (as it is in this case), then re-licensing is a herculean effort that is especially unlikely to succeed if it's designed to take away user rights, so in that sense a GPL'd project is more likely to remain open.

Re:LLVM relicensing update and call for help by dagmx on Sunday November 21, 2021 @12:30AM (#29294407)
Out of curiosity, how does the GPL promise that versus the other common open source licenses? E.g MIT, BSD or Apache?
Re:LLVM relicensing update and call for help by purple_turtle on Sunday November 21, 2021 @01:16AM (#29294552)
As I understand it:

MIT code can be freely taken into proprietary fork, with software modified and sold and no patches contributed.

Not sure how often it happens? Has it actually happened and is it a plausible attack? Nowadays at least AGPL is needed to defang "and we will sell it as service rather than selling software" workaround for GPL.

Re:LLVM relicensing update and call for help by pjmlp on Sunday November 21, 2021 @04:25AM (#29295124)
Apple derived OSes, the Windows TCP/IP stack before Windows Vista, PlayStation OSes, Nintendo and Playstation SDK, the BSD stuff taken into commercial UNIXes, just from top of my head, there are surely other examples.
Re:LLVM relicensing update and call for help by arka2147483647 on Sunday November 21, 2021 @03:12AM (#29294911)
As a practical matter, it means you cant just copy the files into your sources to some subdir, or you cant just link it statically. So you cant release a single-exe version of your project.

These are things some projects like to do, and GPL blocks that. So all thing considered, it may be easiest to just not use GPL code.

Re:LLVM relicensing update and call for help by chayleaf on Sunday November 21, 2021 @03:36AM (#29294978)
you can't copy MIT-licensed files without crediting it either.

And you can statically link GPL code, assuming you release the source to all app users. You might be confusing it with LGPL, which says you can link to proprietary apps dynamically, but have to release source in all other cases.

Re:LLVM relicensing update and call for help by shoozza on Sunday November 21, 2021 @04:14AM (#29295092)
You can also link to proprietary apps statically if you provide the object files: https://softwareengineering.stackexchange.com/questions/3127...
Re:LLVM relicensing update and call for help by rocqua on Sunday November 21, 2021 @04:18AM (#29295106)
I thought useing GPL code without modifications was acceptable without any licensing, or is that a 'lesser GPL' license?
Re:LLVM relicensing update and call for help by still_grokking on Sunday November 21, 2021 @04:40AM (#29295173)
You can use GPL code however you want.

You have only obligations when you distribute the results. Whatever you do in your private basement is completely unaffected by that. The GPL gives you freedom to do whatever you please. That's the whole point of it!

When you distribute binaries resulting form work based on GPL code than the people receiving those binaries (and only them) are eligible to get alongside the source code which allows them to rebuild the binaries you distributed to them. That makes sure that those other people also have the same freedom as you to do whatever they please with the programs and code. So the GPL preserves freedom among users of GPL code.

Re:LLVM relicensing update and call for help by orra on Sunday November 21, 2021 @04:25AM (#29295125)
You're thinking on the LGPL.

The GPL is the prototypical copyleft licence, designed to encourage the liberation of software, in part via its dependencies.

Re:LLVM relicensing update and call for help by rocqua on Sunday November 21, 2021 @04:07AM (#29295077)
Apple's OS is a fork of BSD without the fork being open source.
Re:LLVM relicensing update and call for help by kergonath on Sunday November 21, 2021 @04:35AM (#29295157)
It’s more complicated than that. It was not a fork, they just copied some parts of FreeBSD and OpenBSD. The kernel is XNU, and descended from Mach. Also, Darwin (the base OS, which includes the BSD bits) is open source. What isn’t is the GUI on top of it, which comes from OPENSTEP.
Re:LLVM relicensing update and call for help by chalst on Sunday November 21, 2021 @07:05AM (#29295773)
The open source part of Darwin/XNU doesn't deserve to be called a "base OS" since version 6, when Apple closed the sources of a lot of drivers. There's no hardware that will boot these systems if you restrict to what is available under the APSL.

https://web.archive.org/web/20091118172944/http://www.pureda...

Re:LLVM relicensing update and call for help by TravelPiglet on Sunday November 21, 2021 @04:38AM (#29295167)
Re:LLVM relicensing update and call for help by still_grokking on Sunday November 21, 2021 @01:20AM (#29294562)
GPL software, and extensions to it, are free and will stay like that.

That can't be said about software under the above mentioned licenses.

Re:LLVM relicensing update and call for help by dagmx on Sunday November 21, 2021 @01:29AM (#29294589)
I'm not sure how the GPL guarantees that it will stay like that anymore than those other licenses?

You can always relicense GPL content as long as everyone agrees. You can also change it to source on request versus always accessible.

Re:LLVM relicensing update and call for help by rocqua on Sunday November 21, 2021 @04:19AM (#29295109)
If you wrote the code, you can refuse to relicense.
Re:LLVM relicensing update and call for help by chayleaf on Sunday November 21, 2021 @03:37AM (#29294985)
key is "as long as everyone agrees"
Re:LLVM relicensing update and call for help by kitd on Sunday November 21, 2021 @03:13AM (#29294918)
OP also said it was a sign of 'quality'. Not sure how GPL promises that over other OS licenses.
Re:LLVM relicensing update and call for help by still_grokking on Sunday November 21, 2021 @04:17AM (#29295100)
I'm the OP and I'm not a native speaker but to my knowledge "quality" denotes in English besides a few other things the meaning of "value" (in the sense of worthiness) or (related to that meaning) "excellence". Something being high-quality makes this thing valuable.

I didn't mean "code quality", or the like, as a license can not enforce that obviously.

Re:LLVM relicensing update and call for help by systemvoltage on Sunday November 21, 2021 @12:39AM (#29294442)
> I see GPL as a sign of quality

Personal opinion is that BSD > GPL. Free as in properly free. I always donate to BSD license folks. When corporations use BSD software, they usually get engaged in the BSD community - under the stilts of management, suited lawyers and spreadsheet bean counters, it's just us programmer folk... you know. We like tinkering things and BSD software tends to have a different philosophy. Very welcoming to people who want to propel the world forward. Truly liberating, try BSD software.

Re:LLVM relicensing update and call for help by rapnie on Sunday November 21, 2021 @01:09AM (#29294527)
This is a matter of hot debate, and I don't want to trigger such discussion. AFAIU it is a bit of perspective of where the freedom is. With BSD there's more 'freedom' to incorporate with proprietary code, which eases commercialization. Companies like it better because of that and are likelier contributors. With GPL, while you can still monetize your code, protects the freedom of the Commons better by preventing the proprietary commercialization of open source code. And that is a reason why many businesses shun it. Personally I am in favor of the 4 freedoms of open-source and like to use (A)GPL.
Re:LLVM relicensing update and call for help by systemvoltage on Sunday November 21, 2021 @01:48AM (#29294648)
Yeah, agree it is hotly debated and not worth discussing further. I've recently been bitten by GPL and it's fresh on my mind how insidious it can be. That said, I work in commercial environment where BSD-licensed software is highly regarded.
Re:LLVM relicensing update and call for help by tarsinge on Sunday November 21, 2021 @02:25AM (#29294752)
Saying that corporations prefer something they can profit from without giving back vs something they can not is circular reasoning to me. Conversely if you look on the other side you'll see developers bitten by permissive software licences (MongoDB, Elasticsearch, ...).
Re:LLVM relicensing update and call for help by snovv_crash on Sunday November 21, 2021 @03:20AM (#29294938)
"without giving back" is a bit of an exaggeration. You could have a giant 20M line proprietary codebase, and if you incorporate a 20-line function from a GPL source, GPL says you need to relicense the whole thing.

I prefer the MPLv2, it lets commercial users actually use the code, but they still have to contribute back any changes they make.

Re:LLVM relicensing update and call for help by fn-mote on Sunday November 21, 2021 @08:22AM (#29296079)
> I prefer the MPLv2, it lets commercial users actually use the code, but they still have to contribute back any changes they make.

Sure, but how is this verifiable? Not verifiable = not happening.

Anyway, the idea of using a 20 line function in a 20M line codebase is a total strawman. Think of it from the 20 line function author's point of view - free money for corporate? They lack the expertise internally to write this function?? It's crypto code and getting it 100% right is extremely valuable? Then they need to be licensing it from the author.

It sounds like the idea you have here is that someone has licensed their code under the GPL but "didn't really mean it"? I think you should flesh out that side of your argument... why should corporate be permitted to use this code? Authors who are worried can release their stuff as MIT or CC0.

Re:LLVM relicensing update and call for help by snovv_crash on Monday November 22, 2021 @11:24AM (#29308122)
Companies have a legal department to make sure this kind of thing is followed, otherwise they have potentially huge liabilities.

For things that have a single author, the relicense option is possible, yes. But how about projects that have several?

To me the great thing about software is that other people can use the code I wrote without it costing me anything. I understand the various attitudes of wanting others to be bound by some terms of sharing the work they do too, or paying for a license, but at least from my experience it limits the adoption of my code, and I'd rather my code be useful in as many places as possible, with the only requirement being that if you fix any bugs or extend the functionality in a deeply intrusive way, you contribute that back.

Re:LLVM relicensing update and call for help by yeahforsureman on Sunday November 21, 2021 @05:12AM (#29295271)
Or lacking adequate case law, that's what the FSF et al. would want you to believe, anyhow. Although a bit vaguely drafted in this respect, the copyleft effect of GPL depends on the concept of a derivative work under copyright law. It would be a bit far-fetched to claim that in your example, the combination of the function and the codebase is a derivative of the function you incorporated.

Anyway, because the fact that people think GPL is that extensive is enough to create unnecessary problems, I too prefer MPL, where the copyleft scope is defined very clearly for its use case.

Re:LLVM relicensing update and call for help by reshlo on Sunday November 21, 2021 @07:05AM (#29295772)
I don’t think it matters whether the GPL can successfully be enforced against the example you describe. The license’s author intended that it could be, and that is what matters.

A philosophical disagreement with the license’s intent shouldn’t be overlooked just because the license might not actually be enforceable.

Re:LLVM relicensing update and call for help by rini17 on Sunday November 21, 2021 @06:50AM (#29295692)
So you would be actually fine with GPL if excerpts up to 1000 lines were not covered by copyleft?
Re:LLVM relicensing update and call for help by snovv_crash on Monday November 22, 2021 @11:23AM (#29308113)
No, the GPL is for what it's for, large codebases like Linux where you want to make sure it doesn't fragment too badly. Most code isn't this, though.
Re:LLVM relicensing update and call for help by systemvoltage on Sunday November 21, 2021 @07:44PM (#29301375)
Not all corporations are assholes. Many give back, many people contribute code often becomes the reason for the project to exist. They give life to open source projects by buying support and sustenaining their livelihood.

I am sick of this constant myopic view that all corporations are evil and people working there have no regard for open source development.

The truth is probably closer to being opposite than the anti-corporate crusader zeitgeist of HN. The point of the original comment was to express that behind all the corporations, there are just real people like you and me.

Re:LLVM relicensing update and call for help by tarsinge on Tuesday November 23, 2021 @04:26AM (#29316025)
I was only commenting on the reasoning. It's not a question of evil, just of basic business incentives.

> The truth is probably closer to being opposite than the anti-corporate crusader zeitgeist of HN. The point of the original comment was to express that behind all the corporations, there are just real people like you and me.

I'm a (small) business owner so I'm fully conscious of that. But it's a reality that past a certain size a corporation will optimize for its best interests given the current set of rules (law). If a company contribute to open-source it's not because they are nice, it's because the added value in marketing/hiring/commoditizing their competitors makes business sense, otherwise no matter their convictions people would get punished in their performance review, and the stock value would tank. Only specific corporate structures allow people inside a company to go against the baseline.

Re:LLVM relicensing update and call for help by Seirdy on Sunday November 21, 2021 @03:54AM (#29295032)
With few exceptions, I generally view the purpose of permissive licenses as "encouraging derivative software with EULAs and other restrictions", and the purpose of copyleft licenses as only allowing derivatives that don't restrict such freedoms.

Copyleft software therefore guarantees more freedom than permissively licensed software.

Re:LLVM relicensing update and call for help by reshlo on Sunday November 21, 2021 @07:16AM (#29295822)
The choice often isn’t between having a given derivative work be permissively licensed or copyleft. It’s between having the derivative work exist at all or not.

As a software author, choosing a license that requires people to be subject to more conditions to use my software is giving them less freedom, not more. If someone makes a derivative work with a restrictive license, that doesn’t make my software any less free.

Re:LLVM relicensing update and call for help by fn-mote on Sunday November 21, 2021 @08:32AM (#29296111)
> that doesn’t make my software any less free

You might say it makes your software less yours, though.

A restrictive license protects your interest in the code. After all, that's why companies are releasing their code under restrictive licenses.

100% agree there's a tradeoff of this with popularity, and it will never matter for almost everyone. But the people for whom it does matter get upset sometimes --- licensing is a choice that needs to be made with eyes wide open.