LLVM relicensing update and call for help
blog.llvm.org
LLVM relicensing update and call for help
1–10 of 198 posts
Re: LLVM relicensing update and call for help
#2Re: LLVM relicensing update and call for help
#3Re: LLVM relicensing update and call for help
#4This might be the largest contributor relicensing project of any IP category: 2800 people and companies. 94% progress is impressive.
Re: LLVM relicensing update and call for help
#5Here, 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.
Re: LLVM relicensing update and call for help
#6Re: LLVM relicensing update and call for help
#7This might be the largest contributor relicensing project of any IP category: 2800 people and companies. 94% progress is impressive.
Wikipedia changed its license around 10 years ago, I think.
Re: LLVM relicensing update and call for help
#8why not gpl it D:
Re: LLVM relicensing update and call for help
#9This might be the largest contributor relicensing project of any IP category: 2800 people and companies. 94% progress is impressive.
Wikipedia changed its license around 10 years ago, I think.