From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by sourceware.org (Postfix) with ESMTPS id 0722938515D4 for ; Wed, 31 Mar 2021 15:23:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0722938515D4 Received: by mail-wr1-x430.google.com with SMTP id z2so20087810wrl.5 for ; Wed, 31 Mar 2021 08:23:22 -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=xIuRLCwoo9rxkAU6bFUljuqMjP++I312Me37Ta9qCGM=; b=cde/Wsn52es20efSTR9QHFB7BSaPkKJb2Ou8SVjPF3dov6420kHBosl//WrnjaHYb3 HS0fR10C3Jg3ymYJCF8wX4q03Z3tTBQF621l6v67XA1Mr1WLRAZAbQFRErXM9DsV5Va1 Zf+FxAJO8xd48P0i1hTiT3A0XjXd9FrPwOG05nfOn6BzT/pvOGJAru2s7ssnylnIl2R1 ISU8HDECfMN6IQ6TO75hVllKlAaRHHFkKNuONabzg4JRpAHBJkysj5F2YYWX0UsVPYxS /HIs36Amqwe4XKLUGA880VGqgUQ8TXCuQO+ZjLBa72vTdmRiBEHvCrTHJB2VM5pZ/dBl pzag== X-Gm-Message-State: AOAM530Yvbz7DRq/uyz1gjjI0LJqPftME+K3WDlyxL5CMFXpMtc6bgWh c6bd8zTMh2l3SUz1R6lcWlZ0M8aTd7ZrEaw7unc= X-Google-Smtp-Source: ABdhPJzaktf5WSXYXHurFdRguvcWe1uIM+t7LbT/3QZ6STdrccenAtYYfFMyPUTcOxB54YI3sfyG6YBIj97Gor8yT/E= X-Received: by 2002:adf:e441:: with SMTP id t1mr4307452wrm.21.1617204202074; Wed, 31 Mar 2021 08:23:22 -0700 (PDT) MIME-Version: 1.0 References: <20210330151656.00007e20@tesio.it> <20210330232849.00001697@tesio.it> <20210331113417.GU2685@wildebeest.org> <87wntnqvvm.fsf@mid.deneb.enyo.de> In-Reply-To: <87wntnqvvm.fsf@mid.deneb.enyo.de> From: David Edelsohn Date: Wed, 31 Mar 2021 11:23:09 -0400 Message-ID: Subject: Re: Remove RMS from the GCC Steering Committee To: Florian Weimer Cc: David Edelsohn via Gcc , Richard Biener , Mark Wielaard , Nathan Sidwell Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.4 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:23:24 -0000 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. > > What about the plugin framework? The libgcc licensing change would > not have happened naturally. Someone had to step in and delay the > plugin framework feature until the licensing changes were in place. I wrote blocked, not delayed. 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. We didn't feel that a rupture with the FSF would be beneficial. 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. Richard Stallman, Richard Fontana, Brad Kuhn and I all worked to resolve the issue. 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. 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. I, at least, view that as my role as a member of the GCC SC. 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. Thanks, David