[Savannah-cvs] administration/docs/hacking_savannah hacking_sa...

[Sylvain Beucler]

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        04/12/04 09:18:33

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        Added a paragraph about dual-licensing, and precised the use of GPL 
exceptions.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.78&tr2=1.79&r1=text&r2=text

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.78 
administration/docs/hacking_savannah/hacking_savannah.texi:1.79
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.78     Fri Dec 
 3 20:19:36 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Sat Dec  4 
09:18:33 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.78 2004/12/03 20:19:36 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.79 2004/12/04 09:18:33 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -2710,12 +2710,29 @@
 @url{http://www.gnu.org/@/licenses/@/gpl-faq.html#GPLIncompatibleLibs}. We
 feel it is a delicate point and urge you to contact the GPL Compliance
 Lab in such case. In addition, this solution is not recommended, as
-the project will be incompatible with the GNU GPL (the exception is
-not part of the standard GNU GPL). Anyone can remove this
-``exception'' though.
+the project will be in a way incompatible with the GNU GPL (the
+exception is not part of the standard GNU GPL). Anyone can remove this
+``exception'' though. Keep in mind that this solution does not work in
+all cases. For example, one cannot release a GPL'd plug-in for Eclipse
+(released under the Eclipse Public License or EPL) ; it would require
+an exception from the Eclipse copyright holders as well.
+
+Another solution is to use dual licensing. For the Eclipse issue
+mentioned above, and if you're the sole copyright holder, you can
+simply add a notice like the following:
 
-Another solution we do not recommand either is to switch from the GNU
-GPL to the Expat license. This solves the incompatibility, but the
address@hidden
+You may copy, modify, and redistribute this file under the terms of the
+GNU General Public License version 2 (or, at your option, any later
+version), and/or the Eclipse Public License version 1.0.
+
+[standard GPL notice]
+
+[standard EPL notice]
address@hidden quotation
+
+Yet another solution we do not recommand either is to switch from the
+GNU GPL to the Expat license. This solves the incompatibility, but the
 project also lose its copyleft.
 
 The GNU Lesser General Public License (LGPL) is basically compatible