Skip to contentSkip to conversation

Monta Vista software license terms

DISCUSSION [email protected] 3 participants 4 messages Feb 12, 2003 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 20030212213022.AAA17490%shell.webmaster.com@whenever

#1 lore raw
Quoted 1 line · David Schwartz

You already have the right to produce derivative works.

No. At least in the US, 17 USC 106 says producing a derivative right is reserved to the copyright holder, except for the cases enumerated in 17 USC 107-121.

So if you're producing a derivative work without having gotten the rights to do so, you're screwed in the legal sense.

Clause 2 of the GPL gives you the right to produce derivative works *IF* you accept the conditions. Having accepted that clause, you're bound by it - that's what makes the GPL work.

Please enumerate what *OTHER* way you are getting the right to produce a derivative work, rather than via the GPL clause 2. (Note that this *could* happen, if for instance code is dual-licensed and you are getting the right via the other license).

Quoted 6 lines

You already
have the right to distribute the original work. You already have the right to distribute the modifications. Your recipient already has the right to use and possess the original. There is no additional right to the original work for this section to give you. The right it seeks to give you is the simple sum of rights you already have.

Note again that two of these rights (distribute the original, distribute the modifications) are *NOT* ones you inherently have - you are getting them *WITH RESTRICTIONS* on what you can and can't do (see clause 2 again).

Quoted 2 lines

"Distributing derived works" is not a specific right under any
copyright law I know of. It's the sum of other rights. You need some

It's the sum of several rights, one of which is "creating a derived work". If you can't legally create a derived work, you can't legally distribute same.

Signature · 3 lines
				Valdis Kletnieks
				Computer Systems Senior Engineer
				Virginia Tech
#2 lore raw
Quoted 10 lines · On Wed, 12 Feb 2003 16:43:10 -0500, [email protected] wrote:
Quoted 1 line · David Schwartz

You already have the right to produce derivative works.

No. At least in the US, 17 USC 106 says producing a derivative right is reserved to the
copyright holder, except for the cases enumerated in 17 USC 107-121.

So if you're producing a derivative work without having gotten the rights to do so, you're screwed in the legal sense.

You have been given that right. The GPL, without clause 2, gives you
the right to use the work (see citation below). For source code, the only way to use it is to produce derivative works.

Quoted 6 lines

Clause 2 of the GPL gives you the right to produce derivative works *IF*
you accept the conditions. Having accepted that clause, you're bound by
it - that's what makes the GPL work.

Quoted 6 lines

Please enumerate what *OTHER* way you are getting the right to produce a
derivative work, rather than via the GPL clause 2. (Note that this *could*
happen, if for instance code is dual-licensed and you are getting the right via the other license).

The GPL says:

"Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."

Please explain to me, say for the case of the Linux kernel source
code, how you can run it without first producing a derivative work. Granting a person the right to *use* source code means granting them the right to produce derivative works of that source code because that is how source code is used.

How can I use the Linux kernel, say on an FTP site or a CD that I
ordered, without copying it onto my computer? How can I compile it without copying it into memory?

You cannot use a C source file without modifying it. In order to
compile it, you must pass it through a preprocessor. This produces a modified copy of the original.

Source code is like a recipe. The right to use it implicitly
includes the right to follow the recipe and eat the results because that is how one uses a recipe. Along the way, one makes copies and derived works. It's simply unavoidable.

This doesn't mean that all copying and modifying is automatically
allowed for all cases where you have the right to use source code. However, it does mean that absent a restrictive agreement to the contrary that limits your *usage* rights, you can create derived works and you can make copies because that's how you use source code.

