public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Valentino Giudice <valentino.giudice96@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: GCC Mission Statement
Date: Fri, 11 Jun 2021 06:58:24 +0200	[thread overview]
Message-ID: <CANC0hWjx=+4yAn+cX=e0VDcc5frPStoeisY_Q6-=uUd1pMaUoA@mail.gmail.com> (raw)
In-Reply-To: <CANC0hWjbiuF-Zsd-o8qKmhZG1Mzh+EvQR3Mvm4V5t_Vu0u7s2g@mail.gmail.com>

I am glad this email created some discussion.

Some users seem to think the change was either reckless or nontransparent.
This includes one user who replied me off list:
> Please continue until they tell the truth.

Given the additional context provided by the answers, I agree with that opinion.

I therefore call for the Steering Committee to reconsider the decision
and, at minimum, discuss it openly and transparently both on this
mailing list (seeking for consensus) and the FSF (especially given its
strong role in the previous mission statement).

I think the SC is accountable to the users as well, given that it
being guided by the mission statement is plainly stated on the GCC
homepage. But of course, it is also accountable to the people directly
involved.

I think the SC needs to clarify whether it gets to do whatever it
wants and change the mission of the project at will, for any reason
whatsoever.

I personally believe a positive answer is in contradiction with what
the SC is meant to be:

> The primary purpose of the steering committee is to make major decisions in the best interests of the GCC project and to ensure that the project adheres
to its fundamental principles found in the project's mission statement.

https://gcc.gnu.org/steering.html

      parent reply	other threads:[~2021-06-11  4:58 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
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 ` Valentino Giudice [this message]

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='CANC0hWjx=+4yAn+cX=e0VDcc5frPStoeisY_Q6-=uUd1pMaUoA@mail.gmail.com' \
    --to=valentino.giudice96@gmail.com \
    --cc=gcc@gcc.gnu.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).