> Sent: Saturday, April 03, 2021 at 2:06 AM
> From: "Giacomo Tesio" <giac...@tesio.it>
> To: "Jonathan Wakely" <jwakely....@gmail.com>
> Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, "Nathan Sidwell" <nat...@acm.org>
> Subject: Re: RMS removed from the GCC Steering Committee
>
> Dear Jonathan,
> 
> everybody can see it...
> 
> On Fri, 2 Apr 2021 14:05:10 +0100 Jonathan Wakely wrote:
> 
> > On Fri, 2 Apr 2021 at 11:06, Giacomo Tesio wrote:
> > > But from outside your "cultural bubble", we all see that a bunch of
> > > highly controversial [3][4] US corporations (with long term ties
> > > with the USA DoD [5]) are kicking out of the GCC Steering Committee
> > > their only connection with both the FSF and the GNU project.  
> > 
> > If that's what you think happened, you've not been paying attention to
> > this thread. 
> 
> ...I wrote such a long mail, full of references to so many passages of
> your mails in these threads... without paying attention to them.
> 
> What a lucky guy, I am! :-D
> 
> 
> > The SC just did was they were requested to do by (some
> > of) the developers of the project.
> 
> Yeah, "some of".
> 
> In this specific moment, when a global (and well financed) mob is
> attacking RMS personally, for anything they can frame as mischief,
> you were fine to comply with what "some of the developers" asked.
> 
> What about the others?
> Did you consider that many of them might be to scared to oppose?

Even if you consider those who are not scared, the list clearly outstrips
any legitimacy of the anti-stallman group.  I clearly remember Ludovic Courtès
trying to hamstring all Gnu Maintainers and force them to implement Codes of 
Conduct without any authority whatsoever.  Free Software is about having NO 
Owners.
 
Despite corporations' proliferation of codes of conduct, codes oftentimes 
suffer from numerous weaknesses that undermine the whole thing.

> 
> Yet my request is not about Stallman, but about the Steering Committee.
> 
> Please fix the huge global hazard that his removal uncovered.
> 
> 
> Giacomo
>

Reply via email to