Commit graph

404 commits

Author SHA1 Message Date
Bradley M. Kuhn
9f34658440 Integrate pasted text regarding LGPL.
Much of the pasted text here was useful.  However, some of the claims
were broad reaching, I've reigned those in.  (e.g., saying "Taken
together, these provisions mean:" was a bit strong).

Also, in that specific spot, the conclusions made in the text were
described as applying to LGPLv2.1, but are clearly conclusions about
LGPLv3.  I've corrected that herein.

Finally, I had to write a bunch of next text to make the pasted text
work, and also added one FIXME for later of where things could be
improved further.
2014-11-13 12:25:13 -05:00
Bradley M. Kuhn
895d387cc7 Add label for discussion of GPLv2§3(b). 2014-11-13 12:24:39 -05:00
Bradley M. Kuhn
e5669e4779 Correct \begin and \end{itemize} spelling. 2014-11-13 11:34:33 -05:00
Bradley M. Kuhn
d8d666d5da Pasted sentence usable as is.
I simply combined this pasted sentence with the previous paragraph; I
think it probably works as-is.
2014-11-13 10:57:50 -05:00
Bradley M. Kuhn
065a88d180 Incorporate pasted text re: AGPLv3/GPLv3 combos.
This text was mostly useful as is.  However, it failed to make a key
point I've often made: that the combinations created by comingling
AGPLv3'd code with GPLv3'd code may be difficult to disentangle, and
thus in practice, it may turn out that such a combination effectively
must be licensed as a whole under AGPLv3, even if technically some
copyrights included therein are GPLv3'd.

In practice, this nuance is only a technical barrier, since complying
fully with AGPLv3 automatically complies with GPLv3.
2014-11-13 10:54:37 -05:00
Bradley M. Kuhn
65179995e9 Comment out text that may or may not be useful.
I'm not sure this text is actually useful, so I've commented it out.
2014-11-13 10:52:45 -05:00
Bradley M. Kuhn
c3815b0689 Integrate pasted introductory text for GPLv3§11.
This text was (on the whole) useful as introductory text to this
tutorial's existing extensive section on GPLv3§11.

The example, however, belonged further down in the section, so I've
placed it there.
2014-11-13 10:50:57 -05:00
Bradley M. Kuhn
1e0d39fe72 Integrate pasted text on GPLv3§10.
Most of this text was useful, particularly since there was a previous
FIXME here that GPLv3§10 was not extensively discussed.

However, the same footnote regarding Jaeger's opinion under German
copyright law applies to this text, so a reference back to it has herein
been added.
2014-11-13 10:41:56 -05:00
Bradley M. Kuhn
345da0fc2e Integrate pasted & commented out text for GPLv3§7.
The pasted text, most of which was useful, is now integrated as the
desired laundry-list of GPLv3§7 subsection explanations.

This also allowed for easy integration of some of the older
commented-out text that originally came from GPLv3 rationale documents.

Meanwhile, however, I discovered, upon more careful examination of the
pasted text, a serious and grave error regarding GPLv3§7(d).
Specifically, GPLv3§7(d) makes the modern "third clause" of the 3-Clause
BSD compatible with the GPL, *not* the problematic old-school BSD
advertising clause (from the 4-Clause BSD).

I'm amazed that anyone versed in licensing could make this error,
frankly, and readers should be told, since other materials are now
disseminated by others, that the point is incorrect.  Therefore, I've
not only noted the correct compatibility conclusion, but also
affirmatively identified the incorrectness of the wrong conclusion that
was previously added via the pasted text from SFLC's "Guide".

Finally, on a LaTeX formatting note, the enumitem package is now needed
since I'm using that for the list of GPLv3§7 subsections.
2014-11-13 10:32:54 -05:00
Bradley M. Kuhn
fd69b39c38 Properly close \footnote{}. 2014-11-13 07:57:18 -05:00
Bradley M. Kuhn
ea8cab561d Rewrite pasted paragraph with historical context.
This change perhaps is somewhat controversial, but reflects honest
reality of this history of additional requirements on GPL.  The
additional requirements that GPLv3 permits mostly represent historically
known situations where GPLv2 permitted license compatibility with Free
Software licenses containing such requirements.

