8 ms·

And, if those projects had been licensed using AGPL, then Hashicorp would not be able to relicense this without negotiating a non-GPL license for themselves, fi

And, if those projects had been licensed using AGPL, then Hashicorp would not be able to relicense this without negotiating a non-GPL license for themselves, first. I don't understand why GPL gets so much hate on HN.

afiori 3y ago
deploying AGPL software is complicated
- orthoxerox 3y ago
  Not really, just push the tarball with sources to nginx when you deploy a specific commit.
  - sitzkrieg 3y ago
    yea this is definitely user friendly and realistic
    - jen20 3y ago
      If you make modifications, and deploy them in a way accessible to a given user, the changes must be made available to that user. I fail to see what is unrealistic about that, or indeed user-unfriendly, unless you consider the user to be the developer and not the person on the other end of the wire.
    - post-it 3y ago
      Glad you agree.
  - arlcode 3y ago
    You don't even need to do that immediatly afaik. You can wait for the first person to request the source and do it then manually (or link to the nginx github). Most likely that will never happen for most people who deploy it. After all it's a pretty good price for what you are getting in exchange.
  - yencabulator 3y ago
    There are AGPL software vendors who think making HTTP requests to their AGPL software forces you to license the client as AGPL too.
- eatonphil 3y ago
  Why do you say that? (Or to anyone, why do people think this?) I don't know anything about AGPL.
  - chii 3y ago
    It's not complicated, unless what you intend to do when deploying AGPL software is actually to try circumvent the license in some way; e.g., you would like some proprietary modifications to be added but still comply with the AGPL requirements.
    - JamesDeansSon 3y ago
      [flagged]
- josephcsible 3y ago
  The AGPL's extra requirements only apply if you modify the program. If you don't, then deploying it is just as easy as deploying an MIT-licensed program.
  - afiori 3y ago
    I believe that the AGPL has the same boundaries as the GPL that is if you for example run a nodejs server using a single AGPL package in your node_modules then users should be able to download the source code of your entire node app.
    - josephcsible 3y ago
      But now you're talking about using an AGPL library in your own program, rather than deploying just an AGPL-licensed program.
      - afiori 3y ago
        libraries are software
        josephcsible 3y ago
        Yes, but my point is there's a difference between "just deploy their software" and "combine their software with your software and deploy the result".
        afiori 3y ago
        I agree, but for example it is not obvious whether you can deploy mixed licenses with docker-compose.
      - andrewl-hn 3y ago
        When you include an AGPL library your program becomes a derivative work, so the rest of your program becomes AGPL-licensed as well. The boundaries of what part of the system should or should not be included are vague, because *GPL licenses are written with C semantics in mind. So, while having a library directly in the same running process definitely makes you work a derivative, it's not clear if you the same is true if the library is a part of a different process and your program talks to it via an IPC, a filesystem, a database, an API, etc. Depending of the interpretation you may have toped-source just a tiny part of your program running on a server, or all server-side and client-side code and all supplemental scripts, tools, etc. needed for the system to run. So, it's legally ambiguous, and since no-one has legally tested the waters the interpretation of the license can be very different, but most people prefer to stay away from AGPL code altogether.
fractalb 3y ago
I definitely feel GPL has its own merits. It's time people recognize that.
- pydry 3y ago
  They do. The merits are what make FAANG angry. They want the right to profit from your work without any corresponding obligations and GPLv3, AGPL, SSPL, BPL, etc. all deny them that right.
  - josephcsible 3y ago
    It's not really about profit. The GPL doesn't restrict that. It's about wanting to leech off of the FOSS community by turning other people's FOSS code into proprietary products. By the way, the SSPL isn't free or open source, so lumping it in with the GPL and AGPL like that could easily mislead people.
- demizer 3y ago
  My personal open source contributions will only be GPL. Damn the torpedoes! I will only contribute to lesser licenses if I am getting paid by a corp, which I do, and of course that software cannot be GPL'd.
redeeman 3y ago
because people prefer not to pay back, GPL and AGPL has a cost that many consider to be limiting their ability to earn money based on it, so it gets hate. its really quite simple, you're no worse off than if there were no GPL/AGPL to begin with, so just dont use it if you dont agree. I personally am very concerned with the newer trends of going away from GPL, I think its gonna turn out bad for everyone
- chii 3y ago
  Stallman's foresight has been eerily accurate - look at what google's web environment integrity proposal to say the least. It's time the OSS community stop making free software with a loose license such that control and ownership is taken from them, and for profit to be made without any give backs.
