> 3. What are the implications of this change for end users of HashiCorp’s open source products?
> For end users who are using HashiCorp’s current open source products and new releases using the BSL license for their internal or personal usage, there is no change.
> 19. How does HashiCorp now refer to the freely available versions of products that were formerly known as open source (or OSS)?
> We have referred to versions of our products as either open source (OSS), Enterprise, or Cloud. Going forward, we will refer to the open, freely available versions as “community”. The BSL license is open, free, and source-available. However, it does not meet the definition of open source as defined by OSI, and that is why we will refer to the products as the "community" edition rather than the "open source" edition as we did previously. There are many references to open source on our websites and we are actively working to clarify these language changes in the coming weeks
fine i will split the hair with you.
Where is source available not good enough for the things that regular orgs do with terraform (or other products) right now.
What really is changing in the way you or even developers of provisioners handle the software?
You can't use the bsl licensed version if you're at all concerned that Hashicorp might decide at any point in the future that your business "competes" with theirs.
It's not about the source code. It's about the freedom.