From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id 6EDC23858004 for ; Sun, 28 Mar 2021 18:14:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 6EDC23858004 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org Received: from librem (deer0x15.wildebeest.org [172.31.17.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 0CC97302FB96; Sun, 28 Mar 2021 20:14:43 +0200 (CEST) Received: by librem (Postfix, from userid 1000) id 20158C32C4; Sun, 28 Mar 2021 20:13:27 +0200 (CEST) Date: Sun, 28 Mar 2021 20:13:27 +0200 From: Mark Wielaard To: JeanHeyd Meneide Cc: GCC Development , Nathan Sidwell Subject: Re: Remove RMS from the GCC Steering Committee Message-ID: <20210328181327.GS2685@wildebeest.org> References: <20210328124744.GQ2685@wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no 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: Sun, 28 Mar 2021 18:14:47 -0000 Hi, On Sun, Mar 28, 2021 at 10:33:15AM -0400, JeanHeyd Meneide wrote: > This is unacceptable. The only reason I was told - as early as > yesterday, by Free Software advocates, to my socially distanced face - > that Stallman was still here is because he was powerless and had no > effect on the project. That it was run by the caring, > community-oriented stewardship of the "real volunteers" doing the > "actual work". I do not think those people were lying or trying to deceive you. This is what we hope the actual situation is. But... > Further digging into Stallman's own words and behavior also > reveals that he continues to flex this influence throughout the > project (and in other places), showing up (generally unsolicited) into > places to do this kind of gross and extreme harassment and engaging in > canceling our own hardworking contributors that actually write code > and do work. This is not a person who is just here for "historical > reasons" and who has "no power"; this is an active, perpetual threat > to hardworking and contributing members of the Free Software movement. He does indeed show up randomly claiming authority even if the GNU community has told him no. And it is important to say upfront he has no authority and that his attempts to cancel the work of hardworking GNU contributors is unwelcome. IMHO for the GCC community this means to be explicit he doesn't have any authority and he shouldn't be on the GCC steering committee. > I will never, ever contribute another line of code, another > proposal implementation[6], another optimization, or another > new/better library implementation to GCC and all of its affiliated > projects, including the compilers, glibc, libstdc++, the potential > upcoming Rust implementation, and more until this problem is not > "address", but *fixed*. If you never fix it, I will never return. > > Wish you and your community all the best in sorting this out, Thanks. I do hope we can finally fix this and welcome you back. Cheers, Mark