gnustandards ChangeLog maintain.texi

[Karl Berry]

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       09/03/12 18:56:39

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        suggestions for announcement contents

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.92&r2=1.93
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.170&r2=1.171

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -b -r1.92 -r1.93
--- ChangeLog   5 Mar 2009 14:08:02 -0000       1.92
+++ ChangeLog   12 Mar 2009 18:56:39 -0000      1.93
@@ -1,3 +1,8 @@
+2009-03-12  Karl Berry  <address@hidden>
+
+       * maintain.texi (Announcements): suggestions for
+       announcement contents.
+
 2009-03-04  Karl Berry  <address@hidden>
 
        * gnu-oids.texi: allocate .6 to GNU Shishi for

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.170
retrieving revision 1.171
diff -u -b -r1.170 -r1.171
--- maintain.texi       5 Feb 2009 18:44:31 -0000       1.170
+++ maintain.texi       12 Mar 2009 18:56:39 -0000      1.171
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate February 1, 2009
address@hidden lastupdate March 12, 2009
 @c %**end of header
 
 @dircategory GNU organization
@@ -1490,25 +1490,51 @@
 strongly recommend using the (moderated) general GNU announcements
 list, @email{info-gnu@@gnu.org}.  Doing so makes it easier for users
 and developers to find the latest GNU releases.  On the other hand,
-please do not announce test releases on @code{info-gnu} unless it's an
-unusual situation.
+please do not announce test releases on @code{info-gnu} unless it's a
+highly unusual situation.
 
 @cindex @url{http://planet.gnu.org}
 @cindex Savannah, news area
 Please also post release announcements in the news section of your
 Savannah project site.  It is fine to also write news entries for test
 releases and any other newsworthy events.  The news feeds from all GNU
-projects at savannah are aggregated at @url{http://planet.gnu.org}.
-(You can also post items directly, or arrange for feeds from other
-locations; see contact information on the GNU Planet web page.) 
+projects at savannah are aggregated at @url{http://planet.gnu.org}
+(GNU Planet).  You can also post items directly, or arrange for feeds
+from other locations; see contact information on the GNU Planet web
+page.
 
 @cindex announcement mailing list, project-specific
 You can maintain your own mailing list (typically
 @address@hidden@@gnu.org}) for announcements as well if you
-like.  For your own list, of course you can decide as you see fit what
+like.  For your own list, of course you decide as you see fit what
 events are worth announcing.  (@xref{Mail}, for more suggestions on
 handling mail for your package.)
 
address@hidden contents of announcements
+When writing an announcement, please include the following:
+
address@hidden @bullet
address@hidden
+A very brief description (a few sentences at most) of the general
+purpose of your package.
+
address@hidden
+Your package's web page (normally
address@hidden://www.gnu.org/software/@var{package}/}).
+
address@hidden
+Your package's download location (normally
address@hidden://ftp.gnu.org/gnu/@var{package}/}).  It is also
+useful to mention the FTP mirror list at
address@hidden://www.gnu.org/order/ftp.html}, and that
address@hidden://ftpmirror.gnu.org/@var{package/}} will automatically
+redirect to a nearby mirror.
+
address@hidden
+The NEWS (@pxref{NEWS File,,, standards, GNU Coding Standards}) for
+the present release.
address@hidden itemize
+
 
 @node Web Pages
 @chapter Web Pages
@@ -1521,11 +1547,11 @@
 on information rather than flashy eye candy, and to keep the site
 simple and uniform.
 
-The simplest way to maintain the web pages for your project is to
-register the project on @code{savannah.gnu.org}.  Then you can edit
-the pages using CVS.  You can keep the source files there too, but if
-you want to use @code{savannah.gnu.org} only for the web pages, simply
-register a ``web-only'' project.
+The best way to maintain the web pages for your project is to register
+the project on @code{savannah.gnu.org}.  Then you can edit the pages
+using CVS.  You can keep your source files there too, but if you want
+to use @code{savannah.gnu.org} only for the web pages, that's ok;
+simply register a ``web-only'' project.
 
 If you don't want to use that method, please talk with
 @email{webmasters@@gnu.org} about other possible methods.  For