Orthodox compatibility theory demands that such additional requirements
have explicit codification in a copyleft license, which hints at why
GPLv3 needed to include this section.

However, historical copyright holder toleration of these sorts of
requirements placed on GPLv2 works is well-documented, and failure to
mention it here is a disservice to the reader.
2014-11-13 07:41:08 -05:00
Bradley M. Kuhn
f03369c7ed Integrate introductory paragraph from pasted text
Most of the pasted text served as a useful introductory paragraph.

I also made some wordsmith changes to the following few paragraphs.
2014-11-13 07:36:41 -05:00
Bradley M. Kuhn
11fd5c29ca Once sentence here was not redundant.
Most of the pasted text was redundant to the existing guide text, but
one sentence reiterates a useful point in a creative way, so that
sentence is herein integrated into the preceding paragraph.
2014-11-12 14:02:42 -05:00
Bradley M. Kuhn
387f2c4ace Incorporate pasted text into intro paragraph.
Some of this text was useful as part of the introduction paragraph.
2014-11-12 13:59:04 -05:00
Bradley M. Kuhn
2145b87982 Simply remove this pasted text.
Upon second reading of this text, I don't know why I saved it.  The
existing guide already covers these issues adequately, and there is no
specific place I could find where this new text worked well as an
introductory paragraph (as has been done with others of these pasted
texts).
2014-11-12 13:26:47 -05:00
Bradley M. Kuhn
14d8ee9b16 Wordsmith last sentence of the footnote.
The word "nearly" appeared far too much in the previous version of this
text.
2014-11-12 12:23:29 -05:00
Bradley M. Kuhn
8a3a8434dd Qualify "additional copies == new license" claim.
The last commit brought in text that categorically claims: "automatic
termination cannot be cured by obtaining additional copies from an
alternate supplier".  While this position is by far the overwhelming
majority position among copyleft advocates, theorists, and legal
experts, the small minority dissenting opinion is simply too strongly
sourced to ignore.

Specifically, Till Jaeger's position was central to Harald Welte's
gpl-violations.org community-oriented GPL enforcement efforts.
Therefore, this tutorial must include his position when covering the
issue of automatic license reinstatement in this tutorial.

I have told Till that I can't believe his position is possibly correct.
(I understand that many other copyleft theorists and legal experts have
done so as well.)  However, Till remains steadfast that this position is
correct, at least under German copyright law.  Speaking for myself, I
have never met a legal expert as well-versed in both copyleft and German
copyright law as Till Jaeger is, and therefore I cannot in good
conscience allow this tutorial to remain silent regarding Till's
position, lest the tutorial propagate an inappropriate bias for the
majority belief.

That said, I still feel that a footnote is the right place for the
argument.  It *is* a tiny minority position [0] among an overwhelming
consensus to the contrary, and therefore adding the point to the main
text would only serve to distract the tutorial reader.

[0] In particular, I am convinced Jaeger's argument, if true, is a
    peculiarity of German law exclusively.  For example, French lawyers
    I've spoken with believe that the standard USA legal position on
    this issue is also accurate under French copyright law.  I therefore
    conclude the minority position (if accurate) is unrelated to
    differences between civil law and common law copyright regimes, and
    is instead a unique peculiarity to German copyright law.
2014-11-12 11:51:28 -05:00
Bradley M. Kuhn
d6bf6f07b1 Edit pasted automatic downstream license text.
This pasted text was quite useful and well-written.  I've incorporated
it fully, although it needed some copy edit work and additional
material.
2014-11-12 11:48:12 -05:00
Bradley M. Kuhn
bf85191e63 Add subsections for GPLv2§2 discussion.
The GPLv2§2 has gotten long enough that it really needed subsections.
2014-11-12 11:32:05 -05:00
Bradley M. Kuhn
c88f72765a Integrate pasted text on "separate & independent".
This pasted text was pretty useful, and is now integrated fully, with
additional text I wrote to improve and expand the point.
2014-11-12 11:28:51 -05:00
Bradley M. Kuhn
67bb09ea17 Integrate pasted explanation of GPLv2§2(c).
The tutorial did not previously have an adequate description of
GPLv2§2(c), so this pasted text is as good as any that I could think of,
although I reworded it slightly.