- sneak 3y ago
  You don't need to "pay back" for a gift. The problem is entitlement and thinking that anyone owes you anything after you have given software away to the world. It's no longer yours, there is no "back".
  - redeeman 3y ago
    but its not a gift when its GPL, its distribution under certain terms, and to complain someone chooses GPL rather than BSD is not legit
bombcar 3y ago
The variously GPLs have always received hate of different kinds, and time and time again it's proven why they have the clauses they do. Reminds me of the picture of the smug cat surrounded by knives. GPL is that cat.
- ethbr0 3y ago
  People say lawyers are assholes, but they don't think about why lawyers are assholes. It's a lawyer's job to imagine the worst future outcomes and guard against them in the present. Everybody focuses on "It's crazy you put that clause in there that was never needed," but few folks appreciate "Thank god we included that clause just in case." Which isn't to opine there's a right or wrong, only multiple parties each negotiating (skillfully or poorly) in their own interests. If you're a developer and don't want your code to slide into corporate controlled ownership... well, there are licenses for that. https://github.com/readme/guides/open-source-licensing https://github.com/readme/guides/open-source-licensing https://arstechnica.com/gadgets/2020/02/how-to-choose-an-open-source-license/ https://arstechnica.com/gadgets/2020/02/how-to-choose-an-ope...
  - deleted 3y ago
    [deleted]
  - JohnFen 3y ago
    Yes. As a rough analogy that my lawyer told me early on, lawyers are like software engineers, and the law is like the operating system. A good lawyer writes robust "code" designed to deal with edge cases and unexpected conditions gracefully.
  - kjs3 3y ago
    I think every single one of my attorneys over the years has made it clear that if something is in the contract/license/etc, you absolutely have to assume it will be enforced, to the letter. No matter how stupid, no matter how unlikely. If it's written down, it was written down for a reason. One of the worst mistakes you can make in life is believing anyone who says things like "oh, that's just boilerplate...we'd never act on it" or "don't worry, we would never enforce that" or similar. That's someone who is deliberately setting you up to get screwed.
appplication 3y ago
GPL gets hate because it’s a self-killing license. Sure, it’s great idealism, but it just creates an incentive for any corporate interests to create either a closed source offering or a better funded competing OSS offering that can be commercialized. If some software provides value, it will eventually be monetized in some form. It makes no sense for a corporation, whose entire existence is predicated on monetization, to see GPL software and say “I guess I’ll just stop charging for our products!” Instead, the completely predictable response is “this is valuable, but I can’t use it, so I’m going to make something like it that I can actually use”. Like it or not, you cannot “hide” value from capitalism. The machine will find and extract value wherever it can. GPL establishes unrealistic ideals for software that are inconsistent with the reality of how and where it is used.
- chii 3y ago
  > it just creates an incentive for any corporate interests to create either a closed source offering or a better funded competing OSS offering that can be commercialized. what's wrong with that? If they produce their own version, then the world now has another piece of software, and this competition is going to make the ecosystem better imho. The only problem with lenient licenses is that they allow leeching. MIT, eclipse, and apache licenses, all are basically allow free commons which others leech off as much as possible. The corps may continue to contribute, but only because they see value they could extract more than what it costs them. I would say AGPL should be the _only_ license anyone contributing to OSS should pick. And if you own the project, make it dual licensed - a commercial offering, and AGPL. If said software is good, a commercial offering can be profit generating enough fund further development.
  - appplication 3y ago
    There’s nothing wrong with that, and there’s nothing wrong with people who want to build GPL software - do what you like, consistent with your ideals. This is really only in response to the perennial “why don’t more people use GPL” questions that seem to always pop up any time software licensing is discussed. It’s fine for some people, but there’s a reason corps tend to avoid it or have internal policies against using GPL software.
spaceribs 3y ago
Hacker news is a mix of venture capital and technologists, the AGPL3 is a wedge between those two groups needs and objectives.
- dilyevsky 3y ago
  For agpl specifically I believe it’s due to muddy waters surrounding the “derivative work” clause. Some companies have traditionally bent the definition (eg insinuating that api calls result in larger application fall under combined work) and it’s never been tested in court so understandably the lawyers do the lawyer thing and tell you not to use it
  - spaceribs 3y ago
    Yeah, but even stepping back there, lawyers are paid to prevent companies from entering those muddy waters as a risk to their profits. Profit isn't a concern to someone who wishes to publish open source software, in fact you could say Open Source is an inherently socialist venture (your socializing the tools/means to do something). The AGPL3 makes it more difficult for others with probably more means to profit on that work, so it's a net benefit to the folks who actually write code (and a detriment to those who would wish to exploit it).
    - dilyevsky 3y ago
      Right so as long as food and shelter is not a concern AGPL is v good license!
      - spaceribs 3y ago
        Yep! I'd say 95% of open source is subsidized by those thriving rather than surviving, having the education/equipment/access/free-time to deliver open source software is a product of privilege and abundance.
  - _cenw 3y ago
    Not only some companies - API calls being linking also seems to be the opinion of the FSF.
adrr 3y ago
Because most startups can’t use AGPL. I had to provide audits of our licenses of libraries we use in our code base to investors and attest we didn’t have AGPL code in our code/software in our stack. This was at an e-commerce company and not a company that directly monetized software. Companies are free to choose whatever license but it will limit who can use their software.
- _xivi 3y ago
  > I had to provide audits of our licenses of libraries we use in our code base to investors and attest we didn’t have AGPL code in our code/software in our stack. A little off topic, but how are these audits usually done? I'd like to familiarize myself Not necessarily your specific case, if there's a resource online that'd be fine
  - adrr 3y ago
    We run a script that scans our source code and generates a manifest of all included libraries including license/copyright. Here's one of them: https://github.com/nexB/scancode-toolkit https://github.com/nexB/scancode-toolkit
    - pabs3 3y ago
      There are others, but scancode is probably the best one, their license database is truly huge. https://wiki.debian.org/CopyrightReviewTools https://wiki.debian.org/CopyrightReviewTools https://scancode-licensedb.aboutcode.org/ https://scancode-licensedb.aboutcode.org/
  - __jonas 3y ago
    Fossa built a business around this: https://fossa.com/ https://fossa.com/
  - nijave 3y ago
    The less automated version is a list of requirements to the effect "list all the OSS libraries you use and their licenses" are pushed down to each team and someone spends a day or 2 going through their code base. Usually that amounts to looking at a lock/dependency file and finding the software's license online. You can also run an audit against your artifact store/cache if you have one. JFrog Artifactory has built-in tools for auditing dependencies (and can act as a pull through cache) so you can run reports that way but it can be harder to tie dependencies to what's using them. Back when I worked at Chase, it was against company policy so use 3rd party dependencies that weren't in their internal components database. Part of getting something in the components database was establishing an owner, the license, and the version (basically a paperwork/approval process). In addition, part of the deploy process was running a vulnerability check against your dependencies using some proprietary enterprise software that tracked CVEs and could (somewhat...) parse what dependencies an application was using (ideally, automatically...).
thayne 3y ago
They were licensed under MPL, which would have also prevented a relicense like this without the CLA. And I don't think the MPL would even prevent them from selling their commercial products.
kj4ips 3y ago
With the CLA in place, it doesn't matter. All contributors already gave hashicorp a broad license for everything that they don't already own, so hashicorp has license to largely do whatever regardless of what license they use to offer it to others.
- josephcsible 3y ago
  Only the code in HashiCorp's own code is covered by the CLAs, not the code in the third-party dependencies it has. If said dependencies used copyleft licenses like (A)GPL instead of pushover licenses like MIT, that would have prevented what HashiCorp did.
- _msw_ 3y ago
  The CLA was put in place in December of 2018 [1]. Presumably contributions made before that were under inbound=outbound terms [2], meaning the contributing author licensed their exclusive rights under MPL 2.0, which is a file-based copyleft license. (see the chart at [3]). [1] https://www.hashicorp.com/blog/introducing-a-cla https://www.hashicorp.com/blog/introducing-a-cla [2] https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#6-contributions-under-repository-license https://docs.github.com/en/site-policy/github-terms/github-t... [3] https://en.wikipedia.org/wiki/License_compatibility#Compatibility_of_FOSS_licenses https://en.wikipedia.org/wiki/License_compatibility#Compatib...
