Terraform infrastructure-as-code tool recently switched to a BSL license. As a result, it was forked into a new project called OpenTF. Let's look at open-sou...
    • cpressland@devops.pizzaEnglish
      14·
      11 个月前

      Doing what’s right is always wrong if it’s against a large corporation. I’m grateful to HashiCorp for making Terraform, but I’m absolutely done with them as a company.

    • makingStuffForFun@lemmy.mlEnglish
      26·
      11 个月前

      Agree. A tiny text description even. I despise clicking a tracker like you tube. Glad that piped bot is here though.

      Description:

      Terraform infrastructure-as-code tool recently switched to a BSL license. As a result, it was forked into a new project called OpenTF. Let’s look at open-source licensing and find out why this drama occurred.

    • Earl Turlet@lemmy.zipEnglish
      141·
      11 个月前

      Hashicorp recently changed the license of Terraform and its other core products from MPL to BSL, restricting commercial use and preventing competitors from offering services based on the code. While this makes business sense for the now-public Hashicorp, it upset many users who saw it as undermining the open source nature of the projects. In response, the OpenTF project was launched to fork Terraform and maintain it under a truly open source license. While Terraform is not as likely to cause vendor lock-in as databases, its dominance as a developer tool could be impacted by this change and emerging alternatives. Interestingly, the video ends by humorously discouraging viewers from supporting the OpenTF project in opposition to Hashicorp’s licensing change.

      Via Kagi universal summarizer

    • AureumTempus@lemmy.worldEnglish
      81·
      11 个月前

      Not trying to defend Hashicorp, but you also have to understand that this is more and less our fault for using big-tech platforms.

      Devs want convenient solution for the cloud, and we use tools from big-tech, at the cost of getting vendor-locked and also watching them exploit other open-source project.

      Hashicorp, just like MongoDB and Elasticsearch were sick of Amazon raking in profits from these sources. These companies wouldn’t have gone to such lengths. Clearly, Amazon is the bigger villain here, but almost everyone here fails to acknowledge the same.

      • TheLordHumungus@lemmy.worldEnglish
        5·
        11 个月前

        I do get that, it is kind of a gut punch though. I really wonder if it matters especially since the open source version may be coming out (I am not completely sold on the fork), could that kill hashicorp? I hope they keep their jobs and get to keep doing what they love. I do feel bad for the devs and others who really are put between a rock and a hard place. I do want to give them credit for their licence, I think they probably did the best with a bad situation. I am preferential towards open source but I am not an open-source/libre absolutist. I understand the hard decisions must be made when you are toiling away to get exploited by even bigger assholes like Amazon, Google, etc.

        • AureumTempus@lemmy.worldEnglish
          21·
          11 个月前

          I really wonder if it matters especially since the open source version may be coming out

          I’d like to believe that Amazon folks might be drooling at this idea, but not for too long. In all honesty, BSL isn’t a bad license per se. If anything, it is better than a license that hides source code. To be exact, it’s a source-available license, just not open-source. Their earlier license was MPL, which is generally regarded as a better permissive open-source license. I’m more of a “prefers GNU, but can settle” type, so I don’t see any issue with it.

          If you’re not an absolutist, you should not worry about this drama. You only have to choose which of the either team provides better service, and the direction the project takes in. The original maintainers are part of the company, and so in a way, I don’t see the value this fork adds - perhaps, it is a preventive measure for the worst case, just like Apple did with XNU. They get paid to write code, but the people putting their effort in a fork do not. Amazon might be forced to pay donations to full-time maintainers and contributors. Either way, it’s a win-win situation. People still use Elasticsearch, MongoDB and Redis, so this too, shall pass.