@c For double-sided printing, uncomment:
@c @setchapternewpage odd
@c This date is automagically updated when you save this file:
-@set lastupdate October 29, 2004
+@set lastupdate May 10, 2005
@c %**end of header
@dircategory GNU organization
Information for maintainers of GNU software, last updated @value{lastupdate}.
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
-2001, 2002, 2003, 2004 Free Software Foundation, Inc.
+2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
@quotation
Permission is granted to make and distribute verbatim copies
papers to sign. The @file{request-} file also raises the issue of
getting a copyright disclaimer from the contributor's employer.
+When the contributor emails the form to the FSF, the FSF sends per
+papers to sign. If person signs them right away, the whole process
+takes about two weeks--mostly waiting for letters to go back and
+forth.
+
For less common cases, we have template files you should send to the
contributor. Be sure to fill in the name of the person and the name
of the program in these templates, where it says @samp{NAME OF PERSON}
You should have received a copy of the GNU General Public License
along with @var{program}; see the file COPYING. If not, write to
-the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
-Boston, MA 02111-1307, USA.
+the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+Boston, MA 02110-1301 USA.
@end quotation
But in a small program which is just a few files, you can use
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
-59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
+51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
@end quotation
Documentation files should have license notices also. Manuals should
notice and this notice are preserved.
@end smallexample
+If your package distributes Autoconf macros that are intended to be
+used (hence distributed) by third-party packages under possibly
+incompatible licenses, you may also use the above all-permissive
+license for these macros.
+
If you would like help with license issues or with using the GFDL,
please contact @email{licensing@@gnu.org}.