* gnulib-tool: New parameter --lgpl.

[gnulib.git] / doc / maintain.texi

diff --git a/doc/maintain.texi b/doc/maintain.texi
index e0b740b..667cbe8 100644 (file)
--- a/doc/maintain.texi
+++ b/doc/maintain.texi
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
-@set lastupdate April 11, 2004
+@set lastupdate June 28, 2004
 @c %**end of header
 
 @dircategory GNU organization
@@ -478,7 +478,12 @@ released, were @emph{completed}.  So if you finish a version on Dec 31,
 of 1994, but doesn't require the inclusion of 1995.
 
 Do not abbreviate the year list using a range; for instance, do not
-write @samp{1996--1998}; instead, write @samp{1996, 1997, 1998}.
+write @samp{1996--1998}; instead, write @samp{1996, 1997, 1998}.  Do
+write each relevant year as a four-digit number.  In the normal course
+of maintenance, you may come across copyright notices which omit the
+century, as in @samp{1996, 97, 98}---change these to include the
+century.  However, there is no need to systematically change the
+notice in every old file.
 
 The versions that matter, for purposes of this list, are versions that
 were ancestors of the current version.  So if you made a temporary
@@ -803,6 +808,14 @@ bug-reporting list for your program.  To set up a new list, contact
 @email{new-mailing-list@@gnu.org}.  You can subscribe to a list managed
 by Mailman by sending mail to the corresponding @samp{-request} address.
 
+You should moderate postings from non-subscribed addresses on your
+mailing lists, to prevent propagation of unwanted messages (``spam'')
+to subscribers and to the list archives.  For lists controlled by
+Mailman, you can do this by setting @code{Privacy Options - Sender
+Filter - generic_nonmember_action} to @code{Hold}, and then
+periodically (daily is best) reviewing the held messages, accepting
+the real ones and discarding the junk.
+
 @cindex responding to bug reports
 When you receive bug reports, keep in mind that bug reports are crucial
 for your work.  If you don't know about problems, you cannot fix them.
@@ -1419,14 +1432,15 @@ doesn't mean that all GNU contributors and maintainers have to agree;
 your views on these issues are up to you, and you're entitled to express
 them when speaking for yourself.
 
-However, due to the much greater publicity that the Open Source Movement
-receives, the GNU Project needs to overcome a widespread mistaken
-impression that GNU is @emph{and always was} an activity of the Open
-Source Movement.  For this reason, please use the term ``free
-software,'' rather than ``open source,'' in GNU software releases, GNU
+However, due to the much greater publicity that the Open Source
+Movement receives, the GNU Project needs to overcome a widespread
+mistaken impression that GNU is @emph{and always was} an activity of
+the Open Source Movement.  For this reason, please use the term ``free
+software,'' not ``open source,'' 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 well.
+above, to explain the difference, is a useful thing to include as
+well.
 
 @node GNU and Linux
 @section GNU and Linux