Hi, I’m a maintainer of an OSS called TFLint. Let me ask about an OSS that use Hashicorp projects (BSL-licensed) source code.
- Should OSS with partial copy of source code change license to BSL?
- The BSL terms say “All copies of the original and modified Licensed Work, and derivative works of the Licensed Work, are subject to this License”. Also, according to FAQ 14, the modified version cannot be distributed under another lisence.
- On the other hand, FAQ 12 mentions copyleft requirements as a difference between BSL and AGPL/SSPL.
- As a concrete example, TFLint keeps a copy of Terraform’s internal packages for emulating Terraform language semantics. This is due to Terraform’s package internalization.
- Should OSS that uses BSL-licensed source code as a library change license to BSL?
- MariaDB’s BSL FAQ says that mixed code is licensed for both. In the absence of provisions like the GPL linking exceptions, should this also apply to the use of libraries like Go modules?
- Does the TFLint Ruleset powered by OPA violate BSL?
- I’m considering the possibility that this product will be recognized as a competitor to Sentinel.