5 years agoAdd 'Copyleft Sunset' provision.
Richard Fontana [Wed, 20 Feb 2013 02:39:36 +0000 (21:39 -0500)]
Add 'Copyleft Sunset' provision.

See mailing list thread "Limited-term copyleft" beginning at

5 years agoSome rewording of object code distribution condition.
Richard Fontana [Wed, 20 Feb 2013 02:28:49 +0000 (21:28 -0500)]
Some rewording of object code distribution condition.

Mainly restores accidental deletion of the 2-year requirement for
network-available source where binaries are distributed in products.

5 years agoMove inbound=outbound condition earlier in license text.
Richard Fontana [Wed, 20 Feb 2013 02:08:51 +0000 (21:08 -0500)]
Move inbound=outbound condition earlier in license text.

5 years agoMinor improvement to inbound=outbound condition.
Richard Fontana [Wed, 20 Feb 2013 02:06:41 +0000 (21:06 -0500)]
Minor improvement to inbound=outbound condition.

5 years agoAdd inbound=outbound-style contribution condition.
Richard Fontana [Wed, 20 Feb 2013 02:01:30 +0000 (21:01 -0500)]
Add inbound=outbound-style contribution condition.

This is inspired by Apache License 2.0 section 5. The term
'symmetrical licensing' in this context was, to my knowledge, coined
by Mike Milinkovic of the Eclipse Foundation.

5 years agoSimplify object code distribution section.
Richard Fontana [Wed, 20 Feb 2013 01:44:53 +0000 (20:44 -0500)]
Simplify object code distribution section.

With this simplified presentation, network access is the normal way to
comply with the source code requirement, but the distributor of a
'Product' can alternatively comply by accompanying it with the source

5 years agoEconomize 'no remote downstream termination' clause in termination section.
Richard Fontana [Wed, 20 Feb 2013 01:34:35 +0000 (20:34 -0500)]
Economize 'no remote downstream termination' clause in termination section.

5 years agoMinor word order change in pass-through section.
Richard Fontana [Wed, 20 Feb 2013 01:31:11 +0000 (20:31 -0500)]
Minor word order change in pass-through section.

5 years agoAdd 'powered by' clauses to anti-badgeware clause in section 3.
Richard Fontana [Wed, 20 Feb 2013 01:27:44 +0000 (20:27 -0500)]
Add 'powered by' clauses to anti-badgeware clause in section 3.

5 years agoSome rewording of 'nullification' provision.
Richard Fontana [Wed, 20 Feb 2013 01:24:45 +0000 (20:24 -0500)]
Some rewording of 'nullification' provision.

One change here is to refer simply to 'Covered Work' rather than
something that 'would have been a Covered Work had you prepared it'. I
believe the latter language may have been tied to earlier versions of
Covered Work definition.

5 years agoReverse order of child-of-fair-use clause and no-trademark-license clause.
Richard Fontana [Wed, 20 Feb 2013 01:18:22 +0000 (20:18 -0500)]
Reverse order of child-of-fair-use clause and no-trademark-license clause.

5 years agoRevise in various ways.
Richard Fontana [Wed, 20 Feb 2013 01:16:32 +0000 (20:16 -0500)]
Revise in various ways.

5 years agoAdd Masayuki Hatta and Kuno Woudt to THANKS.
Richard Fontana [Wed, 20 Feb 2013 01:06:19 +0000 (20:06 -0500)]
Add Masayuki Hatta and Kuno Woudt to THANKS.

5 years agoSimplify 'Derived Work' definition slightly.
Richard Fontana [Tue, 19 Feb 2013 14:26:51 +0000 (09:26 -0500)]
Simplify 'Derived Work' definition slightly.

The parenthetical about preexisting material is deleted as potentially
creating more confusion than clarity.

5 years agoDelete 'part of' part of 'My Work' definition as potentially confusing.
Richard Fontana [Tue, 19 Feb 2013 14:04:41 +0000 (09:04 -0500)]
Delete 'part of' part of 'My Work' definition as potentially confusing.

