www/server/standards/translations details.html

[Yavor Doganov]

CVSROOT:        /web/www
Module name:    www
Changes by:     Yavor Doganov <yavor>   07/11/24 10:38:28

Modified files:
        server/standards/translations: details.html 

Log message:
        (Web Translation Teams): Add my general recommendation for managing
        reviews of not-yet-published translations.  
        Suggested by RMS (Addresses: RT #344946).
        (Mailing Lists): Delete www-discuss.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/translations/details.html?cvsroot=www&r1=1.1&r2=1.2

Patches:
Index: details.html
===================================================================
RCS file: /web/www/www/server/standards/translations/details.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- details.html        4 Jun 2007 19:46:46 -0000       1.1
+++ details.html        24 Nov 2007 10:38:11 -0000      1.2
@@ -57,6 +57,41 @@
 contact and translation coordinator, thus having a few
 extra rights and responsibilities.</p>
 
+<p>It is very important that translations are reviewed by a team,
+rather than a single person.  Usually, a translator makes several
+errors of different nature that are easily spotted by people who have
+not participated in the translation of the article under question.
+The team leader has to make sure that prospective translations are
+reviewed, that they do not contain obvious errors and/or confusing
+expressions and that they match the spirit and intention of the
+original essay.  However, many teams tend to suffer from a specific
+problem: team members rely on the leader to make these extensive
+reviews.  That is fine, as far as it goes, and the leader should
+always review translations before installing them in the repository
+&mdash; but it is nearly impossible (especially for a large team) to
+rely on a single person for such tasks.  Team coordinators often do
+not manage to make such reviews in time, resulting in frustration
+among the team members and generally slowing the translation
+process.</p>
+
+<p>A solution to this specific problem is to distribute the load among
+more people.  For example: Member D makes a translation of foo.html
+and uploads foo.bg.html in the translation's project repository at
+Savannah, marking the relevant task as &ldquo;Ready for Test&rdquo;
+(of course, the equivalent is sending a message with the attached
+translation to the team's mailing list, or similar).  Then Member A, B
+and C (or only A and B if C is currently busy) review it independently
+and post comments/suggestions/errors in the bug tracker.  Discussion
+goes on between them and D, problems are rectified and finally the
+leader (who may happen to be one of A, B, C, D) makes a final review.
+It is easier to make the final review when most of the issues are
+already fixed in previous revisions. Finally, the translation is
+published.  The result is better quality of the translation (since
+more people looked at it) and the whole burden does not fall on the
+shoulders of the leader.  You can also set up an internal formal rule:
+If a member makes a translation, he has to review another one (or two)
+as well.</p>
+
 <h3>Savannah</h3>
 <p>Every translation team should have a project in
 <a href="http://savannah.gnu.org/";>Savannah</a>.  For
@@ -145,7 +180,6 @@
 manager should be subscribed to:</p>
 
 <ol>
-<li>www-discuss (member)</li>
 <li>www-commits (admin)</li>
 <li>trans-coord-discuss (member+admin)</li>
 <li>trans-coord-news (admin)</li>
@@ -186,7 +220,7 @@
 There are also <a href="/contact/">other ways to contact</a> 
 the FSF.
 <br />
-Please send broken links and other corrections (or suggestions) to
+Please send broken links and other corrections or suggestions to
 <a href="mailto:address@hidden";><em>address@hidden</em></a>.
 </p>
 
@@ -202,7 +236,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2007/06/04 19:46:46 $
+$Date: 2007/11/24 10:38:11 $
 <!-- timestamp end -->
 </p>
 </div>