Lots of projects on GitHub have a GPL3 License, as it's easily created by their software when you want to add a license and you choose GPL3. However, unlike the MIT license, you don't put your own name in the license. Furthermore, the GPL3 license text says you can't modify it:
Copyright (C) 2007 Free Software Foundation, Inc. https://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
I understand the reasons this file can't be modified.
However, where should one put in a GitHub repo the information that you can find in an MIT license, e.g., the copyright that belongs to the person who created the work?
The FSF has the following FAQ and answer:
I want to get credit for my work. I want people to know what I wrote. Can I still get credit if I use the GPL? (#IWantCredit)
You can certainly get credit for the work. Part of releasing a program under the GPL is writing a copyright notice in your own name (assuming you are the copyright holder). The GPL requires all copies to carry an appropriate copyright notice.
GitHub's "add a license" feature doesn't cover this dimension of GPL. How is this done properly. Is it a "Copyright" file that's separate? Are there examples of GitHub repos where this has been done?
My reason for asking is I want to reuse a GPL3 repo and give credit to the original author. However, their own repo doesn't have their copyright info (and I think it's pretty common with GPL3 on GitHub).
My question is related, but significantly different from GPL and original author's copyright text in completely rewritten code, because the answer there doesn't explain where the copyright info is stored (in each source file, in a LICENSE.md, etc.)