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 13:54:56 -0800 [thread overview]
Message-ID: <opr1zq5urvq5eh14@localhost> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKEEEIJKAA.davids@webmaster.com>
Hi
>
> It doesn't "ask" for anything. It states a license requirement. And
> yes, it does restrict rights, it removes your right to remove that
> notice. Any license clause that prohibits you from making particular
> modifications to the source code is a restriction. The only issue is
> whether it's a "further restriction" for purposes of clause 6 of the
> GPL. As I read the GPL, a restriction is a "further restriction" if it
> is imposed in addition to those stated in the GPL.
>
Blah blah blah. You can't remove copyright notices in GPL'ed software
either, so it is no additional restriction.
>> 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?"
>
> Yep, that's what it says.
>
>> GPL is ok with that.
>
> No, GPL is "you may modify however you please". It imposes only a
> specific set of restrictions and specifically prohibits the imposition
> of additional restrictions. These are *exactly* the type of additional
> restrictions the GPL was carefully worded to prohibit!
>
Blah blah blah. Read the GPL section 1 and 2.
=====
1. You may copy and distribute verbatim copies of the Program's source
code as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this
License and to the absence of any warranty; and give any other recipients
of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you
may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it,
thus forming a work based on the Program, and copy and distribute such
modifications or work under the terms of Section 1 above, provided that
you also meet all of these conditions:
...
=====
See? Must keep the appropriate copyright notice and disclaimer of warranty
in each copy.
> DS
>
>
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
next parent reply other threads:[~2004-01-18 21:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MDEHLPKNGKAHNMBLJOLKEEEIJKAA.davids@webmaster.com>
2004-01-18 21:54 ` Misshielle Wong [this message]
[not found] <MDEHLPKNGKAHNMBLJOLKAEGJJKAA.davids@webmaster.com>
2004-01-19 4:17 ` License question Misshielle Wong
2004-01-19 10:05 ` David Schwartz
2004-01-22 7:37 ` David Meybohm
[not found] <MDEHLPKNGKAHNMBLJOLKKEFLJKAA.davids@webmaster.com>
2004-01-19 0:25 ` Misshielle Wong
2004-01-17 18:57 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
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
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=opr1zq5urvq5eh14@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