mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: nipponmail@firemail.cc
To: linux-kernel@vger.kernel.org, torvalds@osdl.org, esr@thyrsus.com
Subject: I'm being accused of "killing foss", how do I respond?
Date: Tue, 23 Jun 2020 15:36:51 +0000	[thread overview]
Message-ID: <986afee43e6dcf11a812a595f1d55c77@firemail.cc> (raw)

Dear RMS, a commentator is now accusing me of being the executioner of 
"foss" :

> oh it's you, the schizo who killed foss by trying to defend it and 
> thinks he's a lawyer

Later the commentator clarifies :

> You went on a mailing list for some foss project with the intention of 
> exposing a patent violation by some
> other project using the code, but instead of talking about that, you 
> just ranted for a few days about how much
> you want to fuck little girls.
> Then RMS got labeled a pedophile and eaten up by cancel culture.
> I'm flabbergasted you're honestly too stupid to see the connection.


The issue is copyright, not patent, and there was nothing wrong with 
your past statements.

I would think that the fact that the GPL is effectively toothless is 
what would "kill free and opensource software" by causing would-be 
contributors to now lack faith in the "share and share alike" promise of 
the GPL. The FSF won't enforce it's GCC copyrights, nor will the linux 
kernel contributors (both regarding GRSecurity linux kernel patches and 
GCC plugins (and their no-redistribution attached clauses))

I also wonder about this
> for a few days
invective.
Are days suddenly a euphemism such as is imagined regarding various 
creation stories?

How should I respond and set the record straight? And when did "FOSS" 
die? I remember when that term was coined, early 2000s, has it now 
fallen out of favor? Why is it my fault? I never really liked that term 
to begin with: it's a corporate conflation of two specific idea sets: A 
gloss. If said term is gone what is the injury?



                 reply	other threads:[~2020-06-23 15:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=986afee43e6dcf11a812a595f1d55c77@firemail.cc \
    --to=nipponmail@firemail.cc \
    --cc=esr@thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®