[PATCH v2 0/6] copyleft-next: project name / remove anti-tivoization clause

[PATCH v2 0/6] copyleft-next: project name / remove anti-tivoization clause

[Luis R. Rodriguez]

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

My last series of patches require a rebase based on the
latest changes, so patches 1-4 are a simple rebase.
Patch 5 and 6 address removing the anti-tivoization
clause, section 7. This will at the very least clarify
whether or not copyleft-next can or cannot be considered
as a licensing project with hopes of using it for the
Linux kernel.

Given copyleft-next's focus on separating from the
Church and in my views any possible 'corporate taint',
I'm in hopes that copyleft-next *can* consider the
Linux kernel community as a possible future and
valuable stakeholder.

Luis R. Rodriguez (6):
  copyleft-next: remove issue tracker references
  copyleft-next: more project name updates Copyleft.next->copyleft-next
  copyleft-next: rename the file COPYLEFT.next to copyleft-next
  copyleft-next: embrace the Signed-off-by practice
  copyleft-next: remove section 7 - Tivoization
  copyleft-next: re-enumerate sections

 ABOUT                          |   10 ++---
 CONTRIBUTING                   |   45 ++++++++++++++------
 COPYLEFT.next => copyleft-next |   90 ++++++++++------------------------------
 3 files changed, 60 insertions(+), 85 deletions(-)
 rename COPYLEFT.next => copyleft-next (82%)

-- 
1.7.10.rc1.22.gf5241

[PATCH v2 1/6] copyleft-next: remove issue tracker references

[Luis R. Rodriguez]

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

