From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: Seeking input from developers: glibc copyright assignment policy.
Date: Mon, 14 Jun 2021 17:22:54 -0300 [thread overview]
Message-ID: <aeadf6cd-a6c9-d4cf-8bd9-d9d54a2db120@linaro.org> (raw)
In-Reply-To: <e13a4072-a53e-d9e1-d5c7-bf4179fead56@redhat.com>
On 14/06/2021 15:52, 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.
From the gcc maillist thread [1], it seemed that the vast majority if not
all gcc developers were in favor of the change. I also agree this is the
way forward to help improve contributions and the project engagement.
[1] https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html
next prev parent reply other threads:[~2021-06-14 20:22 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 18:52 Carlos O'Donell
2021-06-14 19:08 ` Rich Felker
2021-06-14 19:25 ` Khem Raj
2021-06-14 20:05 ` Florian Weimer
2021-06-14 20:22 ` Matt Turner
2021-06-15 20:28 ` Carlos O'Donell
2021-06-14 21:16 ` Paul Eggert
2021-06-14 20:18 ` Matt Turner
2021-06-14 20:22 ` Adhemerval Zanella [this message]
2021-06-15 2:48 ` Siddhesh Poyarekar
2021-06-15 3:18 ` DJ Delorie
2021-06-15 17:41 ` Paul Eggert
2021-06-15 18:43 ` DJ Delorie
2021-06-15 19:05 ` Paul Eggert
2021-06-15 19:12 ` DJ Delorie
2021-06-15 19:35 ` Paul Eggert
2021-06-15 19:42 ` DJ Delorie
2021-06-15 20:08 ` Carlos O'Donell
2021-07-02 22:33 ` Carlos O'Donell
2021-07-03 1:59 ` Paul Eggert
2021-07-04 0:40 ` Paul Eggert
2021-07-04 11:55 ` Florian Weimer
2021-07-04 18:32 ` Paul Eggert
2021-07-04 23:25 ` Bradley M. Kuhn
2021-07-05 15:26 ` Christoph Hellwig
2021-07-06 18:02 ` Bradley M. Kuhn
2021-07-05 5:28 ` Carlos O'Donell
2021-07-05 20:21 ` Paul Eggert
2021-07-06 18:05 ` Bradley M. Kuhn
2021-07-06 19:42 ` Paul Eggert
[not found] ` <YOTTfm12jac/NYe5@ebb.org>
2021-07-07 8:51 ` Florian Weimer
2021-07-07 15:01 ` Joseph Myers
2021-07-05 5:00 ` Carlos O'Donell
2021-07-05 5:28 ` Florian Weimer
2021-07-05 20:37 ` Joseph Myers
2021-07-03 3:24 ` Bruno Haible
2021-07-05 5:53 ` Carlos O'Donell
2021-06-15 3:39 ` Daniel Black
2021-06-15 16:09 ` Josh Triplett
2021-06-16 13:01 ` Alyssa Ross
2021-06-16 14:08 ` Adam Sampson
2021-06-16 19:33 ` Joseph Myers
2021-06-16 19:45 ` Phil Blundell
2021-06-30 21:54 ` Bradley M. Kuhn
2021-07-01 5:24 ` Siddhesh Poyarekar
2021-07-01 19:33 ` Bradley M. Kuhn
2021-07-02 3:29 ` Siddhesh Poyarekar
2021-07-03 6:03 ` Eli Zaretskii
2021-07-01 8:19 ` Alexandre Oliva
2021-07-02 8:59 ` Florian Weimer
2021-06-30 22:21 ` Mark Wielaard
2021-06-23 1:04 Bruno Haible
2021-06-23 3:19 ` Siddhesh Poyarekar
2021-06-24 19:30 ` Eli Zaretskii
2021-06-25 2:23 ` Siddhesh Poyarekar
2021-06-25 6:26 ` Eli Zaretskii
2021-06-25 6:47 ` Siddhesh Poyarekar
2021-06-25 7:06 ` Eli Zaretskii
2021-06-25 8:57 ` Siddhesh Poyarekar
2021-06-25 9:43 ` Siddhesh Poyarekar
2021-06-25 11:32 ` Eli Zaretskii
2021-06-25 12:07 ` Florian Weimer
2021-06-25 12:11 ` Siddhesh Poyarekar
2021-06-25 12:14 ` Florian Weimer
2021-06-25 12:25 ` Siddhesh Poyarekar
2021-06-25 12:33 ` Florian Weimer
2021-06-25 12:48 ` Siddhesh Poyarekar
2021-06-25 13:44 ` Eli Zaretskii
2021-06-25 14:06 ` Siddhesh Poyarekar
2021-06-26 6:31 ` Eli Zaretskii
2021-06-28 4:11 ` Siddhesh Poyarekar
2021-06-28 12:01 ` Eli Zaretskii
2021-06-28 13:06 ` Siddhesh Poyarekar
2021-06-28 14:04 ` Phil Blundell
2021-06-28 14:57 ` Eli Zaretskii
2021-06-25 11:30 ` Eli Zaretskii
2021-06-25 12:24 ` Siddhesh Poyarekar
2021-06-25 7:24 ` Florian Weimer
2021-06-25 7:52 ` Eli Zaretskii
2021-06-25 8:23 ` Florian Weimer
2021-06-25 11:03 ` Eli Zaretskii
2021-06-25 6:30 ` Eli Zaretskii
2021-07-02 22:23 Craig Topham
2021-07-05 14:59 ` Szabolcs Nagy
2021-07-05 16:48 ` Eli Zaretskii
2021-07-05 18:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aeadf6cd-a6c9-d4cf-8bd9-d9d54a2db120@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/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).