From: Misshielle Wong <mwl@bajoo.net>
To: David Schwartz <davids@webmaster.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: License question
Date: Sun, 18 Jan 2004 09:23:28 -0800 [thread overview]
Message-ID: <opr1zelegnq5eh14@localhost> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKKEPBJJAA.davids@webmaster.com>
Hello
On Sat, 17 Jan 2004 14:06:32 -0800, David Schwartz <davids@webmaster.com>
wrote:
>
>
>> > Is it possile to include in the kernel distro some code with this
>> > BSD-style license ?
>
>> Let me see
>
> Yes, in general. No, not this license.
>
Hahaha
>> > - Redistributions of source code must retain the above copyright
>> > notice, this list of conditions and the following disclaimers.
>
> Sorry, that's an "additional restriction" not permitted under the GPL.
>
This is no restriction. This here just asks for copyright notice and
conditions to NOT be removed, which is perfectly fine. Section 6 never
overrides this. Section 6 asks not to restrict rights, and above clause
does not restrict rights.
>> > - Redistributions in binary form must reproduce the above copyright
>> > notice, this list of conditions and the following disclaimers in the
>> > documentation and/or other materials provided with the distribution.
>
> I believe this is an additional restriction as well.
I find perfectly fine. Is just a request to include the copyright notice
and conditions along with the binary. Section 2, clause c does not
override. Does not infringe Section 6 either. What is the problem?
>
>> Mmmm... I think yes. Code in kernel must be licensed GPL. Above allow
>> sublicense so ok
>
> They allow sublicensing, but the sublicense can't remove the additional
> restriction. See section 6 of the GPL.
>
> To make this license GPL compatible, the two restrictions above would
> have to be modified to be identical to, or a proper subset of, section 2
> clauses b and c of the GPL.
>
Hahaha, those are no restrictions, so no problem. Summarizing this
license, it ends up like this: "Copyright bla bla bla. Keep 'em goddamn
copyrights and disclaimer or else you have no rights to copy, modify,
sublicense, redistribute, sublicense bla bla bla. Software provided 'as
is'. Clear?"
GPL is ok with that.
> DS
>
>
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
next prev parent reply other threads:[~2004-01-18 17:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 18:57 License question Giuliano Pochini
2004-01-17 19:25 ` Valdis.Kletnieks
2004-01-18 9:27 ` Sergey Vlasov
2004-01-17 19:41 ` Misshielle Wong
2004-01-17 22:06 ` David Schwartz
2004-01-18 17:23 ` Misshielle Wong [this message]
2004-01-19 8:14 ` Jes Sorensen
2004-01-19 16:00 ` J. Bruce Fields
2004-01-19 17:03 ` Misshielle Wong
2004-01-19 11:24 ` Giuliano Pochini
2004-01-19 11:31 ` David Schwartz
2004-01-20 9:30 ` Giuliano Pochini
2004-01-20 17:19 ` David Schwartz
2004-01-19 12:15 ` Jes Sorensen
2004-01-18 11:07 ` Andreas Jellinghaus
[not found] <MDEHLPKNGKAHNMBLJOLKEEEIJKAA.davids@webmaster.com>
2004-01-18 21:54 ` Misshielle Wong
[not found] <MDEHLPKNGKAHNMBLJOLKKEFLJKAA.davids@webmaster.com>
2004-01-19 0:25 ` Misshielle Wong
[not found] <MDEHLPKNGKAHNMBLJOLKAEGJJKAA.davids@webmaster.com>
2004-01-19 4:17 ` Misshielle Wong
2004-01-19 10:05 ` David Schwartz
2004-01-22 7:37 ` David Meybohm
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=opr1zelegnq5eh14@localhost \
--to=mwl@bajoo.net \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
/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