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

[Pavel Kharitonov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Pavel Kharitonov <ineiev>       13/01/16 14:41:49

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

Log message:
        (Leaders, Managing): Reduce nesting.
        Move `Review', `Commits', `PO Files', `Savannah', `Co-leaders'
        up from `Managing' to `Leaders'.
        (Review, Tracking Tasks, Unreviewed Translations, Commits):
        (PO Files, Web-based Systems, Savannah, Savannah Members):
        (Savannah Homepage, Savannah Support, Savannah Tasks):
        (Savannah Bugs, News, Mailing Lists, VCS, Co-leaders): Move
        up in hierarchy.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/doc/web-trans.texi?cvsroot=trans-coord&r1=1.45&r2=1.46
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/server/gnun/ChangeLog?cvsroot=trans-coord&r1=1.346&r2=1.347

Patches:
Index: doc/web-trans.texi
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/doc/web-trans.texi,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -b -r1.45 -r1.46
--- doc/web-trans.texi  25 Dec 2012 16:40:02 -0000      1.45
+++ doc/web-trans.texi  16 Jan 2013 14:41:49 -0000      1.46
@@ -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 25.12.2012
address@hidden lastupdate 16.01.2013
 @afourpaper
 @c %**end of header
 
@@ -14,7 +14,7 @@
 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, 2011, 2012 Free Software
+Copyright @copyright{} 2009, 2010, 2011, 2012, 2013 Free Software
 Foundation, Inc.
 
 @quotation
@@ -380,6 +380,11 @@
 @menu
 * New Team::            Procedures to establish a new team.
 * Managing::            General guidelines how to manage a team.
+* Review::              How to review translations.
+* Commits::             CVS commits and best practices.
+* PO Files::            Working with PO files.
+* Savannah::            Taking advantage of Savannah.
+* Co-leaders::          Promoting members as co-leaders.
 * Reports::             Reporting team status and activity.
 * Stepping Down::       Orphaning the team and finding a replacement.
 @end menu
@@ -602,16 +607,8 @@
 teams, and for general organizational work.  Feel free to discuss
 anything related to the translation process there.
 
address@hidden
-* Review::              The importance of peer review.
-* Commits::             What to modify, and how.
-* PO Files::            Tools to edit translations.
-* Savannah::            Using Savannah resources.
-* Co-leaders::          Promoting co-leaders, when necessary.
address@hidden menu
-
 @node Review
address@hidden Peer Review
address@hidden Peer Review
 
 First and foremost, find at least one person for peer review.  You will
 review her translations, and she will review yours (at least in the
@@ -649,7 +646,7 @@
 @end menu
 
 @node Tracking Tasks
address@hidden How to Track Tasks and Bugs Using Savannah
address@hidden How to Track Tasks and Bugs Using Savannah
 
 The team leader has to make sure that prospective translations are
 reviewed, that they do not contain obvious errors and/or confusing
@@ -739,7 +736,7 @@
 details.
 
 @node Unreviewed Translations
address@hidden How to Proceed with Unreviewed Translations
address@hidden How to Proceed with Unreviewed Translations
 
 Sometimes a translation (typically your own) is not reviewed by anyone
 else for a fairly long time.  This is unfortunate, but there is no
@@ -754,7 +751,7 @@
 You may also add a comment to the PO file.
 
 @node Commits
address@hidden CVS Commits and Best Practices
address@hidden CVS Commits and Best Practices
 
 As all team leaders have write access to the CVS repository of the
 @samp{www} project, this technically means that they are able to modify
@@ -845,7 +842,7 @@
 disable mail delivery in Mailman's user interface.
 
 @node PO Files
address@hidden Working with PO Files
address@hidden Working with PO Files
 @cindex PO, editing
 
 We anticipate that some gnu.org translators will find this format odd
@@ -908,7 +905,7 @@
 Various web-based editors.
 @end itemize
 
address@hidden Web-based Systems
address@hidden Web-based Systems
 
 An alternative way to maintain translations is to use one of the
 existing online editors.  There are plans to install a web-based system
@@ -944,7 +941,7 @@
 repository.
 
 @node Savannah
address@hidden Taking Advantage of Savannah
address@hidden Taking Advantage of Savannah
 
 Every translation team should have a project in Savannah.  There are
 some teams that use their own resources outside Savannah; although
@@ -1000,7 +997,7 @@
 @end menu
 
 @node Savannah Members
address@hidden Managing Members
address@hidden Managing Members
 
 You should add active translators as members of the translation team,
 and remove them when they leave.  Team members should have access to all
@@ -1021,7 +1018,7 @@
 @samp{View Members}.
 
 @node Savannah Homepage
address@hidden Homepage of the Team
address@hidden Homepage of the Team
 
 Every Savannah project has a Web repository, which is, for technical and
 historical reasons, only CVS.  By default it is mapped to
@@ -1045,7 +1042,7 @@
 will be removed without warning.
 
 @node Savannah Support
address@hidden Support Tracker
address@hidden Support Tracker
 
 This tracker is supposed to be related to things about the @emph{project
 management} itself, i.e. project members may report here missing
@@ -1054,7 +1051,7 @@
 confusing.  It is OK to disable it if the team is small.
 
 @node Savannah Tasks
address@hidden Tasks Tracker
address@hidden Tasks Tracker
 
 This is a way to manage all sorts of tasks.  They appear in the personal
 Savannah page of the assignee, so it is difficult to miss them out.  It
@@ -1068,7 +1065,7 @@
 Feel free to organize the @samp{Tasks} management as you see fit.
 
 @node Savannah Bugs
address@hidden Bugs Tracker
address@hidden Bugs Tracker
 
 The @samp{Bugs} tracker is designed for tracking bugs.  You can use for
 several purposes:
@@ -1088,7 +1085,7 @@
 @end itemize
 
 @node Savannah News
address@hidden News Tracker
address@hidden News Tracker
 
 That is a way to inform newcomers and interested people (who visit the
 project page from time to time, or subscribe to the @samp{News} RSS
@@ -1103,7 +1100,7 @@
 translations, which is also fine.
 
 @node Savannah Mailing Lists
address@hidden Managing Mailing Lists
address@hidden 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
@@ -1122,7 +1119,7 @@
 You can redirect all messages generated by the trackers to any list.
 
 @node Savannah VCS
address@hidden Version Control Systems
address@hidden Version Control Systems
 
 An easy way to keep up with changes in the original articles and to
 manage continuous contributions is to keep all translations in the
@@ -1141,7 +1138,7 @@
 won't use it so that won't be a net win.
 
 @node Co-leaders
address@hidden Promoting Members as Co-leaders
address@hidden Promoting Members as Co-leaders
 
 When the team grows large and it becomes hard for a single person to
 manage, there is no problem to add another (or even another two) people

Index: ChangeLog
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/server/gnun/ChangeLog,v
retrieving revision 1.346
retrieving revision 1.347
diff -u -b -r1.346 -r1.347
--- ChangeLog   14 Jan 2013 17:50:58 -0000      1.346
+++ ChangeLog   16 Jan 2013 14:41:49 -0000      1.347
@@ -1,3 +1,14 @@
+2013-01-16  Pavel Kharitonov  <address@hidden>
+
+       * web-trans.texi (Leaders, Managing): Reduce nesting.
+       Move `Review', `Commits', `PO Files', `Savannah', `Co-leaders'
+       up from `Managing' to `Leaders'.
+       (Review, Tracking Tasks, Unreviewed Translations, Commits):
+       (PO Files, Web-based Systems, Savannah, Savannah Members):
+       (Savannah Homepage, Savannah Support, Savannah Tasks):
+       (Savannah Bugs, News, Mailing Lists, VCS, Co-leaders): Move
+       up in hierarchy.
+
 2013-01-14  Pavel Kharitonov  <address@hidden>
 
        * GNUmakefile.team (report-pos): Don't report about `HTML'