You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Continuing the conversation from #919 as advised by Sebastian...
Overnight, tens of thousands of businesses, ranging from one-person shops to the Fortune 500 woke up to a new reality where the underpinnings of their infrastructure suddenly became a potential legal risk. The BUSL and the additional use grant written by the HashiCorp team are vague. Now, every company, vendor, and developer using Terraform has to wonder whether what they are doing could be construed as competitive with HashiCorp's offerings. The FAQ provides some solace for end-customers and systems integrators today, but even if you might be in the clear now, how can you build confidence that your usage won't violate the license terms in the future?
The goal of Hashicorp is pretty clear -- prevent 3rd party providers from offering Hashicorp's own products and charge for it without Hashicorp gaining anything. In fact, you can even use Terraform to build and host a product that's competitive to Terraform, using Terraform v1.6+! As long as what you're building and commercially offering doesn't share Terraform v1.6+ source code. This is clarified in their FAQ:
The BSL license does not prevent developers from using our tools to build competing products. For example, if someone built a product competitive with Vault, it would be permissible to deploy that product with Terraform. Similarly, if someone built a competitive product to Terraform, they could use Vault to secure it. What the BSL license would not allow is hosting or embedding Terraform in order to compete with Terraform, or hosting or embedding Vault to compete with Vault.
This means, their license change to BSL 1.1 actually doesn't affect 99% of Terraform users in any way. But the way it is worded (esp. in the paragraph I quoted above) seems to be aimed at causing undue alarm among the readers. To help a reader become more informed about what's actually changing, I think the best way is to link to Hashicorp's FAQ at least. To this end, I've made a pull request #934 with the appropriate change.
I think the manifesto should provide a more balanced perspective on the situation, and help your readers be informed on the subject by encouraging them to read Hashicorp's original announcement and its associated FAQ. What do you guys think?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Continuing the conversation from #919 as advised by Sebastian...
The goal of Hashicorp is pretty clear -- prevent 3rd party providers from offering Hashicorp's own products and charge for it without Hashicorp gaining anything. In fact, you can even use Terraform to build and host a product that's competitive to Terraform, using Terraform v1.6+! As long as what you're building and commercially offering doesn't share Terraform v1.6+ source code. This is clarified in their FAQ:
This means, their license change to BSL 1.1 actually doesn't affect 99% of Terraform users in any way. But the way it is worded (esp. in the paragraph I quoted above) seems to be aimed at causing undue alarm among the readers. To help a reader become more informed about what's actually changing, I think the best way is to link to Hashicorp's FAQ at least. To this end, I've made a pull request #934 with the appropriate change.
I think the manifesto should provide a more balanced perspective on the situation, and help your readers be informed on the subject by encouraging them to read Hashicorp's original announcement and its associated FAQ. What do you guys think?
Beta Was this translation helpful? Give feedback.
All reactions