Distillation

🟡 (21:42) Source inspection completed for the 9th and final assigned record, opentofu-github-pr-1650 (https://github.com/opentofu/opentofu/pull/1650, published 2024-05-15). Exact source order was body, pr_metadata, patch:0; source lengths were 254, 284, and 22,677 bytes respectively; patch:0 is TSC_SUMMARY.md; copied evidence bounds were source_text_truncated=false, files_listing_complete=true, patch_selection_truncated=false, patch_unavailable_count=0.
🟡 (21:42) opentofu-github-pr-1650 top-level record metadata had pr_metadata=null, while its direct pr_metadata source stated changed_files=1, draft=false, state="closed", merged=true, merged_at="2024-05-16T06:28:54Z", and merge_commit_sha="2ef3047ec6bb266e8d91c55519967212c1a0975d".
🟡 (21:42) Merged opentofu-github-pr-1650, “Add Technical Steering Committee missing Summarries through 2024 May,” added the latest TSC meeting summary and backfilled older meeting summaries that had not been posted; its body stated that TSC note-takers would post summaries regularly.
🟡 (21:42) The 2024-05-07 TSC summary accepted the Init-time Constant Evaluation RFC, asked the core team to test performance rigorously, and strongly preferred an iterative rollout to limit blast radius in this order: 1. module source resolution, 2. dynamic provider configuration, 3. further features. Discussion noted the feature would break Terraform support and raised .otf-only support as a possible way for linters/language servers to distinguish the extended language. (meaning May 7, 2024)
🟡 (21:42) The accepted Init-time Constant Evaluation proposal would add a constant-evaluation stage between configuration loading and graph construction, intended to enable variables/locals in module sources and backends, provider for_each, variable-driven module provider mappings, known lifecycle attributes, and known variable defaults/validation; PR #1107 was identified as its proof of concept.
🟡 (21:42) The 2024-05-07 TSC summary said alternate .otf files had already received a green light for OpenTofu 1.8, allowing authors to opt into OpenTofu-specific features while retaining .tf support and helping code-completion/developer tools distinguish the language. (meaning May 7, 2024)
🟡 (21:42) The 2024-05-07 TSC versioning decision was to continue the current scheme with OpenTofu 1.8 next, publish a versioning strategy covering release cadence, semver, and potentially more frequent releases, open a community issue on changing versioning, and track how current/future versioning would handle provider constraints as OpenTofu and Terraform add features in different versions. (meaning May 7, 2024)
🟡 (21:42) The 2024-05-07 TSC decided backends-as-plugins remained low priority and should be reconsidered in 6 months, despite renewed interest from an Oracle employee seeking Oracle Object Storage backend support. (meaning May 7, 2024)
🔴 (21:42) User stated the TSC had “never posted on GitHub summary since February.”
🟡 (21:42) The 2024-05-07 TSC assigned @Roni Frantchi to backtrack and post all missing public meeting summaries dating to February. (meaning May 7, 2024)
🔴 [enforced-workflow] (21:42) User stated: “From now on, whomever takes notes during the TSC meeting will also open the PR posting the public notes.”
🟡 (21:42) The 2024-05-07 TSC approved changing the documentation license in the charter to Mozilla as requested by the Linux Foundation. (meaning May 7, 2024)
🟡 (21:42) The 2024-04-03 TSC unanimously accepted the tofu keyword as an exception despite compatibility concerns, while maintaining that no further divergence—including changes targeted for 1.8—would be accepted until there was a solution to the language-divergence problem. Alternatives considered were rejecting it pending an RFC, accepting this one exception, or reopening unrestricted divergence. (meaning Apr 3, 2024)
🟡 (21:42) The 2024-04-03 TSC considered five versioning approaches: 1. retain 1.x for Terraform-parity features and use 2.x for OpenTofu-specific features; 2. continue the current pattern; 3. solicit dev-team/stakeholder input; 4. let module authors explicitly prohibit OpenTofu use; 5. ignore Terraform module version blocks unless explicit OpenTofu constraints exist. It decided to consult stakeholders openly for one week and resume discussion at the next meeting. (meaning Apr 3, 2024)
🟡 (21:42) The 2024-03-06 TSC generally selected tofu rather than meta as the eventual alias for terraform {}, terraform.workspace, and terraform.env, while noting likely future aliases for terraform.tfvars and .terraformrc; it required an OpenTofu Language Server Protocol RFC and a file or other distinction mechanism before language/syntax divergence because tools such as tflint, tfsec, and IDEs could otherwise fail. (meaning Mar 6, 2024)
🟡 (21:42) The 2024-03-06 TSC unanimously chose Proposal 1a: permit state encryption in OpenTofu 1.7 but block future Terraform-divergent changes until the coexistence RFC landed in 1.8, with the caveat that the plan should be reconsidered if approval and implementation would take more than approximately 1 quarter. Proposal 1—blocking before even choosing/starting a solution—was opposed by everyone. (meaning Mar 6, 2024)
🔴 (21:42) User stated OpenTofu should maintain Tofu 1.6 LTS and “always have it there as a backward compatible way to transition from Terraform.”
🔴 (21:42) User stated users should “switch to that first,” referring to Tofu 1.6 as the initial Terraform-to-OpenTofu transition step before using upgrade guides for newer, potentially breaking OpenTofu releases.
🟡 (21:42) The 2024-03-06 TSC also considered Proposal 3: request an initial placeholder compatibility RFC without blocking divergent releases, label each release-time divergence, and later land the RFC; Roger Simms, Marcin Wyszynski, and Igor Savchenko favored it. Igor alone favored Proposal 2, the long-lived Tofu 1.6 compatibility transition branch. (meaning Mar 6, 2024)
🟡 (21:42) The 2024-02-27 TSC unanimously approved splitting migration guidance into specific tested Terraform x.y.z → OpenTofu a.b.c paths, documenting required code changes and unsupported features, with a commitment to fix bugs in those supported paths. (meaning Feb 27, 2024)
🟡 (21:42) The 2024-02-27 TSC requested holistic, community-reviewed RFCs for .otf and other OpenTofu/Terraform divergence handling, including IDE behavior; the discussed .otf rule would ignore xyz.tf when same-named xyz.otf was present. (meaning Feb 27, 2024)
🟡 (21:42) For module-variable deprecation, the 2024-02-27 TSC rejected Approach 1—embedding @deprecated: message or @deprecated{message} in descriptions as magical/implicit but Terraform-compatible—and deferred Approach 2—an explicit, cleaner deprecated string field that Terraform could not parse—to the OpenTofu/Terraform discrepancy RFC process. (meaning Feb 27, 2024)
🟡 (21:42) The 2024-02-27 TSC agreed provider functions should be implemented eventually, kept them out of OpenTofu 1.7, and added them to the 1.8 roadmap; it also asked that an RFC for OpenTofu’s own formal registry be prioritized. (meaning Feb 27, 2024)
🟡 (21:42) The 2024-02-21 TSC unanimously rejected adding a website compatibility table, unanimously approved improving the “why OpenTofu” page, voted 4–1 to emphasize more strongly that OpenTofu is a drop-in replacement, split 3–2 on a Terraform→OpenTofu migration-check command, rejected an OpenTofu→Terraform check command 4–1, unanimously rejected a compatibility mode that blocks OpenTofu-only features, and allowed any steering-committee member to research migration tools used by other projects. (meaning Feb 21, 2024)
🟡 (21:42) With opentofu-github-pr-1650 inspected, complete source inspection had now been shown for all 9 assigned records before opening v1.2-coding-package.json; direct frozen luna_a, luna_b, and terra_advisory responses and final adjudications were still pending.

Distillation

Observations