public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Giacomo Tesio <giacomo@tesio.it>
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
Date: Sun, 4 Apr 2021 16:38:27 +0200	[thread overview]
Message-ID: <952F2E0A-1E9F-4D21-A6F5-577CEDE0DF8A@tesio.it> (raw)
In-Reply-To: <20210404134957.810FB33CAC@vlsi1.gnat.com>

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

  reply	other threads:[~2021-04-04 14:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 23:11 RMS removed from the GCC Steering Committee (was: Remove RMS...) Giacomo Tesio
2021-03-31 23:35 ` Jeff Law
2021-04-01  0:04   ` Giacomo Tesio
2021-04-01  1:25     ` RMS removed from the GCC Steering Committee Thomas Rodgers
2021-04-02 10:05       ` Giacomo Tesio
2021-04-02 11:50         ` Christopher Dimech
2021-04-02 13:05         ` Jonathan Wakely
2021-04-02 14:06           ` Giacomo Tesio
2021-04-02 14:39             ` Christopher Dimech
2021-04-02 21:25         ` Ian Lance Taylor
2021-04-03 17:31           ` Giacomo Tesio
2021-04-03 19:33             ` Jonathan Wakely
2021-04-03 23:45             ` Ian Lance Taylor
2021-04-04  9:22               ` Jonathan Wakely
2021-04-04 13:10               ` Giacomo Tesio
2021-04-04 13:49                 ` Richard Kenner
2021-04-04 14:38                   ` Giacomo Tesio [this message]
2021-04-04 17:59                     ` Richard Kenner
2021-04-04 14:40                 ` Christopher Dimech
2021-04-04 22:53                 ` Ian Lance Taylor
2021-04-04  1:08             ` David Edelsohn
2021-04-01  9:13     ` RMS removed from the GCC Steering Committee (was: Remove RMS...) Jonathan Wakely
2021-04-01  9:23       ` Jonathan Wakely
2021-04-03  0:22     ` Gerald Pfeifer
2021-04-01  8:06 ` RMS removed from the GCC Steering Committee Andrea Corallo
2021-04-04 14:57 Christopher Dimech

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=952F2E0A-1E9F-4D21-A6F5-577CEDE0DF8A@tesio.it \
    --to=giacomo@tesio.it \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=nathan@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).