news.volyx.in

HashiCorp adopts Business Source License (hashicorp.com)

632 points by rpadovani · 1111 days ago · 731 comments on HN

Article summary

HashiCorp has adopted the Business Source License, which has sparked discussion among users and developers. The licensing model has raised concerns about the company's intentions and the potential impact on small to medium-sized companies. The move is seen as a way for HashiCorp to ensure that large companies contribute to the project's sustainability. The exact implications of the new license are still being debated.

Main themes

  • Open-source licensing
  • Business models
  • Community sustainability
  • Corporate contributions
  • License agreements
  • Free and open-source software philosophy

What commenters say

  • The Business Source License is seen as a way for HashiCorp to profit from its software without contributing back to the open-source community.
  • Some argue that the license is necessary to ensure the sustainability of the project, while others see it as a threat to the open-source spirit.
  • The definition of a 'freeloader' is disputed, with some arguing that it refers to companies that profit from open-source software without contributing back, while others see it as anyone who uses open-source software without contributing.
  • The use of permissive licenses like BSD is seen as a way for companies to use open-source software without contributing back, leading some to argue that stronger licenses like the AGPL are needed to protect the community.
  • The move to the Business Source License is seen as a sign that the open-source model is not sustainable for large companies, and that a new approach is needed to ensure the continued development of open-source software.
  • Some argue that the Business Source License is a pragmatic solution that balances the needs of the company with the needs of the community, while others see it as a step towards closed-source software.
  • The lack of clarity around the license's terms and conditions has led to concerns about its potential impact on the community and the future of open-source software.