From: Tassilo Horn <tsdh@gnu.org>
To: Robert Thorpe <rt@robertthorpeconsulting.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: What license to use for Emacs libraries?
Date: Thu, 20 Aug 2015 06:44:31 +0200 [thread overview]
Message-ID: <87r3myin68.fsf@gnu.org> (raw)
In-Reply-To: <87pp2j0x4v.fsf@robertthorpeconsulting.com> (Robert Thorpe's message of "Wed, 19 Aug 2015 22:46:40 +0100")
Robert Thorpe <rt@robertthorpeconsulting.com> writes:
>> I think one reason why the linux kernel stuck to v2 is that v3 forbids
>> TiVo-ization.
>
> The Linux kernel uses the GPLv2. The files mention GPLv2 and don't
> say anything about optionally using later versions.
>
> The Linux kernel developers received files from people that were GPLv2
> licensed. They don't collect copyright attribution paperwork. Since
> the GPLv3 isn't compatible with the GPLv2 that means they have to keep
> everything in GPLv2. Otherwise contributors could take legal action
> against them for using their code with a different license.
Yes, that's also an organizational issue. But Linus has also made it
very clear that he doesn't share the FSF's position on TiVo-ization,
DRM, and patents which are covered by v3 but not by v2.
Bye,
Tassilo
next prev parent reply other threads:[~2015-08-20 4:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 21:06 What license to use for Emacs libraries? Marcin Borkowski
2015-08-18 21:48 ` Phillip Lord
2015-08-18 22:01 ` Stefan Monnier
2015-08-18 22:15 ` Phillip Lord
2015-08-18 23:46 ` Robert Thorpe
2015-08-19 14:12 ` Phillip Lord
2015-08-20 7:05 ` Steinar Bang
2015-08-18 23:16 ` Marcin Borkowski
2015-08-19 14:36 ` Tassilo Horn
2015-08-19 21:46 ` Robert Thorpe
2015-08-20 4:44 ` Tassilo Horn [this message]
2015-08-19 16:00 ` Phillip Lord
2015-08-18 21:53 ` Stefan Monnier
2015-08-18 23:21 ` Marcin Borkowski
[not found] ` <mailman.8593.1439940074.904.help-gnu-emacs@gnu.org>
2015-08-19 1:11 ` Stefan Monnier
2015-08-19 16:02 ` Phillip Lord
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=87r3myin68.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=rt@robertthorpeconsulting.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.