-
Notifications
You must be signed in to change notification settings - Fork 869
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opentofu #231
Comments
@antonbabenko what do you think? |
Let's have a section in this repository named Opentofu with articles listed there. I don't want us to mix content for both Terraform and Opentofu under the same headers to avoid confusion for the readers on which edition of Terraform we are talking about. Alternatively, we can just focus on Terraform here and let Opentofu mature over time a bit and reconsider if we should be taking it seriously in half a year (at least). PS: I prefer we wait and focus on Terraform 100% in this repository. |
@antonbabenko Makes sense. Thanks for your input. I'm happy with maintaining focus on Terraform. Also, I'd be happy for us to move this repo to a community org like you once suggested. @chenrui333 any thoughts? |
@shuaibiyy Yes, I am still willing to accept the migration of this repository over to my account and keep improving it. Exactly, as I suggested before. Think about it. :) |
why dont we just do a community org ;) (like terraform modules one) |
I noticed that the PR related to OpenTofu (#238) was recently merged, and the repository name was renamed to awesome-tf. Is this a change of policy? |
@minamijoyo I am also a maintainer of this repository and I somehow missed the point when this policy changed. I was sure that we agreed to stick to Terraform in this repository (see my comment above). |
I don't have any strong opinions on accepting tofu or not, but if you are starting to accept tofu-related tools, having a separate section for tofu-specific ones would be a good idea, as you mentioned. |
opentofu is completely a new community fork of terraform and also lots of ecosystem changes, not sure how we want to manage the resources in this repo, so raise this issue for discussions.
Currently, there is a separate awesome-opentofu repo, https://github.com/virtualroot/awesome-opentofu
The text was updated successfully, but these errors were encountered: