Copyleft/guide Changeset - 555a72beb114

Changeset - 555a72beb114

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 9 years ago 2015-03-13 00:15:15
bkuhn@ebb.org

Suggestions for in depth discussion of GPLv2§2(a)

GPLv2§2(a) is mentioned quite cursorily. Olly Betts suggests more
coverage here might useful on IRC. I noted some ideas after he
suggested it.

1 file changed with 10 insertions and 0 deletions:

gpl-lgpl.tex

0 comments (0 inline, 0 general)

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
 copying, as presented in GPLv2~\S1.  Therefore, the details of charging money,
 keeping copyright notices intact, and other GPLv2~\S1 provisions are intact
 here as well.  However, there are three additional requirements.
 \subsection{The Simpler Parts of GPLv2~\S2}
 % FIXME: GPLv2~\S2(a) isn't discussed heavily here and more should be
 % discussed about it.  There have been developer questions.  One idea I had
 % was to write up:
 %        http://ebb.org/bkuhn/blog/2011/03/11/linux-red-hat-gpl.html
 % as a compliance case study specific to GPLv2 Section 2(a)
+%
 % Another point to discuss here -- or maybe it goes better in the compliance
 % case study ? -- is to explain that git logs ARE adequate but possibly
 % overkill.
 The first (GPLv2~\S2(a)) requires that modified files carry ``prominent
 notices'' explaining what changes were made and the date of such
 changes. This section does not prescribe some specific way of
 marking changes nor does it control the process of how changes are made.
 Primarily, GPLv2~\S2(a) seeks to ensure that those receiving modified
 versions know the history of changes to the software.  For some users,

0 comments (0 inline, 0 general)