From: Krzysztof Halasa <khc@pm.waw.pl>
To: Remigiusz Modrzejewski <lkml.only@maxnet.org.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Policy on dual licensing?
Date: Sat, 03 Nov 2007 14:37:28 +0100 [thread overview]
Message-ID: <m3fxzno3fr.fsf@maximus.localdomain> (raw)
In-Reply-To: <slrnfiopoa.9cu.lkml.only@localhost.localdomain> (Remigiusz Modrzejewski's message of "Sat, 3 Nov 2007 12:14:15 +0000 (UTC)")
Remigiusz Modrzejewski <lkml.only@maxnet.org.pl> writes:
> What I propose is implementing a policy on accepting such code.
> According to it, every time a maintainer is considering a driver
> that is derived from BSD and licensed GPL-only, should request
> for dual licensing before accepting the patch. If the submitter is
> reluctant to do so - what can we do, it's better to have this inside
> this way than not at all. However, this should minimize such cases
> and, hopefully, satisfy the claims about Linux maintainers not doing
> all that they could to make the world a better place.
It doesn't make sense in general. Being derived from *BSD may mean
only a tiny fragment comes from *BSD. I can't see any valid reason
to force/ask the author to publish his/her code under BSD
(GPL + BSD = BSD) instead of GPLv2 as used by the whole Linux.
There are exceptions, of course - if you take a *BSD project and
include it with no/minor changes it makes sense to use BSD licence,
because we really want to cooperate, and because we don't have to
fear "evil corporations" taking our code (because it's mostly not
"ours").
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-11-03 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 12:14 Remigiusz Modrzejewski
2007-11-03 13:37 ` Krzysztof Halasa [this message]
2007-11-03 16:36 ` Remigiusz Modrzejewski
2007-11-04 0:04 ` Theodore Tso
2007-11-04 17:30 ` Remigiusz Modrzejewski
2007-11-06 12:40 ` Jarek Poplawski
2007-11-05 23:13 ` David Schwartz
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=m3fxzno3fr.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.only@maxnet.org.pl \
/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®