-
Notifications
You must be signed in to change notification settings - Fork 290
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
libpng changes over the years #2591
Comments
Looking at the delta view, the most material change is a comment stating "Updated LICENSE to say files in the contrib directory are not necessarily under the libpng license, and that some makefiles have other copyright owners." But that is always true ... one can never assume that a top level license applies to other files in the tree. So, I'm inclined to say there aren't substantive differences in this latest version and it could be handled with markup. |
tried to discuss on 12/12 legal call, but my notes above were not sufficient, so will review again and revise |
@jlovejoy Unless there are particular edits you've got ready now, I'll move this to 3.27.0 and we can aim to tackle it quickly after the 3.26.0 release is out. |
adding more thorough time line, starting with:
|
fixes #2591 But will also probably need more edits
It was too hard to try to explain in text, so I've made a PR, which is failing and I can't figure out why. I also have a Google doc with comments and color-coding of the various changes over the years. Overall, there isn't much that has changed substantively, but... mixing acknowledgments in between license text is not optimal for trying to match (and find) the actual license text! |
oh, and there is probably more markup needed, but until I can figure out why it's failing, not worth adding more |
see https://gitlab.com/fedora/legal/fedora-license-data/-/issues/296
http://www.libpng.org/pub/png/src/libpng-LICENSE.txt is the URL for both
libpng-2.0
andLibpng
the first part/license:
libpng-2.0
(and this is the URL is referenced in the SPDX entry) which was added for version 3.5 in 2019the second part/license:
BUT over the years, various things were updated such as the list of names and references to version numbers (which would be replaceable by SPDX matching guidelines, but need markup added)
More substantial text changes occurred as well:
libpng-2.0
was added in Nov 2018, which also altered some of the text order, see pnggroup/libpng@e79085aquestion is for SPDX now: should these various changes over the years be handled with markup or constitute a new license?
The text was updated successfully, but these errors were encountered: