[Savannah-cvs] [594] (Copyrightable files): move the section up; (Copyright notices): new title

[ineiev]

Revision: 594
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=594
Author:   ineiev
Date:     2023-02-22 10:33:36 -0500 (Wed, 22 Feb 2023)
Log Message:
-----------
(Copyrightable files): move the section up; (Copyright notices): new title

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

Modified: trunk/sviki/ValidNotices.mdwn
===================================================================
--- trunk/sviki/ValidNotices.mdwn       2023-02-19 12:46:41 UTC (rev 593)
+++ trunk/sviki/ValidNotices.mdwn       2023-02-22 15:33:36 UTC (rev 594)
@@ -1,6 +1,18 @@
-Valid copyright notices
-=======================
+# Copyright and license notices
 
+## Copyrightable files
+
+For copyright purpose, any file more than ten lines long is nontrivial,
+so it should have copyright and license notices.
+
+If some of your files cannot carry such notices (e.g. binary files),
+then you can add a README file in the same directory containing the
+copyright and license notices. Check
+<http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html>
+for further information.
+
+## Copyright notices
+
 Free software licenses rely on copyright law. The pro is that they are
 enforceable. The con is that you get the administrative burden.
 Fortunately, this merely means having in all your files:
@@ -26,21 +38,8 @@
 is worth reading (although some parts are specific to GNU projects):
 <http://www.gnu.org/prep/maintain/html_node/Legal-Matters.html>
 
-Copyrightable files
--------------------
+## GNU GPL
 
-For copyright purpose, any file more than ten lines long is nontrivial,
-so it should have copyright and license notices.
-
-If some of your files cannot carry such notices (e.g. binary files),
-then you can add a README file in the same directory containing the
-copyright and license notices. Check
-<http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html>
-for further information.
-
-GNU GPL
--------
-
 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
@@ -59,8 +58,7 @@
 example, see
 <http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude>.
 
-GNU LGPL
---------
+## GNU LGPL
 
 In order to release your project properly and unambiguously under the
 LGPL, please place copyright notices and permission-to-copy statements
@@ -75,8 +73,7 @@
 For more information, see
 <http://www.gnu.org/licenses/lgpl.html#SEC4>.
 
-GFDL
-----
+## GFDL
 
 In order to release your project properly and unambiguously under the
 GFDL, please place copyright notices and permission-to-copy statements
@@ -94,14 +91,12 @@
 also covers additional points, including a smaller notice that you can
 use in auxiliary files.
 
-Other licenses
---------------
+## Other licenses
 
 If the license is small (such as the Modified BSD, X11 or Expat), instead of
 a license notice, include it entirely at the top of all your files.
 
-Public domain
--------------
+## Public domain
 
 If the files in question are public domain, instead of copyright and
 license notices, include a note saying it's public domain, listing