Xylakant 3y ago
The projects license is of no concern at all here. Licenses do not bind the owner of the code. Hashicorp required a CLA before contributing, so they own the copyright. They can change the license at any time as they see fit.

afiori 3y ago

deploying AGPL software is complicated

orthoxerox 3y ago
Not really, just push the tarball with sources to nginx when you deploy a specific commit.
- sitzkrieg 3y ago
  yea this is definitely user friendly and realistic
  - jen20 3y ago
    If you make modifications, and deploy them in a way accessible to a given user, the changes must be made available to that user. I fail to see what is unrealistic about that, or indeed user-unfriendly, unless you consider the user to be the developer and not the person on the other end of the wire.
  - post-it 3y ago
    Glad you agree.
- arlcode 3y ago
  You don't even need to do that immediatly afaik. You can wait for the first person to request the source and do it then manually (or link to the nginx github). Most likely that will never happen for most people who deploy it. After all it's a pretty good price for what you are getting in exchange.
- yencabulator 3y ago
  There are AGPL software vendors who think making HTTP requests to their AGPL software forces you to license the client as AGPL too.
eatonphil 3y ago
Why do you say that? (Or to anyone, why do people think this?) I don't know anything about AGPL.
- chii 3y ago
  It's not complicated, unless what you intend to do when deploying AGPL software is actually to try circumvent the license in some way; e.g., you would like some proprietary modifications to be added but still comply with the AGPL requirements.
  - JamesDeansSon 3y ago
    [flagged]
josephcsible 3y ago
The AGPL's extra requirements only apply if you modify the program. If you don't, then deploying it is just as easy as deploying an MIT-licensed program.
- afiori 3y ago
  I believe that the AGPL has the same boundaries as the GPL that is if you for example run a nodejs server using a single AGPL package in your node_modules then users should be able to download the source code of your entire node app.
  - josephcsible 3y ago
    But now you're talking about using an AGPL library in your own program, rather than deploying just an AGPL-licensed program.
    - afiori 3y ago
      libraries are software
      - josephcsible 3y ago
        Yes, but my point is there's a difference between "just deploy their software" and "combine their software with your software and deploy the result".
        afiori 3y ago
        I agree, but for example it is not obvious whether you can deploy mixed licenses with docker-compose.
    - andrewl-hn 3y ago
      When you include an AGPL library your program becomes a derivative work, so the rest of your program becomes AGPL-licensed as well. The boundaries of what part of the system should or should not be included are vague, because *GPL licenses are written with C semantics in mind. So, while having a library directly in the same running process definitely makes you work a derivative, it's not clear if you the same is true if the library is a part of a different process and your program talks to it via an IPC, a filesystem, a database, an API, etc. Depending of the interpretation you may have toped-source just a tiny part of your program running on a server, or all server-side and client-side code and all supplemental scripts, tools, etc. needed for the system to run. So, it's legally ambiguous, and since no-one has legally tested the waters the interpretation of the license can be very different, but most people prefer to stay away from AGPL code altogether.

fractalb 3y ago

I definitely feel GPL has its own merits. It's time people recognize that.

pydry 3y ago
They do. The merits are what make FAANG angry. They want the right to profit from your work without any corresponding obligations and GPLv3, AGPL, SSPL, BPL, etc. all deny them that right.
- josephcsible 3y ago
  It's not really about profit. The GPL doesn't restrict that. It's about wanting to leech off of the FOSS community by turning other people's FOSS code into proprietary products. By the way, the SSPL isn't free or open source, so lumping it in with the GPL and AGPL like that could easily mislead people.
demizer 3y ago
My personal open source contributions will only be GPL. Damn the torpedoes! I will only contribute to lesser licenses if I am getting paid by a corp, which I do, and of course that software cannot be GPL'd.

redeeman 3y ago

because people prefer not to pay back, GPL and AGPL has a cost that many consider to be limiting their ability to earn money based on it, so it gets hate. its really quite simple, you're no worse off than if there were no GPL/AGPL to begin with, so just dont use it if you dont agree. I personally am very concerned with the newer trends of going away from GPL, I think its gonna turn out bad for everyone

