-
Notifications
You must be signed in to change notification settings - Fork 69
Make repository REUSE compliant and relicense to MIT #254
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
Conversation
I honestly don't know :) yes, I would be fine with relicensing |
You wouldn't happen to know where the |
Great, I'll start the process then! Change license to MITHi all, The
I have tagged the contributors of the present and past. Package authors Major contributors (>= 100 line additions) |
|
I agree with the change |
|
Sure, full support! |
|
I think I compiled the binaries myself |
|
Happy as well with relicensing, thanks! |
|
Happy with relicensing! |
|
Yes, I agree with the change |
|
Happy with the change! |
|
Thanks all for the feedback. Given the majority and especially original authors agree, we will proceed with the re-licensing. |
|
PR updated, now RTR. |
|
Merge at will! |
Closes #108 .
Changes proposed in this Pull Request
This PR has two purposes:
powerplantmatchingfrom GPLv3 to MIT, the output file to CC BY 4.0 and some other licenses for config files / duke binaries.The relicensing to MIT is optional, the rest recommend / necessary (espc. the duke binaries have probably always been Apache-2.0? @FabianHofmann @coroa ).
Fun fact: The PR template is already mentioning MIT license, I didn't change it. So most contributors have already agreed ;)
Do we want to relicense? MIT is the standard license for most of our other repositories nowadays.
If yes, I would ask the main contributors to confirm here.
Checklist
doc.doc/release_notes.rstof the upcoming release is included.