How to work with licenses correctly - in which folder to put them, etc.?

Question

Law in IT

How to work with licenses correctly - in which folder to put them, how to figure out which license and what it means, which licenses are better not to use in your project and which ones can and under what conditions, what pitfalls can get in the way?

Answer 1

> How to work with licenses correctly - in which folder to put them
Follow the instructions attached to the license ( for example, here ; here and further links on the example of GNU copyright licenses).
> how to figure out which license and what it means
Read the license itself (for example, GNU GPLv3 ) - free licenses, unlike most legal documents, are written in quite human language. Read the license comments ( for example ). Read licensed FAQ ( eg ). What is not clear - ask in the mailing list / on the web forum. What they cannot unequivocally answer in the mailing list / on the web forum is to write to the license authors ( for example ).
Avoid sources of anonymous / collective authorship: tldrlegal.com, choosealicense.com and other “simplifiers”; Wikipedia with great care.
> which licenses are better not to use in your project
Non-free.
It is also probably wise not to use those licenses that you or someone else may have trouble understanding. That is, those that are written by a non-human clerk. Those that no one comments on and for which they do not constitute a FAQ. Those who are looked at in specialized mailing lists / forums like a sheep at a new gate. Those whose authors do not bother to comment on what they have written.
> and what you can and under what conditions
free. Provided that:
1. In general, you have the right to choose the distribution conditions for at least something, that is, you have exclusive copyright to what you wrote. And this may not be the case at all if, for example, you write your work as part of your work activity or on order.
2. The distribution terms you have chosen for your specific part of the work do not conflict with the distribution terms for parts that you do not own. If there are, of course, but they almost always are. If we are talking about free software, then these are direct borrowings, as well as library dependencies.