I don’t think its enough to link. You just need to copy or create a single txt file named “LICENSE” and put it in the root of your repository. I am not a lawyer. The license text will tell anyone who cares to know what they can do and cannot with the project. If you do not do that, you only make it harder for anyone looking for the license (as explained with the websearch example previously).
There’s no law specifying where the license should be. A link to a page with the license is more than enough. Though if the link ever becomes invalid or shows something else, the license is lost. That’s why copying it with the source code is the best bet.
I don’t think its enough to link. You just need to copy or create a single txt file named “LICENSE” and put it in the root of your repository. I am not a lawyer. The license text will tell anyone who cares to know what they can do and cannot with the project. If you do not do that, you only make it harder for anyone looking for the license (as explained with the websearch example previously).
There’s no law specifying where the license should be. A link to a page with the license is more than enough. Though if the link ever becomes invalid or shows something else, the license is lost. That’s why copying it with the source code is the best bet.