Digger here
Our statement: https://medium.com/@DiggerHQ/diggers-statement-on-the-hashic...
The OpenTF Manifesto
11–20 of 392 posts
Re: The OpenTF Manifesto
#12Massdriver was designed to be infrastructure-as-code agnostic from day 1.
Our goal has been to help companies get great operations, compliance, and security posture from day one.
While Massdriver is not a competitor to HashiCorp, the license language is extremely vague and leaves any infrastructure company running containers for their customers wondering if HashiCorp will consider them a competitor tomorrow.
We are proud to be providing development and community support for this initiative.
Read our statement here: https://blog.massdriver.cloud/posts/2023-08-14-opentf-commit...
Re: The OpenTF Manifesto
#13Part of me hopes a fork comes out of this. I mean maybe features like this PR[1] for local state file encryption can then finally get merged. [1] https://github.com/hashicorp/terraform/pull/28603
I did see https://github.com/diggerhq/open-terraform but have no idea if it is related. And I’m sure there are others. What I’ll be interested to see with the forks is how they will practically be maintained. All the bug and security fixes that HashiCorp is writing can’t just be cherry-picked into these forks (I think?), so what exactly are they supposed to do?
Update: and in the past hour this repo is gone.
Re: The OpenTF Manifesto
#14[flagged]
Re: The OpenTF Manifesto
#15I love it. The list of "pledged companies" is literally just a list of all the offenders that Hashicorp are trying to shake off.
These people have seriously contributed back to the Terraform community. Terraform doesn't have a test suite- Grunt made Terratest, as well as many other tools. These people have seriously contributed back to the ecosystem, in many ways beyond what Hashicorp has done.
Beyond that, I know some of these companies tried to be contributors to Terraform itself but were ghosted by Hashicorp.
At the same time there's only a handful of regular contributors to Terraform[1]. It would not be hard for these companies to provide more resources to Terraform than Hashicorp is.
Re: The OpenTF Manifesto
#16Gruntwork here. You can find our statement here: The Future of Terraform must be open—our plan and pledge to keep Terraform open source. https://blog.gruntwork.io/the-future-of-terraform-must-be-op...
If you want to help us keep Terraform open source, please show your support at https://opentf.org/!
Re: The OpenTF Manifesto
#17>Imagine if the creators of Linux [] suddenly switched to a non-open-source license that only permitted non-competitive usage.
Linux cannot even successfully switch from GPL2 to GPL3 because of the sheer number of contributors and the fact that not all of them have transferred their copyright ownership to any given organization. This patchwork of different copyright owners has historically been seen as a potential weakness for Linux, but it seems like perhaps license inflexibility is a strength for open source.
Re: The OpenTF Manifesto
#18There is zero chance of Hashicorp donating Terraform to an open source foundation. If there was they would have never even considered this change in license. Honestly it's not a bad thing, maybe the maintainers of the Terraform fork will actually listen to feedback from the community of people who use it instead of ignoring them.
[deleted]
Re: The OpenTF Manifesto
#19I think the problem is that if hashicorp thinks you are a competitor you and your clients now have legal/operational issues. Ie you are now a competitor because we are releasing a product just like yours, here is a letter from a lawyer telling you to stop using terraform.
Re: The OpenTF Manifesto
#20Part of me hopes a fork comes out of this. I mean maybe features like this PR[1] for local state file encryption can then finally get merged. [1] https://github.com/hashicorp/terraform/pull/28603
I did see https://github.com/diggerhq/open-terraform but have no idea if it is related. And I’m sure there are others. What I’ll be interested to see with the forks is how they will practically be maintained. All the bug and security fixes that HashiCorp is writing can’t just be cherry-picked into these forks (I think?), so what exactly are they supposed to do? Update: and in the past hour this repo is gone.
Hi! OpenTF is not connected with a single company. This is an united, community-driven effort.
You can check on the manifesto side who is behind. And we welcome all support!
The fork you mentioned is no longer existing.