Developers can choose to assign copyright to the FSF. Use this template email to help developers work through the process of copyright assignment to the FSF.
Dear [Developer], The glibc project accepts patches with or without copyright assignment to the FSF. You may contribute patches via DCO without copyright assignment, or you may assign copyright to the FSF. However, some files require copyright assignment because they are shared with projects that require copyright assignment e.g. gnulib. If you choose to assign copyright to the FSF then we can help you with that process. I don't currently see any copyright status for your name and email with the FSF for glibc (something I check for as a steward for the project in the FSF's copyright.list file). Please see: https://sourceware.org/glibc/wiki/CopyrightFSF It would be easiest if you followed the future's assignment process: http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future Once completed we could accept any patches from you going forward, and that would make review easier. Thank you very much for your interest and contributions in glibc. If you have any questions about the process or need any help, please don't hesitate to reach out to any of the stewards listed here: https://sourceware.org/glibc/wiki/MAINTAINERS#Project_stewards_.28GNU_package_maintainers.29 Cheers, [Your name]