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

Legal License Change Issues #37

Closed
leviem1 opened this issue Aug 26, 2020 · 3 comments
Closed

Legal License Change Issues #37

leviem1 opened this issue Aug 26, 2020 · 3 comments
Assignees
Labels

Comments

@leviem1
Copy link

leviem1 commented Aug 26, 2020

I noticed you changed how your software was licensed between a couple of versions. Version 1.0.0 was released under LGPL-3.0, version 2.0.0 was released under no license (automatic copyright), and version 2.0.5 was released under GPL-3.0.

I'm assuming that this wasn't intentional as this has some nasty legal implications that render this project basically unusable until they are resolved. I guess the options would be to...

  1. Revert to the LGPL-3.0 license along with any code not made under that license (2.0.0 - 2.0.4)
  2. Change to GPL-3.0 and provide the written approvals from each contributor, removing code from any contributor that denies permission (approvals would ideally be accessible from the repository as outlined here)
  3. Revert to the LGPL-3.0 license and provide the written approvals from each contributor who made contributions since 1.0.1 to license under LGPL-3.0 as explained above.

The root of the issue is that the developers who contributed to version 1.0.0 - 1.0.1 have not given permission to have the license for their code removed as it was in version 2.0.0 - 2.0.4, and developers who contributed to 2.0.0 - 2.0.4 have not given permission to license their code under GPL-3.0 as in 2.0.5. There's no way to prove that proper permission was granted by contributors since version 2.0.0. This may seem nit-picky, but the issue can result in DMCA takedowns which threaten the usability of the software. People using code from version 2.0.0 - 2.0.5 of this project may also be subject to legal consequences.

There's probably a loophole somewhere in the fact that your README hasn't been updated which you might be able to use as "proof" that the licence change was unintentional. However, I'm not qualified to give legal advice, so I suggest you speak to a lawyer before moving forward.

TL;DR call a lawyer.

@omatron
Copy link
Contributor

omatron commented Aug 27, 2020

Hello @leviem1 thanks for the heads up, we are working on it.

@danilodeveloper
Copy link
Contributor

working on #38
Tks @leviem1!

@omatron
Copy link
Contributor

omatron commented Sep 1, 2020

New License is up https://github.com/insidersec/insider/blob/master/LICENSE commit: fe5d2fe

Thanks @leviem1 !

@omatron omatron closed this as completed Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants