[Savannah-cvs] [543] update links, merge news entry, reformat headings

[ineiev]

Revision: 543
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=543
Author:   ineiev
Date:     2023-02-06 03:05:40 -0500 (Mon, 06 Feb 2023)
Log Message:
-----------
update links, merge news entry, reformat headings

Modified Paths:
--------------
    trunk/sviki/LicensingRequirements.mdwn

Modified: trunk/sviki/LicensingRequirements.mdwn
===================================================================
--- trunk/sviki/LicensingRequirements.mdwn      2023-02-05 18:35:23 UTC (rev 
542)
+++ trunk/sviki/LicensingRequirements.mdwn      2023-02-06 08:05:40 UTC (rev 
543)
@@ -1,19 +1,24 @@
-Requirement
------------
+# Licensing requirements
 
-### Software
+The practice of verifying all licenses for consistency is an important
+aspect of Savannah policies.
 
-Your license should be compatible with the GNU GPL, current version or
-later. (This includes LGPL2.\*-only, since those LGPL versions can be
-converted to the GPL version 2 or later. Of course, we strongly recommend
-against using LGPL\*-only. And GPL\*-only is not acceptable.)
+## Software
 
-### Manuals
+Your license should be compatible with the GNU GPL, current version and
+any later version.  This includes LGPL2.\*-only, since those LGPL versions
+can be converted to the GPL version 2 or later.  It also includes
+LGPLv3-or-later because we assume that the future versions fo the LGPL
+will be compatible with the corresponding version of the GPL.  Of course,
+we strongly recommend against using LGPL\*-only.  And GPL\*-only is not
+acceptable.
 
+## Manuals
+
 Your license should be compatible with the GNU FDL, current version or
 later.
 
-### Others
+## Others
 
 We accept any free license for images and other data that are a
 secondary part of a package that is mainly software.
@@ -20,30 +25,38 @@
 
 In any case, you cannot rely on incompatible dependencies.
 
-Explanation
------------
+## Explanation
 
-These licenses are the ones that the GNU project uses for its own
+These licenses are the ones that the GNU Project uses for its own
 packages, and recommends for everybody else to use. They are also the
 most widespread, and being incompatible with them is a practical
 problem, because you would then be unable to combine code under those
 licenses with yours, and vice versa, even if it is free software.
 
-Well-known licenses compatible with the GNU GPL are listed at
-<http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses>.
+Well-known licenses compatible with the GNU GPL are listed in the [dedicated
+secion](//www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses)
+of the GNU license list.
 
+### Documentation
+
 Informal materials, FAQs, and so on can be under a license compatible
 with either the GNU GPL or the GFDL (or both). Manuals themselves needs
 a license compatible with the GFDL.
 
-In some case, it may be useful to dual license your application - that
-is, release it under two different licenses - to meet this criteria. See
-[[DualLicensing]] for details.
+Historically released manuals (before 2006) of hosted non-GNU packages
+which were licensed under GPL-2-or-later can remain on Savannah
+with their licenses, though we would like to change them if possible.
+However, existing manuals with other GFDL-incompatible licenses
+represent bigger problems, that we need to solve sooner or later.
+In addition, it is vital for all documentation files to have clear
+statements of their licenses.
 
-<https://savannah.gnu.org/forum/forum.php?forum_id=4303>
-describes more rationale with respect to requiring the GFDL for the
-manuals' license (and needs to be merged here).
+In some case, it may be useful to [[dual license|DualLicensing]] your
+application - that is, release it under two different licenses - to
+meet this criterion.
 
+### Dependencies
+
 Your project dependencies also need to be compatible with the license
 you chose. This is not a Savannah-specific requirement, because doing
 otherwise would make your project legally inconsistent, and as such not
@@ -54,30 +67,30 @@
 incompatible. However, you can combine GNU GPL'd code with code released
 under the Expat license.
 
-licensing@fsf.org, that is, the FSF Licensing Team, may offer
+The [FSF Licensing Team](mailto://licensing@fsf.org), may offer
 suggestions to find the best way to handle legal issues.
 
+### "Free" is for freedom
+
 For non-software, non-documentation works, when we say "free" this
-refers to
-<http://www.gnu.org/philosophy/free-sw.html>.
-Licenses listed as "free" at
-<http://www.gnu.org/licenses/license-list.html>
-(whatever the kind of work) are good examples.
+refers to [freedom](//www.gnu.org/philosophy/free-sw.html).
+Licenses listed as free in the [GNU license
+list](//www.gnu.org/licenses/license-list.html) are good examples.
 
 
<http://lists.gnu.org/mailman/private/savannah-hackers-private/2005-July/000142.html>
 (private archive) is the discussion thread with RMS about that point,
 and is summed-up in the previous sentence.
 
-Fonts: there's an interesting article at
-<http://www.fsf.org/blogs/licensing/20050425novalis>
+Fonts: there's an [interesting
+article](https://www.fsf.org/blogs/licensing/20050425novalis) on www.fsf.org.
 
-#### subtopics:
+## Subtopics
 
--   [[DocumentationFormats]]
--   [[DocumentationNotices]]
--   [[DualLicensing]]
--   [[GnuGplTwoOrLater]]
+-   [[Documentation formats|DocumentationFormats]]
+-   [[Documentation notices|DocumentationNotices]]
+-   [[Dual licensing|DualLicensing]]
+-   [[Why no GPLv\*-only|GnuGplTwoOrLater]]
 -   [How know if a license is free in 3
-    
points](http://savannah.gnu.org/maintenance/HowKnowIfALicenseIsFreeIn3Points)
--   [[ProprietaryUseOfFreeSoftware]]
--   [[ValidNotices]]
+    points|HowKnowIfALicenseIsFreeIn3Points]]
+-   [[Don't advertise nonfree licensing|ProprietaryUseOfFreeSoftware]]
+-   [[Copyright and license notices|ValidNotices]]