From: Phil Turmel <philip@turmel.org>
To: Richard Weinberger <richard.weinberger@gmail.com>,
Eric Appleman <erappleman@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: GPL violators (charging for a Linux kernel by itself and then charging again for source)
Date: Fri, 03 Jan 2014 17:25:04 -0500 [thread overview]
Message-ID: <52C738C0.5090604@turmel.org> (raw)
In-Reply-To: <CAFLxGvzVw31Z=hLi35J5_zE4PA5RDMgyQmcNd0kgk9LXr-kQAg@mail.gmail.com>
On 01/03/2014 05:07 PM, Richard Weinberger wrote:
> On Fri, Jan 3, 2014 at 7:56 PM, Eric Appleman <erappleman@gmail.com> wrote:
>> Wasn't the whole idea of a fee being permitted an acknowledgment that
>> physical distribution of source was acceptable if electronic was not
>> possible (low bandwidth ISP, security concerns, etc).
>
> GPLv2 states:
> "You may charge a fee for the physical act of transferring a copy, and
> you may at your option offer warranty protection in exchange for a
> fee."
Yeah, that's section #1. Charge all you want for general distribution.
But you are forgetting section #3, which kicks in if you distribute in
compiled or executable form. It limits the fee for separate source code
delivery to "no more than your cost of physically performing source
distribution"
Only your customers are entitled to that service, though.
But IANAL.
Regards,
Phil
next prev parent reply other threads:[~2014-01-03 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 18:56 GPL violators (charging for a Linux kernel by itself and then charging again for source) Eric Appleman
2014-01-03 22:07 ` Richard Weinberger
2014-01-03 22:25 ` Phil Turmel [this message]
2014-01-03 22:52 ` Richard Weinberger
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=52C738C0.5090604@turmel.org \
--to=philip@turmel.org \
--cc=erappleman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/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