If I am a cloud provider and maintain a Terraform binding I now have a strong reason to target OpenTF over HashiTF as they inevitably begin to diverge. It's hard to see how Hashicorp survives trying to compete over a consortiom of companies for whom TF is a complement and not the product and are incentivized to use it as a free value add. Especially when those same companies are the primary targets for Terraform usage.
The Terraform Registry Terms of Service have been updated
51–60 of 136 posts
Re: The Terraform Registry Terms of Service have been updated
#52Companies want the benefits of open source (massive community contributions, lower development costs, better security, community exposure, marketshare) but don't like the downsides (from their perspective: forks, lack of control, freeloaders etc). TOS changes like this are fine, it's their garden, but ultimately all they'll do is put even more power behind forks and alternatives. Because the people that were motivate…
I think this damages all commercial OSS projects. Because after Docker and Terraform, any effort to bring in some OSS project as a dependency will be met with "Sure, it's open source now, but what about when...".
On the contrary, it shows how opensource is a reliable long term choice through the possibility of forking.
Re: The Terraform Registry Terms of Service have been updated
#53Companies want the benefits of open source (massive community contributions, lower development costs, better security, community exposure, marketshare) but don't like the downsides (from their perspective: forks, lack of control, freeloaders etc). TOS changes like this are fine, it's their garden, but ultimately all they'll do is put even more power behind forks and alternatives. Because the people that were motivate…
I think this damages all commercial OSS projects. Because after Docker and Terraform, any effort to bring in some OSS project as a dependency will be met with "Sure, it's open source now, but what about when...".
It's a cautionary tale about CLAs, not FOSS.
Re: The Terraform Registry Terms of Service have been updated
#54Re: The Terraform Registry Terms of Service have been updated
#55Earlier quoted context omitted.
It's sad too, mitchellh used to be fairly active in the HN community but it seems he is not able to for likely professional reasons after the BSL fiasco.
Mitchell is a wonderful hacker. He’s someone who gets what an open source company is/should be better than many who tried. I suspect he doesn’t feel great about what’s happening with the company…
Remember, he was CEO but didn't like that role. He stepped down from the CEO role as well as the board so he could continue to hack rather than lead. I agree, its likely not how he wants things to be run but its not his decision anymore.
https://www.hashicorp.com/blog/mitchell-s-new-role-at-hashic...
Re: The Terraform Registry Terms of Service have been updated
#56Earlier quoted context omitted.
I think this damages all commercial OSS projects. Because after Docker and Terraform, any effort to bring in some OSS project as a dependency will be met with "Sure, it's open source now, but what about when...".
It's a cautionary tale about CLAs, not FOSS.
Are there commercial FOSS projects that don't have CLAs?
Re: The Terraform Registry Terms of Service have been updated
#57I had Hashicorp in my mind as a cool and respectful company. These recent events have made to reconsider and throw them into the same bag as Oracle. I find this pretty sad.
It actually was a respectable company. But the guy who started it all (Mitchell Hashimoto) isn't there anymore (at least not as a decision maker) so the corporate drones are taking over.
Co-founder Armon is still the CTO. Maybe his influence isn’t as great any more, or maybe even he went along with this terrible idea…
Re: The Terraform Registry Terms of Service have been updated
#58Earlier quoted context omitted.
I think this damages all commercial OSS projects. Because after Docker and Terraform, any effort to bring in some OSS project as a dependency will be met with "Sure, it's open source now, but what about when...".
On the contrary, it shows how opensource is a reliable long term choice through the possibility of forking.
It doesn't matter if you agree, it only matters if there are some decision makers that agree, and I know for a fact that there are. So the damage has already happened.
Re: The Terraform Registry Terms of Service have been updated
#59Hey! Just wanted to say that this doesn't impact OpenTF too much. It's an extra step we need to take before a stable release, but long-term it'll make us more decoupled, which is great. As someone else commented, all providers and modules other than Hashicorp's are hosted on GitHub and the registry is just a "redirector". We'll do something similar, other than some special handling for Hashicorp's providers. Also, I…
Out of curiosity, why isn't OpenTF's development, done, well, in the open? What's the rationale for keeping it closed for now?
I'm not critiquing, not a Terraform user so don't have any stake in this discussion, just curious.
Re: The Terraform Registry Terms of Service have been updated
#60Earlier quoted context omitted.
Mitchell is a wonderful hacker. He’s someone who gets what an open source company is/should be better than many who tried. I suspect he doesn’t feel great about what’s happening with the company…
I'm sure he's been well compensated for his hurt feelings.
Yeah, by those of us who bought in post IPO at $82… this BSL nonsense is particularly annoying to me because I lost a bit of dosh on HCP.