From: Jean Louis <bugs@gnu.support>
To: "František Kučera" <konference@frantovo.cz>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"help-guix@gnu.org" <help-guix@gnu.org>,
Matt Lee <mattl@cnuk.org>
Subject: Re: Matt, here is kind question to provide facts on your statements about RMS
Date: Thu, 10 Oct 2019 06:39:10 +0200 [thread overview]
Message-ID: <20191010043910.GE20430@protected.rcdrun.com> (raw)
In-Reply-To: <44c2b616-76dc-d2c7-ae9c-377f4de8aa75@frantovo.cz>
* František Kučera <konference@frantovo.cz> [2019-10-09 18:11]:
> Dne 09. 10. 19 v 23:41 Wilson Bustos napsal(a):
> > Seems they don't want to reply, probably because they don't have argument.
> > Also, the project signs without as anyone to do it, they just did it.
> > There is not a vote to say 'The project is agree with this issue'.
> >
> > At least everyone now they don't want to discuss this.
> > Don't waste your energy on them ;)
>
> We saw the same behavior on the FSF Member Forum - those people who started
> the which hunt was then unable or unwilling to discuss and bring arguments.
> They rather misused the flag feature in Discourse software as a „dislike
> button“ to hide comments, they do not liked (if three users flag a post, it
> became automatically hidden).
>
> Franta
Well, policies on communication can be established better, if you have
any improvement suggestion, why not write to FSF and those who
maintain that forum?
Jean
I am asking those people who are pretending to represent all of the
GNU project and who are defaming and slandering RMS[1] to step down
and resign, do your software hacking somewhere else, you do not
deserve funding that RMS is giving you. Ludovic Courtès, Ricardo
Wurmus, Matt Lee, Andreas Enge, Samuel Thibault, Carlos O'Donell, Andy
Wingo, Jordi Gutiérrez Hermoso, Mark Wielaard, Ian Lance Taylor,
Werner Koch, Daiki Ueno, Christopher Lemmer Webber, Jan Nieuwenhuizen,
John Wiegley, Tom Tromey, Jeff Law, Han-Wen Nienhuys, Joshua Gay, Ian
Jackson, Tobias Geerinckx-Rice, Andrej Shadura, Zack Weinberg, John
W. Eaton, RESIGN and step down from GNU projects, disassociate
yourself, find another house for your excessive and uncrontollable
fear of the free speech.
Facts:
https://geoff.greer.fm/2019/09/30/in-defense-of-richard-stallman/
https://sterling-archermedes.github.io/
https://gnu.support/richard-stallman/Ludovic-Court%C3%A8s-Guix-is-accusing-Stallman-of-Thoughtcrime-on-his-own-domain-GNU-org.html
next prev parent reply other threads:[~2019-10-10 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN-t_fJGSYQj0uc6HF=1iJuoq1U8jFUnzfChDv5diYFVZDrSEg@mail.gmail.com>
2019-10-09 6:25 ` bug#37676: Matt, here is kind question to provide facts on your statements about RMS Jean Louis
2019-10-09 17:06 ` P
2019-10-09 21:41 ` Wilson Bustos
2019-10-10 2:56 ` Jean Louis
2019-10-10 4:38 ` Jean Louis
[not found] ` <44c2b616-76dc-d2c7-ae9c-377f4de8aa75@frantovo.cz>
2019-10-10 4:39 ` Jean Louis [this message]
[not found] ` <d23abb86-5c0d-5da4-fa34-7e594ad8550b@frantovo.cz>
2019-10-10 4:37 ` Matt, here is kind question to provide facts on your statements about RMS - that statement caused this discussion Jean Louis
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191010043910.GE20430@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=konference@frantovo.cz \
--cc=mattl@cnuk.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).