Add isnan module.

[gnulib.git] / doc / maintain.texi

diff --git a/doc/maintain.texi b/doc/maintain.texi
index 22a7e81..c790f13 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 March 10, 2008
+@set lastupdate July 6, 2008
 @c %**end of header
 
 @dircategory GNU organization
@@ -300,6 +300,16 @@ manual.  For smaller changes, use
 changes to a manual, you can use @file{assign.future.manual}.
 For a translation of a manual, use @file{assign.translation.manual}.
 
+For translations of program strings (as used by GNU Gettext, for
+example; @pxref{Internationalization,,,standards,GNU Coding
+Standards}), use @file{disclaim.translation}.  If you make use of the
+Translation Project (@url{http://translationproject.org}) facilities,
+please check with the TP coordinators that they have sent the
+contributor the papers; if they haven't, then you should send the
+papers.  In any case, you should wait for the confirmation from the
+FSF that the signed papers have been received and accepted before
+integrating the new contributor's material, as usual.
+ 
 If a contributor is reluctant to sign an assignment for a large change,
 and is willing to sign a disclaimer instead, that is acceptable, so you
 should offer this alternative if it helps you reach agreement.  We
@@ -539,7 +549,7 @@ To update the list of year numbers, add each year in which you have
 made nontrivial changes to the package.  (Here we assume you're using
 a publicly accessible revision control server, so that every revision
 installed is also immediately and automatically published.)  When you
-add the new year, it is not required to keep track which files have
+add the new year, it is not required to keep track of which files have
 seen significant changes in the new year and which have not.  It is
 recommended and simpler to add the new year to all files in the
 package, and be done with it for the rest of the year.
@@ -821,8 +831,8 @@ important one, important enough to be worth the work of cleaning it up.
 The GNU Coding Standards are a good thing to send people when you ask
 them to clean up changes (@pxref{Top, , Contents, standards, GNU Coding
 Standards}).  The Emacs Lisp manual contains an appendix that gives
-coding standards for Emacs Lisp programs; it is good to urge authors to
-read it (@pxref{Tips, , Tips and Standards, elisp, The GNU Emacs Lisp
+coding standards for Emacs Lisp programs; it is good to urge Lisp authors to
+read it (@pxref{Tips, , Tips and Conventions, elisp, The GNU Emacs Lisp
 Reference Manual}).
 
 
@@ -1707,7 +1717,7 @@ different movements which differ in their basic philosophy.  The Free
 Software Movement is idealistic, and raises issues of freedom, ethics,
 principle and what makes for a good society.  The Open Source Movement,
 founded in 1998, studiously avoids such questions.  For more explanation,
-see @url{http://www.gnu.org/philosophy/free-software-for-freedom.html}.
+see @url{http://www.gnu.org/philosophy/open-source-misses-the-point.html}.
 
 The GNU Project is aligned with the Free Software Movement.  This
 doesn't mean that all GNU contributors and maintainers have to agree;