From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Richard Fontana <fontana2012@gmail.com>,
"Bradley M. Kuhn" <bkuhn@ebb.org>,
tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/6] copyleft-next: remove section 7 - anti-tivoization
Date: Thu, 12 Jul 2012 19:19:03 +0100 [thread overview]
Message-ID: <20120712191903.3fba11aa@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1342115325-9443-6-git-send-email-mcgrof@do-not-panic.com>
On Thu, 12 Jul 2012 10:48:44 -0700
"Luis R. Rodriguez" <mcgrof@do-not-panic.com> wrote:
> From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
>
> The anti-tivoization clauses must go if we want this license
> to be ever considered for usage with the Linux kernel.
> This patch removes that entire section.
The kernel license won't be changing anyway. It's too big a task to
figure out. Plus if you want to change license and the new license
doesn't contain protection against DRM abusers then I for one will be
withholding my permission to change it until one is added, because the
existing GPLv2 protection while unclear is there and remains to be
litigated.
Given there are people who hold the reverse true your lock detector
should have spewed ...
There are much more important things a GPL-next needs because of its use
beyond software - protection against "design right" and "design patent"
abuses. Without that the current habit of using the GPL for 3D print
designs is potentially going to end in tears.
The way to allow DRM abuse is to have a "lesser" license which allows
abuse, just as with lesser licenses for linking.
Alan
next prev parent reply other threads:[~2012-07-12 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 17:48 [PATCH v2 0/6] copyleft-next: project name / remove anti-tivoization clause Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 1/6] copyleft-next: remove issue tracker references Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 2/6] copyleft-next: more project name updates Copyleft.next->copyleft-next Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 3/6] copyleft-next: rename the file COPYLEFT.next to copyleft-next Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 4/6] copyleft-next: embrace the Signed-off-by practice Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 5/6] copyleft-next: remove section 7 - anti-tivoization Luis R. Rodriguez
2012-07-12 18:19 ` Alan Cox [this message]
2012-07-12 17:48 ` [PATCH v2 6/6] copyleft-next: re-enumerate sections Luis R. Rodriguez
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=20120712191903.3fba11aa@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bkuhn@ebb.org \
--cc=fontana2012@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=tytso@mit.edu \
/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®