Dashboard › institutional-transition-lab › Distillation
bf1d97c3-5780-417f-ae77-2d9be22f8bd0["lore_tm_v1_a5tdYv1Q_8utaZpSVJ2BPhk9u9BrTaLhsSepRNbNWSw","lore_tm_v1_mVIwkkDDHoM1qX_bsUM5yU__NxSMFWDcwAFLEHd81zw","lore_tm_v1_4J88iJhdlRa-S5ukDy_teO8fFvFVi-cGfYn3YeQva_E"]
opentofu-github-pr-823 identifies a GitHub pull request published by opentofu/opentofu, with source URL https://github.com/opentofu/opentofu/pull/823, source type github_pull_request, and entity ID opentofu; evidence bounds report files_listing_complete: true, patch_selection_truncated: false, patch_unavailable_count: 0, and source_text_truncated: false. (meaning November 5, 2023)GOVERNANCE.md with a single link to https://github.com/opentofu/org/blob/main/GOVERNANCE.md; it also changed local Charter, Governance, and TSC-note links in contributor documentation and feature-request documentation to corresponding opentofu/org URLs.#741. Reasons included keeping the core team focused on the CLI rather than operating highly available mission-critical SaaS, relying on GitHub/AWS for availability, preserving git-repository transparency, and decoupling artifact resolution from documentation and signing; the core team deferred a user-facing registry design. (meaning November 2, 2023)@RLRabinowitz and @cube2222 were: 1. announce the selected RFC ASAP; 2. investigate implementation details, specifically scraping existing modules/providers and keys, key submission, version bumps, sharing the detailed design, and defining core-team scope and task breakdown. (meaning November 2, 2023)@allofthesepeople; agenda suggestions had to be posted at least 24 hours in advance or the meeting would be cancelled. It also stated Spacelift had hired 2 dedicated maintainers and built a Tofu-specific hiring profile and pipeline to share with interested companies. (meaning November 2, 2023)#874 unanimously accepted and raised in priority; 4. OpenTofu support in the VS Code Language Server issue #970 could be accepted but was not assigned to the core team; 5. gunzipbase64 PR #799 unanimously accepted; 6. filesystem state-backend performance PR #579 unanimously accepted. (meaning December 5, 2023)#988; alternatives were (a) change the namespace, (b) add a deprecation notice for unqualified names, and (c) make neither change and mention the issue as softly as possible in documentation. Option (c) was chosen unanimously. (meaning December 11, 2023)(a) soft-launch December 20 with marketing January 10, (b) launch December 20, or (c) launch January 10, with an RC expected at least one week before GA. Option (c), January 10, was chosen unanimously. (meaning December 11, 2023)#812, allowing unknown input variables in tofu plan, broadened into workspace dependencies, Terragrunt’s role, and whether first-party support belonged in OpenTofu core or should remain layerable; the TSC ran out of time and deferred defining criteria and requesting RFCs. (meaning December 11, 2023)1.10; it also noted that the 1.9 release was expected that week. (meaning January 7, 2024)SOC2 / ISO 27001; 2. external code/security audit; 3. security-scanning tools such as Snyk, DependaBot, and Go Report Card; 4. a written security-disclosure, escalation, remediation, notification, and patch process. Security scanning and disclosure processes received unanimous support; Yevgeniy Brikman also voted for a code audit, and Spacelift’s Head of Security was to present further findings. (meaning January 22, 2024)check command, rejected an OpenTofu-to-Terraform check command 4–1, requested research on other projects’ migration tools, and unanimously rejected a compatibility mode blocking OpenTofu-only features. (meaning February 21, 2024)x.y.z versions to specific OpenTofu a.b.c versions; for .otf language divergence it requested holistic RFCs addressing use cases and IDE handling. (meaning February 27, 2024)@deprecated: message or @deprecated{message} in the variable description, compatible with Terraform but magical and implicit; 2. adding an explicit deprecated string field, cleaner and first-class but incompatible with Terraform parsing. It rejected approach 1 and deferred approach 2 to the OpenTofu/Terraform discrepancy RFCs. (meaning February 27, 2024)1.7, and add them to the 1.8 roadmap; it also asked that an RFC for an official registry receive priority. (meaning February 27, 2024)tofu keyword as a one-time exception despite compatibility concerns, because it was opt-in and already had a community PR; members said additional divergence should wait for the longer-term solution targeted for 1.8. (meaning April 3, 2024)1.X for Terraform-parity features and use 2.X for OpenTofu-specific features; 2. continue current versioning; 3. solicit dev-team and stakeholder input; 4. let module authors explicitly disallow OpenTofu; 5. ignore Terraform version constraints unless explicit OpenTofu constraints are supplied. The decision was to consult stakeholders for one week and resume at the next meeting. (meaning April 3, 2024)#1042 with proof of concept PR #1107, proposed a stage between configuration loading and graph construction to identify effectively constant variables/locals. Intended use cases included variable module sources, provider for_each, variable/for_each module-provider mappings, variable backend configurations, known lifecycle attributes, and known variable defaults/validation; Igor Savchenko supported proceeding but requested performance tests on large configurations and noted it would break Terraform compatibility. (meaning May 7, 2024)https://github.com/opentofu/opentofu/pull/823 had body text Add Technical Steering Committee Summary for 2023-11-02, changed exactly 1 file (TSC_SUMMARY.md), was not a draft, and was merged as commit 60a3f72d43c002f83246e657a15b9b2157fd74c6; base SHA was b2069bb0bbfc7dd121a5d72613bb71ca12375405 and head SHA was f449ce3afb8fe0bc1866291652348499c20d35ae. (meaning November 6, 2023 at 11:21:40 UTC)TSC_SUMMARY.md in PR #823 listed attendees Igor Savchenko (@DiscyDel), Marcin Wyszynski (@marcinwyszynski), Roger Simms (@allofthesepeople), and Roni Frantchi (@roni-frantchi), and absent members Yevgeniy Brikman (@brikis98) and Omry Hary (@omry-hay). (meaning November 2, 2023)