30 ms·
LLVM relicensing update and call for help
- viktorcode 5y agoMy question may sound naive, but why not use BSD zero close license from the start?
- yeahforsureman 5y agoApache-2.0 has corporate-friendly patent clauses missing from most other permissive licenses.
- ajkjk 5y agoThis kind of thing feels like such a waste of humanity's time. Is there an approach you can choose early in a project on that prevents ever getting in trouble later? I guess if I start some big library I will hope that everyone assigns the copyright for their contributions entirely to the project so that I never have to go through that nonsense. But I guess that has other ramifications.
- ilammy 5y ago> Is there an approach you can choose early in a project on that prevents ever getting in trouble later? 1. Never accept outside contributions in principle. Works fine for SQLite, for example. 2. Pick a well-known copyleft license and just stick with it. Works fine for Linux, for example. 3. Use a well-known permissive license that allows redistribution of modified code under a different license without burdensome conditions. Works for lots of projects. 4. Force contributors to assign copyright to an entity that people will trust forever. Ostensibly works for FSF folks, academia, etc. 5. Don't worry about it. Let others pay for lawyers doing law stuff. You can delay making the decision until you have at least a dozen of actual contributors.
- varajelle 5y agoThere is also 6. Have a CLA (contributor license agreement) that lets the project the right to change the licence. (Different from 4. because there is no copyright transfer).
- Avamander 5y agoCLAs are shaky, it might not be valid in some countries that e.g. do not allow reassigning copyright.
- chrismsimpson 5y agoZero clause MIT or BSD or the Unlicense are seemingly the only licenses that protect from the tyranny of copyleft licenses.
- josephcsible 5y agoWhy do you call copyleft "tyranny"? If overnight, every single piece of open source software were somehow magically relicensed to AGPLv3 only, would there be any negative consequences at all for anyone besides people who wanted to write non-free software?
- ajkjk 5y ago> besides people who wanted to write non-free software? Would there be any negative consequences besides the negative consequences? No, I guess not. Lots of people want to write non-free software, for instance for their jobs or businesses or hobbies.
- josephcsible 5y agoBut users can do even less with non-free software than they can with copyleft software, so calling the latter "tyranny" while simultaneously being okay with the former makes no sense at all.
- ajkjk 5y agoIt really doesn't. You're pretending like non-free software has no value and that's clearly nonsense. There's no argument with that pretense because it has no bearing in reality.
- josephcsible 5y ago> You're pretending like non-free software has no value I'm not saying it has no value or that it should all go away. I'm saying that its value doesn't come from being non-free, so it would be better if it had to be free instead.
- bawolff 5y agoI think rolling your own license is like rolling your own crypto: just say no.
- deleted 5y ago[deleted]
- vortico 5y agoThis might be the largest contributor relicensing project of any IP category: 2800 people and companies. 94% progress is impressive.
- throwaway81523 5y agoWikipedia changed its license around 10 years ago, I think.
- remram 5y agoThis was enabled by the license though (GNU Free Documentation License) so they didn't need to contact individual contributors.
- smitop 5y agoWikipedia was licensed under GFDL 1.2 or later, so relicensed by convincing the FSF to release an updated version of the GFDL (version 1.3) that adds a very narrowly worded clause allowing relicensing that pretty much only applied to Wikipedia.
- bombcar 5y agoWhich does point to the hidden danger of the FSF licenses when “any later version” exists.
- ChrisMarshallNY 5y ago> The copyright owner can be either an individual, for example the person who wrote the code originally; or a company, for example a company that employed the person who wrote the code. Here, there be dragonnes... I can easily see an IC agreeing to a relicensing, thinking they had full rights, but their employer, at the time, had a "shower clause," and trying to (and maybe succeeding in) getting that section of license nullified. At least, costing the LLVM a bunch of money and time. This was one reason that I made sure that my employer did not have a "shower clause," before starting to develop a lot of open-source software. Knowing them, I'll bet that people hired after me had to sign that away, but I was never made to sign anything like that; even retroactively. This is a mammoth effort, and I wish them well. I suspect they have already wargamed a lot of the possible issues.
- brnt 5y ago> The copyright owner can be either an individual, for example the person who wrote the code originally; or a company, for example a company that employed the person who wrote the code. Here be dragons indeed. This is flat out incorrect. In quite some jurisdictions, copyright is a nontransferable inalienable right any authors gains upon writing something, in perpetuity (can't even be transferred after death). Others, such as employers, may merely license is, sometimes exclusively.
- asdfasgasdgasdg 5y agoIs the distinction here really germane? If someone else holds an exclusive, transferrable, perpetual, sublicensable license to a work you produced, that's more or less the same as holding the copyright from LLVM's perspective. Of course all this only matters if they encounter a situation where it is difficult to determine the rightsholder, and they are not able to obtain agreement from all potential holders, and there ends up being a dispute.
- brnt 5y agoIn such jurisdiction, copyright attributions/assignments are simply not legally possible. We've had to scrap the one in place for on of our projects. The type of contract you should have contributors from such jurisdictions sign is a license to use. If you haven't, getting 'permission' is meaningless; the author possibly (in my experience: probably) doesn't know they're actually not legally able to agree to such a change.
- hahnchen 5y agowhy not gpl it D:
- dagmx 5y agobecause LLVM is used in a lot of places where the GPL isn't friendly for integration, and going to it would potentially require many other projects to relicense as well
- KZerda 5y agoBecause that would make llvm a lot less useful and a lot more restrictive on the kind of places the compiler infrastructure could be used in. LLVM would not easily be able to be used in places like mesa if it were under the GPL, for example.
- jagger27 5y agoApple wouldn’t let that happen.
- asdfasgasdgasdg 5y agohttps://foundation.llvm.org/docs/sponsors/ https://foundation.llvm.org/docs/sponsors/ Because the entities who spend the most effort on LLVM to support its construction and maintenance have no interest in the GPL. Even if the LLVM board of directors did vote to move in this direction (which would make little sense since most of them are employed by one of the sponsors), the sponsors would end up forking the entire project and the old LLVM would no longer have much relevance.
- tyingq 5y ago>m8r-9yw8a5@mailinator.com "/dev/humancontroller" That one should be fun. An anonymous mail account service.
- bombcar 5y agoThose will be the code to replace in the final step.
- gruez 5y agoLooking at the spreadsheet, it looks like his only commit is one that changes a bunch of %lu to %zu? I think that's trivial enough that it's not copyrightable.
- sour-taste 5y agoLLVM likely doesn't want to take the risk that a court could find it copyrightable if the author decides to file a lawsuit. My guess is that regardless of the triviality of the change they're requiring these agreements. I am not a lawyer.
- racingmars 5y agoThe article talks about options for remaining contributions for which they can't get in touch with the contributor, and says: "We can check if copyright even applies to the particular contribution. Very small contributions may not be covered by copyright, and hence may not need a license agreement."
- csunbird 5y agoIt is an anonymous e mail address, there is no way for anyone can actually prove that they are the contributer. not a lawyer, obviously
- Someone 5y agoI think that, depending on circumstances, it _can_ be trivial to prove in court. Examples: - If the contributor can prove they checked that specific mailbox during the period involved (for example from logs, or because the git repo of their system config shows they ran a cron script checking it) - If the contributor can have a few others state in court that they received other messages sent from that account around the time that must have come from them. - if the contributor mailed a few friends saying they contributed to LLVM, giving some details of the changes. I would expect courts to accept either as enough evidence.
- rectang 5y agoI found at least one name I recognize in the list, and I'm emailing that person. Hopefully we can get the long tail shortened!
- kbeyls 5y agoThank you!
- User23 5y agoOnce again the FSF is shown to be prescient. Their copyright assignment policy completely eliminates this problem.
- compiler-guy 5y agoIt eliminates this problem by creating another one. That you need to jump through a couple of hoops before you contribute. It is arguable which method is better.
- purple_turtle 5y agoAnd you need to trust project and future project controllers far more.
- StephanTLavavej 5y agoI opened the spreadsheet, and now I can't remove it from my list of Google Sheets (unlike most shared spreadsheets). Am I missing some obscure way to remove it, despite the Remove option being grayed out? (It does respect the "Owned by me" filter so this isn't the end of the world.)
- missblit 5y agohttps://jakebinstein.com/blog/google-drive-remove-option-grayed-out/ https://jakebinstein.com/blog/google-drive-remove-option-gra... > The right-click menu option with the trash can symbol can’t be clicked, but dragging the file over to the trash can works just fine.
- StephanTLavavej 5y agoThank you!
- Decabytes 5y agoRacket had to do this to go from lGPL to Mit, it was a long process. But they did it to make the language more accessible to developers. Developers are scared away by lGPL. Not all contributions were relicensed (resulting in code being rewritten), and we lost some code in the standard library (the csv parser). Now Racket is trying to make it more friendly to people by created a new language (called Rhombus for now) that is Racket without the parenthesis. They are playing the long game. But I hope these changes attract new Racketeers in the future
- still_grokking 5y ago> 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.
- dagmx 5y agoOut of curiosity, how does the GPL promise that versus the other common open source licenses? E.g MIT, BSD or Apache?
- purple_turtle 5y agoAs 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.
- deleted 5y ago[deleted]
- arka2147483647 5y agoAs 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.
- wyldfire 5y agoIs Rafael de Espindola on that list? He seems to have left on not that great terms and I can imagine him not being interested in supporting a license change. He was a prolific contributor.
- m0zg 5y agoI don't see why he would necessarily be against relicensing, frankly. His rejection of racial discrimination (which LLVM indirectly supported in that case) has nothing to do with licensing of the code.
- respindola 5y agoI guess I should be, but I don't see myself there. I haven't agreed to changing the license from the beginning: https://lists.llvm.org/pipermail/llvm-dev/2017-August/116370.html https://lists.llvm.org/pipermail/llvm-dev/2017-August/116370... I have contributed to LLVM while working for INdT in Brazil, Google in Ireland and Canada, Mozilla and Sony Interactive Entertainment (both in Canada). I probably also got a few patches in between jobs. Maybe they have tracked every patch to every employer and checked that the copyright is OK. Maybe they also rewrote the patches I did in between jobs, but I am not aware of any of that. While my reason for leaving LLVM are indeed different from the license change, having to abandon what was a fairly successful career for refusing to accept racism does make it less likely that I will reconsider.
- wyldfire 5y agoThanks for your contributions, Rafael. Do you ever regret your decision? I think I understand your perspective, but does it ever seem a bit impractical to move away over the CoC? It seems like Renato had similar misgivings but resolved to stay, for example. I can understand not wanting to agree to the CoC but what about continuing to contribute without agreeing? Also, the association with "outreachy" seems to have little impact on most developers work. Why let it bother you any more than the evils of companies who use llvm in their products supporting censorship or other things you might oppose?
- 5y ago
- Firehawke 5y agoMAMEdev hit this problem a few years back as well. Thankfully, the end result of code that needed to be ripped out and rewritten ended up being pretty small comparative to the whole project. A lot of that came down to there being no corporate interests involved, so no corp VS author arguments-- the worst ones to deal with were contributors who were adamant about keeping the original non-commercial license on their contributions.
- kayamon 5y agoDid they? That's interesting. No one ever contacted me about my contributions and whether I'd like to relicense them or not. I also noticed someone went through a long time ago and scrubbed a lot of names out of the source code entirely. Which is nice.
- Firehawke 5y agoAs far as I know, anything that they couldn't find an author on was eventually rewritten from scratch. That's the only time a name would be removed from a driver-- a complete redo.
- Firehawke 5y agoExpect to have someone reach out to you soonish, though, so we can be absolutely sure of what happened and correct any mistakes on our part that may exist.
- sam_bishop 5y agoIt was a good idea to post this to HN. Back when I was an LLVM contributor I was using an email address from a provider who is no longer around. I had no idea that the LLVM maintainers were trying to get a hold of me. There's probably a lot of overlap between LLVM contributors and HN readers.
- mattl 5y agoWhich provider? What was their domain name?
- dataflow 5y agoJust Ctrl+F their name in the spreadsheet.
- DominikD 5y agoAccessibility of that blog is absolutely abysmal. I read the post thinking "cool, too bad you have no contributor list easily available" but the problem is that links are no-underline white, just like the text itself.
- ksec 5y agodhs.org in case anyone is wondering.
- mattl 5y agoThanks for not telling me to use a Windows keyboard shortcut against a spreadsheet I didn't know existed.
- mattl 5y agoWhere in that page is a spreadsheet? Maybe I’m just not seeing it on mobile device.
- dataflow 5y ago
- tekknolagi 5y agoThanks for posting. I filled out the form.
- kbeyls 5y agoThat's great, thank you!
- m0zg 5y ago> That made it impossible for some companies to contribute. It did all right regardless. Why bother with coddling the companies? As someone who wants software patents to die in a fire, I think coddling of this kind is counterproductive in the long run. I do buy the rest of their arguments though.
- deknos 5y agoYou should perhaps post this also on reddit.com/r/programming and on similar sites.
- rhn_mk1 5y agoThis sounds unsustainable. Will a death of a core contributor mean that the project is stuck on a license forever?
- breakingcups 5y agoLast line of the article: "If copyright does apply and the code is still in the code base, we can remove the contribution. Depending on whether current contributors and users still value the effect of that contribution, it may need to be reimplemented."
- rhn_mk1 5y agoMy question is more about the general case. Is this something project authors should rely on in their future? Will it sometimes be easier to just fork? Would fork-relicensing be a good thing for the community? Or should there be a different approach to ownership that does not allow for relicensing? As a contributor to some projects that relicensed, I felt pressured to accept a change that was packaged up together with some major downsides.
- anticensor 5y ago> We can check if copyright even applies to the particular contribution. Very small contributions may not be covered by copyright, and hence may not need a license agreement. This is not the case in the United Kingdom, where the threshold of creativity for copyright is basically zero.
- supermatt 5y agoIs it really OK that the top of the license calls it "Apache License"? https://foundation.llvm.org/relicensing/LICENSE.txt https://foundation.llvm.org/relicensing/LICENSE.txt You need to scroll to the bottom to see that its not.
- the_mitsuhiko 5y agoYes because it is the Apache license. You are free to disregard the exceptions if you do not want to use them.
- matthewmacleod 5y agoYes – the software is licensed under the Apache license and you are free to use it as such. It also separately grants additional rights on top of that license, which don't affect your rights under the Apache license. It's similar to the GPLv2 with the Classpath exception.
- atq2119 5y agoFWIW, going with Apache 2.0 is/was a mistake. There is a clause in the license which implies that almost everybody who uses GitHub/GitLab/etc. to work on an Apache 2.0 project in the common workflows is in breech of the license. Specifically, the license says that every file with modifications has to include a corresponding notice that the file was changed. Nobody does this in practice. Unfortunately the license is simply badly written. Licenses like the GPL don't have this problem because they only require that a modified version of the software is clearly marked as such without stating how that marking should be done. So the metadata contained in the Git history should be enough to satisfy those superior licenses.
- vadfa 5y ago>Specifically, the license says that every file with modifications has to include a corresponding notice that the file was changed. Nobody does this in practice. Can't you achieve this easily with a git hook or something like that?
- bmn__ 5y agoIt can be achieved easily by manually editing the file. This is not the problem. People are in violation of the licence not because it's bothersome to produce the notice, but because they are unaware of the clause.
- est31 5y agoYeah it's horrible how Apache 2.0 has become an industry standard with this clause in place. I think this industry standard status was the main reason why LLVM has chosen it.
- minitoar 5y agoIf the corporate lawyers all agree it’s a standard and they don’t care about that clause then going with the license that the lawyers are all comfortable with seems like absolutely the right choice.
- ksec 5y agoI knew LLVM was doing a relicensing for a long time. And it was great that MAMAA all had lawyers agreeing on Apache 2.0 with Exceptions. ( Which in itself is probably a multi million operation ). I keep wondering they they did not make Apache 3.0 with all their problems solved. And instead becomes Apache 2.0 with Exceptions?
- orf 5y agoWhat happens if one of the contributors has died? I think it’s highly unlikely you’re going to get agreements from even the majority of the long tail, so moving towards the “end-game” before 2023 might be prudent.
- arlcode 5y agoCopyright gets passed on to their heirs.
- bla3 5y agoIt wasn't clear to me that "the list of remaining individuals and corporations we need to get agreements from" in "Call for help" was a link since it's not underlined and styled with exactly the same color, font, and font size as normal text. The link points to https://docs.google.com/spreadsheets/d/18_0Hog_eSwES8lKwf7WJal3yBwwcYfvPu1yCfZnTcek/edit?usp=sharing https://docs.google.com/spreadsheets/d/18_0Hog_eSwES8lKwf7WJ... If you know anyone on that list, consider reaching out to them with a link to this blog post.
- Lord_Nightmare 5y agoMy personal issue with the LLVM re-licensing and its exception clause is that it made no effort to deal with a few projects which had used the LLVM core in an LGPLV2.1 context, only those projects in a GPLV2 context. This screwed over a few projects which are unable to re-license to an apache2-compatible license. Offhand, I believe it affected the LGPLV2.1 licensed Wine/Codeweavers win32 emulation layer for running windows 32-bit programs on a 64-bit-only mac, and affected several other programs as well.