We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
While performing some review of swagger-ui, I ran into the following code snippet at https://github.com/swagger-api/swagger-ui/blame/master/src/core/plugins/deep-linking/layout.js#L138: Function getScrollParent apparently is derivative work from code published on stackoverflow in 2017, as attributed in the accompanying comment (pointing to https://stackoverflow.com/a/42543908/3933724). However, this code from stackoverflow was presumably published under a CC-BY-SA 3.0 license by default (see https://stackoverflow.com/help/licensing). Here it is re-licensed under the Apache-2.0 license, which AFAIK is not compatible with CC-BY-SA 3.0. Isn't there a license issue here with the inclusion of this code snippet?
Best regards, Alain Le Guennec
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
While performing some review of swagger-ui, I ran into the following code snippet at
https://github.com/swagger-api/swagger-ui/blame/master/src/core/plugins/deep-linking/layout.js#L138:
Function getScrollParent apparently is derivative work from code published on stackoverflow in 2017, as attributed in the accompanying comment (pointing to https://stackoverflow.com/a/42543908/3933724).
However, this code from stackoverflow was presumably published under a CC-BY-SA 3.0 license by default
(see https://stackoverflow.com/help/licensing).
Here it is re-licensed under the Apache-2.0 license, which AFAIK is not compatible with CC-BY-SA 3.0.
Isn't there a license issue here with the inclusion of this code snippet?
Best regards,
Alain Le Guennec
The text was updated successfully, but these errors were encountered: