Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

github.com

Post reply on HN
Print view View original

91–100 of 127 posts

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#91

Post by the-lazy-guy »

dtech wrote: post #68
the-lazy-guy wrote: post #28

Earlier quoted context omitted.

How exactly do you fundamentally disagree with the author of the PR? He literally did no statements beyond saying that this is not an Apache License anymore.

The author of the module disagrees with the author of the PR that adding this additional restriction does not make the project Apache License anymore.

Thanks for the explanation. English is not my native language and I read the comment as if the commenter had fundamental disagreements with the author of the PR but had to agree with him on this particular point about license terms.

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#92

Post by res0nat0r »

jen20 wrote: post #65
nrmitchi wrote: post #41

Okay, so while this title is technically true , it is phrased in a way to incite panic. Just to be clear, AWS/Hashicorp is NOT beginning to charge people for the use of Terraform modules.

This is neither an AWS project nor a HashiCorp project. Why would that even be in question?

I'm sure just due to the repository naming many people think it is official. I did before I started using them and looking deeper.

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#93

Post by jhugo »

antonbabenko wrote: post #89
jhugo wrote: post #61

Earlier quoted context omitted.

terraform-aws-modules is a community thing, that consists of modules that are thin wrappers around the official AWS provider, that serve very little purpose other than to add a dependency and create problems like this.

lol

Thanks for the downvote and the no-content comment, I guess? I've worked with numerous large Terraform configurations, and the ones that use terraform-aws-modules are harder to maintan, have more churn due to updates of the modules, and are more divorced from the actual underlying cloud resources due to random decisions made by the module authors.

I really struggle to understand the reason for using the modules rather than the underlying resources, except that there are a lot of tutorials and blog posts written based on using the modules.

Maybe you can enlighten me rather than writing a three-letter comment?

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#94

Post by jhugo »

antonbabenko wrote: post #79
jhugo wrote: post #63

Earlier quoted context omitted.

By definition, it's not under the Apache 2 license if you add extra terms, even if those terms only apply to some people.

That's why I call it "Additional information for ..." and links to wikipedia (not yet blocked in those countries, I guess). It is the same Apache2 license.

I applaud you for fixing that. As you know, when I wrote my comment, it still said "Additional terms for …"

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#95

Post by jhugo »

res0nat0r wrote: post #92
jen20 wrote: post #65

Earlier quoted context omitted.

This is neither an AWS project nor a HashiCorp project. Why would that even be in question?

I'm sure just due to the repository naming many people think it is official. I did before I started using them and looking deeper.

It's an unfortunate fact that many people think terraform-aws-modules is the way to manage AWS resources with Terraform.

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#96

Post by reacharavindh »

jen20 wrote: post #62
reacharavindh wrote: post #10

As much as I hate what Russia is doing, I’d hate even more for software to come under political purviews. If an author of a library chooses to apply political condition(however justified they may be), then the software is simply not free by definition. I’m neither Russian nor Ukrainian. I cannot turn a blind eye simply because it doesn’t apply to me. What if another library that I use apply a license that says “those…

> I’d hate even more for software to come under political purviews. You would hate a statement being added to README file EVEN MORE than civilians being shelled indiscriminately, entire families shot while waiting in bread lines, and the targeting of war correspondents by a foreign army? Got it.

That’s a twisted interpretation of what I wrote. One can be disgusted to a high extent, and then from that baseline even more disgusted by some _added_ on top of it. Just because a despicable thing is happening, one must not justify viewing the whole world through that lens _alone_ and refuse to reason things in other contexts.

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#97

Post by AitchEmArsey »

The only appropriate response here is for a corporate owner (Hashicorp preferably) to fork the repo just before the license change and to assert that their version is the default, and drive future development there.

The original author is entitled to their opinion and can restrict their own development to a repo with license conditions they define, but it is not reasonable to expect companies to accept non-standard and politically charged license terms. Getting shit done is hard enough and this change will not move the needle on Ukraine/Russia sentiment one iota.

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#98

Post by antonbabenko »

AitchEmArsey wrote: post #97

The only appropriate response here is for a corporate owner (Hashicorp preferably) to fork the repo just before the license change and to assert that their version is the default, and drive future development there. The original author is entitled to their opinion and can restrict their own development to a repo with license conditions they define, but it is not reasonable to expect companies to accept non-standard a…

You are asking a corporation to clone "a community-driven project" and maintain it. Ok. There are 2.7K of forks of just this module already if you want to use them.

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#99

Post by rgoulter »

joshmanders wrote: post #22
black_puppydog wrote: post #13

Earlier quoted context omitted.

> I’d hate even more for software to come under political purviews. Really? Making software free is just about as political as it gets. Restricting that freedom, as happens here, is equally political. I guess you just don't this special kind of politics in your software.

Right? Like the whole open source movement was a massive political thing... Open source by definition is political.

I think "open source is political" uses the word 'political' in a significantly different way than stuff like "I'd hate to see more politics in software discussions".

Consider: "Open source is political": the power 'open source' relates to is the power of the licensed software's users to read the program's source code, and to redistribute/modify the program. Insofar as there's a moral vision to it, the idea of a world where users are unable to distribute/modify/etc. their software is worse than a world with open source software.

Whereas, the meta-statement "don't bring politics into discussions" is more like rules-of-engagement for discussion involving a diverse group of people. The 'political' in the statement refers to e.g. moral or ideological points of view. -- "asl2.0, but you have to agree abortion is murder" is 'political' in a different way than "asl2.0, you can't use this software if your name is Jared", because the restrictions itself is about a moral disagreement.

Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license

#100

Post by antonbabenko »

jhugo wrote: post #93
antonbabenko wrote: post #89

Earlier quoted context omitted.

lol

Thanks for the downvote and the no-content comment, I guess? I've worked with numerous large Terraform configurations, and the ones that use terraform-aws-modules are harder to maintan, have more churn due to updates of the modules, and are more divorced from the actual underlying cloud resources due to random decisions made by the module authors. I really struggle to understand the reason for using the modules rathe…

no
Post reply on HN