Skip to contentSkip to conversation

Dual-Licensing Linux Kernel with GPL V2 and GPL V3

DISCUSSION Al Boldi 7 participants 21 messages Jun 17, 2007 – Jun 27, 2007

lore
Share & tools
lore

Al Boldi

author
#0 lore raw
Quoted 10 lines · Alexandre Oliva
Quoted 4 lines · Gabor Czigola

I wonder why the linux kernel development community couldn't propose an own GPL draft (say v2.2) that is "as free as v2" and that includes some ideas (from v3) that are considered as good (free, innovative, in the spirit of whatever etc.) by the majority of the kernel developers.

For one, because the text of the GPL is copyrighted by the FSF, and licensed without permission for modification. And that's as it should be, you don't want others to modify the terms of the license you chose for your code, do you?

Wow!

Under what circumstances would it be possible to receive permission for modification?

Thanks for being GPL!

--
Al

#1 lore raw
Quoted 2 lines · Al Boldi

Under what circumstances would it be possible to receive permission for modification?

You have to ask the copyright holder.

Affero did just that, and so the Affero GPL was born.

Just don't assume the FSF will grant such permissions lightly.

Signature · 4 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
author
#2 lore raw
Quoted 9 lines · Alexandre Oliva
Quoted 2 lines · Al Boldi

Under what circumstances would it be possible to receive permission for modification?

You have to ask the copyright holder.

Affero did just that, and so the Affero GPL was born.

Just don't assume the FSF will grant such permissions lightly.

But wouldn't this be against the spirit of the GPL?

Thanks!

--
Al

#3 lore raw
Quoted 5 lines · Al Boldi
Quoted 4 lines · Alexandre Oliva
Quoted 2 lines · Al Boldi

Under what circumstances would it be possible to receive permission for modification?

Quoted 7 lines
Quoted 5 lines

You have to ask the copyright holder.

Affero did just that, and so the Affero GPL was born.

Just don't assume the FSF will grant such permissions lightly.

But wouldn't this be against the spirit of the GPL?

I'm not sure what you mean.

The moment you modified it, it would no longer be the GPL and, as long as it's not the FSF publishing it as later version of the GPL, it wouldn't be bound by the public commitment that all versions of the GPL would have the same spirit, and as long as it's not the FSF publishing it, it wouldn't be bound by the FSF's public mission and the copyright assignments it received.

Signature · 4 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
#4 lore raw
In reply to Al Boldi
Quoted 5 lines · Al Boldi
Quoted 4 lines · Alexandre Oliva
Quoted 2 lines · Al Boldi

Under what circumstances would it be possible to receive permission for modification?

Quoted 7 lines
Quoted 5 lines

You have to ask the copyright holder.

Affero did just that, and so the Affero GPL was born.

Just don't assume the FSF will grant such permissions lightly.

But wouldn't this be against the spirit of the GPL?

This may be helpful to you :

http://www.gnu.org/licenses/gpl-faq.html#ModifyGPL

It describes the scenario and how to go about doing it.

Best,
--Tim

#5 lore raw
In reply to Al Boldi
Quoted 12 lines · Al Boldi

Wow!

Under what circumstances would it be possible to receive permission for modification?

Thanks for being GPL!

--
Al

If the GPL2 were itself modifiable, there would be so many GPL licenses that the term "Relased under the GPL 2" would only indicate you chose one of a million licenses or wrote your own.

That may not be a bad thing, not for me to debate. But I think that's why the FSF imposes the restriction. I don't feel that is unreasonable, but you might, and its your right to do so and be vocal about it.

You could, of course take what language that you agree with, re-write it and make it your own and add a clause that allows people to modify the license provided that they do not call it the "XYZ" license any longer.

But you wouldn't be making a license - you'd be making the raw material for people to make their own license.

I don't think that's what the FSF wanted to accomplish. Again, just my opinion. I didn't make the GPL so there's no way I could know.

Best,
--Tim

author
#6 lore raw
In reply to Al Boldi
Quoted 17 lines · Alexandre Oliva