I chose to integrate this text *before* the discussion of GPLv2§2(b)
because the latter section requires so much attention, it seems
appropriate to get the less complex parts of GPLv2§2 out of the way
before diving into that essential discussion of GPLv2§2(b).
2014-11-12 10:19:01 -05:00
Bradley M. Kuhn
b8f084be3a Incorporate pasted text as chapter's introduction.
The pasted text, moved in an earlier commit to this chapter, is now
incorporated as the introduction for the chapter on derivative works.

Changes also included to the previous introduction so it properly flows
from the new text.
2014-11-12 10:10:41 -05:00
Bradley M. Kuhn
5e195ab80a Integrate this short sentence from pasted text.
This was easily integrated, but I am now not sure what I was thinking
with the FIXME note about linking back to the copyleft definition.  The
right link is a forward-link to the derivative works chapter, and thus
I've added that.
2014-11-12 07:50:28 -05:00
Bradley M. Kuhn
e36a9a4f4c Rework copyleft definition utilizing pasted text.
Some of the pasted text was useful as a method of introducing briefly
the legal details of copyleft, to an appropriate level of detail for
this initial copyleft definition found in the tutorial.  However,
substantial additional text was needed to both properly integrate the
pasted text, and also improve the copyleft definition overall in light
of the pasted text content.

Meanwhile, part of the pasted text definitely doesn't belong here, but I
noticed it likely makes a good addition to the introductory paragraph in
the derivative works section.
2014-11-12 07:44:47 -05:00
Bradley M. Kuhn
00ac5cfb9a Incorporate copyleft defn from copyleft.org site
I wrote a pretty good copyleft definition, originally based on the one
found on Wikipedia, for use on the front page of copyleft.org.  Herein
it is integrated with the tutorial as well.
2014-11-12 07:18:59 -05:00
Bradley M. Kuhn
e24942c98b Integrate this LGPL text properly.
Upon a more detailed reading, it's clear this pasted text belongs in the
LGPL license analysis section, but that in fact some other text was
needed to improve the end of the section on LGPL in the compliance
guide.
2014-11-11 19:21:50 -05:00
Bradley M. Kuhn
746eff5786 Link LGPL compliance section to LGPL analysis.
Since so little material is currently given on LGPL compliance, it's
likely best to link back to the chapter on LGPL compliance.

Besides, I don't think there really is anything additional the
compliance guide can add regarding LGPL compliance, other than the
detail license analysis on LGPL already available in that part of the
text.

(Note labels had to be added for the chapters that didn't previously
exist.)
2014-11-11 19:21:21 -05:00
Bradley M. Kuhn
82831c9b81 Integrate this text and rewrite to make it work.
Also creates some label for references back.
2014-11-11 11:40:38 -05:00
Bradley M. Kuhn
c83c789fd0 Correct formatting on footnote. 2014-11-10 21:57:48 -05:00
Bradley M. Kuhn
4a22feba06 This should say GPLv3 here. 2014-11-10 21:11:28 -05:00
Bradley M. Kuhn
a43a205f9b Incorporate new text fully into this section. 2014-11-10 21:10:57 -05:00
Bradley M. Kuhn
a32bea9563 Properly quote & characters. 2014-11-10 19:14:01 -05:00
Bradley M. Kuhn
851be52e62 Rework two compliance guide sections in Background
Some of the text pasted in earlier commits was certainly useful, but
needed a complete rework.

Also, the text pasted was far too terse, and more detail was needed.

Therefore, I've moved text around and build a more comprehensive
Background section.  I've moved the burgeoning "Understanding Who's
Enforcing" section into the Background chapter and made it complete.

