From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 4.mo7.mail-out.ovh.net (4.mo7.mail-out.ovh.net [178.32.122.254]) by sourceware.org (Postfix) with ESMTPS id 6C5A4385781D for ; Sun, 4 Apr 2021 14:38:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6C5A4385781D Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tesio.it Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=giacomo@tesio.it Received: from player693.ha.ovh.net (unknown [10.109.146.53]) by mo7.mail-out.ovh.net (Postfix) with ESMTP id 1B25219E17F for ; Sun, 4 Apr 2021 16:38:40 +0200 (CEST) Received: from tesio.it (93-41-149-224.ip82.fastwebnet.it [93.41.149.224]) (Authenticated sender: giacomo@tesio.it) by player693.ha.ovh.net (Postfix) with ESMTPSA id AE9511CB913AD; Sun, 4 Apr 2021 14:38:36 +0000 (UTC) Authentication-Results: garm.ovh; auth=pass (GARM-98R0024b79dc16-a55a-452f-9f9a-8acbb8f8b51a, 47AF7A05D6EDC344C6EE698DD213A9F2DD1C99D8) smtp.auth=giacomo@tesio.it X-OVh-ClientIp: 93.41.149.224 Date: Sun, 4 Apr 2021 16:38:27 +0200 From: Giacomo Tesio To: kenner@vlsi1.ultra.nyu.edu Cc: gcc@gcc.gnu.org, iant@google.com, nathan@acm.org Subject: Re: RMS removed from the GCC Steering Committee Message-ID: <952F2E0A-1E9F-4D21-A6F5-577CEDE0DF8A@tesio.it> In-Reply-To: <20210404134957.810FB33CAC@vlsi1.gnat.com> References: <20210401011133.00001e9c@tesio.it> <20210401020415.00002c77@tesio.it> <20210402120541.000068a5@tesio.it> <20210403193133.00005b3d@tesio.it> <20210404134957.810FB33CAC@vlsi1.gnat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Ovh-Tracer-Id: 14947447164703076030 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduledrudejtddgjeelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucenucfjughrpeffhffvuffkjghfgggtgfesthejmhdttddtvdenucfhrhhomhepifhirggtohhmohcuvfgvshhiohcuoehgihgrtghomhhosehtvghsihhordhitheqnecuggftrfgrthhtvghrnhepleeuudetkefhgefhffdttedtlefhtdeuveelueekieeiteeuleetieduhfdvleeinecuffhomhgrihhnpehgnhhurdhorhhgnecukfhppedtrddtrddtrddtpdelfedrgedurddugeelrddvvdegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpqdhouhhtpdhhvghlohepphhlrgihvghrieelfedrhhgrrdhovhhhrdhnvghtpdhinhgvtheptddrtddrtddrtddpmhgrihhlfhhrohhmpehgihgrtghomhhosehtvghsihhordhithdprhgtphhtthhopehgtggtsehgtggtrdhgnhhurdhorhhg X-Spam-Status: No, score=4.2 required=5.0 tests=BAYES_40, KAM_DMARC_STATUS, KAM_SHORT, LIKELY_SPAM_BODY, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Level: **** 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: Sun, 04 Apr 2021 14:38:44 -0000 Thanks Kenner... On April 4, 2021 1:49:57 PM UTC, kenner@vlsi1.ultra.nyu.edu wrote: > > I'm scared by the dangerous influence that dangeours US corporations > > and a dangerous military nation with a long history of human rights > > violations (see Snowden's and Assange's revelations and the ongoing > > Assange's trial) HAVE over the GCC development. > > I agree that that's a concern ... at least this is a step forward. :-) > but the point being made is that the SC is not relevant to this > because they, as a practial matter, have almost no influence on GCC > development. Yet enough to slow down certain developments such as Nathan's libcody or the plugin framework. > GCC development is mostly influenced by those companies that pay > people to work on GCC. It is a fact that most of these are US > corporations. But the only way to change that is to encourage > companies that are *not* in the US to contribute too. False: it's not the only way. You can also put trustworthy and credible observers to protect the interests of the global Free Software movement. Stallman serving in the Steering Committee, had such function. So far, what I've read in these threads makes me doubt he was actually paying attention to GCC, but if the SC workload was as light as you say, I'm reasaured he probably was. > > Except that the President of FSF (and Chief GNUissance himself) was > > receiving copy of all the communications of the Steering Committee. > > Do we know this as a fact? Ian wrote so in his response to Nathan. https://gcc.gnu.org/pipermail/gcc/2021-April/235269.html > > You said you involved him in SC discussions. > > You said you treated him as a member of the Steering Committee. > > You're missing the point here. The role of the SC is to act as the > official maintainer of GCC. The official maintainer of a GNU project > coordinates things with the GNU project (a tautology). RMS is indeed > involved in those communications (which I suspect are quite rare), but > as a representative of the GNU project, *not* of the GCC SC. What I have to say for you to understand that I'm NOT arguing here for RMS? The removal of Stallman revealed a huge issue in GCC. Maybe you can't see it. Maybe you don't want to see it. But it's evident to any seasoned programmer outside the US. It's like when you fix an UI glitch and you uncover a terrible consinstency bug causing a severe data corruption that is ongoing on your database and that the glitch was hiding. I did not request to put back the UI glitch. I asked to fix the Steering Committee. Don't you want to? Fine! Everybody can draw their conclusion. Giacomo