Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The TF/HC CLA empowered the licence change, will OpenTofu be avoiding a CLA? #1079

Open
06kellyjac opened this issue Sep 20, 2023 · 0 comments

Comments

@06kellyjac
Copy link

Since when changing the license of software you need to request sign-off from all the Copyright holders, the CLA granting a perpetual copyright license allowed for unilateral change to be made to the project's software license.

As OpenTofu is going to be under the Linux Foundation's umbrella (where most projects seem to use EasyCLA) and there's already been mention of a potential new CLA I'm asking here if that is in fact the intention going forward.

If that is the case I'd be curious to understand why this decision was taken when the lesson here seems to me that "the community" at large can not trust promises of good will when faced with the reality of possible unilateral re-licensing.

I'm no lawyer but the LF CLA doesn't seem materially different to the Hashicorp one

https://github.com/cncf/cla/blob/master/individual-cla.pdf

https://www.hashicorp.com/cla


The case for CLAs

...
1. Easy relicensing:
...
There are benefits in relicensing being hard because it results in stable legal expectations around a project and encourages projects to consult their contributor communities before undertaking significant legal policy changes.

https://opensource.com/article/19/2/cla-problems

For successful relicensing the agreement of all involved copyright holders, typically the developers, to a changed license is required. While in the free and open-source domain achieving 100% coverage of all authors is often impossible due to the many contributors involved, often it is assumed that a great majority is sufficient. For instance, Mozilla assumed an author coverage of 95% to be sufficient.

https://en.wikipedia.org/wiki/Software_relicensing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant