Seeking input from developers: glibc copyright assignment policy.

[Khem Raj]

On Mon, Jun 14, 2021 at 12:08 PM Rich Felker <dalias@libc.org> wrote:
>
> On Mon, Jun 14, 2021 at 02:52:03PM -0400, Carlos O'Donell via Libc-alpha wrote:
> > Community,
> >
> > glibc was created as part of the GNU Project but has grown to operate as
> > an autonomous project. As part of the GNU Toolchain the glibc stewards
> > support the gcc project policy changes presented here:
> > https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html
> >
> > The glibc stewards are seeking input from developers to decide if the project
> > should relax the requirement to assign copyright for all changes to the
> > Free Software Foundation as follows:
> >
> > 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.
> >
> > The changes to accept patches with or without FSF copyright assignment
> > would be effective on August 2nd, and would apply to all open branches.
> >
> > The glibc stewards, like the GCC SC, continue to affirm the principles of
> > Free Software, and that will never change.
> >
> > 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.
> >
> > Input on this issue is accepted until July 1st 2021.
>
> I am very much in favor of removing the assignment requirement.

+1.  adding an option to accept patches with DCO would greatly
simplify this for new/occasional
contributors

> not, and have never, had an assignment in place (it's a running joke
> that my patch contributions have been all-minus-signs) but given
> recent behavior by the FSF board, I am completely unwilling to assign
> copyright to them in the future, so not making this change may affect
> my ability to contribute.

+1

>
> Rich