From: vnsndalce@memeware.net
To: linux-kernel@vger.kernel.org, gentoo-user@lists.gentoo.org,
freebsd-chat@freebsd.org, misc@openbsd.org
Subject: Threats of "blackballing" from industry if copyright-holders rescind.
Date: Sun, 06 Jan 2019 08:58:53 +0000 [thread overview]
Message-ID: <2ca83c9db45b19df105d9613cdc40ab4@memeware.net> (raw)
> lol, you people are idiots. In a time where you can and will be fired
> and ruined for ticking the wrong box, rescinding your code from a
> project such as the linux kernel will just blackball you from the
> entire industry forever. For good reason too. I wouldn't play with
> someone who takes the ball home when he gets mad either.
Why to think like a wageslave.
The old-school linux contributors did not do it for money, and their
copyrights (obviously) are still good.
Why would you give a shit if you were blacklisted from "the industry",
you have a cause of action in your hands. Legal action can reap you
dividends that you would never otherwise achieve through your entire
life.
A cause of action is worth 100 or 1000 of your earning years, often.
> lol, you people are idiots. In a time where you can and will be fired
> and ruined for ticking the wrong box, rescinding your code from a
> project such as the linux kernel will just blackball you from the
> entire industry forever. For good reason too. I wouldn't play with
> someone who takes the ball home when he gets mad either.
If bloc-recissions and litigation happen, you may not have an industry
to blackball them from.
And you can't "just reimplement" the removed code and functionality
either: as that may be infringing on the previous work as-well :). More
litigation follows to determine that.
-------
Explanation in plain American:
Video: https://openload.co/f/mT_AH3xmIUM/TruthAboutLinuxandGPLv2__.mp4
Audio: https://ufile.io/sdhpl
reply other threads:[~2019-01-06 8:58 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=2ca83c9db45b19df105d9613cdc40ab4@memeware.net \
--to=vnsndalce@memeware.net \
--cc=freebsd-chat@freebsd.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=misc@openbsd.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
Powered by JetHome