When I heard that Teleport ist gonna change their license, I almost had a "aight, here we go again" moment after being fucked with by #Lightbend and #HashiCorp recently. Thankfully they switched to AGPL and not BSL (which I think stands for bullshit license).
The common tactics of companies "promoting #opensource" to gobble up a larger audience and then pull a bait and switch with the licensing seems to have caused me some serious PTSD.
Hashicorp CEO furious that #FOSS works as intended and he won't be able to pull the rug from under the devs community's feet in ways similar to the MO of web services who accrue vast amounts of data and user-generated content in their siloes built from expropriated information.
HashiCorp CEO predicts OSS-free Silicon Valley unless the open source community lets him destroy the entire concept of open source and rebuild it in his capitalist vision
This is really important: these companies don't just want to relicense their software, they want to destroy open source itself as a concept and replace it with something they can control.
I am really excited to attend Hashiconf in San Fransico for the first time! As a long-time user of tools like Nomad, Vault, and Consul, I cannot wait to meet the teams behind the different tools and learn more about them. Nomad has powered the @bitexpert internal infrastructure for a few years now. Vault & Consul perfectly complement that stack.
Look mom, I’m in the news! After having talked to @BPariseau about #OpenTofu and the #HashiCorp#Terraform drama yesterday. I’m sure we’ll get to read much more on this in the near future, so make sure to follow her!
Idea: An #opensource#secrets manager, with a fancy web UI like #Hashicorp#Vault, that can organize secrets by folders and deployment target (dev, staging, prod) and the CLI tool can translate those folders, keys, and values into structured YAML or JSON output in addition to environment variables. Additionally, it can import secrets into new projects with structure YAML/JSON into the format.
I hope someone else takes the reigns on #opensourcedotcom. I'm the age of #Hashicorp, we need a microphone so that truly #opensource companies can be discovered and gain visibility. The need for such a website is great and timely right now.
This week we’re talking about the launch of #OpenTF and what it’s going to take to successfully fork HashiCorp’s #Terraform 🍴
We’re joined by Josh Padnick to discuss what exactly happened, how #HashiCorp’s license change changes things, who has been impacted by this change, and ultimately what they are doing about it 💪
@changelog@adam@jerod As always a great interview. I really like that Josh Padnick did his best not to bash to much on #HashiCorp. To me it really sounds like OpenTF is a far better position that the original project to succeed.
I guess you have reached out already but a interview with someone at #HashiCorp to get their view on this would also be awesome.
@giffengrabber I agree to all of the above. The fact that #Hashicorp#Vault existed and was so ubiquitous for so long has meant that other FOSS competition just hasn't matured at the same pace.
There is absolutely a business opportunity here for a fully FOSS, commercially supported key manager. If it has a clean web UI and CLI; can run on/integrate with cloud envs, kubernetes, and CI/CD environments; and supports RBAC, it'll become popular real fast.
Imagine if Github said you couldn't use the node registry unless you used NPM and then tried to limit your use of these open source libraries to only hosting on Azure.
Ridiculous right? Well #Hashicorp is trying it with the Terraform Registry.
This goes beyond relicensing. Terraform by itself is useless without the providers and public modules, but Hashicorp relies on volunteers and other companies to write these. It's not even their code!
HashiCorp got the wrong message from the Terraform fork by OpenTF 🤦 and is doubling down on being an ass.
They changed their ToS to state:
"You may download providers, modules, policy libraries and/or other Services or Content from this website solely for use with, or in support of, HashiCorp Terraform. "