Dashboard › institutional-transition-lab › Distillation
f917b3f1-a38a-42ff-b439-ed98ce8f2c33["lore_tm_v1_87Jl-NmOYPbR6pwOmkkk8fSpxFhgU-csdQlO6UTUBVQ","lore_tm_v1_g7vV8H7TNZXSLH5rvQEuiMt_aX-5jO4e8Eycb4I_0Po"]
Date: Sep 8, 2026
opentofu-github-pr-1650, published May 15, 2024, containing Technical Steering Committee notes covering static evaluation, project versioning and compatibility, the tofu alias, .otf files, module-variable deprecation, documentation licensing, meeting-note publication, and Terraform/OpenTofu comparison guidance. (meaning May 15, 2024)#1650 described static evaluation as a mechanism for allowing locals and variables in currently restricted configuration elements. The stated user problem was that dynamic OpenTofu components often cannot reference other objects/configuration, forcing copy/paste; Terragrunt mitigates some cases such as module sources, while -backend-config and override files were characterized as hacky backend-configuration workarounds.#1650: whoever takes notes during a TSC meeting will also open the pull request publishing the public notes.#1650: change the charter’s documentation license to Mozilla as requested by the Linux Foundation.tofu keyword as an opt-in alternative to terraform, despite an earlier vote to block breaking changes until .otf files existed, because an external community contributor had already implemented the feature and freezing it for roughly a month would be discouraging. (meaning Apr 3, 2024)#1650: 1. use the 1.x line for compatibility and begin 2.x for OpenTofu-specific features, while deciding how long to support 1.x and recognizing state encryption came too early for this split; 2. continue the current versioning pattern; 3. solicit input from the development team and other stakeholders; 4. “go on the offense” by giving module authors a way to state explicitly that they do not want their work used with OpenTofu; 5. ignore Terraform version constraints in modules and require explicit OpenTofu constraints. Decision: discuss openly with stakeholders for one week, then resume at the next meeting.#1156 considered aliases for the terraform {} block and the terraform.workspace and terraform.env configuration variables: tofu matched the project’s existing theme, while meta was more tool-agnostic and potentially better as a long-term community option. A Tofu-specific namespace had already been accepted; the remaining decision was which alias fit best, and an external contributor’s open PR was blocked pending that choice. (meaning Mar 6, 2024)#1650: if an RFC could likely be approved, implemented, and included in OpenTofu 1.8 within approximately one quarter once staffed, proceed; otherwise reconsider..otf compatibility behavior: introduce .otf as an OpenTofu-specific extension and, when both xyz.tf and xyz.otf exist in one directory with the same basename, ignore xyz.tf, allowing a configuration to support both ecosystems. For issue #1275, the TSC requested holistic RFC(s) on which it could vote, including community feedback, divergence use cases from both HashiCorp Terraform and OpenTofu, and IDE handling.#1005 had already been accepted to introduce module-variable deprecation, with the steering committee being asked to choose among implementation approaches after extensive discussion.nedinthecloud dated January 22, 2024 was cited, and the option to add a compatibility table to the website was rejected.opentofu-github-pr-2830 declared a truncated patch selection. The assistant planned to inspect every supplied patch and treat unselected files as an explicit evidence limitation rather than infer their contents.