Kuba Martin, Software Engineering Team Lead at Spacelift and Interim Tech Lead of OpenTofu, the open-source fork of Terraform, discusses how OpenTofu handled licensing and copyright, benefits of a technical steering committee, recreating the community registry, and more.
OpenTofu is a community-driven fork of Terraform, aiming to continue the open source spirit and provide a platform for community-driven development.
The process of forking Terraform and establishing OpenTofu involved challenges like trademark compliance and the creation of a separate registry, but the initiative successfully garnered community interest and support.
Deep dives
The Open Tofu initiative and its goal to continue the open source spirit of Terraform
The Open Tofu initiative, previously called OpenTF, is a fork of Terraform designed to declaratively manage infrastructure using code. It allows users to describe the desired state of their infrastructure using a special DSL, and Open Tofu handles the process of creating and modifying the infrastructure accordingly. Open Tofu is also an ecosystem of providers, which are plugins that enable communication with various cloud and SAS backends. The initiative aims to continue the open source spirit of Terraform and provide a platform for community-driven development.
The motivation behind forking Terraform into Open Tofu
The decision to fork Terraform and create Open Tofu was prompted by a licensing change made by HashiCorp, the original creator of Terraform. The license change raised concerns among companies heavily involved in the Terraform ecosystem, as it shifted away from the open source MPL license. These companies came together and decided to fork Terraform as Open Tofu, ensuring the project remains in the open source spirit and under the MPL license. The initiative expresses gratitude to HashiCorp for its work in creating a thriving community around Terraform.
The process of forking and establishing Open Tofu
The process of forking Terraform and establishing Open Tofu involved various challenges. Trademark compliance was a crucial aspect, requiring careful renaming and a thorough review of the codebase to ensure no trademark infringements. Additionally, the creation of a separate registry was necessary due to changes in the Terraform registry's terms of service. Open Tofu successfully navigated these complexities and garnered significant community interest and support. The initiative announced its intent to fork through a manifesto, received pledges of support from individuals and companies, and eventually made the codebase public.
The governance and roadmap of the Open Tofu project
Open Tofu adopts a community-driven and open approach to its governance and roadmap. The initiative has a technical steering committee comprised of companies backing the project, and it operates under the governance of the Linux Foundation. Major changes and feature developments undergo an RFC (Request for Comments) process, allowing for public input and discussion. Open Tofu's roadmap includes features such as end-to-end state file encryption and integration with existing artifact registries. The project encourages community participation through its Slack community, GitHub discussions, and weekly updates.
Kuba Martin (@cube2222_2) is Software Engineering Team Lead at Spacelift and Interim Tech Lead of OpenTofu, the open-source fork of Terraform. Terraform is a declarative infrastructure-as-code (IaC) tool that recently switched to a source-available license. Spacelift and other companies that heavily relied on Terraform came together to fork it into a community-driven project originally called OpenTF, which has now become OpenTofu and is governed by the Linux Foundation.
Contributor is looking for a community manager! If you want to know more, shoot us an email at eric@scalevp.com.