Consider this scenario: vendor tivoizes Linux in the device, and includes the corresponding sources only in a partition that is theoretically accessible using the shipped kernel, but that nothing in the software available in the machine will let you get to. Further, sources (like everything else on disk) are encrypted, and you can only decrypt it with hardware crypto that is disabled if the boot loader doesn't find a correct signature for the boot partition, or maybe the signature is irrelevant, given that everything on disk is encrypted in such a way that, if you don't have the keys, you can't update the kernel properly anyway. The vendor refuses to give customers other copies of the sources. To add insult to the injury, the vendor configures the computer to set up the encrypted disk partition containing the sources as a swap device, such that the shared-secret key used to access that entire filesystem is overwritten upon the first boot, rendering the entire previous contents of the partition holding the source code into an incomprehensible stream of bits.

Quoted 1 line

Does anyone think this is permitted by the letter of GPLv2?

Yes.

Quoted 1 line

Is it in the spirit of GPLv2?

No, but that's besides the point.

You can only hold people responsible for the letter, lest there be chaos.

If there is a specific usage spirit you want to protect, then you must formulate it in letter.

Quoted 2 lines

How are the sources passed on in this way going to benefit the user or the community?

They still have to provide the source by other GPL means of their choosing.

Quoted 1 line

Is this still desirable by the Linux developers?

Looks undesirable to me, but still valid.

Thanks!

--
Al

#7 lore raw
Quoted 3 lines · Al Boldi
Quoted 1 line

Is it in the spirit of GPLv2?

No, but that's besides the point.

Thanks for informing me about the point *I*'m trying to make ;-)

Quoted 1 line

You can only hold people responsible for the letter, lest there be chaos.

That's not *quite* how it works, but that's a general idea, yes.

Quoted 4 lines
Quoted 2 lines

How are the sources passed on in this way going to benefit the user or the community?

They still have to provide the source by other GPL means of their choosing.

This is contradictory. You said the scenario I described was permitted, and the scenario included the vendor's refusal to give customers other copies of the sources.

Which is it?

Signature · 4 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
author
#8 lore raw
Quoted 15 lines · Alexandre Oliva
Quoted 3 lines · Al Boldi
Quoted 1 line

Is it in the spirit of GPLv2?

No, but that's besides the point.

Thanks for informing me about the point *I*'m trying to make ;-)

Quoted 2 lines

You can only hold people responsible for the letter, lest there be chaos.

That's not *quite* how it works, but that's a general idea, yes.

Quoted 3 lines
Quoted 2 lines

How are the sources passed on in this way going to benefit the user or the community?

Quoted 8 lines
Quoted 2 lines

They still have to provide the source by other GPL means of their choosing.

This is contradictory. You said the scenario I described was permitted, and the scenario included the vendor's refusal to give customers other copies of the sources.

Which is it?

I read your scenario of the vendor not giving you the source to mean: not directly; i.e. they could give you a third-party download link.

Thanks!

--
Al

#9 lore raw
Quoted 2 lines · Al Boldi

I read your scenario of the vendor not giving you the source to mean: not directly; i.e. they could give you a third-party download link.

This has never been enough to comply with GPLv2.

FWIW, it is one of the improvements in GPLv3.

Signature · 4 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
#10 lore raw
Quoted 8 lines · Alexandre Oliva
Quoted 2 lines · Al Boldi

I read your scenario of the vendor not giving you the source to mean: not directly; i.e. they could give you a third-party download link.

This has never been enough to comply with GPLv2.

FWIW, it is one of the improvements in GPLv3.

either it's an improvement in the GPLv3 or it's a violation of GPLv2.

you can't say that the GPLv2 prohibits it _and_ it's an improvement in the GPLv3.

unless you are saying that the GPLv3 is saying that a third party link now _is_ sufficiant. this seems to be counter to what the FSF is claiming (with good reasoning. after all, you don't control the third party site, so it could change or go away and now the people who got the binaries from you can't get the sources)

David Lang

#11 lore raw
Quoted 2 lines · On Jun 26, 2007, [email protected] wrote:

unless you are saying that the GPLv3 is saying that a third party link now _is_ sufficiant.

