Information about implications of licenses from used libraries about reuse-website HOT 2 OPEN

You're right in your assessments and understood it correctly. However, the devil is in the details, and there are hundreds of them.

I wholeheartly understand your need for simple explanations and I'd love to give them, but I'm afraid this is where the "out of scope zone" begins for REUSE. Perhaps a first step would be to look for easy yet somewhat exhaustive guides for this which we could reuse or link to. I'm not aware of any from the top of my head, but there certainly is the demand.

from reuse-website.

I understand that, for sure, each community , language, framework, whatsoever has it's own common licenses, special topics, common ceavats etc.
So I fully understand that a exhaustive coverage is impossible to achieve and out of scope.

But one example to show that this aspect exist and how to approach it, would be really nice. A growing list to other examples (which I didn't found one of) would be nice too.

At least I guess it would be helpful to add a FAQ item behind the one dealing with copying files, that even usage of libraries can create need to add those licenses.

I guess most people even don't know about that and simply place any kind of license to their repo and forget about it.

Personally I don't have any meaningfull public repo yet, and don't think the future ones will be of broad interest. But I like to get things done propperly and especially don't want to create any risk to become sueable. I don't believe that I have high risk of getting that attention, but on topics like that, I have always the crazy german Impressum laws in mind.

from reuse-website.