X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2Fmaintain.texi;h=992d33e91e15700c6464e431d61313cc2311762b;hb=3c6b19e8e32d893fb50c5455eb5e3223a01df616;hp=60220f87fe0b854347cd596b85718dab75a337cf;hpb=e9b552cf52b6200633c335b19a2f703f72f8683a;p=gnulib.git diff --git a/doc/maintain.texi b/doc/maintain.texi index 60220f87f..992d33e91 100644 --- 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 November 20, 2009 +@set lastupdate March 25, 2010 @c %**end of header @dircategory GNU organization @@ -23,7 +23,7 @@ Information for maintainers of GNU software, last updated @value{lastupdate}. Copyright @copyright{} 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, -2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software +2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc. @quotation @@ -96,14 +96,17 @@ interface at @url{http://lists.gnu.org/mailman/listinfo/gnustandards-commit}. Archives are also available there. -@cindex @code{maintainers@@gnu.org} email address +@cindex @code{bug-standards@@gnu.org} email address +@cindex Savannah repository for gnustandards +@cindex gnustandards project repository Please send corrections or suggestions for this document to @email{bug-standards@@gnu.org}. If you make a suggestion, please include a suggested new wording for it, to help us consider the -suggestion efficiently. We prefer a context diff to the -@file{maintain.texi} file, but if you don't have that file, you can -make a context diff for some other version of this document, or -propose it in any way that makes it clear. +suggestion efficiently. We prefer a context diff to the Texinfo +source, but if that's difficult for you, you can make a context diff +for some other version of this document, or propose it in any way that +makes it clear. The source repository for this document can be found +at @url{http://savannah.gnu.org/projects/gnustandards}. @cindex @code{mentors@@gnu.org} mailing list If you have general questions or encounter a situation where it isn't @@ -558,9 +561,12 @@ which file it is generated from. A copyright notice looks like this: @example -Copyright (C) @var{year1}, @var{year2}, @var{year3} @var{copyright-holder} +Copyright (C) @var{year1}, @var{year2}, @var{year3} @var{copyright-holder} @end example +The word @samp{Copyright} must always be in English, by international +convention. + The @var{copyright-holder} may be the Free Software Foundation, Inc., or someone else; you should know who is the copyright holder for your package. @@ -571,7 +577,8 @@ stick with parenthesized @samp{C} unless you know that C-in-a-circle will work. For example, a program's standard @option{--version} message should use parenthesized @samp{C} by default, though message translations may use C-in-a-circle in locales where that symbol is -known to work. +known to work. Alternatively, the @samp{(C)} or C-in-a-circle can be +omitted entirely; the word @samp{Copyright} suffices. 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 @@ -1311,15 +1318,19 @@ uploaded via ftp to the host @code{ftp-upload.gnu.org}. @enumerate @item -The file to be distributed (for example, @file{foo.tar.gz}). +The file to be distributed; for example, @file{foo.tar.gz}. @item -Detached GPG binary signature for (1), made using @samp{gpg -b} -(for example, @file{foo.tar.gz.sig}). +Detached GPG binary signature file for (1); for example, +@file{foo.tar.gz.sig}. Make this with @samp{gpg -b foo.tar.gz}. + @item -A clearsigned @dfn{directive file}, made using @samp{gpg --clearsign} -(for example, @file{foo.tar.gz.directive.asc}). +A clearsigned @dfn{directive file}; for example, +@file{foo.tar.gz.directive.asc}. Make this by preparing the plain +text file @file{foo.tar.gz.directive} and then run @samp{gpg +--clearsign foo.tar.gz.directive}. @xref{FTP Upload Directive File - +v1.1}, for the contents of the directive file. @end enumerate The names of the files are important. The signature file must have the @@ -1351,8 +1362,8 @@ are sent a message if there are any problems processing an upload for your package. You also receive a message when your upload has been successfully processed. -One relatively easy way to create and transfer the necessary files is -to use the @code{gnupload} script, which is available from the +One automated way to create and transfer the necessary files is to use +the @code{gnupload} script, which is available from the @file{build-aux/} directory of the @code{gnulib} project at @url{http://savannah.gnu.org/projects/gnulib}. @code{gnupload} can also remove uploaded files. Run @code{gnupload --help} for a @@ -1361,10 +1372,10 @@ description and examples. @code{gnupload} uses the @code{ncftpput} program to do the actual transfers; if you don't happen to have the @code{ncftp} package installed, the @code{ncftpput-ftp} script in the @file{build-aux/} -directory of @code{gnulib}. serves as a replacement which uses plain +directory of @code{gnulib} serves as a replacement which uses plain command line @code{ftp}. -If you have difficulties processing an upload, email +If you have difficulties with an upload, email @email{ftp-upload@@gnu.org}.