3 ms·
> All HashiCorp have done is made their own future contributions subject to BSL, not relicensed any previous contribution, There's are only 2 .go files left in
by pxc 3y ago
> All HashiCorp have done is made their own future contributions subject to BSL, not relicensed any previous contribution,
There's are only 2 .go files left in the hashicorp/terraform repo on GitHub which still have MPL-2.0 in their license headers, so either there are virtually no such contributions left in Terraform or they have in fact attempted to relicense code.
This looks like relicensing to me: https://github.com/hashicorp/terraform/commit/53c34ff49cfbc1f70d7cdd3dca8040551c53737a https://github.com/hashicorp/terraform/commit/53c34ff49cfbc1...
Btw, no .go file that you still show up in `git blame` for has an MPL notice header.
- jen20 3y agoI will follow up on that, it was not the case even quite recently. If they really have rewritten all code, then great - I have no problem with this!
- pxc 3y agoReplacing code whose license you don't want is definitely a fair-and-square way to manage a project and change the overall terms under which you can distribute it. (As it happens, that tactic is often essential to efforts to open-source formerly proprietary projects, too.)
- therealpygon 3y ago*Provided that the replacement is not simply a rewritten version of the same code that achieves the same result through overwhelmingly similar methodology.
- jolux 3y agoThe function of code is explicitly not protected by copyright and the breadth of this exemption was clarified and expanded by Google vs Oracle.
- chris_wot 3y agoThe LibreOffice project faced a similar dilemma and have carefully kept the old licenses in their files, and new license in new code in new files.
- asddubs 3y agowhat license did they change to/from?