Changeset - d55d2787c8a5
[Not reviewed]
0 1 0
donaldr3 - 10 years ago 2014-03-21 19:56:37
donald@copyrighteous.office.fsf.org
removed 'that'
1 file changed with 1 insertions and 1 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -943,25 +943,25 @@ copyleft differs.  Specifically, copyleft works only because of its
 
requirement that downstream licensors use the \textit{same} license for
 
combined and modified works.  As such, software licensed under the terms of
 
``GPLv2-only'' cannot be combined with works licensed ``GPLv3-or-later''.
 
This is admittedly a frustrating outcome.
 

	
 
Other copyleft licenses that appeared after GPL, such
 
as the Creative Commons ``Share Alike'' licenses, the Eclipse Public License
 
and the Mozilla Public License \textbf{require} all copyright holders choosing
 
to use any version of those licenses to automatically accept and relicense
 
their copyrighted works under new versions.  Of course ,Creative Commons, the
 
Eclipse Foundation, and the Mozilla Foundation (like the FSF) have generally
 
served as excellent stewards of their licenses.  Copyright holders using
 
those licenses seems to find it acceptable that to fully delegate all future
 
those licenses seems to find it acceptable to fully delegate all future
 
licensing decisions for their copyrights to these organizations without a
 
second thought.
 

	
 
However, note that FSF gives herein the control of copyright holders to
 
decide whether or not to implicitly trust the FSF in its work of drafting
 
future GPL versions.  The FSF, for its part, does encourage copyright holders
 
to chose by default ``GPLv$X$-or-later'' (where $X$ is the most recent
 
version of the GPL published by the FSF).  However, the FSF \textbf{does not
 
  mandate} that a choice to use any GPL requires a copyright holder ceding
 
its authority for future licensing decisions to the FSF.  In fact, the FSF
 
considered this possibility for GPLv3 and chose not to do so, instead opting
 
for the third-party steward designation clause discussed in
0 comments (0 inline, 0 general)