[Top][All Lists]

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

gnustandards maintain.texi

From: Richard M. Stallman
Subject: gnustandards maintain.texi
Date: Wed, 19 Mar 2014 17:28:16 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Richard M. Stallman <rms>       14/03/19 17:28:16

Modified files:
        .              : maintain.texi 

Log message:
        (GNU and Linux): Minor cleanup.
        (Free Software and Open Source): Minor cleanup.
        (Crediting Authors, Binary Distribution): New sections.


Index: maintain.texi
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.242
retrieving revision 1.243
diff -u -b -r1.242 -r1.243
--- maintain.texi       9 Oct 2013 20:38:22 -0000       1.242
+++ maintain.texi       19 Mar 2014 17:28:15 -0000      1.243
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate October 9, 2013
address@hidden lastupdate March 19, 2014
 @c %**end of header
 @dircategory GNU organization
@@ -284,6 +284,7 @@
 * Copyright Notices::
 * License Notices::
 * External Libraries::
+* Crediting Authors::
 @end menu
 @node Copyright Papers
@@ -1048,6 +1049,18 @@
 programs and released separately for general use.  For anything that was
 written as a contribution to your package, please get papers signed.
address@hidden Crediting Authors
address@hidden Crediting Authors
address@hidden crediting authors
+Strictly speaking, this is not a legal issue, but it seems to belong
+with copyright notices.
+In any FSF-copyrighted GNU package, the authors of a file are not
+named in the copyright notice.  Therefore, it is nice to include a
+comment line @samp{Authors: @var{authors of this file}} at the top
+near the copyright notice, to give them credit in close association
+with their contribution.
 @node Clean Ups
 @chapter Cleaning Up Changes
@@ -1083,7 +1096,6 @@
 read it (@pxref{Tips, , Tips and Conventions, elisp, The GNU Emacs Lisp
 Reference Manual}).
 @node Platforms
 @chapter Platforms to Support
@@ -1332,6 +1344,7 @@
 * Distribution tar Files::
 * Distribution Patches::
+* Binary Distribution::
 * Distribution on
 * Test Releases::
 * Automated FTP Uploads::
@@ -1425,6 +1438,22 @@
 It's wise to test your patch by applying it to a copy of the old
 version, and checking that the result exactly matches the new version.
address@hidden Binary Distribution
address@hidden Binary Distribution for Nonfree Platforms
+Some package maintainers release pre-compiled binaries proprietary
+for systems such as Microsoft Windows or MacOS.  It's entirely up to you
+whether to do that; we don't ask you to do it, but we don't object.
+Please do not let anyone make you feel you have an obligation to do
+If you distribute them, please inform their users prominently that
+those non-free platforms trample their freedom.  It is useful to refer
+them to
+You can say, ``This program respects your freedom, but Windows does
+not.  To have freedom, you need to stop using Windows and other
+software that denies your freedom.''
 @node Distribution on
 @section Distribution on @code{}
@@ -2363,7 +2392,7 @@
 receives, the GNU Project needs to overcome a widespread
 mistaken impression that GNU is @emph{and always was} an ``open
 source'' activity.  For this reason, please use the term ``free
-software'', not ``open source'', in GNU software releases, GNU
+software'', not ``open source'' or ``FOSS'', in GNU software releases, GNU
 documentation, and announcements and articles that you publish in your
 role as the maintainer of a GNU package.  A reference to the URL given
 above, to explain the difference, is a useful thing to include as
@@ -2409,15 +2438,17 @@
 the difference between the kernel and the system, and could encourage
 readers to overlook the distinction.
-To contrast the GNU system properly with respect to GNU/Linux, you can
-call it ``GNU/Hurd'' or ``the GNU/Hurd system''.  However, when that
-contrast is not specifically the focus, please call it just ``GNU'' or
-``the GNU system''.
+To contrast the GNU system proper with GNU/Linux, you can call it
+``GNU/Hurd'' or ``the GNU/Hurd system''.  However, when that contrast
+is not specifically the focus, please call it just ``GNU'' or ``the
+GNU system''.
 When referring to the collection of servers that is the higher level
 of the GNU kernel, please call it ``the Hurd'' or ``the GNU Hurd''.
 Note that this uses a space, not a slash.
+For more about this point, see
 @node Interviews and Speeches
 @chapter Interviews and Speeches

reply via email to

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