The GCC project now allows contributions to use the "sign-off" procedure originally introduced by the Linux Kernel project, and subsequently adopted by many other free software projects. This procedure is required for contributions not covered by either FSF copyright assignment or the MAINTAINERS DCO list.
The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to pass it on as a free software patch. The rules are pretty simple: if you can certify the below:
By making a contribution to this project, I certify that:
Signed-off-by: Random J Developer <email@example.com>using your real name (sorry, no pseudonyms or anonymous contributions.) This will be done for you automatically if you use `git commit -s`.
Some people also put extra optional tags at the end. The GCC project does not require tags from anyone other than the original author of the patch, but other people involved in passing along the patch can add their own Signed-off-by if they wish.
Developers with write access should certify the DCO for all their patches by adding themselves to the DCO list in the MAINTAINERS file.