From: "David Schwartz" <davids@webmaster.com>
To: <pavel@ucw.cz>
Cc: "pradeep singh rautela" <rautelap@gmail.com>, <hjk@linutronix.de>,
"Greg KH" <greg@kroah.com>, <linux-kernel@vger.kernel.org>
Subject: RE: [Q]Can a file be dual licensed in upstream kernel?
Date: Wed, 14 May 2008 16:36:14 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKEEEJMKAC.davids@webmaster.com> (raw)
In-Reply-To: <20080514152834.GA6888@ucw.cz>
> On Thu 2008-05-01 07:59:54, David Schwartz wrote:
> > In my _personal_opinion_, dual licensing gives you the right to choose
> > between two licenses.
> > Dual licensing gives every recipient both licenses from the
> > original author.
> > You can choose which license you will obtain rights from.
> >
> > > If a file is dual licensed BSD/GPLv2, anybody
> > > (including yourself) is free to get rid of the BSD part and make it
> > > GPLv2 only.
> > Really? Which license or law gives you the right to change the licensing
> > terms on code you didn't write? At least in the United States,
> > you cannot
> You don't change licensing. You got choice of two licenses, and you
> selected one. GPL gives you right to remove the BSD licensing terms
> you did not choose.
GPL gives you the right to remove the BSD licensing *TERMS*, but this has no
effect on the actual license. The works do not become GPLv2 only just
because you removed the licensing terms.
> (People still can use the code under BSD license _if_ they know it was
> originally BSD/GPL.. as long as you don't modify it).
Exactly. So you *cannot* change the license, you can only remove the
licensing terms. And even if you do modify it, that still has no effect on
the available licenses for any creative elements you did not author.
"6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions."
For both the GPL and the BSD license, anyone who receives covered works or
elements receives the offered licenses directly from the original author.
There is nothing you can do to change this.
Neither the BSD license nor the GPL license allow you to in any way modify
the license or licenses offered by anyone else to creative elements they
authored. In the United States, at least, this is not even possible without
a written re-licensing agreement. The licenses always flow from each
creative element's original author to the final end user. Distributors
simply provide copies of the works, they do *NOT* relicense them. People who
modify the works simply add and license other creative elements, they do not
relicense the existing ones.
DS
next prev parent reply other threads:[~2008-05-14 23:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 5:37 pradeep singh rautela
2008-04-29 5:53 ` Greg KH
2008-04-29 6:10 ` pradeep singh rautela
2008-04-29 6:26 ` Hans J. Koch
2008-04-29 6:31 ` pradeep singh rautela
2008-05-01 14:59 ` David Schwartz
2008-05-14 15:28 ` Pavel Machek
2008-05-14 23:36 ` David Schwartz [this message]
2008-05-15 18:23 ` Pavel Machek
2008-04-29 6:33 ` Bart Van Assche
2008-04-29 8:50 ` Alan Cox
2008-04-29 9:16 ` pradeep singh rautela
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=MDEHLPKNGKAHNMBLJOLKEEEJMKAC.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=greg@kroah.com \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rautelap@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
all inboxes | Powered by JetHome®