@c For double-sided printing, uncomment:
@c @setchapternewpage odd
@c This date is automagically updated when you save this file:
-@set lastupdate January 22, 2025
+@set lastupdate March 18, 2025
@c %**end of header
@documentencoding UTF-8
years (@samp{2008, 2009, 2010}) if and only if: 1)@tie{}every year in
the range, inclusive, really is a ``copyrightable'' year that would be
listed individually; @emph{and} 2)@tie{}you make an explicit statement
-in a @file{README} file about this usage.
+in a @file{README} file about this usage:
+
+@example
+For any copyright year range specified as YYYY-ZZZZ in this package
+note that the range specifies every single year in that closed
+interval.
+@end example
For files which are regularly copied from another project (such as
@samp{gnulib}), leave the copyright notice as it is in the original.
Every nontrivial file needs a license notice as well as the copyright
notice. (Without a license notice giving permission to copy and
-change the file, the file is nonfree.)
+change the file, the file is non-free.)
The package itself should contain a full copy of GPL in plain text
(conventionally in a file named @file{COPYING}) and the GNU Free
complex and ugly, if you think that they will increase the burden of
future maintenance, you can and should reject them. This includes
both free or mainly-free platforms such as OpenBSD, FreeBSD, and
-NetBSD, and nonfree platforms such as Windows.
+NetBSD, and non-free platforms such as Windows.
@node Patches Not to Accept
@chapter Patches Not to Accept
@menu
* Non-GNU-only Features:: Every feature in a GNU package should work on GNU.
-* Interoperation with Nonfree:: Don't interoperate better with nonfree
+* Interoperation with Non-Free:: Don't interoperate better with non-free
than with free software.
* Uninstalled Code in Repo:: Putting code in the package repo without
installing it.
the GNU system equally well in the new feature. If there is no hope
of that, just ``No thanks'' is enough.
-@node Interoperation with Nonfree
-@section Interoperation with Nonfree Applications
+@node Interoperation with Non-Free
+@section Interoperation with Non-Free Applications
It is quite usual to implement features in GNU programs to make them
-work conveniently with widely used nonfree tools and applications.
+work conveniently with widely used non-free tools and applications.
But there are situations where you should not implement cooperation
-with a nonfree program, which we can refer to here as ShackleMe.
+with a non-free program, which we can refer to here as ShackleMe.
@itemize @bullet
@item
If ShackleMe is not well-known, reject the idea. GNU packages should
-not even @emph{mention} an obscure nonfree program
+not even @emph{mention} an obscure non-free program
(@pxref{References,,, standards, GNU Coding Standards}).
@item
@item
You never have an obligation to write, install or maintain any sort of
-support for a nonfree program. If it is unmaintained and breaks, and
+support for a non-free program. If it is unmaintained and breaks, and
nobody else wants to maintain it you can delete it. Don't feel
trapped into working on it!
@end itemize
version, and checking that the result exactly matches the new version.
@node Binary Distribution
-@section Binary Distribution for Nonfree Platforms
+@section Binary Distribution for Non-Free Platforms
Some package maintainers release pre-compiled binaries for proprietary
systems such as Microsoft Windows or MacOS@. It's entirely up to you
this.
If you distribute them, please inform their users prominently that
-those nonfree platforms trample their freedom. It is useful to refer
+those non-free platforms trample their freedom. It is useful to refer
them to
@url{https://www.gnu.org/philosophy/free-software-even-more-important.html}.
You can say, ``This program respects your freedom, but Windows does
the site runs on free software alone. (It is ok if the site uses
unreleased custom software, since that is free in a trivial sense:
there's only one user and it has the four freedoms.) If the web site
-for a GNU package runs on nonfree software, the public will see this,
-and it will have the effect of granting legitimacy to the nonfree
+for a GNU package runs on non-free software, the public will see this,
+and it will have the effect of granting legitimacy to the non-free
program.
If you use multiple sites, they should all follow that criterion.
no licensing consortium has been set up. GNU programs and their web
sites should not distribute video in MPEG-2 or MPEG 4 formats.
-A GNU package should not recommend use of any nonfree program, nor
-should it require a nonfree program (such as a nonfree compiler or
+A GNU package should not recommend use of any non-free program, nor
+should it require a non-free program (such as a non-free compiler or
IDE) to build. Thus, a GNU package cannot be written in a programming
language that does not have a free software implementation. Now that
GNU/Linux systems are widely available, all GNU packages should
provide full functionality on a 100% free GNU/Linux system, and should
-not require any nonfree software to build or function.
+not require any non-free software to build or function.
The GNU Coding Standards say a lot more about this issue.
-Similarly, a GNU package should not require the use of nonfree
+Similarly, a GNU package should not require the use of non-free
software, including JavaScript, for the coordination of its
development. For example, please don't use Transifex for translation
-of your software because it requires your translators to use nonfree,
+of your software because it requires your translators to use non-free,
JavaScript-based editing tools. Instead, a service without any
ethical concerns should be used, such as The Translation Project
(@url{https://translationproject.org}).
-A GNU package should not refer the user to any nonfree documentation
+A GNU package should not refer the user to any non-free documentation
for free software. The need for free documentation to come with free
software is now a major focus of the GNU project; to show that we are
serious about the need for free documentation, we must not contradict
our position by recommending use of documentation that isn't free.
Please don't host discussions about your package in a service that
-requires nonfree software. For instance, Google+ ``communities''
-require running a nonfree JavaScript program to post a message, so
+requires non-free software. For instance, Google+ ``communities''
+require running a non-free JavaScript program to post a message, so
they can't be used in the Free World. Google Groups has the same
problem. To host discussions there would be excluding people who live
by free software principles.
for informing the public about the GNU system and the ideas of the
free software movement. Please avoid saying ``open source'' and avoid
calling the GNU system ``Linux'', just as you would in the package
-itself (@pxref{Terminology}). Likewise, avoid promoting nonfree
+itself (@pxref{Terminology}). Likewise, avoid promoting non-free
programs (@pxref{References,,, standards, GNU Coding
Standards}) as you would in the package itself.
We don't recommend any specific payment service. However, GNU
developers should not use a service that requires them to sign a
proprietary software license, such as Google's payment service.
-Please also avoid sites that requires users to run nonfree software in
+Please also avoid sites that requires users to run non-free software in
order to donate. (This includes JavaScript software, so try it with
LibreJS or with JavaScript disabled.)
@quotation
You've asked us to install support for doing XYZ on ShackleOS. We can't
do that until we have support for XYZ on the GNU system. GNU Project
-policy is not to add special support for a nonfree operating system
+policy is not to add special support for a non-free operating system
until we have equivalent support for the GNU system.
-A nonfree system subjugates users. You may not notice this if you
+A non-free system subjugates users. You may not notice this if you
have become accustomed to such subjugation, but we do. The Free Software
-Movement aims to liberate those users by replacing nonfree systems
+Movement aims to liberate those users by replacing non-free systems
with free software such as the GNU system.
This program does not aim to replace ShackleOS, but the GNU system does.
@quotation
You've asked us to install a feature specifically to work with
-ShackleMe, but that program is nonfree. GNU Project policy is not to
-add special support for interoperation with a nonfree program until we
+ShackleMe, but that program is non-free. GNU Project policy is not to
+add special support for interoperation with a non-free program until we
support interoperation with comparable free programs equally well or
better.
-A nonfree program subjugates users. You may not notice this if you
+A non-free program subjugates users. You may not notice this if you
have become accustomed to such subjugation, but we do. The mission of
-the GNU Project is to liberate those users by replacing the nonfree
+the GNU Project is to liberate those users by replacing the non-free
programs with free programs.
This program does not aim to replace ShackleMe, but other free