Copyleft/guide Changeset - dc84691b9398

...

@@ -57,3 +57,3 @@ to have learned the following:

  \item The redistribution options under the GPLv2 and GPLv3.

  \item The redistribution options under GPLv2 and GPLv3.

...

@@ -70,3 +70,3 @@ to have learned the following:

  \item The basics of LGPLv2.1 and LGPLv3, and how they

    differ from the GPLv2 and GPLv3, respectively.

    differ from GPLv2 and GPLv3, respectively.

...

@@ -827,3 +827,3 @@ In January 1989, the FSF announced that the GPL had been converted into a

programs, but also by anyone else.  As the FSF claimed in its announcement of

the GPLv1:\footnote{The announcement of GPLv1 was published in the

GPLv1:\footnote{The announcement of GPLv1 was published in the

  \href{http://www.gnu.org/bulletins/bull6.html\#SEC8}{GNU's Bulletin, vol 1,

...

@@ -1066,4 +1066,4 @@ access to is and should remain unregulated and unrestricted.

Thus, the GPLv2 protects users' fair and unregulated use rights precisely by

not attempting to cover them.  Furthermore, the GPLv2 ensures the freedom

Thus, GPLv2 protects users' fair and unregulated use rights precisely by

not attempting to cover them.  Furthermore, GPLv2 ensures the freedom

to run specifically by stating the following:

...

@@ -1513,3 +1513,3 @@ an essential discussion in the interpretation and consideration of copyleft.

That is why this chapter was included in this tutorial.  However, as we

return from this digression and resume discussion of the detailed text of the

return from this digression and resume discussion of the detailed text of

GPLv2, we must gain a sense of perspective: most GPL questions center around

...

@@ -1746,3 +1746,3 @@ In summary, GPLv2\ 2(b) says what terms under which the third parties must

receive this no-charge license.  Namely, they receive it ``under the terms

of this License'', the GPLv2.  When an entity \emph{chooses} to redistribute

of this License'', GPLv2.  When an entity \emph{chooses} to redistribute

a work based on GPL'd software, the license of that whole

...

@@ -2052,6 +2052,6 @@ Software, because software licensed under the GPL grants the licensee the

right to make, use, and sell the software, each of which are exclusive

rights of a patent holder. Therefore, although the GPLv2 does not expressly

rights of a patent holder. Therefore, although GPLv2 does not expressly

grant the licensee the right to do those things under any patents the

licensor may have that cover the software or its reasonably contemplated

uses, by licensing the software under the GPLv2, the distributor impliedly

uses, by licensing the software under GPLv2, the distributor impliedly

licenses those patents to the GPLv2 licensee with respect to the GPLv2'd

...

@@ -2085,3 +2085,3 @@ is distributed among many entities within the community for the purpose

of constant evolution and improvement. In this way, the law of implied

patent license used by the GPLv2 ensures that the community mutually

patent license used by GPLv2 ensures that the community mutually

benefits from the licensing of patents to any single community member.

...

@@ -2097,6 +2097,6 @@ against either:

\item any software other than that licensed under the GPLv2 by the patent

\item any software other than that licensed under GPLv2 by the patent

  holder, and

\item any party that does not comply with the GPLv2

\item any party that does not comply with GPLv2

with respect to the licensed software.

...

@@ -2108,3 +2108,3 @@ with respect to the licensed software.

For example, if Company \compA{} has a patent on advanced Web browsing, but

also licenses a Web browsing program under the GPLv2, then it

also licenses a Web browsing program under GPLv2, then it

cannot assert the patent against any party based on that party's use of

...

@@ -2113,6 +2113,6 @@ creation and use of modified versions of that GPL'd program.  However, if a

party uses that program without

complying with the GPLv2, then Company \compA{} can assert both copyright

complying with GPLv2, then Company \compA{} can assert both copyright

infringement claims against the non-GPLv2-compliant party and

infringement of the patent, because the implied patent license only

extends to use of the software in accordance with the GPLv2. Further, if

extends to use of the software in accordance with GPLv2. Further, if

Company \compB{} distributes a competitive advanced Web browsing program

...

@@ -2121,3 +2121,3 @@ program, Company \compA{} is free to assert its patent against any user or

distributor of that product. It is irrelevant whether Company \compB's

program is also distributed under the GPLv2, as Company \compB{} can not grant

program is also distributed under GPLv2, as Company \compB{} can not grant

implied licenses to Company \compA's patent.

...

@@ -2126,3 +2126,3 @@ This result also reassures companies that they need not fear losing their

proprietary value in patents to competitors through the GPLv2 implied patent

license, as only those competitors who adopt and comply with the GPLv2's

license, as only those competitors who adopt and comply with GPLv2's

terms can benefit from the implied patent license. To continue the

...

@@ -2130,3 +2130,3 @@ example above, Company \compB{} does not receive a free ride on Company

\compA's patent, as Company \compB{} has not licensed-in and then

redistributed Company A's advanced Web browser under the GPLv2. If Company

redistributed Company A's advanced Web browser under GPLv2. If Company

\compB{} does do that, however, Company \compA{} still has not lost

...

@@ -2136,3 +2136,3 @@ to any of its patents that cover the program. Further, if Company \compB{}

relicenses an improved version of Company A's program, it must do so under

the GPLv2, meaning that any patents it holds that cover the improved version

GPLv2, meaning that any patents it holds that cover the improved version

are impliedly licensed to any licensee. As such, the only way Company

...

@@ -2147,3 +2147,3 @@ Chapters~\ref{run-and-verbatim} and~\ref{source-and-binary} presented the

core freedom-defending provisions of GPLv2\@, which are in GPLv2~\S\S0--3.

GPLv2\S\S~4--7 of the GPLv2 are designed to ensure that GPLv2~\S\S0--3 are

GPLv2\S\S~4--7 of GPLv2 are designed to ensure that GPLv2~\S\S0--3 are

not infringed, are enforceable, are kept to the confines of copyright law but

...

@@ -2261,3 +2261,3 @@ license from the original licensor to the next recipient.  This creates a

chain of grants that ensure that everyone in the distribution has rights

under the GPLv2\@.  In a mathematical sense, this bounds the bottom ---

under GPLv2\@.  In a mathematical sense, this bounds the bottom ---

making sure that future licensees get no fewer rights than the licensee before.

...

@@ -2369,4 +2369,4 @@ GPLv2~\S8 was not included at all in GPLv3.

GPLv2~\S\S0--7 constitute the freedom-defending terms of the GPLv2.  The remainder

of the GPLv2 handles administrivia and issues concerning warranties and

GPLv2~\S\S0--7 constitute the freedom-defending terms of GPLv2.  The remainder

of GPLv2 handles administrivia and issues concerning warranties and

liability.

...

@@ -2506,3 +2506,3 @@ with GPLv2 and who did not participate in the GPLv3 process.

Those who wish to drink from the firehose and take a diachronic approach to

GPLv3 study by reading the step-by-step public drafting process of the GPLv3 (which

GPLv3 study by reading the step-by-step public drafting process of GPLv3 (which

occurred from Monday 16 January 2006 through Monday 19 November 2007) should

...

@@ -2624,3 +2624,3 @@ counterparts.

Next, to avoid locking GPLv3 into specific copyright statues, the GPLv3

Next, to avoid locking GPLv3 into specific copyright statues, GPLv3

defines two terms that are otherwise exotic to the language of international

...

@@ -2661,3 +2661,3 @@ copyright holders.

Therefore, the GPLv3 defines the term ``propagate'' by reference to activities

Therefore, GPLv3 defines the term ``propagate'' by reference to activities

that require permission under ``applicable copyright law'', but excludes

...

@@ -2859,3 +2859,3 @@ privately modifying and running the program.  While these basic freedoms were

generally considered a standard part of users' rights under GPLv2 as well,

the GPLv3 states them herein more explicitly.  In other words, there is no

GPLv3 states them herein more explicitly.  In other words, there is no

direct analog to the first sentence of GPLv3~\S2\P2 in GPLv2

...

@@ -3011,3 +3011,3 @@ software.

GPLv3~\S4 is a revision of GPLv2~\S1 (as discussed in \S~\ref{GPLv2s1} of

this tutorial).   There are almost no changes to this section from the

this tutorial).   There are almost no changes to this section from

GPLv2~\S1, other than to use the new defined terms.

...

@@ -3033,3 +3033,3 @@ removes the term ``physical.''

GPLv3~\S4 has also been revised from its corresponding section in GPLv2 in

light of the GPLv3~\S7 (see \S~\ref{GPLv3s7} in this tutorial for more).

light of GPLv3~\S7 (see \S~\ref{GPLv3s7} in this tutorial for more).

Specifically, a distributor of verbatim copies of the program's source code

...

@@ -3117,3 +3117,3 @@ the offer.  (Note that this is a substantial narrowing of requirements of

offer fulfillment, and is a wonderful counterexample to dispute claims that

the GPLv3 has more requirements than GPLv2.)

GPLv3 has more requirements than GPLv2.)

...

@@ -3597,3 +3597,3 @@ requirements, GPLv3\S7 accomplishes additional objectives as well, since it

permits the expansion of the base of code available for GPL developers, while

also encouraging useful experimentation with requirements the GPLv3 does not

also encouraging useful experimentation with requirements GPLv3 does not

include by default.

...

@@ -3803,3 +3803,3 @@ Therefore, GPLv3~\S11 introduces the terms ``contributor'', ``contributor versio

``essential patent claims'', which are

used in the GPLv3~\S11\P3.   Viewed from the perspective of a recipient of the

used in GPLv3~\S11\P3.   Viewed from the perspective of a recipient of the

Program, contributors include all the copyright holders for the Program,

@@ ... @@
 is a course unto itself, educating the reader on a myriad of topics from the
-deep details of the GPLv2 and GPLv3, common business models in the copyleft
 deep details of GPLv2 and GPLv3, common business models in the copyleft
 licensing area (both the friendly and unfriendly kind), best practices for