public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: giacomo@tesio.it
Cc: gcc@gcc.gnu.org, iant@google.com, nathan@acm.org
Subject: Re: RMS removed from the GCC Steering Committee
Date: Sun, 04 Apr 2021 13:59:13 EDT	[thread overview]
Message-ID: <20210404175913.5A85233CAC@vlsi1.gnat.com> (raw)
In-Reply-To: <952F2E0A-1E9F-4D21-A6F5-577CEDE0DF8A@tesio.it>

> Yet enough to slow down certain developments such as Nathan's libcody
> or the plugin framework.

The SC had no role in that, as was discussed here.

> You can also put trustworthy and credible observers to protect the
> interests of the global Free Software movement.

How is an "observer" going to influence which people are willing to
spend their time developing software and how much time they're willing
spend?  As a practical matter, the direction of any Free Software project
is dictated by those who actually work on it from day to day and who pays
for their time, not by groups like the SC or the maintainers.

> > > 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

That says he was "involved in SC discussions", which to me, means that
he *didn't* get a copy of all their communications.  If somebody says
they're a member of the XYZ committee and "involved Bob in our
discussions", to me, that means that Bob is *not* in the committee and
doesn't get all committee communications, but that they chose to
involve him in some of their discussions.

> 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.

I just don't see it as a "removal".  RMS is still in charge of the GNU
project.  That means that he, at some level, is involved in every GNU
project, including GCC.  As a practical matter, that involvement was
very slight and still is.  I don't see any change whatsoever in the
day-to-day operations of GCC.


  reply	other threads:[~2021-04-04 17:59 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
2021-04-04 17:59                     ` Richard Kenner [this message]
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=20210404175913.5A85233CAC@vlsi1.gnat.com \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=giacomo@tesio.it \
    --cc=iant@google.com \
    --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).