Dashboard › institutional-transition-lab › Distillation
81641474-947b-4cf0-9459-5f25c9b1a317["lore_tm_v1_efZlDDLkFOuLCwoUXpHBv76NRZo0i8O47fr0mF9-7IQ","lore_tm_v1_m_FoZ12eBIVpipdC1lvj_OdL8ZZLX5Qu_L1UeFWESHw","lore_tm_v1_udtWSMkDPlB_57EYk_THNHZPJ9gawF41ofUhck3DKbw","lore_tm_v1_r10m98Ly6b97NF1_zdLTCksXTiQTOTPWvHMySVwcmYk","lore_tm_v1_rq6GnjENZQp-e4HQA7Cb3fS5DU5NJ5ZhUAHrxsyS5vk","lore_tm_v1_iJ02-Va_bm0rtWqj_S30sMKp9Qmi6xtxVBPmfTYHuPU","lore_tm_v1_ZT88VXJb-0bjkeY07slX-gRUpCChuArS-6ekvQmR_VQ","lore_tm_v1_Hs5DyiBobUl-u35PXjV1U-TFKo_W-WvAzUU-FW1X2Ek","lore_tm_v1_DMgJIad9hed6PPwQ63Ja3pDAaS5kTb2z6UyQu2DG030","lore_tm_v1_I-Qs-ZNPa8StD798o18-pqiquwDFxWOQDDnwlhakI3I"]
Date: Sep 8, 2026
opentofu-github-pr-2830 (https://github.com/opentofu/opentofu/pull/2830), titled “OpenTofu Charter and Governance,” published May 20, 2025. The PR had 43 changed files, base SHA 6f0d3d3a07a49309b30960d57225c9f7c701e9a9, head SHA da4ac00ca09d1d9e06e47efd77523a235d49f10c, merge commit SHA 59d24390b712b87954ee175c38912e56d8f5d974, and was merged May 23, 2025 at 12:18:56 UTC. The supplied files listing was complete, patch selection was truncated, no selected patch was unavailable, and source text was not truncated. (meaning May 20-23, 2025)#2830 said its charter and governance changes resulted from extended discussion between OpenTofu’s founding members and the Linux Foundation. Its stated aim was deeper community interaction and movement from a necessary initial “Cathedral” model toward a “Bazaar” model.#2830 identified the initial TSC members as people already serving that role, representing organizations heavily invested in OpenTofu’s future, plus the current Technical Lead.CHARTER.md patch established OpenTofu as a Series of LF Projects, LLC, with initial adoption dated September 15, 2023 and amendment dated May 20, 2025. Its mission is to develop and preserve open-source infrastructure as code; its scope includes documentation, testing, integration, tools, libraries, and other artifacts supporting development, deployment, operation, or adoption, with the project intended to be impartial and community-driven.CHARTER.md assigned the TSC all technical oversight. Initial voting members are Committers listed as “TSC Members” in CONTRIBUTING; members serve until resignation or TSC replacement, and any alternative membership-selection approach must be documented in CONTRIBUTING. TSC meetings are intended to be public and may occur electronically, by teleconference, or in person.CHARTER.md defined roles: Contributors are anyone contributing code, documentation, or other technical artifacts; Committers are Contributors who earned authority to modify project artifacts; the TSC approves promotion to Committer and may remove a Committer by majority approval. Participation is open to anyone complying with the Charter.CHARTER.md enumerated TSC responsibilities in order: 1. coordinate technical direction; 2. interpret the Charter; 3. address legal matters with the Series Manager; 4. approve sub-project/system proposals, including incubation, deprecation, and scope changes; 5. organize or remove sub-projects; 6. create subcommittees or working groups; 7. appoint representatives to other open-source/open-standards communities or organizations; 8. establish documented norms and rules for contributions, workflows, release candidates, and security reporting; 9. enable discussion, seek consensus, and vote where needed on cross-project codebase matters; 10. coordinate project marketing, events, or communications.CHARTER.md established consensus as the TSC’s primary decision method, with voting when consensus fails. Each member normally has one vote, but members employed by the same company or related-company group are collectively capped at 2 votes when the TSC has at least 5 members and 1 vote when it has 4 or fewer.CHARTER.md voting rules: in-meeting votes require at least 50% of all voting members present and ordinarily pass by majority of votes cast; asynchronous motions require affirmative votes from at least 50% of all voting members; supermajority votes require participation by all voting members, permit a requested postponement of 14 calendar days, and require two-thirds of all voting members; unresolved votes may be referred by any voting member to the Series Manager.CHARTER.md required supermajority votes for 1. Charter amendments, subject to LF Projects approval; 2. project legal matters; and 3. alternative-license approval under Section 7.c. Asynchronous voting may use any suitable medium providing every voting member at least 14 calendar days of verifiable notice.CHARTER.md required TSC decisions to be documented publicly in the main repository within 14 days of a vote, with detailed pre-vote discussion notes for non-confidential decisions.CHARTER.md required transparent, open, collaborative, ethical, and nondiscriminatory operation; project discussions, proposals, timelines, decisions, and status should be openly and easily visible, and potential violations should be reported immediately to the Series Manager.CHARTER.md intellectual-property rules: contributors retain copyright; inbound and outbound code uses Mozilla Public License 2.0; inbound code requires Developer Certificate of Origin sign-off through a TSC-approved process; documentation uses Creative Commons Attribution 4.0 International; upstream contributions follow the upstream project’s licensing and contribution process; alternative licenses require a two-thirds vote of the entire TSC; contributed files should include license information such as SPDX short-form identifiers.GOVERNANCE.md patch required a new TSC member to be nominated by an existing member, demonstrate significant contribution through code, documentation, community support, or technical leadership, receive a two-thirds supermajority of existing members, and then receive appropriate project-resource access.GOVERNANCE.md specified TSC departure/removal paths: 1. voluntary written resignation with no acceptance vote; 2. inactivity removal after 3 consecutive months without substantial participation, by majority of active members and with at least 14 days’ notice; 3. removal for cause, including Code of Conduct violations or detrimental actions, by two-thirds of the TSC excluding the affected member and after an opportunity to respond; 4. affiliation-change rebalancing by consensus or vote where organization-based voting limits would be violated.GOVERNANCE.md set TSC meetings every two weeks, required proposed agendas at least 3 days in advance, kept meetings public, and required decisions to be documented in a public TSC folder within 3 days of the vote, including detailed discussion notes where information is not confidential.GOVERNANCE.md declared projects under the OpenTofu GitHub organization part of the OpenTofu project family and gave the TSC ultimate authority over them. Delegation to project maintainers requires an explicit TSC vote, counts as a documented major decision, and requires the project to maintain MAINTAINERS.md; the TSC retains override authority but should exercise restraint.GOVERNANCE.md distinguished external relationships: formal relationships require a TSC vote and may involve technical collaboration, shared governance, or co-maintained specifications/standards; informal relationships are community-driven integrations or extensions needing no formal governance oversight. Contributions should follow the specific project’s governance, the OpenTofu Code of Conduct, and any TSC cross-project guidelines.CONTRIBUTING.md patch changed the contribution workflow so feature, bug-fix, refactoring, and CI-tooling work should start from an issue bearing both accepted and help wanted: contributors should 1. find such an issue, 2. comment that they want to work on it, 3. wait for maintainer assignment, and 4. submit code through the repository comparison page.CONTRIBUTING.md stated that OpenTofu cannot merge pull requests without prior discussion, regardless of how trivial a change seems, and directed readers to contributing/FAQ.md, contributing/DEVELOPING.md, CHARTER.md, GOVERNANCE.md, MAINTAINERS.md, and the TSC meeting-notes folder.CONTRIBUTING.md defined Contributors as anyone advancing OpenTofu through issues, bug investigation, PRs, or other help, and Maintainers as Charter-defined Committers to one or more repositories.@RLRabinowitz, env0); Christian Mesh (@cam72cam, Spacelift); Igor Savchenko (@DiscyDel, link targeting https://github.com/DicsyDel, Scalr Inc.); James Humphries (@Yantrio, Spacelift); Roger Simms (@allofthesepeople, Harness Inc.); and Zach Goldberg (@ZachGoldberg, Gruntwork, Inc.).main and the target branch and identifying the commit to backport.GOOS and GOARCH values with your target platform if you wish to cross-compile.”CONTRIBUTING.md backport instructions used git checkout -b backports/ISSUE_NUMBER followed by git cherry-pick -s COMMIT_ID_HERE, then an additional changelog commit and PR.GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -o tofu -v -buildvcs=false ./cmd/tofu, producing ./tofu; CGO_ENABLED=0 was used on almost all platforms except macOS/Darwin because of DNS-resolution issues.Co-authored-by when authorized third-party code is included, and avoid LLM coding assistants because they may emit BSL-licensed Terraform-derived code.help wanted; 3. more information or an RFC needed; 4. more community input needed via needs community input; 5. rejected with an explanation; 6. referred to the TSC for substantial core-development commitments, legal implications, or other leadership attention.records, schema_version, and summary; records was an array. Record entries exposed canonical_ledger_eligible, full_response_agreement, luna_a, luna_b, provisional_core_agreement, record_id, route_reasons, source_url, and terra_advisory.luna_a, luna_b, and terra_advisory object used keys elapsed_ms, model, reasoning_effort, response, schema_valid, and validation_errors.opentofu-github-issue-1353, Luna A classified the documentation/UI style-framework issue as a proposal_only control_rights event proposing that OpenTofu gain set_policy authority over technical documentation and user-interface writing, citing “I'm proposing a framework for technical documentation and user interface writing.” and “getting all authors to set aside their pet styles and use the standard style for OpenTofu.” Luna B and Terra instead classified it as no_event; all three outputs were schema-valid with no validation errors. The recorded announcement date was March 8, 2024. (meaning Mar 8, 2024)opentofu-github-issue-2109, Luna A and Luna B classified direct GitHub provider installation as a proposal_only control_rights event adding user power, citing “This would enable users to specify a GitHub repository as a provider source, allowing for more flexible and decentralized provider management.” Luna A labeled the right override targeting the centralized registry, while Luna B labeled it steward targeting provider management; Terra classified it as no_event. All three outputs were schema-valid with no validation errors. The recorded announcement date was October 28, 2024. (meaning Oct 28, 2024)opentofu-github-issue-2573, Luna A and Luna B both classified the TSC-summary year correction as no_event, with titles “Correct year in TSC summaries” and “Use correct year in Technical Steering Committee (TSC) Summary”; both were schema-valid with no validation errors. Terra had no response or validation result.opentofu-github-issue-258, Luna A, Luna B, and Terra unanimously classified the choice of a Homebrew-like stable registry design as a control_event of event kind product, with no power changes. All outputs were schema-valid with no validation errors, and confidence values were 0.98, 0.96, and 0.98. The recorded announcement date was November 3, 2023. (meaning Nov 3, 2023)opentofu-github-issue-340, Luna A classified the proposal to enable GitHub Discussions as a control_event of event kind product; Luna B and Terra classified it as no_event. Terra’s ambiguity note said the issue proposed enabling GitHub Discussions and offered moderation but did not evidence an implemented organizational-rights change. All outputs were schema-valid with no validation errors; Luna A recorded September 7, 2023 as the announcement date, while Luna B and Terra left it null. (meaning Sep 7, 2023)