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

[Yavor Doganov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   12/01/30 07:22:10

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

Log message:
        (Joining, Savannah): Don't suggest non-GNU lists are acceptable.
        (Savannah Mailing Lists): Typo fix.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.240&r2=1.241
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.21&r2=1.22

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.240
retrieving revision 1.241
diff -u -b -r1.240 -r1.241
--- ChangeLog   29 Jan 2012 11:28:46 -0000      1.240
+++ ChangeLog   30 Jan 2012 07:22:05 -0000      1.241
@@ -1,3 +1,9 @@
+2012-01-30  Yavor Doganov  <address@hidden>
+
+       * doc/web-trans.texi (Joining, Savannah): Don't suggest non-GNU
+       lists are acceptable.
+       (Savannah Mailing Lists): Typo fix.
+
 2012-01-29  Yavor Doganov  <address@hidden>
 
        * doc/gnun.texi (make-prototype): Document that --article is

Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- doc/web-trans.texi  21 Jan 2012 08:16:21 -0000      1.21
+++ doc/web-trans.texi  30 Jan 2012 07:22:07 -0000      1.22
@@ -5,7 +5,7 @@
 @settitle GNU Web Translators Manual
 @c FIXME: Would be nice to have it in the format `%:b %:d, %:y', but
 @c in English.
address@hidden lastupdate 15.02.2011
address@hidden lastupdate 30.01.2012
 @afourpaper
 @c %**end of header
 
@@ -17,7 +17,8 @@
 This manual is a guide for the GNU Web address@hidden Last updated on
 @value{lastupdate}, for GNUnited Nations version @value{VERSION}.
 @sp 1
-Copyright @copyright{} 2009, 2010, 20011 Free Software Foundation, Inc.
+Copyright @copyright{} 2009, 2010, 2011, 2012 Free Software
+Foundation, Inc.
 
 @quotation
 Permission is granted to copy, distribute and/or modify this document
@@ -159,11 +160,11 @@
 next chapter, @pxref{Leaders}.
 
 Contacting the team is best done via Savannah---each translation team
-has its own project, named @address@hidden, with the project page
-being
+has its own project, named @address@hidden, with the project
+page being
 @indicateurl{https://savannah.gnu.org/@/projects/@/address@hidden
-Usually teams have mailing lists, either on Savannah or on some external
-site.  Some teams have homepages,
+Usually teams have mailing lists, typically in the form
address@hidden@address@hidden@@gnu.org}}.  Some teams have homepages,
 @indicateurl{http://gnu.org/@/server/@/standards/@/translations/@var{lang}}
 with additional contact details and procedures for team members.
 
@@ -827,24 +828,29 @@
 Savannah project for each language is obvious: it's a standard way to
 find information for translation teams and their contacts.
 
-Using external hosting facilities is sometimes justified---for example,
-some languages have a single mailing list for all free software-related
-translations, where all translators co-operate.  Others have already
-established repositories and/or bug tracking systems where usual
-contributors already have access.  Some team members prefer to work
-within the established infrastructure of a broad translation team (for
-whatever reason), and this is entirely acceptable.  However, it is
-important to remember that regardless of the technical resources which a
-team decides to use, the responsibility of the team co-ordinator remains
-the same.
+Using external hosting facilities may seem justified sometimes.  Some
+teams may have already established repositories and/or bug tracking
+systems where usual contributors already have access.  Some team
+members prefer to work within the established infrastructure of a
+broad translation team (for whatever reason), but this is discouraged.
+It is required that every team has a mailing list at Savannah
+(@pxref{Savannah Mailing Lists}), because it is easier to pass its
+management to the new co-ordinator when the old one steps down, and it
+helps to keep the archives at one place for future members of the
+team.  Likewise, it is better to use Savannah for the team's
+repository and bug/tasks, but this is not mandatory.
+
+However, it is important to remember that regardless of the technical
+resources which a team decides to use, the responsibility of the team
+co-ordinator remains the same.
 
 Those teams that are using Savannah have a broad variety of tools at
 hand: team membership management, documents, trackers (bugs, tasks and
 support), alerts, CVS (and any other VCS that Savannah supports), home
-pages, mailing lists, etc.  How each team uses these resources is up to
-the team itself, but it often turns out to choose Savannah for nearly
-all of the team activities, as it requires almost zero work; the
-Savannah Hackers are happy to support us.
+pages, etc.  How each team uses these resources is up to the team
+itself, but it often turns out to choose Savannah for nearly all of
+the team activities, as it requires almost zero work; the Savannah
+Hackers are happy to support us.
 
 Whatever you (in your capacity as a team leader) decide, please do it
 with caution: some organizational decisions may become ineffective as
@@ -992,9 +998,9 @@
 @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
+internal communications.  All active translators should be on the
+list.  The list owner should be the co-ordinator 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