chii 3y ago
Stallman's foresight has been eerily accurate - look at what google's web environment integrity proposal to say the least. It's time the OSS community stop making free software with a loose license such that control and ownership is taken from them, and for profit to be made without any give backs.
sneak 3y ago
You don't need to "pay back" for a gift. The problem is entitlement and thinking that anyone owes you anything after you have given software away to the world. It's no longer yours, there is no "back".
- redeeman 3y ago
  but its not a gift when its GPL, its distribution under certain terms, and to complain someone chooses GPL rather than BSD is not legit

bombcar 3y ago

The variously GPLs have always received hate of different kinds, and time and time again it's proven why they have the clauses they do. Reminds me of the picture of the smug cat surrounded by knives. GPL is that cat.

ethbr0 3y ago
People say lawyers are assholes, but they don't think about why lawyers are assholes. It's a lawyer's job to imagine the worst future outcomes and guard against them in the present. Everybody focuses on "It's crazy you put that clause in there that was never needed," but few folks appreciate "Thank god we included that clause just in case." Which isn't to opine there's a right or wrong, only multiple parties each negotiating (skillfully or poorly) in their own interests. If you're a developer and don't want your code to slide into corporate controlled ownership... well, there are licenses for that. https://github.com/readme/guides/open-source-licensing https://github.com/readme/guides/open-source-licensing https://arstechnica.com/gadgets/2020/02/how-to-choose-an-open-source-license/ https://arstechnica.com/gadgets/2020/02/how-to-choose-an-ope...
- deleted 3y ago
  [deleted]
- JohnFen 3y ago
  Yes. As a rough analogy that my lawyer told me early on, lawyers are like software engineers, and the law is like the operating system. A good lawyer writes robust "code" designed to deal with edge cases and unexpected conditions gracefully.
- kjs3 3y ago
  I think every single one of my attorneys over the years has made it clear that if something is in the contract/license/etc, you absolutely have to assume it will be enforced, to the letter. No matter how stupid, no matter how unlikely. If it's written down, it was written down for a reason. One of the worst mistakes you can make in life is believing anyone who says things like "oh, that's just boilerplate...we'd never act on it" or "don't worry, we would never enforce that" or similar. That's someone who is deliberately setting you up to get screwed.

appplication 3y ago

GPL gets hate because it’s a self-killing license. Sure, it’s great idealism, but it just creates an incentive for any corporate interests to create either a closed source offering or a better funded competing OSS offering that can be commercialized. If some software provides value, it will eventually be monetized in some form. It makes no sense for a corporation, whose entire existence is predicated on monetization, to see GPL software and say “I guess I’ll just stop charging for our products!” Instead, the completely predictable response is “this is valuable, but I can’t use it, so I’m going to make something like it that I can actually use”. Like it or not, you cannot “hide” value from capitalism. The machine will find and extract value wherever it can. GPL establishes unrealistic ideals for software that are inconsistent with the reality of how and where it is used.

chii 3y ago
> it just creates an incentive for any corporate interests to create either a closed source offering or a better funded competing OSS offering that can be commercialized. what's wrong with that? If they produce their own version, then the world now has another piece of software, and this competition is going to make the ecosystem better imho. The only problem with lenient licenses is that they allow leeching. MIT, eclipse, and apache licenses, all are basically allow free commons which others leech off as much as possible. The corps may continue to contribute, but only because they see value they could extract more than what it costs them. I would say AGPL should be the _only_ license anyone contributing to OSS should pick. And if you own the project, make it dual licensed - a commercial offering, and AGPL. If said software is good, a commercial offering can be profit generating enough fund further development.
- appplication 3y ago
  There’s nothing wrong with that, and there’s nothing wrong with people who want to build GPL software - do what you like, consistent with your ideals. This is really only in response to the perennial “why don’t more people use GPL” questions that seem to always pop up any time software licensing is discussed. It’s fine for some people, but there’s a reason corps tend to avoid it or have internal policies against using GPL software.

spaceribs 3y ago

Hacker news is a mix of venture capital and technologists, the AGPL3 is a wedge between those two groups needs and objectives.

