Copyleft/guide Changeset - 05d02bfff430

Changeset - 05d02bfff430

Parent rev.

Child rev.

[Not reviewed]

0 2 0

Bradley Kuhn (bkuhn) - 10 years ago 2014-03-21 02:01:07
bkuhn@ebb.org

Various temp changes to handle printing it this weekend.

2 files changed with 11 insertions and 4 deletions:

comprehensive-gpl-guide.tex

gpl-lgpl.tex

0 comments (0 inline, 0 general)

comprehensive-gpl-guide.tex

➞

Show inline comments

@@ ... @@
 by FSF, and they are all licensed under the license, ``Everyone is permitted
 to copy and distribute verbatim copies of this license document, but changing
 it is not allowed.''.  However, those who seek to make modified versions of
 those licenses should note the
 \href{https://www.gnu.org/licenses/gpl-faq.html#ModifyGPL}{explanation given in the GPL FAQ}.
 \vfill
 Patches are welcome to this material.  Sources can be found in the Git
 repository at: \url{https://gitorious.org/gpl-compliance-tools/tutorial/}
+}
 \end{center}
 \end{titlepage}

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
     \href{http://audio-video.gnu.org/audio/}{speech recordings} of his talk,
     \textit{The Free Software Movement and the GNU/Linux Operating System}
     are also widely available}.
 \section{Proto-GPLs And Their Impact}
 %FIXME-LATER: bad line break:
 %\href{http://www.free-soft.org/gpl_history/emacs_gpl.html}{The Emacs
 %  General Public License}
 The earliest copyleft licenses were specific to various GNU programs.  For
 example, \href{http://www.free-soft.org/gpl_history/emacs_gpl.html}{The Emacs
   General Public License} was likely the first copyleft license ever
 example,  The Emacs
 General Public License was likely the first copyleft license ever
 published.  Interesting to note that even this earliest copyleft license
 contains a version of the well-known GPL copyleft clause:
 \begin{quotation}
 You may modify your copy or copies of GNU Emacs \ldots provided that you also
 \ldots cause the whole of any work that you distribute or publish, that in
@@ ... @@
 Internet (i.e., ``from a designated place''), \emph{then} simply providing
 the source code right alongside the binaries in the same place is
 sufficient to comply with GPLv2~\S3.
 \medskip
-As is shown above, Under GPLv2~\S3(a), embedded manufacturers can put the
+As is shown above, under GPLv2~\S3(a), embedded manufacturers can put the
 binaries on the device and ship the source code along on a CD\@.  However,
 sometimes this turns out to be too costly.  Including a CD with every
 device could prove too costly, and may practically (although not legally)
 prohibit using GPL'd software. For this situation and others like it, GPLv2\S~3(b) is available.
 GPLv2~\S3(b) allows a distributor of binaries to instead provide a written
@@ ... @@
 to ``wrap'' their software in an acceptance ceremony to GPL, and nothing in
 GPL prohibits that use.  Furthermore, the ruling in \textit{Jacobsen
   v. Katzer, 535 F.3d 1373, 1380 (Fed.Cir.2008)} indicates that \textbf{both}
 copyright and contractual remedies may be sought by a copyright holder
 seeking to enforce a license designed to uphold software freedom.
 \section{Using GPL Both as a Contract and Copyright License}
 % FIXME-LATER: Write this
 %\section{Using GPL Both as a Contract and Copyright License}
 \section{GPLv2~\S6: GPL, My One and Only}
 \label{GPLv2s6}
 A point that was glossed over in Section~\ref{GPLv2s4}'s discussion of GPLv2~\S4
 was the irrevocable nature of the GPL\@. The GPLv2 is indeed irrevocable,

0 comments (0 inline, 0 general)