[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [804] merge GNU GPL with GNU LGPL, add GNU AGPL to the sa
From: |
ineiev |
Subject: |
[Savannah-cvs] [804] merge GNU GPL with GNU LGPL, add GNU AGPL to the same section |
Date: |
Fri, 27 Sep 2024 11:48:21 -0400 (EDT) |
Revision: 804
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=804
Author: ineiev
Date: 2024-09-27 11:48:20 -0400 (Fri, 27 Sep 2024)
Log Message:
-----------
merge GNU GPL with GNU LGPL, add GNU AGPL to the same section
Modified Paths:
--------------
trunk/sviki/ValidNotices.mdwn
Modified: trunk/sviki/ValidNotices.mdwn
===================================================================
--- trunk/sviki/ValidNotices.mdwn 2024-09-27 15:35:00 UTC (rev 803)
+++ trunk/sviki/ValidNotices.mdwn 2024-09-27 15:48:20 UTC (rev 804)
@@ -38,41 +38,33 @@
is worth reading (although some parts are specific to GNU packages):
<http://www.gnu.org/prep/maintain/html_node/Legal-Matters.html>
-## GNU GPL
+## GNU AGPL, GNU GPL, GNU LGPL
In order to release your project properly and unambiguously under the
-GNU GPL, please place copyright notices and permission-to-copy
-statements at the beginning of every copyrightable file, usually any
+GNU AGPL, GNU GPL, or GNU LGPL, please place copyright notices and license
+notices at the beginning of every copyrightable file, usually any
file more than 10 lines long.
In addition, if you haven't already, please include a copy of the plain
-text version of the GPL, available from
-<http://www.gnu.org/licenses/gpl.txt>,
-into a file named "COPYING".
+text version of the GPL, available from <http://www.gnu.org/licenses/gpl.txt>,
+into a file named COPYING. (If your license is the GNU AGPL,
+use the respective text from <http://www.gnu.org/licenses/agpl.txt>.)
-For more information, see
-<http://www.gnu.org/licenses/gpl-howto.html>.
+The current version of the LGPL (version 3.0) is written as a set
+of additional permissions on top of the GPL version 3.0; so if your
+license is the LGPL, add *both* a copy of the GPL in a file named COPYING
+and a copy of the LGPL in a file named COPYING.LESSER.
+For information on what license notices should look like, and
+for more information on the procedures, see
+<http://www.gnu.org/licenses/gpl-howto.html>. Please use the exact
+form of the license notices recommended in that article.
+
The GPL FAQ explains why these procedures must be followed. To learn why
a copy of the GPL must be included with every copy of the code, for
example, see
<http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude>.
-## GNU LGPL
-
-In order to release your project properly and unambiguously under the
-LGPL, please place copyright notices and permission-to-copy statements
-at the beginning of every copyrightable file, usually any file more than
-10 lines long.
-
-In addition, if you haven't already, please include a copy of the plain
-text version of the GNU LGPL, available from
-<http://www.gnu.org/licenses/lgpl.txt>,
-into a file named "COPYING".
-
-For more information, see
-<http://www.gnu.org/licenses/lgpl.html>.
-
## GFDL
In order to release your project properly and unambiguously under the
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [804] merge GNU GPL with GNU LGPL, add GNU AGPL to the same section,
ineiev <=