What HashiCorp’s License Change Means for Spacelift Customers

Re:What HashiCorp’s License Change Means for Spacelift Custo... by adrr on Friday August 11, 2023 @04:42PM (#37093749)

Because it infects code even if you don't modify it. You could just be using an API of an AGPL service, and it will hit your code. Its universally banned not just startups. I don't know of any organizations that allow it in their code base. If you want people to use your code, don't AGPL it.

Here's google's policy on it. https://opensource.google/documentation/reference/using/agpl...

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by josephcsible on Friday August 11, 2023 @04:46PM (#37093792)

> Because it infects code even if you don't modify it.

No it doesn't. The extra section of the AGPL that the GPL doesn't have explicitly says it only applies if you do modify it.

> Its universally banned not just startups.

You linked me to the rule that it's banned at Google, but still not to the source of any rule that it's banned at any startups.

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by yencabulator on Saturday August 12, 2023 @02:22PM (#37102826)

How about this: There are AGPL software vendors who think making HTTP requests to their AGPL software forces you to license the client as AGPL too. To avoid their lawsuits, companies forbid internal use of AGPL software.

[ Parent | on HN ]

Re:What HashiCorp’s License Change Means for Spacelift Custo... by JohnL4 on Saturday August 19, 2023 @10:51AM (#37189389)

7-day-old comment, but the company I work for (not a startup) flat-out bans creating a dependency on AGPL code.

[ Parent | on HN ]