www-commits
[Top][All Lists]
Advanced

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

www/server fsf-html-style-sheet.html


From: Richard M. Stallman
Subject: www/server fsf-html-style-sheet.html
Date: Sun, 25 Jun 2017 10:12:08 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     Richard M. Stallman <rms>       17/06/25 10:12:08

Modified files:
        server         : fsf-html-style-sheet.html 

Log message:
        Total rewrite of the section about copyrights, copyright notices and
        licenses.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/fsf-html-style-sheet.html?cvsroot=www&r1=1.68&r2=1.69

Patches:
Index: fsf-html-style-sheet.html
===================================================================
RCS file: /web/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -b -r1.68 -r1.69
--- fsf-html-style-sheet.html   17 Apr 2016 08:27:10 -0000      1.68
+++ fsf-html-style-sheet.html   25 Jun 2017 14:12:08 -0000      1.69
@@ -18,19 +18,47 @@
 <li>Every page should have a copyright notice.  See the boilerplate
 document linked below.</li>
 
-<li>If the page is copyrighted by someone else, make sure their
-copyright notice replaces the FSF copyright, but maintains the
-address, etc. The user of our pages should always find the
-copyright information at the same place on each page.</li>
-
-<li>If the source text for a set of pages is copyrighted by someone
-else (i.e., you split a document into more than one page), make sure
-their copyright notice is at the bottom of each page, where the
-default FSF copyright notice would otherwise be.</li>
-
-<li>All pages should have a notice saying that they are freely
-distributable. If you can not get such a permission from the
-author, please discuss this with the webmasters first.</li>
+<li>Every page should have a notice giving everyone permission
+todistribute it.  If you cannot get such a permission from the author,
+please discuss the issue with the webmasters before posting it.  This
+applies to CSS as well as to HTML.
+</li>
+
+<li>Normally you shouldn't post a page that isn't copyright FSF unless
+we have permission to modify the version we publish.  If you cannot
+get such a permission from the author, please discuss the issue with
+the FSF before posting it.  This applies to CSS as well as to HTML.
+</li>
+
+<li>
+If ultimately we decide to post a new page we don't have permission to
+modify, put the text &ldquo;Posted in 201X without FSF permission to
+modify&rdquo; inside an HTML comment, just after the copyright notice.
+</li>
+
+<li>The user of our pages should always find the copyright information
+at the same place on each page.  If the page is copyrighted by some
+other person or entity, use per or its copyright notice instead of the
+FSF copyright notice.  Use the rest of the FSF's normal footer
+material, except when there is a specific reason to change something
+in it.</li>
+
+<li>If the source text for a set of pages is copyrighted by some other
+person or entity (i.e., you split a document into more than one page),
+make sure per or its copyright notice is at the bottom of each page, where
+the default FSF copyright notice would otherwise be.</li>
+
+<li>All pages that explain how to do something, such as how to use
+certain programs, are documentation.  This includes all the pages in
+/software that describe specific programs.  By our
+principles, <a href="/philosophy/free-doc.html"> documentation must be
+free</a>.  So these pages must carry
+a <a href="/licenses/license-recommendations.html">free
+license</a>.  If such a page doesn't have a free license, please report this
+problem to address@hidden</li>
+
+<li>For other pages, use the same license as some other page that serves
+a similar kind of purpose.</li>
 </ul>
 
 <h3 id="GeneralGuidelines">General Guidelines</h3>
@@ -450,7 +478,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2016/04/17 08:27:10 $
+$Date: 2017/06/25 14:12:08 $
 <!-- timestamp end --></p>
 </div>
 </div>



reply via email to

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