From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) by sourceware.org (Postfix) with ESMTPS id 1FDC03851C21 for ; Wed, 31 Mar 2021 15:43:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1FDC03851C21 Received: by mail-ej1-x635.google.com with SMTP id ap14so17618304ejc.0 for ; Wed, 31 Mar 2021 08:43: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:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=BVKAZUqJTumeJa76W+4Jmw5pFk+KXkXTHY3Dmt1n5/s=; b=AbgrMThdBTdryqhpwafE4yC9CXYzn3tWHVU5JiL47Rd4xkUQ9tpUQokPbdmWofz+8R JX6XGD+NfkxbMkqruU52AzxPdOIT0lHgaxd/xd2FqSQN7h+lszp4Tr4wHlXeGNaPO/Fz ICl1V9bcLFDZO8Z0rCyFnNcf0Bcp1uenUWn/ZpsB5FdroX28ePZqXxxLkPFrJ54v8xDG zpfHmvzJddfJfISoQbfm9QQP+AEoOK1GTNqkI5gbQ3Olxgi8EHGSWPSzw+1vfWe0L2+q tD+oRBf24Q9w/uioueBIdAbvBOJbZmT1OIWbO6tkzmu+e/2xUW7vCSqQEXbss0lcsRmE Va5A== X-Gm-Message-State: AOAM531jsFBdrvd+KF4cJkdTi6zhSJId9NN7Teg86cuoOFjhZ+C4kq9D 4SNkbzu0+mzXrUW0A+pGbeY= X-Google-Smtp-Source: ABdhPJzlexc3dOIRJOgR0pTEiwdfyy0rz/yASPf6ZzdYoNdSCw9ck8U/q0bfsCmmLiMZQIO5x16dGQ== X-Received: by 2002:a17:906:cb18:: with SMTP id lk24mr4123620ejb.70.1617205408143; Wed, 31 Mar 2021 08:43:28 -0700 (PDT) Received: from [192.168.178.32] (dynamic-095-114-024-196.95.114.pool.telefonica.de. [95.114.24.196]) by smtp.gmail.com with ESMTPSA id b21sm1395522ejv.13.2021.03.31.08.43.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Mar 2021 08:43:27 -0700 (PDT) Date: Wed, 31 Mar 2021 17:43:27 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: <20210330151656.00007e20@tesio.it> <20210330232849.00001697@tesio.it> <20210331113417.GU2685@wildebeest.org> <87wntnqvvm.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Remove RMS from the GCC Steering Committee To: David Edelsohn ,Florian Weimer CC: David Edelsohn via Gcc , Mark Wielaard , Nathan Sidwell From: Richard Biener Message-ID: 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, 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: Wed, 31 Mar 2021 15:43:30 -0000 On March 31, 2021 5:23:09 PM GMT+02:00, David Edelsohn wrote: >On Wed, Mar 31, 2021 at 9:46 AM Florian Weimer >wrote: >> >> * David Edelsohn via Gcc: >> >> > Has the GCC SC blocked any new port or major feature? Not that I'm >aware of=2E >> >> What about the plugin framework? The libgcc licensing change would >> not have happened naturally=2E Someone had to step in and delay the >> plugin framework feature until the licensing changes were in place=2E > >I wrote blocked, not delayed=2E In order to continue the alignment of >GCC with the FSF, the GCC SC agreed to delay deployment of LTO and >Plugins until a license to allow such features could be implemented=2E >We didn't feel that a rupture with the FSF would be beneficial=2E > >Because I foresaw the need for such features and the need for the >license to accommodate it, I had been designing and negotiating with >the FSF for an appropriate license exception for years before LTO and >Plugins were proposed=2E Richard Stallman, Richard Fontana, Brad Kuhn >and I all worked to resolve the issue=2E > >I and other members of the GCC SC have worked diligently behind the >scenes to ensure that GCC and GNU Toolchain development can proceed as >smoothly and unhindered as possible=2E We have prevented or resolved >many conflicts and issues without disturbing the broader community and >allow the community to focus on its important tasks and great progress >for the toolchain itself=2E I, at least, view that as my role as a >member of the GCC SC=2E It's like a good manager: regardless of the >openness, hopefully the GCC community feels that the GCC SC "has their >back", manages the politics, and removes real or potential roadblocks >so that the software engineer can focus on being productive=2E Indeed=2E I believe without the SC doing this GCC would either have disass= ociated itself from GNU (again) or be of marginal importance today (without= those features)=2E=20 Richard=2E=20 > >Thanks, David