Title: Non-attributive "the GPLvn" unidiomatic
Correct inconsistency in use/nonuse of definite article before non-attributive uses of *GPLvn by opting for typical present-day FSF usage (with no article). I believe the FSF tends to use "GPLvn" (rather than "the GPLvn") when the license is referred to by abbreviation and is not prefixed by "GNU". This can be confirmed by analysis of usage on the fsf.org website.
Under review
1 reviewer
git pull https://k.copyleft.org/guide-fontana gplvn-idiomatic
2014-12-07 04:21:33
Richard Fontana (fontana)
fontana@sharpeleven.org
Git pull requests don't support updates yet.
Pull Request Reviewers
  • Bradley Kuhn (bkuhn)
2 comments (0 inline, 2 general)
Showing 1 commit
1 2015-04-03 00:44:59
fontana
dc84691b9398 gplvn-idiomatic
Correct inconsistency in use/nonuse of definite article before non-attributive uses of *GPLvn by opting for typical present-day FSF usage (with no article). I believe the FSF tends to use "GPLvn" (rather than "the GPLvn") when the license is referred to by abbreviation and is not prefixed by "GNU". This can be confirmed by analysis of usage on the fsf.org website.
Common ancestor: 26def8538a10
2 files changed with 33 insertions and 33 deletions:
↑ Collapse Diff ↑
comprehensive-gpl-guide.tex | master gplvn-idiomatic
...
 
