Why Should DevOps Professionals Care About the OpenTF Manifesto and Terraform’s Licensing Change?
Setting the Stage: A Sudden Shift in Terraform’s Licensing
In the wake of HashiCorp’s sudden decision to switch Terraform’s license from the Mozilla Public License (MPL) to the Business Source License (BSL), the open-source community has responded with concern, confusion, and action. The OpenTF Manifesto, a document penned by a diverse group of engineers, researchers, and enthusiasts, has emerged as a rallying cry for those who believe in the principles of open-source software. This article delves into the manifesto’s content, its implications for the DevOps and Open Source community, and the broader challenges it highlights, including insights from recent articles by Mike Vizard and Max Körbächer on the subject.
The Community Speaks: Unpacking the OpenTF Manifesto
The OpenTF Manifesto is more than a reaction to a licensing change; it’s a statement of belief in the core values of open-source software. The manifesto outlines the community’s concerns about the BUSL license, describing it as a “poison pill” for Terraform. The sudden change has left businesses and developers in a state of uncertainty, questioning the legal risks and future stability of their infrastructure.
The manifesto calls for HashiCorp to revert Terraform back to an open-source license, such as MPL or Apache License 2.0. If HashiCorp refuses, the community proposes to fork Terraform into a foundation, ensuring it remains open source, community-driven, and impartial.
Ripples in DevOps: How the Change Hits Home
Legal Uncertainty
The change to BUSL has created legal ambiguity for tens of thousands of businesses. The vagueness of the license and additional use grant has left companies wondering if their usage could be construed as competitive with HashiCorp’s offerings. As Körbächer points out, companies like env0, spacelift, and weaveworks are actively seeking legal guidance to understand the implications.
Trust in Open Source
The sudden license change has shaken the trust in open-source projects. Companies and developers must now consider the risk of sudden license changes, impacting their willingness to invest in and adopt open-source tools.
Fragmentation of the Community
The manifesto’s call for a fork, if realized, could lead to fragmentation within the Terraform community. This division may slow innovation and collaboration, affecting the overall growth and vitality of the ecosystem.
Open Source at a Crossroads: The Manifesto’s Wider Impact
A Call for True Open Source
The manifesto emphasizes the need for essential building blocks of the modern Internet to remain truly open source. It highlights the importance of well-known and widely-accepted licenses that companies can trust.
Community Governance
The manifesto’s proposal for a community-driven foundation reflects a growing desire for open-source projects to be governed by the community. This approach ensures that valuable features and fixes are accepted based on merit, not the whims of a single vendor. Körbächer’s article also opens a debate on whether open source projects should be under foundations or single vendor maintenance, acknowledging the complex dynamics between foundations, corporations, and individual contributors.
A Warning for the Future
The Terraform situation serves as a cautionary tale for the open-source community. It underscores the importance of transparency, collaboration, and adherence to the principles that have made open source a cornerstone of modern software development.
Looking Ahead: What’s Next for Terraform and Open Source?
The OpenTF Manifesto is a significant development in the ongoing saga of Terraform’s licensing change. It reflects deep-seated concerns within the DevOps and Open Source community and calls for a return to the principles that have guided open-source software for decades.
The manifesto’s call to action, whether realized or not, has already had a profound impact. It has ignited a conversation about the nature of open source, the responsibilities of project maintainers, and the rights of the community. As the situation continues to unfold, the DevOps and Open Source community must remain vigilant, engaged, and committed to the values that have made open source a driving force in innovation and collaboration. The Terraform case is not just a licensing issue; it’s a reminder of what open source stands for and why those principles must be fiercely protected.
The DevOps Joint 
Leave a comment