Mutually Assured Development
Talkat OpenTofu Day North America 2024 · on Tuesday, 2024-11-12· at 14:10· Salt Palace | Level 2 | 250 D·
summary
History of a fork after a license shift from MPL 2.0 to a business source style license sparks a scramble: the registry TOS blocks forks, teams rebuild a registry and a release pipeline, and roughly 150 unique contributors help finish incomplete 1.6 work. Governance lives under the Linux Foundation owns trademark with a TSC and RFC process, no CLA so relicensing is impractical, and the project weathers a DMCA/cease letter while shipping features like dynamic provider config assignment and an exclude flag and enabling PowerPC forks.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:23Terraform’s rise and ecosystem
- 3:57Visible source licensing issues
- 5:06OpenTofu Manifesto and response
- 6:53Forking Terraform challenges
- 9:02Mutually assured development
- 10:49OpenTofu governance at Linux Foundation
- 12:35Core team roles and structure
- 13:59Community roadmap and RFC process
- 16:47Top requested OpenTofu features
- 17:50OpenTofu ongoing challenges
- 20:40Governance and transparency plans
- 22:02Q&A
related talks
25mWhat Makes Open Source Work: Licensing and Beyond
34mWhen Your Open Source Turns to the Dark Side
32mSOS: Sustainable Open Source
32mKeynote: State of the Foundation
43mSoftware Licensing and Compliance: It's All About Community
30mOpen Source Licensing: Use Versus Abuse
32mPanel Discussion: Contribute with Clarity: Choosing Your...
44mLeveraging Specifications in Open Source Projects