public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <lxoliva@fsfla.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: "Carlos O'Donell" <carlos@systemhalted.org>,
	gnutools-advocacy@gcc.gnu.org
Subject: Re: GNU Toolchain web site mock-up
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <ortvlzktz0.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAGWvnynjrfC+WySS5gF9Y9EzFcR5+ML2rZyiWg0FQ-4KB1YYdQ@mail.gmail.com> (David Edelsohn's message of "Sat, 6 Oct 2018 10:32:43 -0400")

On Oct  6, 2018, David Edelsohn <dje.gcc@gmail.com> wrote:

> We can use Google Docs to create a shared plan.  We also can use
> Github issues for feedback and items.

Thanks for stating a separate thread for the discussion about the
design.

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

I've asked nicely, five times already, for us (myself included) not to
use these SaaSS sites that push proprietary software onto users, because
the GNU project and myself won't use them.

Instead of admitting that the conversation in the other thread was
indeed about what tools to use, this is how you respond, blatantly
excluding me and others loyal to the GNU values, or pretending there's
no objection to that selection for us all to use to collaborate?

It suggests you're unilaterally closing the discussion about the tools,
despite the disagreement.  That's not nice at all!  It's not just rude,
arrogant, offensive and harmful to GNU.  It's also insulting and
unwelcoming.

Please reconsider, or clarify.

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

  reply	other threads:[~2018-10-06 14:53 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 [this message]
2018-01-01  0:00   ` Carlos O'Donell
2018-01-01  0:00     ` Richard Stallman
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=ortvlzktz0.fsf@lxoliva.fsfla.org \
    --to=lxoliva@fsfla.org \
    --cc=carlos@systemhalted.org \
    --cc=dje.gcc@gmail.com \
    --cc=gnutools-advocacy@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).