This message was deleted.

We are a product company and we're about to embark on tf integration and obviously stopped. We use pulumi for now. We are reviewing our options on a technical from but not yet looked athe legal angle. Anyways here was a quick point of view to summarize. ------IMHO on the Hashicorp MPL/BSL topic- <The good> I think a good balance where BSL is still like MPL/open source but restrictive use Driven by lack of adoption of their other products so hopefully who ever owns their stocks will see a turnaround (CISCO – are you listening / apparently, they had failed an earlier attempt to acquire) All BSL code too will convert to MPL after 4 years (not exactly sure on the verbiage) From a business sense, this was inevitable I think (150M USD company today with negative EPS and no moves since their IPO a few years ago) / Something had to give We at QMCLOUD had lot of requests from our prospects to get TF included in our Low Code solution and we had it on our roadmap / Good that we didn’t move forward. Even though we use Pulumi’s Open Source components and they in turn use TF providers, we are not clear on how it affects us / Pulumi has assured us that it is the forked code but a lot grey areas / Lawyers will be busy <The NOT so good> What happens to all the crowd sourced code under the MPL ? Will they get remuneration if their code ends up in BSL? Its not fair A lot of companies (including what QMCLOUD uses in the backend) have forked the TF code as Hashicorp refused to merge their contribution / What happens to forked code – Is it MPL or BSL now?) – not clear Some of the TF provider module links are taking us to BSL license repository now (instead of MPL earlier / this will be huge if the provider modules are affected / Thesea re in the thousands and used by lots of commercial vendors) All uses are permitted except for Production unless their product is considered competitive (What if a vendor is developing a solution that Hashicorp is not in business today and decides to venture in) If this trend continues, open source contributors will be hesitant and this may be a chain reaction / only time will tell if it affects the quality of the products May be some thing like Oracle has done and messed up the java ecosystem

Even though we use Pulumi’s Open Source components and they in turn use TF providers, we are not clear on how it affects us / Pulumi has assured us that it is the forked code but a lot grey areas / Lawyers will be busy

This is the part that I find pretty spooky: feeling like you don't know your exposure when using a different package that depends on Terraform

Yes. Pulumi has assured us suggesting their forks are pending approval from Hashi and they thing hashi may not approve. So we will continue with the forked version which Pulumi thinks is out of the bsl license.

yeah I'm sure the Pulumi team will handle it, but it is lending a lot of credence to the idea that the community will fork