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 09:49:57 EDT [thread overview]
Message-ID: <20210404134957.810FB33CAC@vlsi1.gnat.com> (raw)
In-Reply-To: <D6161B47-65E4-4395-8609-D06F577D82ED@tesio.it>
> 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, 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. 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.
> 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? I don't know whether that's the case or
not, but I've read this entire thread and have seen no evidence either
way on that issue. In any event, I suspect that the "all communications"
may be less than a few dozen emails a year, although that's only a
guess on my part.
> Thus, I'm not naive enough to ignore the thousands way your employee
> can get huge advantages by having you in the GCC's Steering Committee.
Thousands? Given how little the SC actually *does*, I find it hard
to come up with any meaningful advantages at all, let alone "huge" ones.
> As a small example among many many others, you are using a @google.com
> mail address while serving in the Steering Committee.
So? How many emails per year do SC members send on behalf of the SC?
As far as I see, it averages maybe two per year, all of which are
announcements of new or changed maintainers of components of GCC.
> On the contrary, it explains WHY you are debating against an urgent
> fix to the GCC Steering Committee on my request, while you had no
> problem to promptly remove Stallman on Nathan's request.
Again, the position taken was that RMS was never *on* the SC to begin
with.
> 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.
next prev parent reply other threads:[~2021-04-04 13:50 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 [this message]
2021-04-04 14:38 ` Giacomo Tesio
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=20210404134957.810FB33CAC@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).