On Mon, Jun 14, 2021 at 01:39:26PM -0700, Paul Eggert wrote: > A proposal to change the glibc copyright assignment policy is being > circulated on libc-alpha. The email thread starts at > <https://sourceware.org/pipermail/libc-alpha/2021-June/127581.html>, and the > text of the email seeking input is at the end of this message. > > I'm sending this to bug-gnulib because we copy some files directly from > glibc and eventually I expect these files to be affected. The simplest > approach I see for Gnulib is to adopt glibc's policy, at least for files or > code copied from glibc.
I would like to make sure the FSF legal department doesn't see any holes in the plan, but I'm certainly okay as going on record as being in favor of the plan. I recall how long it took for me to get permission to sign assignment papers from my previous employer, for work I was doing in my spare time, and being able to use the DCO instead would have made my efforts easier at that time. (My current employer already has a blanket copyright assignment on file for all employees, but not everyone has a company that willing to promote open source involvement.) -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
