Seeking input from developers: glibc copyright assignment policy.

[DJ Delorie]

"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org> writes:
> Contributors who have an FSF Copyright Assignment wouldn't need to
> change anything.  Contributors who wish to utilize the Developer Certificate
> of Origin[1] would add a Signed-off-by message to their commit messages.

I'm for this change, but it's my belief that the DCO will be treated
like a EULA - don't read it, just accept it.  I will consider every
"Signed-off-by:" as a "I-don't-know-if-I-own-this:" admission.  "I don't
need to check with legal, I just need to put this line in my email and
everything is OK."

However, the FSF assignment is the biggest roadblock to new
contributors, and I think that's a bigger potential problem than the
potential DCO problems.

> glibc will continue to be developed, distributed, and licensed under
> the GNU Lesser General Public License v2.1 or any later version as
> published by the Free Software Foundation.

This paragraph was worded poorly.  We will not be developing under any
later version, ever.  We will distribute under terms that allow using
later versions' terms.  The DCO means we will never change the version
of GPL we use, it's important to not blur that point.