Open Source Chronicles

OpenTofu has matured significantly since its fork from Terraform. Here’s where things stand and what it means for teams managing cloud infrastructure.

A year and a half after forking from Terraform, OpenTofu is proving that community-driven infrastructure tooling can thrive — but challenges remain.

The WordPress/WP Engine feud has escalated into a full-blown crisis, raising fundamental questions about open source governance and commercial ecosystems.

The escalating conflict between Automattic and WP Engine raises fundamental questions about open source trademarks, governance, and what happens when a project’s founder picks a fight.

Redis Labs switches from BSD to a dual SSPL/RSALv2 license, and the Linux Foundation responds by backing the Valkey fork.

OpenTofu hits its first GA release, proving that the open-source fork of Terraform is more than a protest — it’s a viable alternative.

As OpenTofu approaches its first stable release, the HashiCorp license change continues to reshape how we think about open source infrastructure tooling.

OpenTofu, the community fork of Terraform born from HashiCorp’s license change, is rapidly building momentum under the Linux Foundation.

HashiCorp’s switch to the Business Source License has triggered a community fork of Terraform called OpenTofu, and the implications for infrastructure-as-code are enormous.

HashiCorp’s decision to relicense Terraform and other products under the Business Source License has sent shockwaves through the infrastructure community.

Red Hat’s decision to restrict public access to RHEL source code sends shockwaves through the enterprise Linux ecosystem and raises fundamental questions about open source sustainability.

As millions flee Twitter for Mastodon, the decentralized social protocol ActivityPub faces its biggest real-world scalability challenge yet.