This uses github, lets not confuse the focus for
development for now.
---
 CONTRIBUTING |   13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 1db3cd2..d06f5da 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -47,15 +47,4 @@ Public Source Locations
 =======================
 
 Gitorious (https://gitorious.org/copyleft-next) is now the centralized
-location of source for this project. It will be mirrored at a GitHub
-repo (currently https://github.com/richardfontana/Copyleft.next) for
-the time being, and perhaps indefinitely.
-
-
-Issue Tracking
-==============
-
-The issue tracker associated with
-https://github.com/richardfontana/Copyleft.next shall be kept open for the
-time being, but at some point it is likely to be disabled.
-
+location of source for this project.
-- 
1.7.10.rc1.22.gf5241

[PATCH v2 2/6] copyleft-next: more project name updates Copyleft.next->copyleft-next

[Luis R. Rodriguez]

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

This reflects the present gitorious.org name and reflects
better with other foo-next git trees out there.
---
 ABOUT         |   10 +++++-----
 COPYLEFT.next |    6 +++---
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/ABOUT b/ABOUT
index eaaa878..6eeef4b 100644
--- a/ABOUT
+++ b/ABOUT
@@ -1,14 +1,14 @@
-Copyleft.next
+copyleft-next
 =============
 
 "Exploring ideas for a modified copyleft license can't hurt."
     - Richard M. Stallman, July 2012
 
-Copyleft.next is an experimental "-ng"-type modification of the GNU
+copyleft-next is an experimental "-ng"-type modification of the GNU
 General Public License, version 3. (It is *not* a fork.)
 Contributions of patches, ideas, and criticism are welcome.  Needless
 to say, no one should actually *use* a development version of
-Copyleft.next as an actual license. Anyone interested in actually
+copyleft-next as an actual license. Anyone interested in actually
 *using* a strong copyleft license for code will wish to use one or
 more of the following licenses: GNU GPLv2, GNU GPLv3, GNU AGPLv3,
 and/or later versions of those licenses. For more information, see
@@ -20,7 +20,7 @@ with (e.g.) Red Hat, or any other corporate entity.** Contributors are
 expected to participate in their individual capacity.
 
 All communications with journalists shall be handled by the
-Copyleft.next Marketing Committee, which does not exist yet and
+copyleft-next Marketing Committee, which does not exist yet and
 probably won't exist for at least another year or three. For the
 avoidance of doubt, Simon Phipps is not considered a
 journalist.
@@ -35,7 +35,7 @@ existing (and future) versions of the GNU GPL, which addresses one of
 the FSF's concerns about modified versions of the GNU GPL.
 
 The meta-license from the FSF stated in its FAQ shall be the license
-of all versions of the Copyleft.next license text (to the extent that
+of all versions of the copyleft-next license text (to the extent that
 such versions retain any copyrightable material from versions of the
 GNU GPL in which the FSF has asserted copyright). Based on the FSF
 FAQ, that meta-license may be stated as follows:
diff --git a/COPYLEFT.next b/COPYLEFT.next
index ec2fc07..32f1274 100644
--- a/COPYLEFT.next
+++ b/COPYLEFT.next
@@ -1,4 +1,4 @@
-                             Copyleft.next
+                             copyleft-next
 
   0. Definitions.
 
@@ -392,9 +392,9 @@ survive such relicensing.
   14. New Versions of this License.
 
   The initial License Steward is [?]. The License Steward may publish
-new versions of Copyleft.next.  Each version will be given a
+new versions of copyleft-next.  Each version will be given a
 distinguishing version number. You may distribute a Covered Work under
-the terms of the version of Copyleft.next under which the Program is
+the terms of the version of copyleft-next under which the Program is
 licensed, or under the terms of any subsequent version published by
 the License Steward.
 
-- 
1.7.10.rc1.22.gf5241

[PATCH v2 3/6] copyleft-next: rename the file COPYLEFT.next to copyleft-next

[Luis R. Rodriguez]

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

Also update the CONTRIBUTING to reflect the new file name
change.
---
 CONTRIBUTING                   |    2 +-
 COPYLEFT.next => copyleft-next |    0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename COPYLEFT.next => copyleft-next (100%)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index d06f5da..8f214b1 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -1,7 +1,7 @@
 
 Contributions of any sort (text suggestions, ideas, feedback,
 criticism) from all interested individuals are welcome and encouraged.
-All original contributions to Copyleft.next are dedicated to the
+All original contributions to copyleft-next are dedicated to the
 public domain to the maximum extent permitted by applicable law,
 pursuant to CC0. See CC0 for further details.
 
diff --git a/COPYLEFT.next b/copyleft-next
similarity index 100%
rename from COPYLEFT.next
rename to copyleft-next
-- 
1.7.10.rc1.22.gf5241

[PATCH v2 4/6] copyleft-next: embrace the Signed-off-by practice

[Luis R. Rodriguez]

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

The idea is taken from Linus Torvald's subsurface
project [0] README file. The Signed-off-by is widely
used in public projects and we stand to gain to make
its usage more prevalent. The meaning of the
Signed-off-by is borrowed from the Linux kernel's.

[0] git://github.com/torvalds/subsurface.git

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
 CONTRIBUTING |   30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 8f214b1..966366c 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -5,6 +5,36 @@ All original contributions to copyleft-next are dedicated to the
 public domain to the maximum extent permitted by applicable law,
 pursuant to CC0. See CC0 for further details.
 
+Please either send me signed-off patches or a pull request with
+signed-off commits.  If you don't sign off on them, I will not accept
+them. This means adding a line that says "Signed-off-by: Name <email>"
+at the end of each commit, indicating that you wrote the code and have
+the right to pass it on as an open source patch.
+
+See: http://gerrit.googlecode.com/svn/documentation/2.0/user-signedoffby.html
+
+Also, please write good git commit messages.  A good commit message
+looks like this:
+
+	Header line: explaining the commit in one line
+
+	Body of commit message is a few lines of text, explaining things
+	in more detail, possibly giving some background about the issue
+	being fixed, etc etc.
+
+	The body of the commit message can be several paragraphs, and
+	please do proper word-wrap and keep columns shorter than about
+	74 characters or so. That way "git log" will show things
+	nicely even when it's indented.
+
+	Reported-by: whoever-reported-it
+	Signed-off-by: Your Name <youremail@yourhost.com>
+
+where that header line really should be meaningful, and really should be
+just one line.  That header line is what is shown by tools like gitk and
+shortlog, and should summarize the change in one readable line of text,
+independently of the longer explanation.
+
 Contributions from individual free/libre/open source software project
 participants, regardless of their views on copyleft, and regardless of
 their opinions on existing licenses such as the GNU GPLv2 and its
-- 
1.7.10.rc1.22.gf5241

[PATCH v2 5/6] copyleft-next: remove section 7 - anti-tivoization

[Luis R. Rodriguez]

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

The anti-tivoization clauses must go if we want this license
to be ever considered for usage with the Linux kernel.
This patch removes that entire section.

The re-enumerating of the sections is done separately
to make it easier for review.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
 copyleft-next |   56 ++++++--------------------------------------------------
 1 file changed, 6 insertions(+), 50 deletions(-)

diff --git a/copyleft-next b/copyleft-next
index 32f1274..fdb20c2 100644
--- a/copyleft-next
+++ b/copyleft-next
@@ -153,17 +153,15 @@ conditions:
     You modified the Program, and giving a relevant date.
 
     b) The Derivative Work must carry prominent notices stating that
-    it is released under this License and any conditions added under
-    section 7.  This requirement modifies the requirement in section 3
-    to "keep intact all notices".
+    it is released under this License. This requirement modifies the
+    requirement in section 3 to "keep intact all notices".
 
     c) You must license the entire Derivative Work, as a whole, under
     this License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the Derivative Work, and all its
-    parts, regardless of how they are packaged. However, if We license
-    a Covered Work under Proprietary Terms, this subsection c shall
-    not apply to Your Derivative Work.
+    License will therefore apply to the whole of the Derivative Work,
+    and all its parts, regardless of how they are packaged. However,
+    if We license a Covered Work under Proprietary Terms, this
+    subsection c shall not apply to Your Derivative Work.
 
     d) If the Program's interactive user interfaces display Legal
     Notices, such Legal Notices must be preserved by Your Derivative
