Like many other companies, HashiCorp has dropped the open source approach that gave its products their start for the source-available Business Source License (BSL).
HashiCorp is moving its products previously licensed as Open Source away from it to Business Source License (BSL) moving forward
Terraform is a popular Infrastructure as Code tool used for provisioning cloud resources like AWS, Azure among others
Terraform version 1.5.5 and earlier are still open source
there is a push for a community maintained open source fork if this decision is not reversed, OpenTF
The integrations with other services are implemented in plugins which are separate programs, that are installed separately, and communicate with the core over RPC. I would imagine these plugins can continue to be licensed however their owners choose. I think this license change just applies to core.
When Canonical originally had such a CLA to contribute to Ubuntu it was pretty controversial (I don’t think it was common at all at the time), this situation with HashiCorp perfectly demonstrates why.
I’m not as familiar with MPLv2 but I don’t think they can with contributions to the fork. Since those contributions won’t be part of the original “we own all your work” agreement they couldn’t simply close source those contributions.
Q: I have written a code patch to a BSL project and would like the BSL vendor to maintain the code as part of the BSL project. How do I contribute it?
A: License your code using the “new BSD” license or dedicate it to the public domain. Code contributions under “new BSD” is compatible with BSL. See BSD on Wikipedia.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
For the people who continue to work on the open source fork of terraform, can HashiCorp pull their commits into their closed source BSL fork?
I would assume not, but I am curious if there’s some weird workaround of their previous license that they still own contributions
The integrations with other services are implemented in plugins which are separate programs, that are installed separately, and communicate with the core over RPC. I would imagine these plugins can continue to be licensed however their owners choose. I think this license change just applies to core.
deleted by creator
ouch… Well, with the fork they wont have to do that anymore… so thats good.
When Canonical originally had such a CLA to contribute to Ubuntu it was pretty controversial (I don’t think it was common at all at the time), this situation with HashiCorp perfectly demonstrates why.
I’m not as familiar with MPLv2 but I don’t think they can with contributions to the fork. Since those contributions won’t be part of the original “we own all your work” agreement they couldn’t simply close source those contributions.
From the BSL FAQ:
That would seem to rule out the MPLv2.
That is for continuing contributions to the commercial project, the fork should be using the old license not the BSL.
The question was if HashiCorp could take contributions to the fork and put them into their commercial product.
That means HashiCorp could only take contributions licensed under the BSD or public domain, or under a CLA. The fork would be none of those.