-
Notifications
You must be signed in to change notification settings - Fork 15
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 license is non-free #17
Comments
This is kinda on purpose. If someone worries about whether the term "intent to harm" applies to them, it does. I don't really have an issue with going to a free license. If someone makes a relicense PR with checkboxes for all past, present and future contributors, I'll merge it without complaint. |
Do you really mean to include future contributors as a criteria for relicensing? |
lol, no, sorry. But the license change should include wording so that any contributions (past and future) are under e.g. Apache2 + MIT licenses. |
Cool. For past contributors, we can try to see if we can contact them to ask if they are willing to switch to a free license. For future contributors, I recommend using the DCO - it's just a way for contributors to certify that their patch is FOSS and more explicitly, that they grant it to the project under the same license as the project. |
Greetings contributors! I propose relicensing this project under an OSI approved license. Could each of you reply with a set of OSI licenses that you would agree with relicensing your past contributions under? If there are some common licenses that you can all agree to, then we can pick that one. @oli-obk suggested Apache 2.0 or MIT above, for example. CC @oli-obk @nakeep @chrisxue815 @quadfault @Ryman @oli-obk The early commits in the repo were from Oliver Schneider - is that you? That's the only name I saw that I didn't CC above. |
I don't mind. Any OSI license works for me. |
I'll keep a record here for contributors we have heard from:
|
Any is fine with me. |
yes |
Same! |
Hello @nakeep - are you OK with the proposed license changes? |
I have written @nakeep an e-mail to see if they are OK with switching the license here. For reference, they have written two commits: https://github.com/oli-obk/rust-si/commits?author=nakeep |
worst case we'll revert their commits and open an issue with the general idea of compile-time checking the correctness |
I've just contributed to this repository. I am OK with the license change. |
Hi @nakeep, if you read this, please visit the following thread, yours is the last one of the contributors permissions they need to change the license of the project, thank you: oli-obk#17 (comment)
Do we have any updates about this progress? |
we could revert @nakeep's commits, their github accounts seems to be dead. |
I executed such command
How can we find the two patches committe by nakeep in this list? |
|
Thanks @oli-obk
Besides, have we tried to connect him by email? |
I haven't |
I'm trying to revert nakeep's first commit by #35 For the other commit fda477c it seems that his change has been overwritten (partially) by otherchanges
|
Thanks @oli-obk |
yes |
Hi @oli-obk , do you plan to change the LICENSE file soon? |
Done! |
I am sorry for very late reply. Please go ahead and change the license. Sadly, years went without me seeing the message. My old Github handle was @nakeep. |
Greetings!
I see that you are using a custom license that includes the restriction "The Software may not be used in
any system whose intent is harm any person's privacy, body or mind." I am not a laywer, but this seems similar to the JSON license's clause that the software must be used for good and not evil. You can use a web search to find analysis on why that license is considered non-free.
Though the goal does seem good, one of the problems with the text is that it does not define what "harm" is (similar to how "evil" and "good" are not easy to define in the JSON license).
I recommend relicensing under an OSI approved license.
The text was updated successfully, but these errors were encountered: