What I miss is a library for Creative Commons work where everything can be registered and content-id-hashed so it is easy to find, even without attribution on the work itself. A set of command line tools to verify that all your data files have proper licensing would be extremely helpful as well. It would also make a nice resource to just browse Creative Commons works instead of having them scattered all over the Web. And it could allow back-linking, so you could see all the places where a given work is used.
> You may satisfy the conditions in (1) and (2) above in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.
> There is no one right way; just make sure your attribution is reasonable and suited to the medium you're working with. That being said, you still have to include attribution requirements somehow, even if it's just a link to an About page that has that info.
This suggests "[Texture Name](http://foobar.com/texture.png) by Foo Bar / CC0" in a CREDITS.md should be enough? Just make sure the CREDITS.md (or a rendered html version?) is in the install dir for the game
If I don't state where it is used, that might work for me, but not for the next guy that comes along and wants to reuse a texture from my game in their own.
This is not just a theoretical concern, some Linux distributions like Debian can be pretty picky when it comes to copyright, so having a clear record of the copyright of every single file would be really helpful. A plain text file is ok if it is properly maintained, but it's also easy to simply lose some files in the process, as it is all done manually. Tools to automate that process that can be integrated into the CI would be very welcome.
My dream would be that tools like Gimp and Krita would be able to automatically keep track of the copyright of the images you copy&paste into them, as that would not just track the copyright of the original images, but also all the remixes that you produce out of them.
I think it's generous that you want to do this, and nothing prevents you from creating a document that breaks down where and how attributed resources are used, but attribution — per Wikipedia, "acknowledgment as credit to the copyright holder or author of a work" — doesn't require that.
And to another point a couple of people have made, one of the big bugbears with crediting media generally is that the attributions are disconnected from the media in general (absent watermarks) so even if you're careful in your presentation, the person reusing some of your material may not be.
So how long does this get as we keep making derivatives? For an open source project, where there is a seperate license file, it is okay to have it go on forever, but I can understand why you don't want 100s of lines of license information inside your news story.
There's probably a distinction that I'm not aware of but this is not true for CC0 (as stated also in the FAQ for CC0 on this same website).
Yagoddabekidding.
How about, First name, initials, last name, city, country, year of birth.
[1] gave a good discussion about whether it is possible to revoke CC license. It doesn't seem likely, but if it does, then it will lead to the license paradox for creators and users alike.
[1] https://scholarlykitchen.sspnet.org/2022/05/11/q-can-you-rev...
They recommend a software-specific license instead, as those licenses handle code distribution requirements much more clearly.
https://support.apple.com/guide/icloud/acknowledgements-mmbb...
If you use external libraries, leave them in their own directory with their own license files, or at the very least leave them in their own files. So it's clear that they aren't part of the project and covered under their own terms.
If you start copy&pasting code snippets, it gets complicated, as now you might be mixing licenses, which might not even be compatible with each other.