@@ -148,13 +148,13 @@ repository at \url{https://gitorious.org/copyleft-org/tutorial/}.
148 148
 

	
149 149
 
\chapter{Preface}
150 150
 

	
151 151
 
This tutorial is the culmination of nearly a decade of studying and writing
152 152
 
about software freedom licensing and the GPL\@.  Each part of this tutorial
153 153
 
is a course unto itself, educating the reader on a myriad of topics from the
154
 
deep details of the GPLv2 and GPLv3, common business models in the copyleft
154
 
deep details of GPLv2 and GPLv3, common business models in the copyleft
155 155
 
licensing area (both the friendly and unfriendly kind), best practices for
156 156
 
compliance with the GPL, for engineers, managers, and lawyers, as well as
157 157
 
real-world case studies of GPL enforcement matters.
158 158
 

	
159 159
 
It is unlikely that all the information herein is necessary to learn all at
160 160
 
once, and therefore this tutorial likely serves best as a reference book.
gpl-lgpl.tex | master gplvn-idiomatic
...
 
@@ -52,26 +52,26 @@ to have learned the following:
52 52
 
\begin{itemize}
53 53
 

	
54 54
 
  \item The freedom-defending purpose of various terms in the GNU GPLv2 and GPLv3.
55 55
 

	
56 56
 
  \item The differences between GPLv2 and GPLv3.
57 57
 

	
58
 
  \item The redistribution options under the GPLv2 and GPLv3.
58
 
  \item The redistribution options under GPLv2 and GPLv3.
59 59
 

	
60 60
 
  \item The obligations when modifying GPLv2'd or GPLv3'd software.
61 61
 

	
62 62
 
  \item How to build a plan for proper and successful compliance with the GPL.
63 63
 

	
64 64
 
  \item The business advantages that the GPL provides.
65 65
 

	
66 66
 
  \item The most common business models used in conjunction with the GPL.
67 67
 

	
68 68
 
  \item How existing GPL'd software can be used in existing enterprises.
69 69
 

	
70 70
 
  \item The basics of LGPLv2.1 and LGPLv3, and how they
71
 
    differ from the GPLv2 and GPLv3, respectively.
71
 
    differ from GPLv2 and GPLv3, respectively.
72 72
 

	
73 73
 
  \item The basics to begin understanding the complexities regarding
74 74
 
    derivative and combined works of software.
75 75
 
\end{itemize}
76 76
 

	
77 77
 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
...
 
@@ -822,13 +822,13 @@ issues discussed earlier in \S~\ref{software-and-non-copyright}.
822 822
 
\section{The GNU General Public License, Version 1}
823 823
 
\label{GPLv1}
824 824
 

	
825 825
 
In January 1989, the FSF announced that the GPL had been converted into a
826 826
 
``subroutine'' that could be reused not just for all FSF-copyrighted
827 827
 
programs, but also by anyone else.  As the FSF claimed in its announcement of
828
 
the GPLv1:\footnote{The announcement of GPLv1 was published in the
828
 
GPLv1:\footnote{The announcement of GPLv1 was published in the
829 829
 
  \href{http://www.gnu.org/bulletins/bull6.html\#SEC8}{GNU's Bulletin, vol 1,
830 830
 
    number 6 dated January 1989}.  (Thanks very much to Andy Tai for his
831 831
 
  \href{http://www.free-soft.org/gpl_history/}{consolidation of research on
832 832
 
    the history of the pre-v1 GPL's}.)}
833 833
 
\begin{quotation}
834 834
 
To make it easier to copyleft programs, we have been improving on the
...
 
@@ -1061,14 +1061,14 @@ many users.  An example of unregulated use is reading a printout of the
1061 1061
 
program's source code like an instruction book for the purpose of learning
1062 1062
 
how to be a better programmer.  The right to read something that you have
1063 1063
 
access to is and should remain unregulated and unrestricted.
1064 1064
 

	
1065 1065
 
\medskip
1066 1066
 

	
1067
 
Thus, the GPLv2 protects users' fair and unregulated use rights precisely by
1068
 
not attempting to cover them.  Furthermore, the GPLv2 ensures the freedom
1067
 
Thus, GPLv2 protects users' fair and unregulated use rights precisely by
1068
 
not attempting to cover them.  Furthermore, GPLv2 ensures the freedom
1069 1069
 
to run specifically by stating the following:
1070 1070
 
\begin{quote}
1071 1071
 
''The act of running the Program is not restricted.''
1072 1072
 
\end{quote}
1073 1073
 
Thus, users are explicitly given the freedom to run by GPLv2~\S0.
1074 1074
 

	
...
 
@@ -1508,13 +1508,13 @@ see\S~\label{GPLv2s6} in this tutorial).  Determining whether software was
1508 1508
 
modified is a substantially easier analysis than the derivative work
1509 1509
 
discussions and considerations in this chapter.
1510 1510
 

	
1511 1511
 
The question of derivative works, when and how they are made, is undoubtedly
1512 1512
 
an essential discussion in the interpretation and consideration of copyleft.
1513 1513
 
That is why this chapter was included in this tutorial.  However, as we
1514
 
return from this digression and resume discussion of the detailed text of the
1514
 
return from this digression and resume discussion of the detailed text of
1515 1515
 
GPLv2, we must gain a sense of perspective: most GPL questions center around
1516 1516
 
questions of modification and distribution, not preparation of derivative
1517 1517
 
works.  Derivative work preparation is ultimately a small subset of the types
1518 1518
 
of modified versions of the software a developer might create, thus, while an
1519 1519
 
excessive focus on derivative works indulges us in the more exciting areas of
1520 1520
 
copyleft, we must keep a sense of perspective regarding their relative
...
 
@@ -1741,13 +1741,13 @@ of the software.  Distribution to all third parties is not mandated here,
1741 1741
 
but GPLv2~\S2(b) does require re-distributors to license the whole work in
1742 1742
 
a way that extends to all third parties who may ultimately receive a
1743 1743
 
copy of the software.
1744 1744
 

	
1745 1745
 
In summary, GPLv2\ 2(b) says what terms under which the third parties must
1746 1746
 
receive this no-charge license.  Namely, they receive it ``under the terms
1747
 
of this License'', the GPLv2.  When an entity \emph{chooses} to redistribute
1747
 
of this License'', GPLv2.  When an entity \emph{chooses} to redistribute
1748 1748
 
a work based on GPL'd software, the license of that whole 
1749 1749
 
work must be GPL and only GPL\@.  In this manner, GPLv2~\S2(b) dovetails nicely
1750 1750
 
with GPLv2~\S6 (as discussed in Section~\ref{GPLv2s6} of this tutorial).
1751 1751
 

	
1752 1752
 
\medskip
1753 1753
 

	
...
 
@@ -2047,16 +2047,16 @@ Hewlett-Packard Co. v. Repeat-O-Type Stencil Mfg. Corp., Inc., 123 F.3d
2047 2047
 

	
2048 2048
 
Of course, Free Software is licensed, not sold, and there are indeed
2049 2049
 
restrictions placed on the licensee, but those differences are not likely
2050 2050
 
to prevent the application of the implied license doctrine to Free
2051 2051
 
Software, because software licensed under the GPL grants the licensee the
2052 2052
 
right to make, use, and sell the software, each of which are exclusive
2053
 
rights of a patent holder. Therefore, although the GPLv2 does not expressly
2053
 
rights of a patent holder. Therefore, although GPLv2 does not expressly
2054 2054
 
grant the licensee the right to do those things under any patents the
2055 2055
 
licensor may have that cover the software or its reasonably contemplated
2056
 
uses, by licensing the software under the GPLv2, the distributor impliedly
2056
 
uses, by licensing the software under GPLv2, the distributor impliedly
2057 2057
 
licenses those patents to the GPLv2 licensee with respect to the GPLv2'd
2058 2058
 
software.
2059 2059
 

	
2060 2060
 
An interesting issue regarding this implied patent license of GPLv2'd
2061 2061
 
software is what would be considered ``uses of the [software] to which
2062 2062
 
the parties might reasonably contemplate the product will be put.'' A
...
 
@@ -2080,75 +2080,75 @@ repair the article to enable it to function properly, Bottom Line Mgmt.,
2080 2080
 
Inc. v. Pan Man, Inc., 228 F.3d 1352 (Fed. Cir. 2000). Additionally, the
2081 2081
 
Federal Circuit extended that rule to include any future recipients of the
2082 2082
 
patented article, not just the direct recipient from the distributor.
2083 2083
 
This theory comports well with the idea of Free Software, whereby software
2084 2084
 
is distributed among many entities within the community for the purpose
2085 2085
 
of constant evolution and improvement. In this way, the law of implied
2086
 
patent license used by the GPLv2 ensures that the community mutually
2086
 
patent license used by GPLv2 ensures that the community mutually
2087 2087
 
benefits from the licensing of patents to any single community member.
2088 2088
 

	
2089 2089
 
Note that simply because GPLv2'd software has an implied patent license does
2090 2090
 
not mean that any patents held by a distributor of GPLv2'd code become
2091 2091
 
worthless. To the contrary, the patents are still valid and enforceable
2092 2092
 
against either:
2093 2093
 

	
2094 2094
 
\begin{enumerate}
2095 2095
 
 \renewcommand{\theenumi}{\alph{enumi}}
2096 2096
 
 \renewcommand{\labelenumi}{\textup{(\theenumi)}}
2097 2097
 

	
2098
 
\item any software other than that licensed under the GPLv2 by the patent
2098
 
\item any software other than that licensed under GPLv2 by the patent
2099 2099
 
  holder, and
2100 2100
 

	
2101
 
\item any party that does not comply with the GPLv2
2101
 
\item any party that does not comply with GPLv2
2102 2102
 
with respect to the licensed software.
2103 2103
 
\end{enumerate}
2104 2104
 

	
2105 2105
 
\newcommand{\compB}{$\mathcal{B}$}
2106 2106
 
\newcommand{\compA}{$\mathcal{A}$}
2107 2107
 

	
2108 2108
 
For example, if Company \compA{} has a patent on advanced Web browsing, but
2109
 
also licenses a Web browsing program under the GPLv2, then it
2109
 
also licenses a Web browsing program under GPLv2, then it
2110 2110
 
cannot assert the patent against any party based on that party's use of 
2111 2111
 
Company \compA{}'s GPL'd Web browsing software program, or on that party's
2112 2112
 
creation and use of modified versions of that GPL'd program.  However, if a
2113 2113
 
party uses that program without
2114
 
complying with the GPLv2, then Company \compA{} can assert both copyright
2114
 
complying with GPLv2, then Company \compA{} can assert both copyright
2115 2115
 
infringement claims against the non-GPLv2-compliant party and
2116 2116
 
infringement of the patent, because the implied patent license only
2117
 
extends to use of the software in accordance with the GPLv2. Further, if
2117
 
extends to use of the software in accordance with GPLv2. Further, if
2118 2118
 
Company \compB{} distributes a competitive advanced Web browsing program 
2119 2119
 
that is not a modified version of Company \compA{}'s GPL'd Web browsing software
2120 2120
 
program, Company \compA{} is free to assert its patent against any user or
2121 2121
 
distributor of that product. It is irrelevant whether Company \compB's
2122
 
program is also distributed under the GPLv2, as Company \compB{} can not grant
2122
 
program is also distributed under GPLv2, as Company \compB{} can not grant
2123 2123
 
implied licenses to Company \compA's patent.
2124 2124
 

	
2125 2125
 
This result also reassures companies that they need not fear losing their
2126 2126
 
proprietary value in patents to competitors through the GPLv2 implied patent
2127
 
license, as only those competitors who adopt and comply with the GPLv2's
2127
 
license, as only those competitors who adopt and comply with GPLv2's
2128 2128
 
terms can benefit from the implied patent license. To continue the
2129 2129
 
example above, Company \compB{} does not receive a free ride on Company
2130 2130
 
\compA's patent, as Company \compB{} has not licensed-in and then
2131
 
redistributed Company A's advanced Web browser under the GPLv2. If Company
2131
 
redistributed Company A's advanced Web browser under GPLv2. If Company
2132 2132
 
\compB{} does do that, however, Company \compA{} still has not lost
2133 2133
 
competitive advantage against Company \compB{}, as Company \compB{} must then,
2134 2134
 
when it re-distributes Company \compA's program, grant an implied license
2135 2135
 
to any of its patents that cover the program. Further, if Company \compB{}
2136 2136
 
relicenses an improved version of Company A's program, it must do so under
2137
 
the GPLv2, meaning that any patents it holds that cover the improved version
2137
 
GPLv2, meaning that any patents it holds that cover the improved version
2138 2138
 
are impliedly licensed to any licensee. As such, the only way Company
2139 2139
 
\compB{} can benefit from Company \compA's implied patent license, is if it,
2140 2140
 
itself, distributes Company \compA's software program and grants an
2141 2141
 
implied patent license to any of its patents that cover that program.
2142 2142
 

	
2143 2143
 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2144 2144
 
\chapter{Defending Freedom on Many Fronts}
2145 2145
 

	
2146 2146
 
Chapters~\ref{run-and-verbatim} and~\ref{source-and-binary} presented the
2147 2147
 
core freedom-defending provisions of GPLv2\@, which are in GPLv2~\S\S0--3.
2148
 
GPLv2\S\S~4--7 of the GPLv2 are designed to ensure that GPLv2~\S\S0--3 are
2148
 
GPLv2\S\S~4--7 of GPLv2 are designed to ensure that GPLv2~\S\S0--3 are
2149 2149
 
not infringed, are enforceable, are kept to the confines of copyright law but
2150 2150
 
also not trumped by other copyright agreements or components of other
2151 2151
 
entirely separate legal systems.  In short, while GPLv2~\S\S0--3 are the parts
2152 2152
 
of the license that defend the freedoms of users and programmers,
2153 2153
 
GPLv2~\S\S4--7 are the parts of the license that keep the playing field clear
2154 2154
 
so that \S\S~0--3 can do their jobs.
...
 
@@ -2256,13 +2256,13 @@ and it is made so formally by GPLv2~\S6.
2256 2256
 

	
2257 2257
 
The first sentence in GPLv2~\S6 ensures that as software propagates down the
2258 2258
 
distribution chain, that each licensor can pass along the license to each
2259 2259
 
new licensee.  Under GPLv2~\S6, the act of distributing automatically grants a
2260 2260
 
license from the original licensor to the next recipient.  This creates a
2261 2261
 
chain of grants that ensure that everyone in the distribution has rights
2262
 
under the GPLv2\@.  In a mathematical sense, this bounds the bottom ---
2262
 
under GPLv2\@.  In a mathematical sense, this bounds the bottom ---
2263 2263
 
making sure that future licensees get no fewer rights than the licensee before.
2264 2264
 

	
2265 2265
 
The second sentence of GPLv2~\S6 does the opposite; it bounds from the top.  It
2266 2266
 
prohibits any licensor along the distribution chain from placing
2267 2267
 
additional restrictions on the user.  In other words, no additional
2268 2268
 
requirements may trump the rights and freedoms given by GPLv2\@.
...
 
@@ -2364,14 +2364,14 @@ explicit geographical distribution limitation, and the reasoning for that one
2364 2364
 
invocation was not fitting with FSF's intended spirit of GPLv2~\S8.  As such,
2365 2365
 
GPLv2~\S8 was not included at all in GPLv3.
2366 2366
 

	
2367 2367
 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2368 2368
 
\chapter{Odds, Ends, and Absolutely No Warranty}
2369 2369
 

	
2370
 
GPLv2~\S\S0--7 constitute the freedom-defending terms of the GPLv2.  The remainder
2371
 
of the GPLv2 handles administrivia and issues concerning warranties and
2370
 
GPLv2~\S\S0--7 constitute the freedom-defending terms of GPLv2.  The remainder
2371
 
of GPLv2 handles administrivia and issues concerning warranties and
2372 2372
 
liability.
2373 2373
 

	
2374 2374
 
\section{GPLv2~\S9: FSF as Stewards of GPL}
2375 2375
 
\label{GPLv2s9}
2376 2376
 

	
2377 2377
 
FSF reserves the exclusive right to publish future versions of the GPL\@;
...
 
@@ -2501,13 +2501,13 @@ sorts of individuals and even for-profit companies.  Nevertheless, in
2501 2501
 
attempting to understand GPLv3 after the fact, the materials available from
2502 2502
 
the GPLv3 process have a somewhat ``drinking from the firehose'' effect.
2503 2503
 
This chapter seeks to explain GPLv3 to newcomers, who perhaps are familiar
2504 2504
 
with GPLv2 and who did not participate in the GPLv3 process.
2505 2505
 

	
2506 2506
 
Those who wish to drink from the firehose and take a diachronic approach to
2507
 
GPLv3 study by reading the step-by-step public drafting process of the GPLv3 (which
2507
 
GPLv3 study by reading the step-by-step public drafting process of GPLv3 (which
2508 2508
 
occurred from Monday 16 January 2006 through Monday 19 November 2007) should
2509 2509
 
visit \url{http://gplv3.fsf.org/}.
2510 2510
 

	
2511 2511
 
\section{Understanding GPLv3 As An Upgraded GPLv2}
2512 2512
 

	
2513 2513
 
Ultimately, GPLv2 and GPLv3 co-exist as active licenses in regular use.  As
...
 
@@ -2619,13 +2619,13 @@ definitions to make complex ones.  The Program is a defined term found
2619 2619
 
throughout GPLv2, and the word ``covered'' and the phrase ``covered by this
2620 2620
 
license'' are used in tandem with the Program in GPLv2, but not as part of a
2621 2621
 
definition.  GPLv3 offers a single term ``covered work'', which enables some
2622 2622
 
of the wording in GPLv3 to be simpler and clearer than its GPLv2
2623 2623
 
counterparts.
2624 2624
 

	
2625
 
Next, to avoid locking GPLv3 into specific copyright statues, the GPLv3
2625
 
Next, to avoid locking GPLv3 into specific copyright statues, GPLv3
2626 2626
 
defines two terms that are otherwise exotic to the language of international
2627 2627
 
copyright.
2628 2628
 

	
2629 2629
 
\subsection{Propagate}
2630 2630
 

	
2631 2631
 
To ``propagate'' a work covered by the license means any activity in a locale
...
 
@@ -2656,13 +2656,13 @@ distribution may not include network transfers of software but may include
2656 2656
 
interdepartmental transfers of physical copies within an organization.
2657 2657
 
Meanwhile, the copyright laws of many countries, as well as certain
2658 2658
 
international copyright treaties, recognize ``making available to the
2659 2659
 
public'' or ``communication to the public'' as one of the exclusive rights of
2660 2660
 
copyright holders.
2661 2661
 

	
2662
 
Therefore, the GPLv3 defines the term ``propagate'' by reference to activities
2662
 
Therefore, GPLv3 defines the term ``propagate'' by reference to activities
2663 2663
 
that require permission under ``applicable copyright law'', but excludes
2664 2664
 
execution and private modification from the definition.  GPLv3's definition
2665 2665
 
also gives examples of activities that may be included within ``propagation''
2666 2666
 
but it also makes clear that, under the copyright laws of a given country,
2667 2667
 
``propagation'' may include other activities as well.
2668 2668
 

	
...
 
@@ -2854,13 +2854,13 @@ unfortunate restrictions on the freedom to run.\footnote{See
2854 2854
 

	
2855 2855
 
GPLv3~\S2\P2 distinguishes between activities of a licensee that are
2856 2856
 
permitted without limitation and activities that trigger additional
2857 2857
 
requirements.  Specifically, GPLv3~\S2\P2 guarantees the basic freedoms of
2858 2858
 
privately modifying and running the program.  While these basic freedoms were
2859 2859
 
generally considered a standard part of users' rights under GPLv2 as well,
2860
 
the GPLv3 states them herein more explicitly.  In other words, there is no
2860
 
GPLv3 states them herein more explicitly.  In other words, there is no
2861 2861
 
direct analog to the first sentence of GPLv3~\S2\P2 in GPLv2
2862 2862
 
(See \S~\ref{gplv2-private-modification} of this tutorial for more on this issue.)
2863 2863
 

	
2864 2864
 
Also, GPLv3~\S2\P2 gives an explicit permission for a client to provide a
2865 2865
 
copy of its modified software to a contractor exclusively for that contractor
2866 2866
 
to modify it further, or run it, on behalf of the client.  However, the
...
 
@@ -3006,13 +3006,13 @@ users who escape technical restriction measures implemented by GPL'd
3006 3006
 
software.
3007 3007
 

	
3008 3008
 
\section{GPLv3~\S4: Verbatim Copying}
3009 3009
 
\label{GPLv3s4}
3010 3010
 

	
3011 3011
 
GPLv3~\S4 is a revision of GPLv2~\S1 (as discussed in \S~\ref{GPLv2s1} of
3012
 
this tutorial).   There are almost no changes to this section from the
3012
 
this tutorial).   There are almost no changes to this section from
3013 3013
 
GPLv2~\S1, other than to use the new defined terms.
3014 3014
 

	
3015 3015
 
The only notable change, of ``a fee'' to ``any price or no price'', is in the
3016 3016
 
first sentence of GPLv3\S4\P2.  The GPLv2\S1\P1 means that the GPL permits
3017 3017
 
one to charge money for the distribution of software.  Despite efforts by
3018 3018
 
copyleft advocates to explain this in GPLv2 itself and in other documents,
...
 
@@ -3028,13 +3028,13 @@ licensing fees on all third parties.  ``Physical'' might be read, however, as
3028 3028
 
suggesting ``distribution in a physical medium only''.
3029 3029
 

	
3030 3030
 
To address these two issues, GPLv3 says ``price'' in place of ``fee,'' and
3031 3031
 
removes the term ``physical.''
3032 3032
 

	
3033 3033
 
GPLv3~\S4 has also been revised from its corresponding section in GPLv2 in
3034
 
light of the GPLv3~\S7 (see \S~\ref{GPLv3s7} in this tutorial for more).
3034
 
light of GPLv3~\S7 (see \S~\ref{GPLv3s7} in this tutorial for more).
3035 3035
 
Specifically, a distributor of verbatim copies of the program's source code
3036 3036
 
must obey any existing additional terms that apply to parts of the program
3037 3037
 
pursuant to GPLv3~\S7.  In addition, the distributor is required to keep
3038 3038
 
intact all license notices, including notices of such additional terms.
3039 3039
 

	
3040 3040
 
Finally, there is no harm in explicitly pointing out what ought to be
...
 
@@ -3112,13 +3112,13 @@ in \S~\ref{GPLv2s3} of this tutorial), the distribution of object code may
3112 3112
 
either be accompanied by the machine-readable source code, or it may be
3113 3113
 
accompanied by a valid written offer to provide the machine-readable source
3114 3114
 
code.  However, unlike in GPLv2, that offer cannot be exercised by any third
3115 3115
 
party; rather, only those ``who possess the object code'' can exercise
3116 3116
 
the offer.  (Note that this is a substantial narrowing of requirements of
3117 3117
 
offer fulfillment, and is a wonderful counterexample to dispute claims that
3118
 
the GPLv3 has more requirements than GPLv2.)
3118
 
GPLv3 has more requirements than GPLv2.)
3119 3119
 

	
3120 3120
 
% FIXME:  probably mostly still right, needs some updates, though.
3121 3121
 

	
3122 3122
 
GPLv3~\S6(b) further revises the requirements for the written offer to
3123 3123
 
provide source code. As before, the offer must remain valid for at least
3124 3124
 
three years. In addition, even after three years, a distributor of a product
...
 
@@ -3592,13 +3592,13 @@ software packages already combined with various non-copylefted Free Software
3592 3592
 
licensed code that carried such additional terms.  Therefore, GPLv3~\S7 is
3593 3593
 
rationalized existing practices of those package authors and modifiers, since
3594 3594
 
it sets clear guidelines regarding the removal and addition of these
3595 3595
 
additional terms.  With its carefully limited list of allowed additional
3596 3596
 
requirements, GPLv3\S7 accomplishes additional objectives as well, since it
3597 3597
 
permits the expansion of the base of code available for GPL developers, while
3598
 
also encouraging useful experimentation with requirements the GPLv3 does not
3598
 
also encouraging useful experimentation with requirements GPLv3 does not
3599 3599
 
include by default.
3600 3600
 

	
3601 3601
 
However, any other non-permissive additional terms apart from those stated
3602 3602
 
above are considered ``further'' restrictions which
3603 3603
 
\hyperref[GPLv3s10]{GPLv3~\S10} prohibits.  Furthermore, as a compliance
3604 3604
 
matter, if you add additional terms in accordance with GPLv3~\S7, you must
...
 
@@ -3798,13 +3798,13 @@ applies only to those distributors that have
3798 3798
 
modified the program.  The other changes we have made in sections 10 and
3799 3799
 
11 provide strengthened defenses against patent assertion and compensate
3800 3800
 
partly for this concession. 
3801 3801
 

	
3802 3802
 
Therefore, GPLv3~\S11 introduces the terms ``contributor'', ``contributor version'', and
3803 3803
 
``essential patent claims'', which are
3804
 
used in the GPLv3~\S11\P3.   Viewed from the perspective of a recipient of the
3804
 
used in GPLv3~\S11\P3.   Viewed from the perspective of a recipient of the
3805 3805
 
Program, contributors include all the copyright holders for the Program,
3806 3806
 
other than copyright holders of material originally licensed under non-GPL
3807 3807
 
terms and later incorporated into a GPL-covered work.  The contributors are
3808 3808
 
therefore the initial GPLv3 licensors of the Program and all subsequent
3809 3809
 
upstream licensors who convey, under the terms of GPLv3~\S5, modified covered
3810 3810
 
works.
Richard Fontana (fontana)
2 years and 7 months ago on pull request "Non-attributive "the GPLvn" unidiomatic"

Status change: Under review

Auto status change to Under Review
Stephen Compall (S11001001)
2 years and 4 months ago on pull request "Non-attributive "the GPLvn" unidiomatic"
Looks good to me.
2 comments (0 inline, 2 general)