trans-coord/gnun/server/gnun/doc web-trans.texi

[Pavel Kharitonov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       12/01/21 07:48:25

Modified files:
        gnun/server/gnun/doc: web-trans.texi 

Log message:
        (Savannah Mailing Lists): Update policies about mailing lists RT 
#718992.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.19&r2=1.20

Patches:
Index: web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- web-trans.texi      20 Nov 2011 11:41:14 -0000      1.19
+++ web-trans.texi      21 Jan 2012 07:48:25 -0000      1.20
@@ -991,15 +991,21 @@
 @node Savannah Mailing Lists
 @subsubsection Managing Mailing Lists
 
+Every team should have a mailing list on lists.gnu.org and use it for
+internal communications.  All active translators should be on the list.
+The list owner should be the coordinator of the team.  The name of the
+list should begin with @address@hidden
+
+The list will make it possible for the GNU project to contact the team
+when the coordinator disappears; its archive will also give access to
+the history for new translators.
+
 You can create new mailing lists via the Savannah interface.  However,
 this should be done after some thought.  If the project membership is
 low (<= 10 members), there is no need to create more than one mailing
-list.  If there is a general translation list common for all translators
-of the language (i.e. GNOME, GNUstep, KDE, and free software in
-general), there is no reason at all to create a list at Savannah.
+list.
 
-You can redirect all messages generated by the trackers to any list
-(including those that are not on GNU servers).
+You can redirect all messages generated by the trackers to any list.
 
 @node Savannah VCS
 @subsubsection Version Control Systems