HashiCorp CEO 预测，除非开源模型发展，否则硅谷将没有开源公司
HashiCorp 开源 Terraform
![](/data/attachment/album/202310/23/100619d754xnee4kksw7sr.jpg)



> 
> 他还称，Linux 基金会接受 OpenTofu 的决策是一个 “悲剧”。
> 
> 
> 


（本文节略自 The Stack 的[文章](https://www.thestack.technology/hashicorp-ceo-predicts-oss-free-silicon-valley-unless-the-open-source-model-evolves/)）


HashiCorp 的 CEO 在该公司本月的用户会议上为其改变许可证的做法辩护。他预测，除非社区重新思考如何保护创新，否则硅谷将 “不再有开源公司”。


作为 IaaC 的先驱者，他在 HashiConf 用户会议上介绍了一系列产品了更新和新特性，这是在该公司将其所有产品的版权协议从 <ruby> Mozilla 公共许可证 <rt>  Mozilla Public License </rt></ruby>（MPL）更改为 <ruby> 商业源代码许可证 <rt>  Business Source License </rt></ruby>（BSL）后不到两个月时间所做的举措。


HashiCorp 当时表明，“除了在与 HashiCorp 商业产品竞争的产品中托管或嵌入软件外，所有生产用途都不受限制，无论是自我管理的还是托管的。”


然而，此举引起了开源社区的强烈反响。在 Linux 基金会的支持下，一个名为 OpenTofu 的 Terraform 分支很快地被发布出来。


HashiCorp 的 CEO Dave McJannet 本周表示，改变许可证的决策是必要的，因为 HashiCorp 的技术对现代云服务起到了关键的作用，随着全球最大的公司将其业务从本地技术转移到云服务，这种关键性只会越来越强。


尽管开源社区猛烈批评了 HashiCorp 改变许可证的决定，但 McJannet 说其最大的客户对此的反应却是，“太好了，因为你是我们的关键伙伴，我们需要你发展成一个大公司。”实际上，他表示，在很多反馈中客户表示，“我们希望你早点这么做”，并补充说，这个决定在公告之前就已经与主要的云供应商进行了讨论。


McJannet 说，“过去三四年间，每个达到一定规模的供应商都已经得出了同样的结论。……这只是意识到，鉴于市场现在的激励机制，开源模型必须演进。”


他声称，过去成立开源基金会的模式现在已经不合时宜了，这些基金会都被传统供应商所主导。以 Hadoop 为例，他说，“基金会就是大公司免遭创新影响的一种机制，如果 Hadoop 流行起来，IBM 这样的公司可以把它拿来，因为他们是基金会的一部分，他们可以以更低的价钱卖出去。”


将开源产品放到 GitHub 上 “的确非常好”，但是，一旦某个项目变得流行，“克隆供应商就开始竞相复制”。


他声称，“我们发出公告后不久，我就开始接到来自硅谷每一个开源创业公司的电话，他们都告诉我，‘我认为这才是正确的模型’。”


“确实是悲剧……”，他感叹道，Linux 基金会接受 OpenTofu 的行动，为我们揭示了一个严重的问题。“如果基金会只是简单地接收并给它找个归宿，那对开源的未来将带来怎样的影响呢？这对开源创新而言，无疑是一场悲剧。我可以坦诚告诉你，如果这样的事情真的发生，硅谷将再也看不到开源公司的身影。”


他更具体地指出，许可证的改变是他们为赢取企业信任而设计的策略的一部分。


“让其他供应商误解我们的产品是一个巨大的风险，对吗？这对我们的长期发展是不利的，对我们的客户而言也同样危险。”


他进一步解释说，赢得这些大型组织的信任是促使 HashiCorp 当时选择上市的一个驱动力。“我们并不全然需要钱，我们之所以这么做，是想要向公众表明，我们有充足的资金，可以成为他们长期信任的合作伙伴。”


他补充说，他们提议继续和受许可证更改影响的四个主要的公司合作，“只需要你们承担一部分研发成本。然而他们却拒绝，声称要另起炉灶，这对我们来说也没问题。”


*（题图：MJ/5cdb5ba0-a7fa-4a29-b3dd-ef0d07bad575）*




---


via: <https://www.thestack.technology/hashicorp-ceo-predicts-oss-free-silicon-valley-unless-the-open-source-model-evolves/> 


作者：[JOE FAY](https://www.thestack.technology/author/joe/) 译者：[ChatGPT](https://linux.cn/lctt/ChatGPT) 校对：[wxy](https://github.com/wxy)


本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](/article-16307-1.html) 荣誉推出


OK
HashiCorp’s CEO predicted there would be “no more open source companies in Silicon Valley” unless the community rethinks how it protects innovation, as he defended the firm’s license switch at its user conference this month.

The IaaC pioneer unwrapped a slew of product updates and features at HashiConf in San Francisco, barely two months after it [switched](https://www.thestack.technology/hashicorps-poison-pill-shift-away-from-open-source-triggers-call-for-terraform-to-be-run-by-a-foundation/) future versions of its entire product set from the Mozilla Public License to the Business Source License (BSL).

At the time, HashiCorp said, “All production uses are allowed other than hosting or embedding the software in an offering competitive with HashiCorp commercial products, hosted or self-managed.”

However, the move drew a furious reaction from the open source world. OpenTofu, a fork of Terraform, was [launched](https://www.thestack.technology/opentofu-terraform-fork/) in short order, under the aegis of the Linux Foundation.

CEO Dave McJannet said this week that the license switch had been necessary as HashiCorp’s technology was critical to the modern cloud, and would only become more so the world’s biggest companies complete their shift from on-prem technologies.

While open source advocates had slammed the license switch, McJannet described the reaction from its largest customers as “Great. Because you’re a critical partner to us and we need you to be a big, big company.”

Indeed, he claimed that “A lot of the feedback was, ‘we wished you had done that sooner’” – adding that the move had been discussed with the major cloud vendors ahead of the announcement.

“Every vendor over the last three or four years that has reached any modicum of scale has come to the same conclusion,” said McJannet.

“It’s just the realisation that the open source model has to evolve, given the incentives that are now in the market”

He claimed the historic model of foundations was broken, as they were dominated by legacy vendors. Citing the case of Hadoop, he said: “They’re a way for big companies to protect themselves from innovation, by making sure that if Hadoop becomes popular, IBM can take it and sell it for less because they are part of that foundation.”

The evolution to putting open source products on GitHub had worked “really, really well” but once a project became popular, there was an incentive for “clone vendors to start taking that stuff.”

He claimed that “My phone started ringing materially after we made our announcement from every open source startup in Silicon Valley going ‘I think this is the right model’.”

## "Tragic..."

He said the Linux Foundation’s adoption of Open Tofu raised serious questions. “What does it say for the future of open source, if foundations will just take it and give it a home. That is tragic for open source innovation. I will tell you, if that were to happen, there'll be no more open source companies in Silicon Valley.”

More specifically, McJannet said the licensing change was part of its strategy to earn the confidence of enterprises.

“Having other vendors out there misrepresenting our stuff is dangerous, right? Not only is it not great for us long term is dangerous for our customers.”

That same need to earn the trust of such of large entities was one of the drivers for HashiCorp going public when it did. “We didn't need the money. We did it because we wanted to send the signal that we were funded to be a long term trusted partner.”

He added that it offered to carry on working with the four main companies affected by the switch, saying “You just have to bear some of the r&d costs. And they were like, ‘No, no, we're gonna do something else’. Which is fine.”

## New Hashicorp products unveiled

McJannet’s comments came as HashiCorp unwrapped a slew of beta and GA products.

For its core Terraform IaaC tool, it announced a beta of test-integrated module publishing, and generated module tests.

The former aims to streamline the testing and publication of modules – the containers used to hold and reuse config files in the Terraform architecture - with a new branch-based publishing approach in the HashiCorp Cloud private registry. The firm said this means tests can be executed remotely in a secure environment, eliminating the need for developers to handle sensitive cloud credentials on their workstation.

The latter uses generative AI to produce new module tests. The company worked with a third party to train the underlying model on HCL and Terraform. Senior director of product marketing Chris Van Wesep said the model had been trained on HashiCorp’s own internal data, not customer data: “It's more a sophisticated prompt engineering that we did.”

It also unveiled a private preview of Stacks, which aims to simplify infrastructure provisioning and management at scale, reducing the complexity users face managing dependencies as they repeatedly deploy infrastructure. It allows users to group together different interdependent systems, which become “deployments in a stack” and can be repeatedly replicated even with differing input values.

On security, it announced an alpha program for HCP Vault Radar, which scans code for secrets, as well as other potential nasties including personally identifiable information, non-inclusive language, dependency vulnerabilities, and IAC risks. It is the first deliverable from HashiCorp’s acquisition of BlueBracket in June.

It also announced that Vault Enterprise Secrets sync is now in beta in Vault Enterprise 1.15. It was previously only available in HCP Vault Secrets.

HashiCorp unveiled a “new vision” for its HCP’s Waypoint platform, subtly changing its goal from “helping to standardize application delivery across platforms” to “empower[ing] platform teams to define golden patterns and workflows for developers to management applications at scale”.

The firm said the rework was the result of research with platform teams that showed it made sense to tackle challenges that arose before the deployment and management part of the lifecycle.

HashiCorp’s ultimate focus in on its HashiCorp Cloud Platform (HCP) managed services offering, and new technologies and features will initially be deployed to HCP. However, McJannet said that features will continue to be rolled out to its self-managed product, typically within a month. The exception, he said, was with Waypoint, which he said would be offered solely as a managed service.