Dashboard › institutional-transition-lab › Distillation
11b686a7-49b0-403d-8c26-e0c57b7a3cad["lore_tm_v1_i8jBrpDpjhIpPxtx2d79ADR6xiOF9ZiFVZiIze8kjSI","lore_tm_v1_qsPfJ3N5V1fkfdbjbQywwckyHoDMZzPR1HOPgYO6Cog","lore_tm_v1_5vwDivvoZ4bhg4PMzv6HK7Xwnb9ZUKj1gdGFkEKoSfU","lore_tm_v1_-zOagoKHwM6tHYux1WDg3yaEj5hvpeNmv9wZkLgdGUI"]
opentofu-github-pr-1650 shows a merged one-file update to TSC_SUMMARY.md: 1 changed file, draft: false, state: closed, merged: true, merged at 2024-05-16T06:28:54Z, merge commit 2ef3047ec6bb266e8d91c55519967212c1a0975d. The PR added the latest TSC summary plus older meeting summaries that had not been posted and stated that note-taking TSC members would post them regularly. (meaning May 15-16, 2024)opentofu-github-pr-1650 included discussion of adding tofu as an alternative to the terraform keyword, possible future aliasing to tofu, implications for tools such as tflint and IDEs, and whether an RFC could be approved, implemented, and included in OpenTofu 1.8. It also recorded a decision to keep one discussed feature out of OpenTofu 1.7 and add it to the 1.8 roadmap.opentofu-github-pr-2830, “OpenTofu Charter and Governance,” shows 43 changed files, draft: false, state: closed, merged: true, merged at 2025-05-23T12:18:56Z, merge commit 59d24390b712b87954ee175c38912e56d8f5d974. The body described the change as the result of extended discussion between OpenTofu’s founding members and the Linux Foundation, intended to deepen community participation and move the project from the “Cathedral” toward the “Bazaar.” Patch selection was truncated, while the files listing and source body were complete and no patches were unavailable. (meaning May 20-23, 2025)opentofu-github-pr-2830 added CHARTER.md, titled “Technical Charter (the ‘Charter’) for OpenTofu a Series of LF Projects, LLC,” recording initial adoption on September 15, 2023 and amendment on May 20, 2025. The mission is to develop and preserve open-source infrastructure as code; scope includes collaborative development, documentation, testing, integration, tools, libraries, and artifacts supporting development, deployment, operation, or adoption, with an impartial and community-driven intent.CHARTER.md assigns the TSC all technical oversight. Initial voting members are Committers listed as “TSC Members” in CONTRIBUTING; they serve until resignation or TSC replacement. The TSC may document another membership-selection method in CONTRIBUTING, adopt or modify documented roles, establish workflow procedures, set promotion requirements, create or eliminate roles, and elect a Chair. Contributors are anyone contributing code, documentation, or other technical artifacts; Committers can modify repository artifacts; Contributor-to-Committer promotion requires TSC approval, and Committer removal requires majority TSC approval.CHARTER.md enumerates TSC responsibilities in this 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 and document community norms and rules for contributions, workflows, release candidates, and security reporting, 9. enable discussion, seek consensus, and vote when necessary on cross-project technical matters, and 10. coordinate marketing, events, or communications.CHARTER.md voting rules prioritize consensus and otherwise permit votes. Each TSC member ordinarily has one vote, but members employed by the same company or related-company group have combined votes capped by the “TSC Cap”: 2 when the TSC has at least 5 members and 1 when it has 4 or fewer. In-meeting votes require at least 50% of all voting members present and normally pass by majority of votes cast. Asynchronous motions require affirmative votes from at least 50% of all voting members. Supermajority votes require all voting members to participate in a meeting or asynchronously, allow a requested postponement of 14 calendar days, and require two-thirds of all voting members.CHARTER.md requires supermajority voting for: 1. Charter amendments, subject to LF Projects approval; 2. legal matters; and 3. alternative-license approval under Section 7.c. Asynchronous votes must provide all voting members at least 14 calendar days of verifiable notice. Unresolved votes may be referred by any voting TSC member to the Series Manager. TSC decisions must be documented publicly in the main repository no later than 14 days after the vote, with detailed pre-vote discussion notes when the decision is non-confidential.CHARTER.md requires open, non-discriminatory participation; transparent, open, collaborative, and ethical operation; and publicly visible discussions, proposals, timelines, decisions, and status. Potential transparency violations are to be reported immediately to the Series Manager. LF Projects holds project trademarks; the project develops and owns its GitHub accounts, social-media accounts, and domain registrations as permitted by LF Projects.CHARTER.md intellectual-property rules specify: inbound code under Mozilla Public License Version 2.0; Developer Certificate of Origin sign-off through a TSC-approved process; outbound code under MPL 2.0; documentation under Creative Commons Attribution 4.0 International; compliance with upstream-project contribution and license requirements; and SPDX-style license information in contributed files. Alternative inbound or outbound licenses require a described contribution, proposed alternative license(s), justification, and approval by two-thirds of the entire TSC. Charter amendments likewise require a two-thirds vote of the entire TSC plus LF Projects approval.opentofu-github-pr-2830 added GOVERNANCE.md. New TSC-member admission requires, in order: 1. nomination by an existing TSC member, 2. significant contributions such as code, documentation, community engagement/support, or technical leadership, 3. a two-thirds supermajority of existing TSC members, and 4. addition to the TSC list plus appropriate project-resource access.GOVERNANCE.md defines TSC departure paths: 1. voluntary written resignation with no acceptance vote; 2. inactivity removal after 3 consecutive months without substantial meeting, voting, or project participation, requiring majority approval by active TSC members and at least 14 days’ notice; 3. removal for Code-of-Conduct violations or detrimental conduct, requiring a two-thirds vote excluding the affected member and an opportunity for that member to respond; and 4. membership rebalancing by consensus or vote when an organizational-affiliation change would violate voting-power restrictions.GOVERNANCE.md says the TSC meets every two weeks, meetings are public and may occur electronically, by teleconference, or in person, and proposed agendas should be published at least 3 days ahead. It requires decisions to be documented in a public TSC folder no later than 3 days after a vote, with detailed discussion notes for non-confidential decisions; this is stricter than CHARTER.md’s 14-day publication deadline.GOVERNANCE.md states that projects in the OpenTofu GitHub organization belong to the OpenTofu project family and the TSC has ultimate authority over all of them. Delegating authority to project maintainers requires an explicit TSC vote, counts as a major decision requiring documentation, and requires the delegated project to maintain MAINTAINERS.md; the TSC retains override authority but should exercise restraint.GOVERNANCE.md distinguishes related external projects as: 1. formal relationships established by TSC vote, potentially covering technical collaboration, shared governance, or co-maintained specifications/standards; and 2. informal community-driven integrations and extensions requiring no formal governance oversight. Contributions to related projects should follow, in order: 1. the specific project’s governance model, 2. the OpenTofu Code of Conduct, and 3. any additional TSC cross-project guidelines.