@@ -221,48 +219,6 @@ ways:
          noncommercially, and only if You received the Object Code
          with such an offer, in accord with the preceding option.
 
-  7. User Product Lockdown.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to
-install and execute Derivative Works of a Covered Work in that User
-Product from a Derivative Work of its Corresponding Source.  The
-information must suffice to ensure that the continued functioning of
-the Object Code Derivative Work is in no case prevented or interfered
-with solely because modification has been made.
-
-  If You distribute an Object Code work under section 5 in, or with,
-or specifically for use in, a User Product, and the distributing
-occurs as part of a transaction in which the right of possession and
-use of the User Product is transferred to the recipient in perpetuity
-or for a fixed term (regardless of how the transaction is
-characterized), the Corresponding Source distributed under this
-section must be accompanied by the Installation Information.  But this
-requirement does not apply if neither You nor any third party retains
-the ability to install modified Object Code on the User Product (for
-example, the work has been installed in non-field-modifiable ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
   8. Additional Terms.
 
   Notwithstanding any other provision of this License, for material
-- 
1.7.10.rc1.22.gf5241

[PATCH v2 6/6] copyleft-next: re-enumerate sections

[Luis R. Rodriguez]

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

After the removal of the Tivoization clauses the sections
numbers required an update, this updates those section numbers
and its references.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
 copyleft-next |   28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/copyleft-next b/copyleft-next
index fdb20c2..df141d7 100644
--- a/copyleft-next
+++ b/copyleft-next
@@ -119,7 +119,7 @@ equivalents.
 
   No Covered Work shall be deemed part of an effective technological
 measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
+10 of the WIPO copyright treaty adopted on 20 December 1996, or
 similar laws prohibiting or restricting circumvention of such
 measures.
 
@@ -219,13 +219,13 @@ ways:
          noncommercially, and only if You received the Object Code
          with such an offer, in accord with the preceding option.
 
-  8. Additional Terms.
+  7. Additional Terms.
 
   Notwithstanding any other provision of this License, for material
 You add to a Covered Work, You may (if authorized by the copyright
 holders of that material) supplement the terms of this License with
 terms (a) disclaiming warranty or limiting liability differently from
-the terms of sections 15 and 16 of this License; (b) requiring
+the terms of sections 14 and 15 of this License; (b) requiring
 preservation of specified reasonable legal notices or textual author
 attributions in that material; (c) prohibiting misrepresentation of
 the origin of that material, or requiring that modified versions of
@@ -236,7 +236,7 @@ rights under trademark law for use of trade names, trademarks, or
 service marks.
 
   All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 9.  If the Program as You
+restrictions" within the meaning of section 8.  If the Program as You
 received it, or any part of it, contains a notice stating that it is
 governed by this License along with a term that is a further
 restriction, You may remove that term.  If a license document contains
@@ -248,13 +248,13 @@ does not survive such relicensing or distributing.
   Additional terms may be stated in the form of a separately written
 license or stated as qualifications of this License.
 
-  9. Termination.
+  8. Termination.
 
   You may not copy, distribute or modify a Covered Work except as
 expressly provided under this License.  Any unauthorized act of
 copying, distribution or modification automatically terminates Your
 rights under this License (including any patent licenses granted under
-the third paragraph of section 11).
+the third paragraph of section 10).
 
   However, if You cease all violation of this License, then Your
 license from a particular copyright holder is reinstated (a)
