public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Giacomo Tesio <giacomo@tesio.it>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: RMS removed from the GCC Steering Committee
Date: Sun, 4 Apr 2021 10:22:35 +0100	[thread overview]
Message-ID: <CAH6eHdRCeYNeHfFYAfvM99vfRQkUi36==BQ4LksNEr5hg80xrQ@mail.gmail.com> (raw)
In-Reply-To: <CAKOQZ8wnmmXzcsV4JA_WzzYfZQv2BZzd2QUz-3XR2jf6i48e8w@mail.gmail.com>

On Sun, 4 Apr 2021, 00:46 Ian Lance Taylor via Gcc, <gcc@gcc.gnu.org> wrote:

> On Sat, Apr 3, 2021 at 10:31 AM Giacomo Tesio <giacomo@tesio.it> wrote:
> >
> > But apparently you cannot decide which US-corporation should be thrown.
> > (indeed US-corporations hold the vast majoirity of SC heads, right now).
>

As it clearly says on the steering committee page, appointments are
personal, not based on employer. One SC members just moved job but didn't
lose his SC position, because it's him and not his employer who is on the
committee.


> I don't understand this argument.  If we remove everybody from the
> committee, then it will be more balanced in some sense, but there
> won't be anybody on it.  If you want a more balanced committee, then
> at some point you have to talk about adding people.
>
> And I do think it would make sense to add more people to the
> committee.  Any suggestions?  They should of course be people
> reasonably familiar with GCC and with free software, and with
> compilers and software development tools.



And if you don't allow anybody from big US or German corporations, you're
going to have to keep kicking experienced people off the committee and
replacing them with inexperienced people. That's because experienced,
dedicated contributors tend to get hired to keep working on the project. I
was an unpaid volunteer and maintainer for years before I got hired to work
on GCC. Was I doing good work at first, then became a pawn of evil
business? No, because your arguments are silly (and I don't even think
they're in good faith, I think you're just being a Concern Troll because
you're upset about the removal of RMS).

  reply	other threads:[~2021-04-04  9:22 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 [this message]
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='CAH6eHdRCeYNeHfFYAfvM99vfRQkUi36==BQ4LksNEr5hg80xrQ@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=giacomo@tesio.it \
    /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).