-
Notifications
You must be signed in to change notification settings - Fork 180
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
Incomplete license information #396
Comments
Interesting use case. The patched files are not part of this repository, they are generated during the build and publishing state. So what is the resulting license of a BSD-3 licensed file patched by an MIT licensed file? What would you suggest as solution? |
One could argue that the patches should be subject to the BSD-3-Clause license as well as they refer to BSD-3-Clause code and partially reproduce them. Other approaches might be possible, but I am not a lawyer and therefore I am limiting this to the basic approach. I would recommend to either add a corresponding section to the
|
The wheels apparently ship with patched templates from Django itself:
I could not find any license details for these files (especially relevant on distribution, id est inside the PyPI wheels), although they are subject to the BSD-3-Clause license and have different copyrights compared to your own package code.
The text was updated successfully, but these errors were encountered: