public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Valentino Giudice <valentino.giudice96@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Mission Statement
Date: Wed, 9 Jun 2021 07:09:16 +0200	[thread overview]
Message-ID: <CANC0hWh5mE_=SU93xSG+ikVQqUYdtP47cQQ1EZAeCibN5ZvnVQ@mail.gmail.com> (raw)
In-Reply-To: <5ed046a2-a2f1-f5e3-7399-dbf31808b8ef@gotplt.org>

Thank you.

> Well there was an announcement; the changes in the mission statement reflect the new reality introduced by that announcement:
>
> https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html
>
> Siddhesh

I was aware of that announcement, but it doesn't mention the mission
statement at all.
It appears that the decision in question was, at the time, in contrast
with the mission statement (rather than guided by it).

If the Steering Committee updates the mission statement, it may appear
that the mission statement follows the decisions of the steering
committee (in place of the contrary). In that case, what would be the
purpose of a mission statement?

The mission statement was also updated beyond simply making it
consistent with the change: in "Supporting the goals of the GNU
project, as defined by the FSF" the reference to the FSF was removed.

Was there any announcement about the update of the mission statement itself?
On what basis does the Steering Committee change the mission statement?

  reply	other threads:[~2021-06-09  5:09 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 [this message]
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 ` 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='CANC0hWh5mE_=SU93xSG+ikVQqUYdtP47cQQ1EZAeCibN5ZvnVQ@mail.gmail.com' \
    --to=valentino.giudice96@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=siddhesh@gotplt.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).