public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: lxoliva@fsfla.org, dje.gcc@gmail.com, gnutools-advocacy@gcc.gnu.org
Cc: rms@gnu.org
Subject: Re: GNU Toolchain web site mock-up
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <E1g9qan-0004lK-4j@fencepost.gnu.org> (raw)
In-Reply-To: <CAE2sS1gBwfqGdrnqniGxaU6-M4rzeSBAoTBkFHTWYn06OEq4hA@mail.gmail.com> (carlos@systemhalted.org)

  > > I'm afraid I have to ask who's this 'We' you write about.

  > Everybody else who is willing to use such tools.

The word "tools" is vague and draws attention away from the issue,
which is asking the participants in this group to run the nonfree
client software that Google Docs requires.  The reason Alexandre is
unwilling to run that software is that he supports the ideas and goals
of GNU.

To make this site properly promote GNU, its development needs the
participation of people like Alexandre who hold to those ideas.
That is crucial for a good outcome.

  > Feel free to use any other tools and post mokcups of what you would
  > like a GNU Toolchain website to look like.

He could do this on his own, but that would not enable him to truly
participate.  The question is, could he work with you in the joint
effort while doing it that way?  For instance, could he access your
latest draft, in its source form, and send you proposed patches to
that, without running the nonfree software?

If he can do that, I suppose cooperation could function that way.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)


  reply	other threads:[~2018-10-09 11:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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     ` Richard Stallman [this message]
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           ` Richard Stallman
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=E1g9qan-0004lK-4j@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=carlos@systemhalted.org \
    --cc=dje.gcc@gmail.com \
    --cc=gnutools-advocacy@gcc.gnu.org \
    --cc=lxoliva@fsfla.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).