unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Update to glibc copyright assignment policy
Date: Wed, 28 Jul 2021 15:50:43 -0400	[thread overview]
Message-ID: <24208780-9ae8-3af2-3da9-8f57ef12e68a@redhat.com> (raw)

glibc was created as part of the GNU Project but has grown to operate
as an autonomous project.

The glibc stewards have decided to relax the requirement to assign
copyright for all changes to the Free Software Foundation. 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 change is consistent with the
practices of many other major Free Software projects, such as the
Linux kernel, and GCC [1].

Contributors who have an FSF Copyright Assignment don't need to change
anything.  Contributors who wish to utilize the Developer Certificate
of Origin[2] should add a Signed-off-by message to their commit
messages.

The changes to accept patches with or without FSF copyright assignment
will be effective after August 2nd, and will apply to all open
branches. Code shared with other GNU packages via Gnulib will continue
to require assignment to the FSF.

The glibc stewards continue to affirm the principles of Free Software,
and that will never change.

Signed,
Ryan Arnold
Paul Eggert
Jakub Jelinek
Maxim Kuvyrkov
Joseph Myers
Carlos O'Donell

[1] https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html
[2] https://developercertificate.org/


             reply	other threads:[~2021-07-28 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 19:50 Carlos O'Donell via Libc-alpha [this message]
2021-07-29 10:25 ` Update to glibc copyright assignment policy Siddhesh Poyarekar
2021-07-29 13:58   ` Carlos O'Donell via Libc-alpha
2021-07-29 14:07     ` Siddhesh Poyarekar
2021-07-29 14:21     ` Florian Weimer via Libc-alpha
2021-07-29 19:02       ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=24208780-9ae8-3af2-3da9-8f57ef12e68a@redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).