dilyevsky 3y ago
For agpl specifically I believe it’s due to muddy waters surrounding the “derivative work” clause. Some companies have traditionally bent the definition (eg insinuating that api calls result in larger application fall under combined work) and it’s never been tested in court so understandably the lawyers do the lawyer thing and tell you not to use it
- spaceribs 3y ago
  Yeah, but even stepping back there, lawyers are paid to prevent companies from entering those muddy waters as a risk to their profits. Profit isn't a concern to someone who wishes to publish open source software, in fact you could say Open Source is an inherently socialist venture (your socializing the tools/means to do something). The AGPL3 makes it more difficult for others with probably more means to profit on that work, so it's a net benefit to the folks who actually write code (and a detriment to those who would wish to exploit it).
  - dilyevsky 3y ago
    Right so as long as food and shelter is not a concern AGPL is v good license!
    - spaceribs 3y ago
      Yep! I'd say 95% of open source is subsidized by those thriving rather than surviving, having the education/equipment/access/free-time to deliver open source software is a product of privilege and abundance.
- _cenw 3y ago
  Not only some companies - API calls being linking also seems to be the opinion of the FSF.

adrr 3y ago

Because most startups can’t use AGPL. I had to provide audits of our licenses of libraries we use in our code base to investors and attest we didn’t have AGPL code in our code/software in our stack. This was at an e-commerce company and not a company that directly monetized software. Companies are free to choose whatever license but it will limit who can use their software.

_xivi 3y ago
> I had to provide audits of our licenses of libraries we use in our code base to investors and attest we didn’t have AGPL code in our code/software in our stack. A little off topic, but how are these audits usually done? I'd like to familiarize myself Not necessarily your specific case, if there's a resource online that'd be fine
- adrr 3y ago
  We run a script that scans our source code and generates a manifest of all included libraries including license/copyright. Here's one of them: https://github.com/nexB/scancode-toolkit https://github.com/nexB/scancode-toolkit
  - pabs3 3y ago
    There are others, but scancode is probably the best one, their license database is truly huge. https://wiki.debian.org/CopyrightReviewTools https://wiki.debian.org/CopyrightReviewTools https://scancode-licensedb.aboutcode.org/ https://scancode-licensedb.aboutcode.org/
- __jonas 3y ago
  Fossa built a business around this: https://fossa.com/ https://fossa.com/
- nijave 3y ago
  The less automated version is a list of requirements to the effect "list all the OSS libraries you use and their licenses" are pushed down to each team and someone spends a day or 2 going through their code base. Usually that amounts to looking at a lock/dependency file and finding the software's license online. You can also run an audit against your artifact store/cache if you have one. JFrog Artifactory has built-in tools for auditing dependencies (and can act as a pull through cache) so you can run reports that way but it can be harder to tie dependencies to what's using them. Back when I worked at Chase, it was against company policy so use 3rd party dependencies that weren't in their internal components database. Part of getting something in the components database was establishing an owner, the license, and the version (basically a paperwork/approval process). In addition, part of the deploy process was running a vulnerability check against your dependencies using some proprietary enterprise software that tracked CVEs and could (somewhat...) parse what dependencies an application was using (ideally, automatically...).

thayne 3y ago

They were licensed under MPL, which would have also prevented a relicense like this without the CLA. And I don't think the MPL would even prevent them from selling their commercial products.

kj4ips 3y ago

With the CLA in place, it doesn't matter. All contributors already gave hashicorp a broad license for everything that they don't already own, so hashicorp has license to largely do whatever regardless of what license they use to offer it to others.

josephcsible 3y ago
Only the code in HashiCorp's own code is covered by the CLAs, not the code in the third-party dependencies it has. If said dependencies used copyleft licenses like (A)GPL instead of pushover licenses like MIT, that would have prevented what HashiCorp did.
_msw_ 3y ago
The CLA was put in place in December of 2018 [1]. Presumably contributions made before that were under inbound=outbound terms [2], meaning the contributing author licensed their exclusive rights under MPL 2.0, which is a file-based copyleft license. (see the chart at [3]). [1] https://www.hashicorp.com/blog/introducing-a-cla https://www.hashicorp.com/blog/introducing-a-cla [2] https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#6-contributions-under-repository-license https://docs.github.com/en/site-policy/github-terms/github-t... [3] https://en.wikipedia.org/wiki/License_compatibility#Compatibility_of_FOSS_licenses https://en.wikipedia.org/wiki/License_compatibility#Compatib...

Xylakant 3y ago

The projects license is of no concern at all here. Licenses do not bind the owner of the code. Hashicorp required a CLA before contributing, so they own the copyright. They can change the license at any time as they see fit.