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.
Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
41–50 of 127 posts
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#42It sucks to have to agree with someone that you don't fundamentally agree with but I think the author of the PR is correct. This is a modification of the Apache license and while I appreciate and support their stance, it does seem to mean that the license is non compliant. I support anyone's desire to protest things (no matter which side I'm on) but you can't just make up your own rules.
> but you can't just make up your own rules Sure you can. Your project, your rules.
Sure, but you can't make up your own definition of the Apache 2.0 license, which was the point of the original comment (and the PR in question).
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#43It is fine for people to reuse/derive from the Apache license but it is _not_ fine to continue to use the name "Apache" in the license name as "Apache" is trademarked.
I believe this is a changed license as it does not matter whether the change is in another file or not.
Edit: https://www.apache.org/foundation/license-faq.html#mod-licen...
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#44I'm not sure what the title here should be, but this one seems incomplete Edit: maybe this? > Terraform-AWS-modules/Terraform-AWS-eks restricts license for Russian/Belarussian users
The title is technically true, but it makes a strong effort to paint it as a bad thing.
Nothing is being painted, the title is factually correct
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#45It sucks to have to agree with someone that you don't fundamentally agree with but I think the author of the PR is correct. This is a modification of the Apache license and while I appreciate and support their stance, it does seem to mean that the license is non compliant. I support anyone's desire to protest things (no matter which side I'm on) but you can't just make up your own rules.
> but you can't just make up your own rules Sure you can. Your project, your rules.
Sure, but that doesn't mean he can redefine terms. He can't both change the license and claim it's compliant with that license. That contradiction exists regardless of his ownership of the project.
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#46I’m ethically torn here. On one hand, I ask myself what I would have done if I worked at IBM in the 1930s[0] On the other hand, as an LGBT person, I firmly believe that maximal freedom of speech protects vulnerable people from erasure. What this means for free software is a tough question. [0] https://en.wikipedia.org/wiki/IBM_and_World_War_II
I don't think there is a tradeoff. Not all actions constitute speech. Supporters of Russian actions should be able to spout off their horrible thoughts, but that doesn't mean companies the need to sell their goods or services to Russia. The two categories of acts aren't the same.
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#47Ugh. Lookit: it sucks to be forced to say anything at all , whether you agree with it or not. One thing I can say for certain is that my employer (and probably yours ) is only into virtue signalling when it's 100% safe, everyone else is doing it and it has zero negative repercussions. I don't get to decide what my employer's stance is on licenses. I guarantee you that many people will end up moving away from these mo…
FYI this is not an employer doing the "virtue signaling", it's the individual contributor to the project.
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#48Hi. I am Anton Babenko, maintainer (ukrainian by heart) here. I have updated the wording in README to state the facts about Russia (facts with links to wikipedia) - https://github.com/terraform-aws-modules/terraform-aws-eks#a...
It was never my intention to make changes in a license in any way. It would be just wrong to drop 5+ years of my life working on all terraform-aws-modules and betray everyone who have been participating as contributors and users.
If there are questions, please ask here or twitter (@antonbabenko).
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#49Earlier quoted context omitted.
Nothing is non-political. You do not exist in a vacuum.
Funny how the people who say this always seem to have the same political ideology, which they want to loudly push.
You don't know what my "ideology" is, and that is precisely because I didn't push any. A Ukranian developer don't want Russians to use his code, on account of the latter country invading the former.
Re: Terraform-AWS-modules/Terraform-AWS-eks transitions to non-free license
#50Earlier quoted context omitted.
> but you can't just make up your own rules Sure you can. Your project, your rules.
Sure, but that doesn't mean he can redefine terms. He can't both change the license and claim it's compliant with that license. That contradiction exists regardless of his ownership of the project.
I have updated the wording. It was and will be the same Apache 2 license.