Yup. The improvement in GPLv3 is to relax the requirement of providing source code in physical medium if you choose to not distribute it along with the binaries. It's recognizing that internet access is no longer a barrier that could stop someone from obtaining the sources they're entitled to. Even someone who doesn't have regular or fast internet access can hire a third party who does to perform the download and record it.

I.e., with GPLv3, you *can* point at the sources you used, even in a site that you don't control.

However, if the site takes the sources out, you're still responsible for providing sources to those who received the sources from you from that point on. Or something like that, IANAL ;-)

Signature · 4 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
#12 lore raw
Quoted 13 lines · Alexandre Oliva
Quoted 2 lines · On Jun 26, 2007, [email protected] wrote:

unless you are saying that the GPLv3 is saying that a third party link now _is_ sufficiant.

Yup. The improvement in GPLv3 is to relax the requirement of providing source code in physical medium if you choose to not distribute it along with the binaries. It's recognizing that internet access is no longer a barrier that could stop someone from obtaining the sources they're entitled to. Even someone who doesn't have regular or fast internet access can hire a third party who does to perform the download and record it.

Quoted 6 lines

I.e., with GPLv3, you *can* point at the sources you used, even in a site that you don't control.

However, if the site takes the sources out, you're still responsible for providing sources to those who received the sources from you from that point on. Or something like that, IANAL ;-)

this sounds like a step backwards, you may not have the sources at that point if you were relying on the other site to host them.

and by the way, internet access never was a barrier that could stop someone from obtaining them, the only issue was you hosting the source vs someone else hosting the source.

David Lang

#13 lore raw
Quoted 2 lines · [email protected] wrote:

this sounds like a step backwards, you may not have the sources at that point if you were relying on the other site to host them.

You would then be violating the GPL, under any version. The GPL is quite clear that being unable to comply with it means you do not get the benefits it offers rather than excusing you from meeting its requirements.

You *MUST* have the source code in order to distribute it on request. You cannot ship GPL'd works without offering source code just by arranging it (deliberately or accidentally) so that you don't have the source code.

Quoted 3 lines

and by the way, internet access never was a barrier that could stop someone from obtaining them, the only issue was you hosting the source vs someone else hosting the source.

The GPLv2 never specified one way or the other.

If you do allow someone else to host them, you are responsible for making sure they remain available for at least three years from the last time you used them as an offer. Should they stop distributing, you would be violating the GPL. Nothing in the GPL says you can't rely on third parties for your GPL compliance. Of course, this could be a very risky thing to do. However, there is no GPL violation so long as they do in fact remain operational for three years from the last time you distributed.

In fact, a third party is no more risky than any other setup. Any company can go out of business within the three-year period after distribution. There are many real-world cases where a third party having the source is actually more likely to result in actual GPL compliance than the distributor. (Consider a fly-by-night company selling Fedora binary distributions burnt to CDROM on the stop for $1 on a street corner.)

One way to avoid this problem is to maintain your own web page that links to the third party's download. You would have to host the sources yourself if you couldn't make other arrangements at any point during the three year period.

This is no different from any other case where the offer is not honored. If the offer is not honored in a case where the GPL requires that it be, the GPL is being violated.

DS

#14 lore raw
In reply to [email protected]
Quoted 6 lines · On Jun 26, 2007, [email protected] wrote:
Quoted 3 lines

However, if the site takes the sources out, you're still responsible for providing sources to those who received the sources from you from that point on. Or something like that, IANAL ;-)

this sounds like a step backwards, you may not have the sources at that point if you were relying on the other site to host them.

You should have them. This provision is not an excuse from your obligations, it's just a pragmatic concession.

Quoted 2 lines

and by the way, internet access never was a barrier that could stop someone from obtaining them

Back when GPLv2 was written, it really was.

Signature · 4 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
#15 lore raw
In reply to Alexandre Oliva

Alexandre Oliva:

Quoted 7 lines · Al Boldi
Quoted 4 lines

I read your scenario of the vendor not giving you the source to
mean: not
directly; i.e. they could give you a third-party download link.

This has never been enough to comply with GPLv2.

