Live data from Hacker News

OpenTF is now OpenTofu

github.com

241–250 of 260 posts

Re: OpenTF is now OpenTofu

#241

Hey! Interim tech lead of OpenTofu here. I'd like to add that as of today (announced just now at OSS Bilbao) we're officially part of the Linux Foundation[0]! Hope you like the new name (it basically won the votes anywhere it was proposed) and happy to answer any questions! [0]: https://www.linuxfoundation.org/press/announcing-opentofu

Will there be any effort to rebrand the Hashicorp Configuration Language?

Re: OpenTF is now OpenTofu

#242

Hey! Interim tech lead of OpenTofu here. I'd like to add that as of today (announced just now at OSS Bilbao) we're officially part of the Linux Foundation[0]! Hope you like the new name (it basically won the votes anywhere it was proposed) and happy to answer any questions! [0]: https://www.linuxfoundation.org/press/announcing-opentofu

Congrats! I was hoping the icon would be the stinky variant[1], that would be so fun.

[1] https://en.wikipedia.org/wiki/Stinky_tofu

Re: OpenTF is now OpenTofu

#243

Earlier quoted context omitted.

"OpenTofu" is cute, but tofu has nothing to do with terraforming. How about "Genesis" or "Reliant" or "Marcus" or "Kruge"?

terraform has nothing to do with terraforming either

It absolutely does, in a metaphoric way:

It's just like the Genesis torpedo. You simply fire this torpedo from your starship at a (hopefully lifeless) planet or moon, and the Genesis Effect will re-form all the matter on the world, creating a world full of life, just the way you want it. You don't have to do any hard work like earth-moving, planting trees, etc., because the Genesis device does it all for you, quickly and automatically, according to your design.

terraform is the same: you just write a text file describing how you want a bunch of resources provisioned, run `terraform`, and it does all the work of provisioning those resources for you, quickly and automatically, according to your design. Honestly, I think it's a brilliant name.

Re: OpenTF is now OpenTofu

#245
post #159

Earlier quoted context omitted.

I’ve had this argument with people ad infinitum; it seems some people just see “AGPL” and any further thought process just stops. “You could ask or pay for an alternate licence” or “you’re almost certainly not using this in a way that means you need to open source your entire product” and any other rational argument you can think of are just met with “yeah but agpl” and that’s apparently just the end of it.

The thing is, at that point, why not just put it under a proprietary license in the first place? Lots of companies simply don’t have AGPL on their list of legal approved open source licenses and they’re not going to change that for you. ADDED: If you want to go the dual licensing route, at least just state this up front.

Because AGPL is open source and not proprietary, that's the reason. Open source doesn't necessarily mean that anyone can use it as they please, they must abide by the terms of the license. If they don't want to, then they can find another project, or get a different license for it.

Re: OpenTF is now OpenTofu

#246
post #121

Earlier quoted context omitted.

Tofu is great, just misused as a meat alternative. The Chinese and Japanese don’t use it as a meat alternative (dishes like mapo tofu and agedashi tofu contain both meat/fish and tofu), they use it to provide textural support and contrast to rich, full-flavoured dishes. If the negative association you have is because of its use in organic kale tofu salads and the like, that’s not exactly tofu’s problem.

It's not tofu's fault, but it kind of is tofu's problem imo, since it seems to be a common view. Until a couple of years ago I had pretty much the same view as GP, that tofu was bland with an unpleasant texture and I couldn't imagine anyone eating it for pleasure - based on my experiences of how it was cooked/served by restaurants and friends here in England. Eventually I tried a tofu dish while sharing plates with a…

I mean, disliking a food because it was cooked incorrectly is the problem of the eater, not the food. I can cook a steak well-done, that doesn't mean all steak is now bad.

Re: OpenTF is now OpenTofu

#247

Earlier quoted context omitted.

> OpenTofu has garnered massive support, with the project gaining admission to the Linux Foundation and even receiving public support from companies like Allianz. I don't know. It feels like this support comes from the vocal minority and competitors. I'll believe such a statement when more big multinational companies show support. Right now, I don't believe there is as much support as is currently made out.

There are around 19 full-time engineers staffed for the project from various companies. That is a lot more engineers than HashiCorp themselves had developing Terraform at the time of the license change.

I do wish, for their own good, OpenTF/Tofu would stop making this comparison. What insight do they have about HashiCorp’s resourcing beyond some git commit history? Surely these folks know there are many more folks involved in providing a product with the scope of TF than just those committing code. While I do find myself nodding along to many of the OpenTF points, whenever I hear this one on podcasts and such it comes off as very naive.

Re: OpenTF is now OpenTofu

#248

Earlier quoted context omitted.

> There are around 19 full-time engineers staffed for the project from various companies Various companies being all HashiCorp competitors: https://opentofu.org/supporters

Does it make them lesser engineers?

No, and I never suggested they are, what point are you trying to make?

Re: OpenTF is now OpenTofu

#249
post #247

Earlier quoted context omitted.

There are around 19 full-time engineers staffed for the project from various companies. That is a lot more engineers than HashiCorp themselves had developing Terraform at the time of the license change.

I do wish, for their own good, OpenTF/Tofu would stop making this comparison. What insight do they have about HashiCorp’s resourcing beyond some git commit history? Surely these folks know there are many more folks involved in providing a product with the scope of TF than just those committing code. While I do find myself nodding along to many of the OpenTF points, whenever I hear this one on podcasts and such it com…

Indeed we do have that insight. We actually spoke with many people intimately involved in the process.
Post reply on HN