It seems that substantially unmodified portions of the work I license
(think particularlly of source code) ought to similarly fit the simple
'My Work' definition.

5 years agoRemove 'Distributor' definition and remaining capitalized 'Distribut-' usages.
Richard Fontana [Tue, 19 Feb 2013 13:57:42 +0000 (08:57 -0500)]
Remove 'Distributor' definition and remaining capitalized 'Distribut-' usages.

5 years agoSome changes to 'Derived Work' and 'My Work' definitions.
Richard Fontana [Tue, 19 Feb 2013 13:34:40 +0000 (08:34 -0500)]
Some changes to 'Derived Work' and 'My Work' definitions.

'Derived Work' adds 'derivative work' and its definition and that of
'My Work' clarify that they do not refer to preexisting material as
such (cf. 17 U.S.C. 103(b).

5 years agoRemoved definitions of 'Distribute' and 'Distributor'.
Richard Fontana [Tue, 19 Feb 2013 13:16:38 +0000 (08:16 -0500)]
Removed definitions of 'Distribute' and 'Distributor'.

The definition of 'Distribute' did not really do very much. Taking it
out makes 'Distributor' unnecessary; the only remaining references to
'Distributor' were in the disclaimer provisions where they can be
substituted with 'distributor of My Work'. (Note that any mere
licensee-distributor must be distributing an upstream 'My Work' by

5 years agoConspicuousness markers: ## -> **
Richard Fontana [Tue, 19 Feb 2013 07:15:36 +0000 (02:15 -0500)]
Conspicuousness markers: ## -> **

M. Hatta indicated a preference for the asterisk over the hashmark in

5 years agoEffectively revert copyleft nullification generalization and 'Give' definition.
Richard Fontana [Mon, 18 Feb 2013 04:14:29 +0000 (23:14 -0500)]
Effectively revert copyleft nullification generalization and 'Give' definition.

Trying to cover the scenario of the licensor who nominally licenses a
binary under the GPL without providing Corresponding Source seems more
trouble than it is worth.

The main point I suppose is that the licensee should be relieved from
having to comply with the (effectively impossible) Corresponding
Source requirement. However, it is possible that even worrying about
explicitly covering this scenario (though it has occurred in real
life) is falling into GPL hyperlegalization trap.

5 years agoFix line lengths in I/You definition and change 'any' to 'each'.
Richard Fontana [Mon, 18 Feb 2013 03:53:27 +0000 (22:53 -0500)]
Fix line lengths in I/You definition and change 'any' to 'each'.

5 years agoMerge "I" and "You" definitions for common handling of legal entity issue.
Richard Fontana [Mon, 18 Feb 2013 03:49:46 +0000 (22:49 -0500)]
Merge "I" and "You" definitions for common handling of legal entity issue.

5 years agoMerge 'No Trademark License' into section 1.
Richard Fontana [Mon, 18 Feb 2013 03:38:57 +0000 (22:38 -0500)]
Merge 'No Trademark License' into section 1.

5 years agoGeneralize copyleft nullification; define 'Give' Corresponding Source.
Richard Fontana [Mon, 18 Feb 2013 03:29:35 +0000 (22:29 -0500)]
Generalize copyleft nullification; define 'Give' Corresponding Source.

The 'poison pill' section is now titled "Copyleft Nullification" and
adds a second trigger: if the licensor provides only a binary without
providing Corresponding Source (as has sometimes been known to happen
with the initial licensor in GPL experience). Whether this is really
worth adding (at the cost of three lines and ~16 words) is open to

As a consequence of this change, the notion of providing Corresponding
Source was factored out of section 7 into a new definition of 'Give'
[Corresponding Source] in the final section, which is generalized to
cover any Distributor, including the initial licensor.

5 years agoignore
Richard Fontana [Sun, 17 Feb 2013 06:40:00 +0000 (01:40 -0500)]

5 years agoignore
Richard Fontana [Sun, 17 Feb 2013 06:34:57 +0000 (01:34 -0500)]

5 years agoAdd third-party beneficiary clause to object code distribution section.
Richard Fontana [Sun, 17 Feb 2013 04:19:58 +0000 (23:19 -0500)]
Add third-party beneficiary clause to object code distribution section.

This commit may be the most iconoclastic in the history of the
drafting of copyleft-next to date.

The intent of this change is that recipients of binaries, in addition
to the upstream copyright holder(s), will be able to enforce
compliance with the Corresponding Source requirements stated in the
section, if applicable law allows such a cause of action.

5 years agoFix line lengths.
Richard Fontana [Sat, 16 Feb 2013 23:42:49 +0000 (18:42 -0500)]
Fix line lengths.

5 years agoCombine object code distribution sections into one section.
Richard Fontana [Sat, 16 Feb 2013 23:38:44 +0000 (18:38 -0500)]
Combine object code distribution sections into one section.

5 years agoDelete unnecessary 'in any medium' from copyright license grant.
Richard Fontana [Sat, 16 Feb 2013 22:15:43 +0000 (17:15 -0500)]
Delete unnecessary 'in any medium' from copyright license grant.

This is ancient GPL phrasing. While harmless, I see no harm in
deleting it. The idea (the only objection I can anticipate) that the
deletion opens up some possible argument that some particular
*unspecified* 'medium' through which the copyright licensee exercises
the license grant is closed off through failure to say "in any medium"
is self-evidently preposterous.

5 years agoRevise copyright license grant language to use statutory language.
Pamela Chestek [Sat, 16 Feb 2013 20:09:53 +0000 (15:09 -0500)]
Revise copyright license grant language to use statutory language.


Issue noted by @pchestek:

    In the grant, my practice is to use the statutory language
    (admittedly U.S.) of the exclusive rights of the author so it's
    unassailably clear which rights you are licensing. If you don't
    like that, I would be ok with “copy” instead of "reproduce"
    (although there are statements in case law that “copy” is
    shorthand for “infringe any of the exclusive rights of the
    author,” so using the word “copy” leaves room for a little bit of
    mischief) but I have no idea what “make” might mean in a copyright
    context. (I think compiling the source code would be preparing
    derivative work, so that wouldn't be “making” a work.) You also
    should specifically grant the right to prepare derivative works –
    it's clearly intended and implied, but a little odd not to
    expressly state it when it's probably the most important right
    you're granted. I debated whether to say “prepare Derived Works”
    or “prepare derivative works” and decided the latter was right
    because then there couldn't be any ambiguity about whether there
    was some type of derivative work that the license didn't allow you
    to create, i.e., one that would be a derivative work but that
    wouldn't be a Derived Work. For the same reason I lower-cased
    “Distribute,” to make it clear that you were granting a license
    for all distribution rights, not just ones you define.

    You might want to consider looking at foreign law to see whether
    there are any other concepts you should include in the grant.

5 years agoFix line lengths.
Richard Fontana [Sat, 16 Feb 2013 19:35:12 +0000 (14:35 -0500)]
Fix line lengths.

5 years agoRemove explicit requirement for CS to be under 'this License'.
Richard Fontana [Sat, 16 Feb 2013 19:26:31 +0000 (14:26 -0500)]
Remove explicit requirement for CS to be under 'this License'.

This seems to cause more potential for conceptual puzzlement than is

Source code in the strictest sense (cf. GPLv3 definition of complete
source code) will need to comply with the conditions stated earlier in
the license anyway.

As for such things as build scripts, those that I have encountered
(and it is notable that they seem to be customarily treated as what
copyleft-next calls 'Separate Works') are of rather dubious
copyrightability. This will be all the more true of 'instructions and
similar information' and the new 'list of Separate Works'.

5 years agoFix line lengths.
Richard Fontana [Sat, 16 Feb 2013 18:50:05 +0000 (13:50 -0500)]
Fix line lengths.

5 years ago'Received Work' -> 'My Work'.
Richard Fontana [Sat, 16 Feb 2013 17:58:54 +0000 (12:58 -0500)]
'Received Work' -> 'My Work'.

"Received Work" is a suboptimal symbol for the underlying concept,
because what's being licensed is essentially what GPLv3 (using a term
from MPL 1.1) calls the 'contributor version' in its patent license
grant. It may or may not be identical to what is *actually* received
by "You", the downstream licensee.

This change may create or expose a further suboptimality, which is
that 'My Work' sounds like it might just cover "the things I added",
which is not the intention. A clarification to the definition of "My
Work" may be useful.

5 years agoRevert "Delete child-of-fair-use sentence in section 1."
Richard Fontana [Sat, 16 Feb 2013 15:25:56 +0000 (10:25 -0500)]
Revert "Delete child-of-fair-use sentence in section 1."

This reverts commit c2ac8dc3dd555fe8e481e8554385d318cc127bc5.

This is a result of reading Pam Chestek's comment on the mailing list:

5 years agoDelete child-of-fair-use sentence in section 1.
Richard Fontana [Sat, 16 Feb 2013 15:16:09 +0000 (10:16 -0500)]
Delete child-of-fair-use sentence in section 1.

This follows from discussion initiated by Luis Villa on the mailing
list concerning the generalization of the earlier language that was
proposed by Pam Chestek and implemented in 0.1.1.

I think the subject matter of this sentence is better stated in a FAQ.

5 years agoDouble hashmarks surrounding disclaimers for conspicuousness.
Luis Villa [Sat, 16 Feb 2013 03:24:09 +0000 (22:24 -0500)]
Double hashmarks surrounding disclaimers for conspicuousness.

As suggested by Luis Villa on the mailing list:

5 years agoMove definition of 'GPL' to section 5.
Richard Fontana [Sat, 16 Feb 2013 03:16:10 +0000 (22:16 -0500)]
Move definition of 'GPL' to section 5.

5 years agoEase comprehensibility of proprietary relicensing poison pill.
Richard Fontana [Sat, 16 Feb 2013 03:01:39 +0000 (22:01 -0500)]
Ease comprehensibility of proprietary relicensing poison pill.

One of the problems of drafting this provision is how to define
'proprietary license'. I do not know a good way to do so in positive
terms, so I've done so by trying to say what a proprietary license
*isn't*, with the expectation that this won't sweep in anything that
shouldn't be swept in. In the previous version, a proprietary license
effectively meant a license that wasn't (i) an authorized version of
copyleft-next, (ii) an OSI-approved license (as of the beginning of
2013), or (iii) a version of the GPL.

In this commit, I replace all that with the notion of compliance with
the Open Source Definition. (I don't think we can count on OSI
approval of any particular version of copyleft-next, let alone *all*
of them, so using "OSI-approved licenses" would require restoring the
separate reference to authorized versions of copyleft-next. That
actually may be worthwhile, despite the additional length.

Another issue with this provision is that the basic hack is a bit
non-obvious to the casual reader. I've addressed this already by
changing the section heading, but here I go a step further. Instead of
saying the immediately cryptic 'sections 4 through 8 no longer apply'
(as the casual reader may not have read those sections yet), in this
new version the copyleft-next verson nominally remains but the
licensor additionally licenses the Received Work under the Apache
License 2.0.

The reference to an external license instead of the technique of
making copyleft conditions of copyleft-next disappear represents a
significant loss of elegance, but the result is hopefully easier to

5 years ago'We' -> 'I'
Richard Fontana [Sat, 16 Feb 2013 01:20:58 +0000 (20:20 -0500)]
'We' -> 'I'

Use of 'We' to refer to a single-instance upstream licensor may be
more confusing than simply using singular 'I'. The only real
disadvantage to 'I' is that it seems out of place when talking about a
corporate licensor (in common US English, at least, corporations
typically refer to themselves using 'We').

5 years agoImprove title of section 3.
Richard Fontana [Sat, 16 Feb 2013 01:16:18 +0000 (20:16 -0500)]
Improve title of section 3.

5 years agoFix bug in poison pill introduced by deletion of old section 10.
Richard Fontana [Thu, 14 Feb 2013 03:57:36 +0000 (22:57 -0500)]
Fix bug in poison pill introduced by deletion of old section 10.

5 years agoAdd Martin Michlmayr to THANKS.
Richard Fontana [Tue, 12 Feb 2013 12:51:41 +0000 (07:51 -0500)]
Add Martin Michlmayr to THANKS.

5 years agoUpdate NEWS to reflect 0.1.1 release.
Richard Fontana [Tue, 12 Feb 2013 12:49:34 +0000 (07:49 -0500)]
Update NEWS to reflect 0.1.1 release.

5 years agoRemove trailing whitespace.
Richard Fontana [Tue, 12 Feb 2013 12:43:26 +0000 (07:43 -0500)]
Remove trailing whitespace.

5 years agoRemove full stops from section headers as I see no need for them.
Martin Michlmayr [Tue, 12 Feb 2013 05:31:36 +0000 (00:31 -0500)]
Remove full stops from section headers as I see no need for them.

5 years agoMerge branch 'master' of git://
Richard Fontana [Tue, 12 Feb 2013 05:14:36 +0000 (00:14 -0500)]
Merge branch 'master' of git://

5 years agoCosmetic fixes: fix formating of text
Martin Michlmayr [Sun, 10 Feb 2013 20:27:48 +0000 (20:27 +0000)]
Cosmetic fixes: fix formating of text

5 years agoIncorporate outbound GPL compatibility into basic copyleft provision.
Richard Fontana [Tue, 12 Feb 2013 04:39:52 +0000 (23:39 -0500)]
Incorporate outbound GPL compatibility into basic copyleft provision.

This commit deletes the 'Outbound GPL Compatibility' section and adds
a new paragraph to section 5, influenced by MPL 2.0's section 3.3.

With this change, outbound GPL compatibility is expressed as an
optional supplementary act that can be done when satisfying the
copyleft requirement. Distributed Derived Works must be licensed under
copyleft-next, but 'You' can *additionally* license the Derived Work
under any version of the GPL.

One thing that has changed here is that there is no explicit
permission to 'relicense' the *Received Work* (what You received,
unmodified, at least conceptually) under the GPL. It does not seem to
be necessary (much as the drafters of MPL 2.0 did not seem to regard
it as necessary to achieve downstream GPL/LGPL/AGPL compatibility
outside of the context of what the MPL calls 'Larger Works'). In any
case where outbound GPL compatibility is thought of as desirable or
necessary, we should be within the definition of 'Derived Work'.

5 years agoLimit section 10 to GPL compatibility.
Richard Fontana [Mon, 11 Feb 2013 21:38:28 +0000 (16:38 -0500)]
Limit section 10 to GPL compatibility.

It is not particularly useful or necessary to provide for outbound
AGPLv3+ compatibility (if we assume that future versions of the GPL
and AGPL will continue to be compatible to at least the same extent
GPLv3 and AGPLv3 are, an assumption that seems reasonable to make).

Since copyleft-next is outbound GPLv3 compatible, it is by definition
outbound AGPLv3 compatible. This allows for simplification of this
provision. Effective AGPLv3 compatibility can be noted in a FAQ.

Any value in specifically noting AGPL compatibility seems to be purely
political in nature. It is already a basic principle of copyleft-next
drafting that mere political benefit is never a good enough reason for
retention or inclusion of a license provision.

But that political value seems rather negligible in any case. AGPLv3
sees little use, most of it by proprietary relicensing companies or
entrepreneurs engaging in a licensing tactic that copyleft-next is
designed to discourage. By contrast, GPLv3 is a very widely used

5 years agoGeneralize child-of-fair-use clause further.
Richard Fontana [Mon, 11 Feb 2013 17:59:41 +0000 (12:59 -0500)]
Generalize child-of-fair-use clause further.

As proposed by Mike Linksvayer

5 years agoAdd README in Releases/ indicating license files aren't meant to be modified.
Richard Fontana [Sun, 10 Feb 2013 02:21:07 +0000 (21:21 -0500)]
Add README in Releases/ indicating license files aren't meant to be modified.

5 years agoChange conspicuousness marker in disclaimer provisions from '*' to '#'.
Richard Fontana [Sat, 9 Feb 2013 19:03:23 +0000 (14:03 -0500)]
Change conspicuousness marker in disclaimer provisions from '*' to '#'.

5 years agoAdd Tom Marble to THANKS.
Richard Fontana [Sat, 9 Feb 2013 18:59:46 +0000 (13:59 -0500)]
Add Tom Marble to THANKS.

5 years agoEliminates horizontal star lines delimiting disclaimer provisions.
Richard Fontana [Sat, 9 Feb 2013 18:52:28 +0000 (13:52 -0500)]
Eliminates horizontal star lines delimiting disclaimer provisions.

As suggested by Tom Marble
(see )

5 years agoAdd v0.1.1 in Releases/ directory. v0.1.1
Richard Fontana [Fri, 8 Feb 2013 06:29:12 +0000 (01:29 -0500)]
Add v0.1.1 in Releases/ directory.

5 years agoDelete 'would' from child-of-fair-use sentence.
Richard Fontana [Fri, 8 Feb 2013 06:15:09 +0000 (01:15 -0500)]
Delete 'would' from child-of-fair-use sentence.

5 years agoFix line lengths.
Richard Fontana [Fri, 8 Feb 2013 06:13:16 +0000 (01:13 -0500)]
Fix line lengths.

5 years agoDelete 'direct or indirect' from 'You' legal entity definition.
Richard Fontana [Fri, 8 Feb 2013 06:11:06 +0000 (01:11 -0500)]
Delete 'direct or indirect' from 'You' legal entity definition.

This is basically stylistic; the verb 'direct' is now used in
close proximity to the deleted words.

5 years agoShift word order in 'Distribute' definition.
Richard Fontana [Fri, 8 Feb 2013 05:47:16 +0000 (00:47 -0500)]
Shift word order in 'Distribute' definition.

In line with pchestek suggestion
(see: )

5 years agoDelete 'copyright permission' language in 'Distribute' definition.
Richard Fontana [Fri, 8 Feb 2013 05:44:00 +0000 (00:44 -0500)]
Delete 'copyright permission' language in 'Distribute' definition.

As suggested by pchestek:

 "'Distribute': I wanted to get rid of 'such that copyright permission
 is required' here too, plus I was troubled by the absence of an
 object in the sentence, so added that."


5 years agoFix line lengths.
Richard Fontana [Fri, 8 Feb 2013 05:41:04 +0000 (00:41 -0500)]
Fix line lengths.

5 years agoDelete unnecessary language from 'Derived Work' definition.
Richard Fontana [Fri, 8 Feb 2013 05:35:08 +0000 (00:35 -0500)]
Delete unnecessary language from 'Derived Work' definition.

As noted by pchestek: "such that copyright permission is required"
"doesn't add anything. A Derived Work by definition requires
permission to create; if it didn't it's not an infringement and the
license doesn't need to be invoked."

Though pchestek follows that with this note: "I agree, though, that it
seems clearer with the extra wording so it might be worth the
verbosity sacrifice."

5 years agoRemove ref. to pass-through in proprietary relicensing poison pill.
Richard Fontana [Fri, 8 Feb 2013 05:19:54 +0000 (00:19 -0500)]
Remove ref. to pass-through in proprietary relicensing poison pill.

As suggested by pchestek.

5 years agoRevise child-of-fair-use sentence to use pchestek's subsequent version.
Richard Fontana [Fri, 8 Feb 2013 05:15:21 +0000 (00:15 -0500)]
Revise child-of-fair-use sentence to use pchestek's subsequent version.

5 years agoRemove ref. to pass-through provision as 'condition' in section 4.
Richard Fontana [Fri, 8 Feb 2013 05:08:34 +0000 (00:08 -0500)]
Remove ref. to pass-through provision as 'condition' in section 4.

As suggested by pchestek in her github pull request.


5 years agoClarify intended immutability of files in Releases/.
Richard Fontana [Thu, 7 Feb 2013 06:38:55 +0000 (01:38 -0500)]
Clarify intended immutability of files in Releases/.

5 years agoExclude trademark legends from 'Legal Notices'.
Richard Fontana [Thu, 7 Feb 2013 05:43:27 +0000 (00:43 -0500)]
Exclude trademark legends from 'Legal Notices'.

As suggested by pchestek.

This is consistent with an earlier change in the copyleft-next
drafting history, and seems like a good clarification.

5 years agoBroaden fair use clause as suggested by pchestek.
Richard Fontana [Thu, 7 Feb 2013 05:09:47 +0000 (00:09 -0500)]
Broaden fair use clause as suggested by pchestek.


HBR cure: bkuhn made a very similar suggestion in our conversation on
the flight from Brussels to New York on 2013-02-04.

5 years agoDelete 'and otherwise transfer' from patent license grant.
Richard Fontana [Thu, 7 Feb 2013 04:58:43 +0000 (23:58 -0500)]
Delete 'and otherwise transfer' from patent license grant.

As suggested by pchestek.

5 years agoGet rid of explicit condition enumeration in section 1.
Richard Fontana [Thu, 7 Feb 2013 04:37:27 +0000 (23:37 -0500)]
Get rid of explicit condition enumeration in section 1.

Follows alternative suggestion of pchestek: see

5 years agoFollowed pchestek suggestion of using 'condition' in condition section titles.
Richard Fontana [Thu, 7 Feb 2013 04:35:17 +0000 (23:35 -0500)]
Followed pchestek suggestion of using 'condition' in condition section titles.

Not entirely sure I like this. It can save a line from current section
1 but at the cost of increasing the word count. :-)

5 years agoSpecify conditions in section 1 (per suggestion from pchestek).
Richard Fontana [Thu, 7 Feb 2013 04:17:24 +0000 (23:17 -0500)]
Specify conditions in section 1 (per suggestion from pchestek).

Query whether this makes section 3 less clear.

5 years agoMoved section 6 to follow current section 9 per pchestek suggestion.
Richard Fontana [Thu, 7 Feb 2013 04:08:22 +0000 (23:08 -0500)]
Moved section 6 to follow current section 9 per pchestek suggestion.


5 years agoAdd Pamela Chestek to THANKS.
Richard Fontana [Thu, 7 Feb 2013 03:46:21 +0000 (22:46 -0500)]
Add Pamela Chestek to THANKS.

5 years agoFix line lengths.
Richard Fontana [Thu, 7 Feb 2013 03:43:24 +0000 (22:43 -0500)]
Fix line lengths.

5 years agoRevise 'You' definition as suggested by Pam Chestek.
Richard Fontana [Thu, 7 Feb 2013 03:40:17 +0000 (22:40 -0500)]
Revise 'You' definition as suggested by Pam Chestek.


5 years agoFix whitespace in license draft.
Richard Fontana [Wed, 6 Feb 2013 14:31:24 +0000 (09:31 -0500)]
Fix whitespace in license draft.

Thanks to Max Thoursie for pointing out this issue in

5 years agoFix whitespace in
Richard Fontana [Wed, 6 Feb 2013 14:28:48 +0000 (09:28 -0500)]
Fix whitespace in

5 years agoMerge commit 'refs/merge-requests/28' of git://
Richard Fontana [Wed, 6 Feb 2013 08:24:10 +0000 (03:24 -0500)]
Merge commit 'refs/merge-requests/28' of git:// into merge-requests/28

5 years agoBelatedly add Germán Poo-Caamaño to THANKS.
Richard Fontana [Tue, 29 Jan 2013 04:53:19 +0000 (23:53 -0500)]
Belatedly add Germán Poo-Caamaño to THANKS.

5 years agoBelatedly add Michał Masłowski to THANKS.
Richard Fontana [Tue, 29 Jan 2013 04:05:23 +0000 (23:05 -0500)]
Belatedly add Michał Masłowski to THANKS.

5 years agomodified: copyleft-next 28
Stephen Michael Kellat [Mon, 28 Jan 2013 19:24:06 +0000 (14:24 -0500)]
modified: copyleft-next

This will allow for proper handling by Pandoc and other handling tools because it removes two curly marks for straight quote marks.

5 years agoAdd Stephen Michael Kellat to THANKS.
Richard Fontana [Mon, 28 Jan 2013 06:30:48 +0000 (01:30 -0500)]
Add Stephen Michael Kellat to THANKS.

5 years agoAdd Joshua Gay to THANKS.
Richard Fontana [Mon, 28 Jan 2013 06:29:04 +0000 (01:29 -0500)]
Add Joshua Gay to THANKS.

5 years agoUpdated NEWS to note 0.1.0 release and delete FedoraHosted reference.
Richard Fontana [Sun, 27 Jan 2013 23:37:08 +0000 (18:37 -0500)]
Updated NEWS to note 0.1.0 release and delete FedoraHosted reference.

5 years agoAdd v0.1.0 in Releases directory. v0.1.0
Richard Fontana [Sat, 26 Jan 2013 05:05:05 +0000 (00:05 -0500)]
Add v0.1.0 in Releases directory.

5 years agoMinor stylistic changes in informational files.
Richard Fontana [Wed, 23 Jan 2013 03:21:30 +0000 (22:21 -0500)]
Minor stylistic changes in informational files.

Prior uses of "copyleft-next project" are changed either to
"copyleft-next" or to "Copyleft-Next Project" (the latter being
consistent with the use in the current version of the license text).

5 years agoAdd example to category (iii) in Corresponding Source definition.
Richard Fontana [Wed, 23 Jan 2013 03:16:41 +0000 (22:16 -0500)]
Add example to category (iii) in Corresponding Source definition.

5 years agoFix line lengths.
Richard Fontana [Wed, 23 Jan 2013 03:00:41 +0000 (22:00 -0500)]
Fix line lengths.

5 years ago"from a network location" => "through a computer network" (sec. 9).
Richard Fontana [Wed, 23 Jan 2013 02:58:18 +0000 (21:58 -0500)]
"from a network location" => "through a computer network" (sec. 9).

This phrasing is similar to what is used in A/GPLv3 section 0
(qualification of 'convey' definition) and AGPLv3 section 13 paragraph

5 years ago'at no further charge' => 'at no charge' (section 9).
Richard Fontana [Tue, 22 Jan 2013 06:43:57 +0000 (01:43 -0500)]
'at no further charge' => 'at no charge' (section 9).

See: GPLv3 Third Discussion Draft Rationale p. 48, n. 52 (clarifying
the phrase "at no extra charge" which was added in GPLv3 Discussion
Draft 2).

I believe it is clear enough without the word 'further'.

5 years agoClarify in sec. 8: 2-year period is from Your last Distribution date.
Richard Fontana [Tue, 22 Jan 2013 05:59:18 +0000 (00:59 -0500)]
Clarify in sec. 8: 2-year period is from Your last Distribution date.

5 years agoFix line lengths.
Richard Fontana [Tue, 22 Jan 2013 05:56:41 +0000 (00:56 -0500)]
Fix line lengths.

5 years agoRemove 'additional Source Code files' from CS definition.
Richard Fontana [Tue, 22 Jan 2013 05:50:34 +0000 (00:50 -0500)]
Remove 'additional Source Code files' from CS definition.

The (rare) case I was concerned about is probably best treated as
involving 'Separate Works', potentially copyleft-next-incompatible or
even proprietary.

5 years agoIgnore.
Richard Fontana [Tue, 22 Jan 2013 05:19:38 +0000 (00:19 -0500)]

5 years agoMinor phrase substitution in child-of-Liberty-or-Death sentence.
Richard Fontana [Tue, 22 Jan 2013 05:11:22 +0000 (00:11 -0500)]
Minor phrase substitution in child-of-Liberty-or-Death sentence.

5 years agoMerge paragraphs in section 7.
Richard Fontana [Tue, 22 Jan 2013 05:09:11 +0000 (00:09 -0500)]
Merge paragraphs in section 7.

5 years agoChange 'published' to 'released' in section 12 for consistency.
Richard Fontana [Tue, 22 Jan 2013 04:57:58 +0000 (23:57 -0500)]
Change 'published' to 'released' in section 12 for consistency.