public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Giacomo Tesio <giacomo@tesio.it>
To: Gabriel Ravier via Gcc <gcc@gcc.gnu.org>
Cc: Gabriel Ravier <gabravier@gmail.com>,
	Valentino Giudice <valentino.giudice96@gmail.com>,
	Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: GCC Mission Statement
Date: Wed, 9 Jun 2021 12:11:28 +0200	[thread overview]
Message-ID: <20210609121128.0000240f@tesio.it> (raw)
In-Reply-To: <736215d3-72b8-b2e2-f406-80d3d38688e0@gmail.com>

Hi Gabriel,

On Wed, 9 Jun 2021 11:44:10 +0200 Gabriel Ravier via Gcc wrote:
> Speaking on the "change it recklessly" issue, I would personally say 
> that SC has indeed arguably done this [...]
> some people threatened to pull away from GCC entirely if it remained
> tied to the FSF. I personally happen to agree with the change (which
> seems to have especially avoided what would have been a painful split
> that could have had disastrous consequences for GCC as a whole), but
> find it rather disconcerting that such changes with potentially major
> consequences were done without any direct discussion of them with the
> community whatsoever.

Did you consider that, in fact, the lack of transparency of the
Steering Committee has shown since then (or even just the lack of
professionalism, when it comes to explicit intruduce major changes in
major versions) is a "disastrous consequence for GCC as a whole"?

Unilateral undiscussed changes by the Steering Committe is the new norm.


And such Steering Committee is in no way representing the interests of
the worldwide users of GCC, first because its members do not know them
(the vast majority is from the US, work for US corporations or both)
and second because they do not listen to any objection / request that
does not comes from their own circle / social group.


Are you sure that an explicit fork with two projects with different
names and governance would had been worse than what GCC has become?


Giacomo

  reply	other threads:[~2021-06-09 10:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09  4:43 Valentino Giudice
2021-06-09  4:56 ` Siddhesh Poyarekar
2021-06-09  5:09   ` Valentino Giudice
2021-06-09  5:32     ` Siddhesh Poyarekar
2021-06-11  4:42       ` Valentino Giudice
2021-06-09  6:31     ` Didier Kryn
2021-06-09  9:44     ` Gabriel Ravier
2021-06-09 10:11       ` Giacomo Tesio [this message]
2021-06-09 12:41         ` Gabriel Ravier
2021-06-09 14:22           ` Giacomo Tesio
2021-06-09 14:32             ` Richard Biener
2021-06-09 15:26               ` Giacomo Tesio
2021-06-09 15:34                 ` Christopher Dimech
2021-06-09 13:48   ` Christopher Dimech
2021-06-09 14:02     ` Aaron Gyes
     [not found]     ` <01624AC3-781E-4AAC-A469-87A777AD50DA@icloud.com>
     [not found]       ` <trinity-d5e4b50f-600c-41dd-a628-e2c1d0103604-1623252603196@3c-app-mailcom-bs05>
2021-06-09 15:49         ` Aaron Gyes
2021-06-09 20:49           ` Christopher Dimech
2021-06-09 21:07             ` Aaron Gyes
2021-06-10  3:10               ` Christopher Dimech
2021-06-11  4:58 ` GCC " Valentino Giudice

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=20210609121128.0000240f@tesio.it \
    --to=giacomo@tesio.it \
    --cc=gabravier@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=siddhesh@gotplt.org \
    --cc=valentino.giudice96@gmail.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).