From: David Kleuker <post@davidak.de>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: "gnu@gnu.org" <gnu@gnu.org>, "info@fsf.org" <info@fsf.org>
Subject: Recommendation of Gmail violates mission to respects users freedom
Date: Mon, 20 Feb 2023 02:01:06 +0100 (CET) [thread overview]
Message-ID: <57040213.384865.1676854866253@office.mailbox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
Hello,
since the GCC project seem not to be reachable in the Fediverse (only Twitter linked on website), i contact you here about this issue.
https://chaos.social/@davidak/109893176873158932
The Free Software Foundation and the GNU project promote and create Free Software that respects users freedom. The GCC Development Mission Statement is "Supporting the goals of the GNU project."
So i was surprised to see that you recommend the e-mail providers "Gmail, Yahoo, Hotmail, or similar" that are known not to respect the users privacy, on https://gcc.gnu.org/bugzilla/createaccount.cgi.
I suggest removing the examples since most people coming to the bug tracker should know what an e-mail provider is and instead recommend to use an e-mail alias to protect from spam on the main address.
You should also investigate how this recommendation got there and prevent such situations from happening again, as it hurts the reputation of GCC, GNU and the FSF! It did it for me.
It looks it was added in 2011: https://web.archive.org/web/20110611085833/http://gcc.gnu.org/bugzilla/createaccount.cgi
Please inform me when you found a solution. (i'm not subscribed to the mailing list)
kind regards
davidak
PS: Thanks for your work on GCC and other Free Software!
next reply other threads:[~2023-02-20 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 1:01 David Kleuker [this message]
2023-02-20 12:33 ` Jonathan Wakely
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=57040213.384865.1676854866253@office.mailbox.org \
--to=post@davidak.de \
--cc=gcc@gcc.gnu.org \
--cc=gnu@gnu.org \
--cc=info@fsf.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).