savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [364] Explain in more detail what file need notices


From: ineiev
Subject: [Savannah-cvs] [364] Explain in more detail what file need notices
Date: Sun, 20 Jan 2019 13:12:07 -0500 (EST)

Revision: 364
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=364
Author:   ineiev
Date:     2019-01-20 13:12:06 -0500 (Sun, 20 Jan 2019)
Log Message:
-----------
Explain in more detail what file need notices

Move "Binary files" up, rename to "Copyrightable files",
add a note on size of copyrightable files.

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

Modified: trunk/sviki/ValidNotices.mdwn
===================================================================
--- trunk/sviki/ValidNotices.mdwn       2019-01-16 14:49:15 UTC (rev 363)
+++ trunk/sviki/ValidNotices.mdwn       2019-01-20 18:12:06 UTC (rev 364)
@@ -26,6 +26,18 @@
 is worth reading (although some parts are specific to GNU projects):
 <http://www.gnu.org/prep/maintain/html_node/Legal-Matters.html>
 
+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.
+
 GNU GPL
 -------
 
@@ -88,11 +100,3 @@
 If the license is small (such as the mBSD/MIT/Expat license), instead of
 a license notice, include it entirely at the top of all your files.
 
-Binary files
-------------
-
-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.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]