You can't give the derived works or copies to those who have no
right to the original work (because you can't give others rights to code that is not yours). However, no special right to the original work is needed to distribute derived works among those who already have the right to use and possess the original work and make the derived works.

In the case of the GPL, you even have the additional right to
distribute the original work. I would argue that you can distribute derived works even without the right to distribute the original provided all recipients have the right to use and possess the original. But this argument isn't even needed.

Quoted 6 lines

Note again that two of these rights (distribute the original, distribute
the modifications) are *NOT* ones you inherently have - you are getting them
*WITH RESTRICTIONS* on what you can and can't do (see clause 2 again).

No, that is not true. The GPL says:

"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."

There are no significant restrictions placed upon the distribution
of the original work. Even if there were, it's not clear that it would be enforceable considering that you are only distributing the work to people who already have the right to possess and use it. There are only a small number of cases on this point and they're split both ways. In all the cases where the copyright holder prevailed (such as the lawsuit against mp3.com), it was based on a showing that such distribution foreclosed on their sales, an argument that could not be made in the case of the GPL. So this could be argued either way even without clause 1.

As for distributing modifications, as I have already argued at least
four times now, this is not a special right to the *original* work so there is no need to invoke clause 2 to get that right. It is subsumed under the right to make derivative works and the right to distribute the original work. It is the simple sum of those two rights (except the additional rights you need to the modifications themselves).

To make and distribute a derived work, you need certain rights to
the original work. Specifically, you need the right to make the derived work in the first place and you need the right to distribute the original work. I am saying that you have both of these rights without clause 2. It is even arguable that you have them without clause 1.

This will be the last time I repeat myself. I promise. I will not
respond to this thread unless something genuinely new comes up.

DS

#3 lore raw

David,

Quoted 6 lines
Quoted 6 lines

To make and distribute a derived work, you need certain rights
to the original work. Specifically, you need the right to make the derived work in the first place and you need the right to distribute the original work. I am saying that you have both of these rights without clause 2. It is even arguable that you have them without clause 1.

What about clause 5:

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

This clearly states that you have no rights to distribute anything unless you accept all the terms of the GPL.

Signature · 1 line
Dan
#4 lore raw
Quoted 20 lines · Daniel Forrest

David,

Quoted 6 lines
Quoted 6 lines

To make and distribute a derived work, you need certain rights to the original work. Specifically, you need the right to make the derived work in the first place and you need the right to distribute the original work. I am saying that you have both of these rights without clause 2. It is even arguable that you have them without clause 1.

What about clause 5:

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

Quoted 2 lines

This clearly states that you have no rights to distribute anything unless you accept all the terms of the GPL.

I'll repeat section 1 of the GPL again:

"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."

This clearly says that you can distribute the program without
accepting the section 2 restrictions.

I previously addressed "modification". This is not a precise legal
term, and I presume it was intended to mean the production of derived works. The GPL says:

"Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."

This grants the right to use the covered work. As I've argued, using
source code includes the right to produce derived works because there is no other way to use source code. (Well, I suppose you could look at it or paper your wall with it. But its intended purpose is to be a recipe for the production of derived works.) It is quite clear that the GPL was never intended to restrict anyone's ability to use the covered works and RMS has clearly argued that the GPL is not a shrink-wrap agreement, that is, one you must agree to in order to use a copyrighted work.

Section 5 does say, "However, nothing else grants you permission to
modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License." I agree with this statement. However, my argument is that you can distribute derived works under the rights given only in the two sections I cite above, neither of which alone or in combination invokes the section 2 (source disclosure) requirements.
-

To preserve the linux-kernel list from having to see more of this, I
would ask anyone interested in responding to please send any further comments directly to me. I'll respond to them to you privately, and then if you still feel they must go to the linux-kernel list, you can send them with my responses in one shot. This will spare the kernel list from having to see two or three messages where zero or one would suffice.

I'm not trying to silence anyone. You can still send your message to
the kernel list. I'm just saying once you see my response, you may not wish to send it to the list or you may wish to send it with a response to my response. I feel obligated to respond to most public comments that challenge my view for fear that silence will be equated with an inability to rebut.

Signature · 2 lines
David Schwartz
<[email protected]>