public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Valentino Giudice <valentino.giudice96@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Mission Statement
Date: Wed, 9 Jun 2021 11:02:52 +0530	[thread overview]
Message-ID: <45610ffd-5d7d-6b59-143f-bd1289948ed8@gotplt.org> (raw)
In-Reply-To: <CANC0hWh5mE_=SU93xSG+ikVQqUYdtP47cQQ1EZAeCibN5ZvnVQ@mail.gmail.com>

On 6/9/21 10:39 AM, Valentino Giudice wrote:
> 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.

Quite a few projects under the GNU project[1] have dissociated 
themselves from the FSF, so "as defined by the FSF" perhaps doesn't 
apply as consistently as it did before.  That is my understanding 
anyway; maybe there's more context that others may be able to add.

Siddhesh

[1] https://gnu.tools/en/software/

  reply	other threads:[~2021-06-09  5:33 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 [this message]
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=45610ffd-5d7d-6b59-143f-bd1289948ed8@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=gcc@gcc.gnu.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).