From: Valentino Giudice <valentino.giudice96@gmail.com>
To: gcc@gcc.gnu.org
Subject: GCC Mission Statement
Date: Wed, 9 Jun 2021 06:43:12 +0200 [thread overview]
Message-ID: <CANC0hWjbiuF-Zsd-o8qKmhZG1Mzh+EvQR3Mvm4V5t_Vu0u7s2g@mail.gmail.com> (raw)
Hi.
The Mission Statement of the GCC project recently changed without any
announcement.
I am not a contributor to GCC, merely a user.
However, I'd like to understand more, especially about the
transparency of the project.
The GCC Steering Committee is supposed to follow the mission statement
as a guide for its decision.
Who changes the mission statement, and for what reason?
How can a modification of the statement be guided by the mission statement?
How were users and contributors informed of this?
Thank you in advance for your response.
Best regards.
For reference:
- The GCC homepage states the SC is "guided by the mission statement":
https://gcc.gnu.org/
- The mission statement before the update:
https://web.archive.org/web/20210331192925/https://gcc.gnu.org/gccmission.html
next reply other threads:[~2021-06-09 4:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 4:43 Valentino Giudice [this message]
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 ` 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=CANC0hWjbiuF-Zsd-o8qKmhZG1Mzh+EvQR3Mvm4V5t_Vu0u7s2g@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).