The Berne Convention on copyright specifies the Right to Quote as an exception to copyright.
Article 10 (1) It shall be permissible to make quotations from a work which has already been lawfully made available to the public, provided that their making is compatible with fair practice, and their extent does not exceed that justified by the purpose, including ...
Requiring people to contribute their changes back to the original project is a bit of a problem point for licenses.
For open-source license, such a requirement fails the "desert island test" and prevent the license from being an open-source license. The desert island test means that a group of people on a desert island with no way of contacting the outside ...
We can both write a HelloWorld application in the same language and chances are that both programs will look very similar. This does not mean that, if I were to publish mine first, that your version would be derived from mine. Both are independent works, no matter how similar they look.
Copyright law and -judges also recognize the fact that as there become ...
RST supports comments in various forms, which could be used to specify licenses inline. This would be similar to adding a license block to an individual source code file in a program.
If you are asking about something like a directory/subdirectory or a whole source code repository (e.g. a Github repo) with documentation, I personally would look ...
The question has been around, but this is what I noticed based on the current situation:
You mention often posed questions. If the same questions are posed more than once they will often at least contain some common keywords (or synonyms). A common search engine should be able to find hits in your documentation (or FAQ) based on the question, e.g. search ...
Apparently theres this standard/specification/bot:
Here is more info:
And here is a big example: