From: Alexandre Oliva <lxoliva@fsfla.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gnutools-advocacy@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
"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: <oro9c7mnxi.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <45AA782B-502B-4BE9-9CBB-76917338CBD0@gmail.com> (Richard Biener's message of "Sat, 06 Oct 2018 10:43:53 +0200")
On Oct 6, 2018, Richard Biener <richard.guenther@gmail.com> wrote:
> It's the freedom of choice for the contributor.
Individual GNU contributors can indeed pick their own poisons and use
them privately, as long as the outputs, if any, are sufficiently
standards-compliant that they can be further used indistinctly with Free
Software tools.
However, private use doesn't encompass advertising them, or inviting
other users into the same trap.
From the context, it seems to me that Carlos was not suggesting the tool
just for his own private use (why would he even name it?), but for use
by other members of the GNU Tools advocacy project, for collaborative
editing.
That would not only exclude myself and possibly other GNU contributors,
but also amount to advocating tools that oppose the very purpose of GNU.
Google doc is SaaSS, which is equivalent to proprietary software that
spies on the user and with a universal backdoor. It also refuses to run
unless the user allows a huge amount of proprietary software to run on
their own computer, which exposes the user to further objectionable
risk.
It would be self defeating to suggest anyone to use it, therefore we
shouldn't do that. If we can't use Free Software tools for
collaborative editing, we shouldn't use any.
--
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 9:21 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 ` 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 [this message]
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
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
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 ` David Edelsohn
2018-01-01 0:00 ` Joseph Myers
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=oro9c7mnxi.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).