Probably the most bizarre (?) change I've made here is coining this
acronym COGEO.  This is non-optimal for sure, and I've added a FIXME to
seek a better term.
2014-11-10 18:56:14 -05:00
Bradley M. Kuhn
2ce793aa05 Integrate text describing copyright holders.
The enforcement section now has an integrated paragraph describing how
enforcement relates to copyright, and refers back to a related section
much earlier in the tutorial.
2014-11-10 16:46:50 -05:00
Bradley M. Kuhn
8e360c9db8 Formatting fix. 2014-11-10 16:36:59 -05:00
Bradley M. Kuhn
a1b059184c Incorporate useful text from a third party work.
Software Freedom Law Center, a small law firm specializing in Open
Source, recently published its so-called "Guide to GPL Compliance,
Second Edition":
http://softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL_Compliance_2d_ed.html

The Firm's document is substantially less comprehensive than this one;
however, their document contained a few phrases and paragraphs that
seemed useful and accurate.  This commit incorporates the useful
material from that work into this one (as permitted by the CC BY-SA 4.0
license, which the Software Freedom Law Center applied to their work).

The useful sections have been pasted without proper textual integration
into the appropriate sections of this tutorial.  A few are currently
commented out entirely and marked with appropriate FIXME's.  Meanwhile,
the text that seems immediately useful is *not* commented out, and is
marked with "FIXME-URGENT".  Additional work is now required to
integrate the new text properly into this tutorial.

Careful readers who compare this commit with The Firm's document will
find that I passed on inclusion of some seemingly useful material.
Unfortunately, The Firm's text contained some inaccuracies, and frames
discussion primarily from a for-profit perspective.  More disturbingly,
a few statements even directly contradicted the FSF's stated policies.
Of course, The Firm clearly claims "this document does not express the
views, intentions, policy, or legal analysis of any SFLC clients or
client organizations", but I could not in good conscience adopt, as the
official advice in this tutorial, any text that conflicts with the FSF's
policies, nor will I incorporate any puffery that subtly kowtows to
for-profit corporate interests.

Nevertheless, given The Firm's perceived stature, I briefly considered
including policy-conflicting statements, attributing them as alternative
third-party opinions; many of the FSF's own opinions were already
incorporated in that manner earlier this year.  Indeed, I will not prima
facie reject future patches that integrate such statements naturally for
this tutorial.  However, I feel that the didactic value of including The
Firm's attributed dissenting opinions in this tutorial does not outweigh
my editing effort required for such additional textual integration.

Regarding Software Freedom Law Center's copyrights included herein,
I took the following specific actions to comply with CC By SA 4.0:

§3(a)(1)(a)(i):    This log message indicates Software Freedom Law Center
                   as the source of the material herein committed.

§3(a)(1)(a)(i):    Copyright notices at the top level of the document,
                   as well as those in individual parts, are updated to
                   include the 2014 copyright notice from the Software
                   Freedom Law Center.

§3(a)(1)(a)(ii-v): The project already referred to and included a copy
§3(b)(1):          of CC BY SA 4.0 International and its URL.

§3(a)(2):          The attribution information is fully included in
                   this Git repository.

§3(a)(3):          I and this project have received no such request.

§3(b)(1):          The license of the larger work was already
                   CC BY SA 4.0 International.

§3(b)(3):          No such conditions are imposed.
2014-11-10 16:21:53 -05:00
Bradley M. Kuhn
9641db188d FIXME: no discussion of GPLv2 system lib exception 2014-11-10 07:03:28 -05:00
Bradley M. Kuhn
0a37731b72 Rewrote U-Boot Installation section.
My primary goal here was to put the text into a consistent voice, and
convert the text to a more flowing narrative rather than a step-by-step
list.

In a few places, I added commentary on the process where it seemed
appropriate, but I strove to keep that minimal.

