this post was submitted on 19 Aug 2023
115 points (100.0% liked)

Technology

37602 readers
562 users here now

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.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 
  • 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

Gruntwork response on the problem with BSL

you are viewing a single comment's thread
view the rest of the comments
[–] jet@hackertalks.com 12 points 1 year ago (8 children)

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

[–] robyoung@beehaw.org 5 points 1 year ago

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.

load more comments (7 replies)