From: Ian Lance Taylor <iant@google.com>
To: Giacomo Tesio <giacomo@tesio.it>
Cc: Thomas Rodgers <rodgert@appliantology.com>,
Nathan Sidwell <nathan@acm.org>,
JeanHeyd Meneide <phdofthehouse@gmail.com>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: RMS removed from the GCC Steering Committee
Date: Fri, 2 Apr 2021 14:25:34 -0700 [thread overview]
Message-ID: <CAKOQZ8x+8KPLvbYk4jN+iWAtS+8wdOkVJmGi-1LiPErqmZsDGw@mail.gmail.com> (raw)
In-Reply-To: <20210402120541.000068a5@tesio.it>
On Fri, Apr 2, 2021 at 3:06 AM Giacomo Tesio <giacomo@tesio.it> wrote:
>
> I'm sorry for this long mail that rivals with the original Nathan's
> request, but I wanted to back my request properly.
This is free software. If you want to make it better, then make it
better. The EGCS branch that displaced and became GCC came into
existence because the people involved felt that it would make GCC
better (I was a participant myself, though not a major one). See
https://en.wikipedia.org/wiki/GNU_Compiler_Collection#EGCS_fork for a
few more details.
GCC is a successful free software project, but it is not perfect. It
has many problems. Lack of contributor diversity is one of them. If
I knew how to fix that problem, I would work to fix it. I personally
do not believe that the membership of the steering committee is a
significant cause of that problem. But I could be mistaken. So prove
me wrong. Do the work.
Ian
next prev parent reply other threads:[~2021-04-02 21:25 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 [this message]
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
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=CAKOQZ8x+8KPLvbYk4jN+iWAtS+8wdOkVJmGi-1LiPErqmZsDGw@mail.gmail.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=giacomo@tesio.it \
--cc=nathan@acm.org \
--cc=phdofthehouse@gmail.com \
--cc=rodgert@appliantology.com \
/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).