The lack of reaction from Hashicorp on the request to change their license back would, at least on the surface, seem to the be start of the end of Terraform. All the utilities that use the libraries from Hashicorp (tfenv, terraform-docs, tflint, pre-commit handler for Terraform are 4 that come to mind) are now going to also need upgrading in some fashion. I wish Hashicorp could have shared the information that they would seem to have about who is actually/currently incorporating Terraform into competitive products (otherwise why waste the time and effort to make this change if there is no benefit). The sad thing is, but doing this licence change ... AND the fork now existing ... those competitive products can now be further developed unrestricted (I think) and so would seem further defines the start of the end of Terraform.
#Question: won't hashicorp sue OpenTF as they forked their codebase? and will use it? or it can't because it was opensource, but now it is not anymore so it can sue technically, right? please describe.
Short answer, no they can't. The license change is not (and can't be) retrospective. The code previously released, downloaded and copied up until the license change was under the MPL license and that doesn't change. What HashiCorp have done is announced that future releases of their projects will adopt the BSL license. This doesn't affect code already released. If you download software under the MPL license, you're free to continue to do whatever is stipulated in that license, for ever. Any code submitted to Terraform since the license change is licensed under BSL and not open source, the OpenTF fork only contains code that was covered by the MPL open source license. Hope this helps.
The lack of reaction from Hashicorp on the request to change their license back would, at least on the surface, seem to the be start of the end of Terraform. All the utilities that use the libraries from Hashicorp (tfenv, terraform-docs, tflint, pre-commit handler for Terraform are 4 that come to mind) are now going to also need upgrading in some fashion.
I wish Hashicorp could have shared the information that they would seem to have about who is actually/currently incorporating Terraform into competitive products (otherwise why waste the time and effort to make this change if there is no benefit).
The sad thing is, but doing this licence change ... AND the fork now existing ... those competitive products can now be further developed unrestricted (I think) and so would seem further defines the start of the end of Terraform.
Hashicorp be like: "I changed the contract, pray I don't change it further"
#Question: won't hashicorp sue OpenTF as they forked their codebase? and will use it? or it can't because it was opensource, but now it is not anymore so it can sue technically, right? please describe.
Short answer, no they can't. The license change is not (and can't be) retrospective. The code previously released, downloaded and copied up until the license change was under the MPL license and that doesn't change. What HashiCorp have done is announced that future releases of their projects will adopt the BSL license. This doesn't affect code already released. If you download software under the MPL license, you're free to continue to do whatever is stipulated in that license, for ever. Any code submitted to Terraform since the license change is licensed under BSL and not open source, the OpenTF fork only contains code that was covered by the MPL open source license. Hope this helps.