From: Alexandre Oliva <lxoliva@fsfla.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
gnutools-advocacy@gcc.gnu.org,
"Richard M. Stallman" <rms@gnu.org>,
"Carlos O'Donell" <carlos@systemhalted.org>,
iains.gcc@gmail.com
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <or36tjmbll.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAGWvnymLyz7987fEVMP151jtm0P4wn+F9D3cHSZSYegs2-gtvg@mail.gmail.com> (David Edelsohn's message of "Sat, 6 Oct 2018 08:52:15 -0400")
On Oct 6, 2018, David Edelsohn <dje.gcc@gmail.com> wrote:
> Please don't redirect a discussion about advocacy for the GNU
> Toolchain and the design of the web page into a discussion about GNU
> philosophy.
The discussion was about what tools to use within this sub-sub-project..
Last I looked, GNU Tools were still part of the GNU Project.
I happen to be a speaker for the GNU Project, which means its leadership
trusts me to understand the values that matter for the project.
And yet here you are, telling myself and the project leader, both
significant advocates for the GNU Project, to keep GNU values out of the
conversation about what tools to use to advocate for a significant
portion of GNU.
> And it discourages other people from joining and helping.
Pushing proprietary software as a requirement to participate in a part
of GNU does that in a far more harmful way.
> Please stop making the conversation about you and your priorities.
Please don't make that incorrect assumption.
This is about GNU and GNU's priorities.
> There are many other mailing lists and forums to discuss this topic
> for those who wish to participate.
Indeed. And this has already been discussed and settled there:
GNU does not use or promote non-Free Software.
Can we continue the present discussion about what tools to use for GNU
Tools advocacy within this framework?
Thanks,
--
Alexandre Oliva, freedom fighter https://FSFLA.org/blogs/lxo
Be the change, be Free! FSF Latin America board member
GNU Toolchain Engineer Free Software Evangelist
next prev parent reply other threads:[~2018-10-06 13:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 Iain Sandoe
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Joseph Myers
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Carlos O'Donell
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Stallman
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Richard Stallman
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Biener
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva [this message]
2018-01-01 0:00 ` David Edelsohn
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Alexandre Oliva
2018-01-01 0:00 ` Richard Stallman
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=or36tjmbll.fsf@lxoliva.fsfla.org \
--to=lxoliva@fsfla.org \
--cc=carlos@systemhalted.org \
--cc=dje.gcc@gmail.com \
--cc=gnutools-advocacy@gcc.gnu.org \
--cc=iains.gcc@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=rms@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).