@@ -274,15 +274,15 @@ Your receipt of the notice.
 licenses of parties who have received copies or rights from You under
 this License.  If Your rights have been terminated and not permanently
 reinstated, You do not qualify to receive new licenses for the same
-material under section 9.
+material under section 8.
 
-  10. Automatic Licensing of Downstream Recipients.
+  9. Automatic Licensing of Downstream Recipients.
 
   Each time You distribute a Covered Work, the recipient automatically
 receives permission from Us to run, copy, modify and distribute the
 Covered Work, subject to this License.
 
-  11. No Further Restrictions; Liberty-or-Death.
+  10. No Further Restrictions; Liberty-or-Death.
 
   You may not impose any further restrictions on the exercise of the
 rights granted or affirmed under this License. Further restrictions
@@ -321,7 +321,7 @@ or commitment, however denominated, not to enforce a patent (such as
 an express permission to practice a patent or covenant not to sue for
 patent infringement).
 
-  12. Patent License Grant.
+  11. Patent License Grant.
 
   Each one of Us grants You a non-exclusive, worldwide, royalty-free
 patent license under Essential Patent Claims in Our respective
@@ -337,7 +337,7 @@ worldwide, royalty-free patent license under Essential Patent Claims
 in Your Derivative Work, to make, use, sell, offer for sale, import
 and otherwise transfer the contents of Your Derivative Work.
 
-  13. Compatibility with GNU Strong Copyleft Licenses.
+  12. Compatibility with GNU Strong Copyleft Licenses.
 
   Notwithstanding any other provision of this License, You have
 permission to relicense any Covered Work under the terms of any
@@ -345,7 +345,7 @@ version of a GNU Strong Copyleft License. No condition of this License
 that would conflict with the chosen GNU Strong Copyleft License shall
 survive such relicensing.
 
-  14. New Versions of this License.
+  13. New Versions of this License.
 
   The initial License Steward is [?]. The License Steward may publish
 new versions of copyleft-next.  Each version will be given a
@@ -354,7 +354,7 @@ the terms of the version of copyleft-next under which the Program is
 licensed, or under the terms of any subsequent version published by
 the License Steward.
 
-  15. Disclaimer of Warranty.
+  14. Disclaimer of Warranty.
 
   To the extent permitted by applicable law, the Program is provided
 under this License on an "as is" basis, without warranty of any kind,
@@ -367,7 +367,7 @@ necessary servicing, repair or correction.  This disclaimer of
 warranty constitutes an essential part of this License. No use of the
 Program is authorized under this License except under this disclaimer.
 
-  16. Limitation of Liability.
+  15. Limitation of Liability.
 
   In no event unless required by applicable law or agreed to in
 writing will any copyright holder, or any other party who modifies
-- 
1.7.10.rc1.22.gf5241

Re: [PATCH v2 5/6] copyleft-next: remove section 7 - anti-tivoization

[Alan Cox]

On Thu, 12 Jul 2012 10:48:44 -0700
"Luis R. Rodriguez" <mcgrof@do-not-panic.com> wrote:

> From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
> 
> The anti-tivoization clauses must go if we want this license
> to be ever considered for usage with the Linux kernel.
> This patch removes that entire section.

The kernel license won't be changing anyway. It's too big a task to
figure out. Plus if you want to change license and the new license
doesn't contain protection against DRM abusers then I for one will be
withholding my permission to change it until one is added, because the
existing GPLv2 protection while unclear is there and remains to be
litigated.

Given there are people who hold the reverse true your lock detector
should have spewed ...


There are much more important things a GPL-next needs because of its use
beyond software - protection against "design right" and "design patent"
abuses. Without that the current habit of using the GPL for 3D print
designs is potentially going to end in tears.

The way to allow DRM abuse is to have a "lesser" license which allows
abuse, just as with lesser licenses for linking.

Alan