attribution/license for diff-dom (LGPL) #1874
Labels
Dependencies
Any software dependancies problems
Comments
|
Hello, as far as I can tell (this pre-dates my work on the project) the code was copied because the team needed a small change when diff-dom had had a major refactoring compared to the version they were using. In terms of licensing our project uses the REUSE specification, with a copy of the LGPL alongside all other licenses used its application to diff-dom is properly listed and also documented in our lib/changelog. Please let us know if something is missing in terms of crediting/licensing and we can work to correct it. |
|
I see. Yes, that is not where I would have looked for a license - I would have expected it to be mentioned in the same file or at least the same folder. I guess this is legal then. Too bad you decided to go with a fork. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, some years ago you reported a number of issues on the LGPL licensed diff-dom library that I maintain and which you were using. I was wondering why I didn't hear more from you. I noticed you simply added it to your source code, removing all traces of the LGPL license and information about where the code comes from as far as I can tell. It means you now have your own fork of the library and any bug fixes you do do not go back to the original project.
I am wondering if that was intentional.
The text was updated successfully, but these errors were encountered: