From: Jes Sorensen <jes@wildopensource.com>
To: Misshielle Wong <mwl@bajoo.net>
Cc: David Schwartz <davids@webmaster.com>,
linux-kernel@vger.kernel.org, Giuliano Pochini <pochini@shiny.it>
Subject: Re: License question
Date: 19 Jan 2004 03:14:39 -0500 [thread overview]
Message-ID: <yq0d69g8ids.fsf@wildopensource.com> (raw)
In-Reply-To: <opr1zelegnq5eh14@localhost>
>>>>> "Misshielle" == Misshielle Wong <mwl@bajoo.net> writes:
Misshielle> Hello On Sat, 17 Jan 2004 14:06:32 -0800, David Schwartz
Misshielle> <davids@webmaster.com> wrote:
>>> > - 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.
Misshielle> I find perfectly fine. Is just a request to include the
Misshielle> copyright notice and conditions along with the
Misshielle> binary. Section 2, clause c does not override. Does not
Misshielle> infringe Section 6 either. What is the problem?
You may find this one fine, but that doesn't make it fly, sorry.
Requiring people to redistribute the license notice in all
documentation included with the binaries is an additional restriction
which is not found in the GPL. So a very clear no cannot do.
This is also known as the BSD 'advertisement' clause which was the
main reason we could never use BSD code in the old days. Berkeley has
since updated their license and removed this clause from it, however
the license still poses a problem since it doesn't include an explicit
patent license grant, but thats a completely different issue.
Cheers,
Jes
next prev parent reply other threads:[~2004-01-19 8:14 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
2004-01-19 8:14 ` Jes Sorensen [this message]
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=yq0d69g8ids.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwl@bajoo.net \
--cc=pochini@shiny.it \
/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