Finally, labels to some unlabeled sections of gpl-lgpl.tex were needed
for back-references used in my rewrite.
2014-11-09 13:57:14 -05:00
Bradley M. Kuhn
16155bea58 This should be a URL tag. 2014-11-07 10:57:02 -05:00
Bradley M. Kuhn
1837849952 Discuss CCS CD included in package.
This yielded a lesson learned, so that is herein added as well.

A new reference was also added for the discussion of GPLv2§3(a).
2014-11-07 08:07:25 -05:00
Bradley M. Kuhn
b46d1bc16f Correction to formatting on copyright notices. 2014-11-06 21:30:53 -05:00
Bradley M. Kuhn
467a23152a Copyright notice updates.
Joshua Gay made contributions to all the files earlier in 2014 (see git
log) which were copyrighted by the FSF, so FSF's copyright needs
refreshed to include this year.

Denver recently added a section to the enforcement-case-studies.tex, so
his copyright notice needs to go there and at the top file.

I made changes to enforcement-case-studies.tex on top of Denver's.

Also, remove commented-out copyright notices -- the ones in the actual
text are now primary and should be maintained directly.
2014-11-06 16:59:48 -05:00
Bradley M. Kuhn
4a40f09f14 Typo fix. 2014-10-16 10:38:01 -04:00
Bradley M. Kuhn
be62a9b765 Investigate USA-specific-ness of "derivative work"
This FIXME is to remind me to look into this issue later.
2014-10-15 22:21:40 -04:00
Bradley M. Kuhn
2f2e5f9e4c Rework over-abundant use of term "derivative work"
The older portions of this tutorial tended to favor the term "derivative
work", since that was the popular catch-all term used at the time the
text was written.

However, as the newer text regarding GPLv3 now states, FSF abandoned the
use of the term "derivative work" in the text of GPLv3 itself, for
various reasons we already discuss in the tutorial.

Therefore, the tutorial text itself should likely not rely so heavily on
the phrase "derivative work" throughout.  This change herein reworks a
number of places where "derivative work" was used in the tutorial and
replaced it with other terms.

Ultimately, some word-smithing happened as part of the process of doing
this patch.
2014-10-15 22:14:45 -04:00
Bradley M. Kuhn
3d402b8cbf derivative works matter less than you think.
Given the wealth of text this chapter offers regarding derivative works,
this section really is necessary to give context on this point and
assure that the reader is not unduly swayed to believe that the
derivative work discussion is a central tenant of understanding
copyleft.

Long term, it may make sense to move the entire chapter on derivative
works to a different part of the tutorial.  Historically, it was placed
here because when teaching courses on the subject based on this text, I
found as an instructor that questions about derivative works became so
rampant from students during discussions of GPLv2§2 / GPLv3§5 that
derivative works discussion ahead of time was the only way to quell the
onslaught of ultimately off-topic questions.

Thus, the placement of the derivative works section in this location may
in fact be merely an historical artifact that this text was written
originally to accompany an in-course presentation.  While I'd still
recommend organizing a classroom presentation of these topics in that
order, I no longer believe the written materials must follow suit.
2014-10-15 18:53:32 -04:00
Bradley M. Kuhn
090b056608 Formatting typo fix. 2014-09-19 18:24:43 -04:00
Bradley M. Kuhn
012aebd493 Move details of exclusive power to a footnote.
enyst was quite correct that more explanation was needed here about how
an entity achieves exclusive relicensing rights.  However, the details
are somewhat off-point to what the section is trying to explain, so the
details are best placed in a footnote.

I've also separated out copyright assignment from generating all of
one's own copyrights.  This may be a distinction without a difference,
but a laundry list seemed appropriate here.  Perhaps this should be
shortened in future.
2014-09-19 18:16:02 -04:00
enyst
831c21febb Strictly speaking, for proprietary relicensing 'only' unconditional permissions are needed.
Signed-off-by: enyst <engel.nyst@gmail.com>
2014-09-19 18:09:46 -04:00
enyst
f31235afbc Possible fixes for incomplete or unclear phrases
Signed-off-by: enyst <engel.nyst@gmail.com>
2014-09-19 18:09:45 -04:00