From: linuxgpletc@redchan.it
To: editor@lulz.com, editor@lwn.net, news@theregister.co.uk
Cc: misc@openbsd.org, freebsd-chat@freebsd.org,
linux-kernel@vger.kernel.org, gentoo-user@lists.gentoo.org
Subject: Re: Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update 3)
Date: Tue, 29 Jan 2019 09:38:24 +0000 [thread overview]
Message-ID: <d0af58324910b1c75d7d4e5185ab03ee@redchan.it> (raw)
In-Reply-To: <CAAaskFDMjUzonLeHPmiy_VcB=jvQfF9giEaWcmNLKHDTqQt4BA@mail.gmail.com>
Some updates (3):
http://8ch.net/tech/res/1018729.html
Anonymous 01/29/19 (Tue) 09:23:25 No.1024608
>> 1024606
https://copyleft.org/guide/comprehensive-gpl-guidech8.html#x11-540007.4
Sorry lad.
Anonymous 01/29/19 (Tue) 09:25:16 No.1024609
>> 1024604
> Cites previously anonomyous paralegal woman from online rag
> Ignores published lawyers who are men
(Paralegal woman stopped talking after she would outed)
Anonymous 01/29/19 (Tue) 09:27:15 No.1024610
>> 1024608
Sorry, they published that "clarification" after I raised the issue, and
their "clarification" is bullshit.
Guess what: The FSF doesn't make the law.
Quick rundown:
Section 4 of the GPLv2 states "parties who have received..."
The "you" here is the licensee, it is not the grantor (See Section 0 of
the GPLv2 "Each licensee is addressed as "you". "). It is not applicable
against the grantor of the license: it is a rule the licensee has to
abide by, set by the grantor, in-order to have permission to modify or
create derivative works at all.
About the printer driver case: The contract in that case is the
preliminary writing, the offer to do business ("pay us, or alternatively
follow the GPL"). The acceptance of that contract by following the terms
of that preliminary writing (choosing the GPL instead of paying). That
is why both contract and damages under copyright are available. Damages
for the contract portion ("pay us"), or damages for violating the GPL
license.
The parties later settled out of court. The key is that the businesses
offer created two alternative means of acceptance of it's offer to do
business: pay for the commercial license, or follow the GPL. So the
court allowed the biz to recover the lost profit.
Anonymous 01/29/19 (Tue) 09:29:15 No.1024612
>> 1024608
Sorry, read a book *, not a publication by interested parties that was
debunked 5 hours after it was published.
https://lkml.org/lkml/2018/10/26/420
*
https://www.amazon.com/Open-Source-Licensing-Software-Intellectual/dp/0131487876
Anonymous 01/29/19 (Tue) 09:34:06 No.1024614
>> 1024604
>> 1024608
Cites idiot self-sure* paralegal woman who doesn't know her ass from her
elbow, and who went silent after she was outed, plus a publication from
an interested party that was immediately debunked.
(*is there any other type?)
Vs: Cites published lawyers well versed in their field.
Explains why interested party's publication is bullshit immediately once
aware of the fraudulent advice.
Anonymous 01/29/19 (Tue) 09:36:24 No.1024615
Notice no response to >>1024602
Just a change of tactics.
prev parent reply other threads:[~2019-01-29 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 18:19 GRSec is vital to Linux security linuxgpletc
2019-01-23 20:46 ` Ivan Ivanov
2019-01-23 22:28 ` linuxgpletc
2019-01-24 15:31 ` Enrico Weigelt, metux IT consult
2019-01-24 16:03 ` Adam Borowski
2019-01-24 16:22 ` linuxgpletc
2019-01-24 16:31 ` GRSec is vital to Linux security -- SFConservancy = legal malpractice. Use own lawyer linuxgpletc
2019-01-24 16:40 ` Fwd: Re: GRSec is vital to Linux security linuxgpletc
2019-01-28 20:20 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission linuxgpletc
2019-01-29 8:51 ` linuxgpletc
2019-01-29 9:10 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update) linuxgpletc
2019-01-29 9:38 ` linuxgpletc [this message]
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=d0af58324910b1c75d7d4e5185ab03ee@redchan.it \
--to=linuxgpletc@redchan.it \
--cc=editor@lulz.com \
--cc=editor@lwn.net \
--cc=freebsd-chat@freebsd.org \
--cc=gentoo-user@lists.gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=misc@openbsd.org \
--cc=news@theregister.co.uk \
/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