> Sent: Wednesday, March 31, 2021 at 5:45 AM
> From: "Joseph Myers" <jos...@codesourcery.com>
> To: "JeanHeyd Meneide" <phdoftheho...@gmail.com>
> Cc: "GCC Development" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nat...@acm.org>
> Subject: Re: Remove RMS from the GCC Steering Committee
>
> On Tue, 30 Mar 2021, JeanHeyd Meneide via Gcc wrote:
> 
> >      So, it boils down to this for me: either GCC is a place where all
> > contributions are welcome, or GCC is a place of hypocrisy, where
> > contributions are welcome except when Stallman (or someone else in a
> > position of power) lobbies a non-technical, non-factual argument
> > against you and jumps from their high tower to slam down on
> > rank-and-file contributors and participants. You cannot have it both
> > ways.
> 
> All contributions are welcome.  One of the key functions of the SC is 
> actually saying no to RMS.
> 
> Central FSF or GNU project infrastructure is not used in developing GCC; 
> gcc.gnu.org is entirely independent of central FSF or GNU infrastructure 
> such as savannah.  So RMS has no control over policies applied to GCC 
> mailing lists, and any influence he might apply to the moderation of lists 
> hosted on lists.gnu.org does not apply here.  (Although GCC releases are 
> uploaded to ftp.gnu.org, which is central GNU infrastructure, they are 
> also available at https://gcc.gnu.org/pub/gcc/releases/ .)  He has an 
> ordinary restricted user account on gcc.gnu.org giving the same access to 
> push commits as most committers; he does not have shell or administrative 
> access.

People are inflating the power or control he actually has.  I have to say
that at no time has Stallman dictated on any of my work.  Unlike the animosity
that has been demonstrated by Ludovic Courtès in October 2019, by sending
a message disguised to look like an official Gnu Directive to Gnu Maintainers.
A fashionable tool for excommunicating those he find problematic due to their
pesky different points of view.   
 
> -- 
> Joseph S. Myers
> jos...@codesourcery.com
>

Reply via email to