A lot of people seem to say this, but I don't think it's true. Section 3b says:

Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

A web page with a download URL is just such an offer. The Internet is a medium customarily used for software interchange. I do not see why the following statement doesn't meet the requirements above:

"The source code for this product is available under the terms of the GPL from the following web page http://www.mycompanyname.com/gpl"

This assumes that no special steps are needed to obtain the software from that web page.

DS

#16 lore raw
Quoted 5 lines

"The source code for this product is available under the terms of the GPL from the following web page http://www.mycompanyname.com/gpl"

This assumes that no special steps are needed to obtain the software from that web page.

But thats YOURcompanyname.com. Not a third party. If you gave as a link somebodyelsescompany.com/gpl then somebodyelse could get rid of the link, and your offer wouldn't be valid for "at least three years"

T

Signature · 3 lines
|_|0|_|
|_|_|0|
|0|0|0|
#17 lore raw
Quoted 6 lines

But thats YOURcompanyname.com. Not a third party. If you gave as a link somebodyelsescompany.com/gpl then somebodyelse could get rid of the link, and your offer wouldn't be valid for "at least three years"

T

You mean it might not be valid for at least three years. It also might be. You also might go out of business in less than three years.

You're not violating the GPL simply because you might not be able to honor your offer in less than three years. You're violating the GPL when you in fact fail to honor it.

I do agree that providing a link to a third party URL is risky, but I do not agree that it doesn't comply with the GPL.

DS

#18 lore raw
In reply to David Schwartz
Quoted 11 lines · David Schwartz

Alexandre Oliva:

Quoted 7 lines · Al Boldi
Quoted 4 lines

I read your scenario of the vendor not giving you the source to
mean: not directly; i.e. they could give you a third-party download link.

This has never been enough to comply with GPLv2.

A lot of people seem to say this, but I don't think it's true.

http://www.gnu.org/licenses/gpl-faq.html#TOCUnchangedJustBinary and the 3 questions after that should be enlightening as to why people say this ;-)

cost of physically performing source distribution, a complete
^^^^^^^^^^

Why would 'physically' be there if it didn't mean anything? When interpreting legal texts, that's one sort of question you should ask yourself.

Signature · 4 lines
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
#19 lore raw
Quoted 11 lines · David Schwartz
Quoted 8 lines

Alexandre Oliva:

Quoted 5 lines · Al Boldi
Quoted 4 lines

I read your scenario of the vendor not giving you the source to
mean: not directly; i.e. they could give you a third-party download link.

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

This has never been enough to comply with GPLv2.

A lot of people seem to say this, but I don't think it's true.

http://www.gnu.org/licenses/gpl-faq.html#TOCUnchangedJustBinary

This consists of entirely unsupported statements.

Quoted 8 lines

and
the 3 questions after that should be enlightening as to why people say this ;-)

cost of physically performing source distribution, a complete
^^^^^^^^^^

Why would 'physically' be there if it didn't mean anything?

It does. It means you can't charge for adminsitrative or other costs associated with performing the source distribution. It's necessary because otherwise someone could claim that it costs them $10,000 to give you the source code because they need to purchase a license from someone else. This limits what you can charge for but does not specify what you have to do.

Quoted 3 lines

When
interpreting legal texts, that's one sort of question you should ask yourself.

It's obvious why it's there. If you're going to charge for the distribution, the charge must be nominal and justified by actual distribution cost.

Note that even a distribution over the Internet must be physically performed in this sense (actual physical activity by a human being is required to perform this type of distribution, both in setup and in maintenance). I would argue that the GPL allows you to charge these costs if you really wanted to, though it's hard to imagine why anyone would bother.

DS

author
#20 lore raw
In reply to Alexandre Oliva
Quoted 5 lines · Alexandre Oliva
Quoted 2 lines · Al Boldi

I read your scenario of the vendor not giving you the source to mean:
not directly; i.e. they could give you a third-party download link.

This has never been enough to comply with GPLv2.

Section 3a of the GPLv2 mentions "a medium customarily used for software interchange". I would think the Internet is a medium customarily used for software interchange, is it not?

Thanks!

--
Al