-
Notifications
You must be signed in to change notification settings - Fork 39
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
License question #43
Comments
Hi Matthew. It is not quite clear to me what those licenses would give. When stripped of their redundancies they boil down to the same as the onnx2c license (+ some small extra restrictions). What is the problem that needs solving? Personally I am actually more inclined towards GPL-2, but since I have no practical way of protecting the copyrights of my work, the license question a bit academic. I don't know what the other copyright holders think... |
Hi @kraiskil! I did a little research since I wasn't fully certain myself and basically from what I understand, I think you get two things:
|
Any organization that considers using a software need to check that it has an acceptable license. Using a standard license means that existing license approvals can be done. In that case, approval for a software becomes a trivial operation - check/document that the software uses a pre-existing approved license - done. Many have written about this in more detail, the reasons to not create custom licenses for open source software. First example that comes to mind: https://ben.balter.com/2016/08/01/why-you-shouldnt-write-your-own-open-source-license/ |
Hello! This is an awesome project! I'm interested in trying it out but the license language isn't standard even though it is very permissive. I was wondering, would you be open to changing the license (or dual licensing) to something OSI-approved like MIT or BSD 2-Clause?
Warm regards,
Matthew
The text was updated successfully, but these errors were encountered: