From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) by sourceware.org (Postfix) with ESMTPS id 73BE4385781C for ; Mon, 7 Jun 2021 13:27:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 73BE4385781C Received: by mail-lf1-x134.google.com with SMTP id t7so19167761lff.0 for ; Mon, 07 Jun 2021 06:27:08 -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=K1mJ6P33L4B+q7lgVoHqRq89zqnViz2MEoLxAVoLtAQ=; b=JDFh60NsNnnHuxEPh7LWUgSGC1aZ4f1us67CdPQDjBu9pzHJb26dOG7T5QDwzsaBp1 l6qmUcGvPT9MdJLUaNvXow1Lj37itvTkmcejbNoYZwX0DUJ5YDeL/5zLwIEt5J5Q48DQ Tesrh89wEX35AmsmsttHvr6WiKKmc7EK+gSYwYxlZ4rcPb2AWu/3Gw74lTVovH1oPPev Wr0CPsq+JGR6yA6W83k1mqUpbCuDn9AGzeKtkdt0jHRmOqmqXzYw4bKDt9PENqnSJv0A /WcuU6q4SXQeCTzXZ+/QS0HNHwI3YvrSBTSvURRq95xOT0I/sejIuJz/2nzqwBn7b41H WcLQ== X-Gm-Message-State: AOAM530lyGx7oK+S5CRxHFpdr+piGn0o5Dv+hKihU80JH1/DJUsUp2Wh pI8XBfbKUHZxIDZyHGrTYjr/9HiYLXvDP5ePHi0= X-Google-Smtp-Source: ABdhPJy9WPNt9KyLXBupt1YwaW8IIgbKSAmpg8U544AVOY+FhJ7DPVhGIkKAZRtd2IrYf3nMm6ZKMjE38h8/cfn7cqI= X-Received: by 2002:a19:7d83:: with SMTP id y125mr3761065lfc.135.1623072427184; Mon, 07 Jun 2021 06:27:07 -0700 (PDT) MIME-Version: 1.0 References: <20210603143551.00005b3d@tesio.it> <20210603130216.GF7746@tucnak> <20210603160707.00002be6@tesio.it> <20210603141415.GH7746@tucnak> <20210603164502.00004058@tesio.it> <07F6EACD-39B9-45CE-AF5D-9422EF0E450D@tesio.it> In-Reply-To: <07F6EACD-39B9-45CE-AF5D-9422EF0E450D@tesio.it> From: David Edelsohn Date: Mon, 7 Jun 2021 06:26:52 -0700 Message-ID: Subject: Re: Update to GCC copyright assignment policy To: Giacomo Tesio Cc: Richard Biener , Jason Merrill , Jakub Jelinek , gcc Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2021 13:27:19 -0000 On Mon, Jun 7, 2021 at 6:11 AM Giacomo Tesio wrote: > > Hi Richard, > > On June 7, 2021 7:35:01 AM UTC, Richard Biener wrote: > > On Thu, Jun 3, 2021 at 5:27 PM Jason Merrill via Gcc > > wrote: > > > > > > On Thu, Jun 3, 2021 at 10:46 AM Giacomo Tesio > > wrote: > > > > > > > > > > > I would have really appreciated if the GCC SC had announced such > > change > > > > for the upcoming GCC 12 while sticking to the old policy in GCC > > 11. > > > > > > > > > > That is how I was thinking of the change, but I agree that it needs > > > clarification. > > > > I don't think this is very practical - we'd need to check each and > > every commit before considering backporting fixes, no? > > I'm a bit surprised: aren't such commits reviewed anyway on backport? > > Even if they apply smoothly, they could introduce nasty bugs if applied blindly. > > Also, are there many non-FSF-assigned contribution in the development > branch already? > > > > > "tainted" > > Sad word choice, tbh. > > Given that such major development decision was not discussed here but > Imposed unilateraly by the Steering Committee, a bit of forewarning would be > much more professional. > > Not because the new version are somehow "tainted" but because the many different > users of GCC around the world deserve a bit more respect, imho. > > > This is not a minor change and should not be introduced in minor versions. > > It's a breaking change, after all. It's not a new or different license (unlike GPLv2->GPLv3). It's not reverting the existing copyrights and assignments. As Eben Moglen stated in the ZDNet article: "the FSF will long remain the preponderant copyright holder in GCC and related projects... No downstream user, modifier or redistributor of GCC is facing any changes whatsoever." The break mostly is psychological, not technical or legal. Thanks, David