Changeset - ebefdf8de8b8
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-03-20 12:02:05
bkuhn@ebb.org
Move this text out of the way from discussion of section 2.
1 file changed with 6 insertions and 6 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -2498,30 +2498,24 @@ library exception (both the GPLv2 and GPLv3 versions of it), if included
 
herein,  could easily increase this section of the tutorial to a length
 
greater than all the others.
 

	
 
Like any exception to the copyleft requirements of GPL, would-be GPL
 
violators frequently look to the system library exception as a potential
 
software freedom circumvention technique.  When considering whether or not a
 
library qualifies for the system library exception, here is a pragmatic
 
thesis to consider, based on the combined decades of experience in GPL
 
interpretation of this tutorial's authors: the harder and more strained the
 
reader must study and read the system library exception, the more likely it
 
is that the library in question does not qualify for it.
 

	
 
% FIXME: These don't belong here
 

	
 
It is important to note that section 11, paragraph 3 refers to a work that is
 
conveyed, and section 10, paragraph 2 refers to a kind of automatic
 
counterpart to conveying achieved as the result of a transaction. 
 

	
 
\section{GPLv3~\S2: Basic Permissions}
 

	
 
% FIXME: phrase ``unmodified Program'' appears due to User Products exception
 

	
 
We have included the first sentence of section 2 to further internationalize
 
the GPL. Under the copyright laws of some countries, it may be necessary for
 
a copyright license to include an explicit provision setting forth the
 
duration of the rights being granted. In other countries, including the
 
United States, such a provision is unnecessary but permissible.
 

	
 
The first paragraph of section 2 also acknowledges that licensees under the
 
GPL enjoy rights of copyright fair use, or the equivalent under applicable
...
 
@@ -3536,24 +3530,30 @@ and apply in all jurisdictions.
 
% FIXME: needs some work here
 

	
 
Section 9 means what it says: mere receipt or execution of code neither
 
requires nor signifies contractual acceptance under the GPL.  Speaking more
 
broadly, we have intentionally structured our license as a unilateral grant
 
of copyright permissions, the basic operation of which exists outside of any
 
law of contract.  Whether and when a contractual relationship is formed
 
between licensor and licensee under local law do not necessarily matter to
 
the working of the license.
 

	
 
\section{GPLv3~\S10: Explicit Downstream License}
 

	
 
% FIXME: These don't belong here, but it's closer to where it ought to be now.
 

	
 
It is important to note that section 11, paragraph 3 refers to a work that is
 
conveyed, and section 10, paragraph 2 refers to a kind of automatic
 
counterpart to conveying achieved as the result of a transaction. 
 

	
 
% FIXME: needs filled out and more here.
 

	
 
Draft1 removed the words ``at no charge'' from what is now subsection 5b, the
 
core copyleft provision, for reasons related to our current changes to the
 
second paragraph of section 4: it had contributed to a misconception that the
 
GPL did not permit charging for distribution of copies.  The purpose of the
 
``at no charge'' wording was to prevent attempts to collect royalties from
 
third parties.  The removal of these words created the danger that the
 
imposition of licensing fees would no longer be seen as a license
 
violation.
 

	
 
We therefore have added a new explicit prohibition on imposition of licensing
0 comments (0 inline, 0 general)