From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) by sourceware.org (Postfix) with ESMTPS id 3C1A83857C4F for ; Mon, 14 Jun 2021 19:25:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3C1A83857C4F Received: by mail-qt1-x82a.google.com with SMTP id o19so9440220qtp.5 for ; Mon, 14 Jun 2021 12:25:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jhVkGX4KWnfuiFuoihxZZ89Lncjwz7Uoq/kib+SCuuM=; b=EB7IGABDgTgtmBHq2nntzHTiZdyMfvlR24mnVP+w1LCLlv5S0QRLe1MGa7OCrLIA3x 8rD874ZJB2aCMltLY0LIeE+1pomWgQu5cTk2IbCLcLFOES0vUkFsa7Ar9+qTxa6gDFTP WtJCzrWUWvDSAO5LuMxVYt1nILgL4bn9TWwKSiWlcG25qh0T2pDPEYjzPHrUWV0wXa+l YyZwYEZwisVs2v42vZiEx27NHEd1Bc2gp9r/SZcNCMgz9y9blGxSxRFUM05RGGsEZ2BP l3emVzAowJw46DMuG5dv/tMKXUjLfmOsYVDFu/Cz2MsHv4mqd19ai2xpnEZXwDfCEmWp vN5A== X-Gm-Message-State: AOAM532kq5sFz+7H0kHVklvzxMmHC+qI6iodrjgR5GRiTlkugRyclpx7 Hde+5OvASD+5w6C9LyDszHhvCJflOvsXlx2nk+U= X-Google-Smtp-Source: ABdhPJybZRhoaPUl9zCmUB6rXQJPlbkDSy/u4jmrlMPZzZVo2us1US5p+DHdsxOhzckDGZ2FwSm7iXGQnsmQkJyjFeE= X-Received: by 2002:a05:622a:549:: with SMTP id m9mr18083557qtx.369.1623698728808; Mon, 14 Jun 2021 12:25:28 -0700 (PDT) MIME-Version: 1.0 References: <20210614190805.GN13220@brightrain.aerifal.cx> In-Reply-To: <20210614190805.GN13220@brightrain.aerifal.cx> From: Khem Raj Date: Mon, 14 Jun 2021 12:25:02 -0700 Message-ID: Subject: Re: Seeking input from developers: glibc copyright assignment policy. To: Rich Felker Cc: "Carlos O'Donell" , Jakub Jelinek , libc-alpha , "Joseph S. Myers" , Maxim Kuvyrkov Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2021 19:25:30 -0000 On Mon, Jun 14, 2021 at 12:08 PM Rich Felker 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