Copyleft/guide Changeset - 5e6a129b4cd6

Changeset - 5e6a129b4cd6

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 10 years ago 2014-03-19 14:00:03
bkuhn@ebb.org

Rewrite paragraph to mention minified Javascript, and other changes.
Also, update the FIXMEs to be more verbose.

1 file changed with 8 insertions and 6 deletions:

gpl-lgpl.tex

0 comments (0 inline, 0 general)

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
 not tied to any statutory language.  Propagation that does not enable other
 parties to make or receive copies --- for example, making private copies or
 privately viewing the program --- is permitted unconditionally.  Propagation
 that does enable other parties to make or receive copies is permitted as
 ``distribution,'' subject to the conditions set forth in sections 4--6.
 % FIXME: Appropriate Legal Notices
 \section{GPLv3~\S1: Understanding CCS}
 % FIXME: Talk briefly about importance of CCS and reference compliance guide
 % FIXME: reword source code a bit
 % FIXME: verify this still matches final GPLv3 text.
 % FIXME:  link to GPLv2 tutorial sections if possible and where appropriate.
 Section 1 retains GPLv2's definition of ``source code'' and adds an explicit
 definition of ``object code'' as ``any non-source version of a work.''
 GPLv3\~S1 retains GPLv2's definition of ``source code'' and adds an explicit
 definition of ``object code'' as ``any non-source version of a work''.
 Object code is not restricted to a narrow technical meaning and is to be
 understood broadly as including any form of the work other than the preferred
 form for making modifications to it.  Object code therefore includes any kind
 of transformed version of source code, such as bytecode.  The definition of
 object code also ensures that licensees cannot escape their obligations under
 the GPL by resorting to shrouded source or obfuscated programming.
 of transformed version of source code, such as bytecode or minified
 Javascript.  The definition of object code also ensures that licensees cannot
 escape their obligations under the GPL by resorting to shrouded source or
 obfuscated programming.
 % FIXME: CCS Coresponding Source updated to newer definition in later drafts
 Keeping with the desire to ``round up'' definitions that were spread
 throughout the text of GPLv2, the definition of CCS\footnote{Note that the
   preferred term by those who work with both GPLv2 and GPLv3 is ``Complete
   Corresponding Source'', abbreviated to ``CCS''.  Admittedly, the word
   ``complete'' no longer appears in GPLv3 (which uses the word ``all''
   instead).  However, both GPLv2 and the early drafts of GPLv3 itself used
   the word complete, and early GPLv3 drafts even included the phrase
   ``Complete Corresponding Source''.  Meanwhile, use of the acronym ``CCS''
   (sometimes, ``C&CS'') was so widespread among GPL enforcers that its use

0 comments (0 inline, 0 general)