-
Notifications
You must be signed in to change notification settings - Fork 1
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
explicit agree on license changing #16
Comments
@sergmain Why? For example - if one of the contributors is dead, the code-base can't change it's license anymore forever? |
Closed due to inactivity |
Sorry for necro, but for your case ' if one of the contributors is dead' the confirmation still required from heirs. there are a lot of legal cases which you can google or look at cases here - https://law.stackexchange.com/search?q=license |
@sergmain How this agreement is collected? The PR with the license change should be accepted by them, or there's another juridical procedure for this? |
If I'm not mistaken, at Jul 27, 2022 when I opened this ticket there were only 2 contributors with gpl license - you and @marian-rusu . If so, @marian-rusu can just post here that he agree to switch license. Otherwise you need to collect a list who was contributor to gpl-licensed code and ask everyone for confirmation. |
The word "here" is still ambiguous from the juridical point of view. Can you be more precise? |
Here - meaning this discussion thread? - yes |
for changing from GPL to MIT type of licenses, the explicit agree from all contributors, including @asuiu @marian-rusu , must be collected
The text was updated successfully, but these errors were encountered: