# Brouillon de la traduction (ou traduction du brouillon ?).

diff --git a/Debian/debiâneries/réaction-en-chaîne.en.po b/Debian/debiâneries/réaction-en-chaîne.en.po
index ae45592d86f0ba3feb8073fc7658648d7c825185..54bad906f141b2dd93ab6b307eb3f1612eb7c0ea 100644 (file)
--- a/Debian/debiâneries/réaction-en-chaîne.en.po
+++ b/Debian/debiâneries/réaction-en-chaîne.en.po
@@ -1,35 +1,35 @@
 # SOME DESCRIPTIVE TITLE
 # Copyright (C) YEAR Free Software Foundation, Inc.
 # This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+# Charles Plessy <https://launchpad.net/~plessy>, 2011.
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "POT-Creation-Date: 2011-02-10 09:46+0900\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <LL@li.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2011-02-10 09:59+0900\n"
+"Last-Translator: Charles Plessy <https://launchpad.net/~plessy>\n"
+"Language-Team: Hopla\n"
+"Language: en\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"X-Generator: Virtaal 0.6.1\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "[[!meta date=\"vendredi 4 février 2011, 09:45:28 (UTC+0900)\"]]\n"
-msgstr ""
+msgstr "[[!meta date=\"vendredi 4 février 2011, 09:45:28 (UTC+0900)\"]]\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "[[!meta updated=\"vendredi 4 février 2011, 09:45:28 (UTC+0900)\"]]\n"
-msgstr ""
+msgstr "[[!meta updated=\"vendredi 4 février 2011, 09:45:28 (UTC+0900)\"]]\n"
 
 #. type: Plain text
 #, no-wrap
 msgid "[[!tag Debian brouillon]]\n"
-msgstr ""
+msgstr "[[!tag Debian brouillon]]\n"
 
 #. type: Plain text
 #, no-wrap
@@ -51,6 +51,17 @@ msgid ""
 "possible avec un compilateur récent. Bref, chaque paquet laisse son "
 "_empreinte_ dans l'écosystème Debian."
 msgstr ""
+"Now that maintain several dozens of packages in Debian, I think twice before "
+"uploading a new one. Does it have a future, a public ? Some of the packages "
+"I prepare are available on [git.debian.org](http://git.debian.org), and are "
+"listed in Debian Med's [tasks](http://debian-"
+"med.alioth.debian.org/tasks/index) pages. It would not take me long to "
+"finish most of them, but that does not take into account the time others "
+"will spend on it. They will make our archive bigger. Our quality tests "
+"longer to execute. Somebody will translate their description. Somebody else "
+"will perhaps write a security patch someday, or a patch to make the package "
+"compilable with a new version of GCC. All in all, each package has a "
+"_footprint_ in Debian's ecosystem."
 
 #. type: Plain text
 #, no-wrap
@@ -65,6 +76,15 @@ msgid ""
 "CopyrightReview desc=\"correction des nouveaux paquets\"]] qui fonctionne comme\n"
 "une réaction en chaîne.\n"
 msgstr ""
+"That footprint starts early, as soon as the package is sent to the NEW "
+"queue. For instance, I kept by mistake some old content in the copyright "
+"file of `clustalw`, that was recently freed and has to go through the NEW "
+"queue to be transferred from the _non-free_ to the _main_ area of our "
+"archive. That costed a small of exchange of emails, that could have been "
+"avoided. Our packages should be perfect, but that is difficult to achieve "
+"alone. For that reason, I proposed two years ago a [[!debwiki\n"
+"CopyrightReview desc=\"package review system\"]], that functions like a _chain "
+"reaction_."
 
 #. type: Plain text
 msgid ""
@@ -83,3 +103,15 @@ msgid ""
 "tarent.de/2011/02/you-are-uploading-too-fast/). Alors, pourquoi ne pas "
 "essayer de donner un coup de main ?"
 msgstr ""
+"The principle is simple. After uploading to the [NEW queue](http://ftp-"
+"master.debian.org/new.html), download two neighbor packages and check their "
+"_copyright_ file. The errors found can be corrected by their maintainer "
+"before the the FTP team inspects it, which save their time. For instance, "
+"after uploading `tabix`, I found an error in `metiathekview`, that was "
+"corrected. That compensates for my mistake with `clustalw`. If each person "
+"receiving a package review does a review of two other packages, that will "
+"create a chain reaction that will clean the queue from the simplest "
+"mistakes, leaving only the really problematic cases. As Torsten noted "
+"recently, the [NEW queue is getting "
+"long](http://twerne.blog.tarent.de/2011/02/you-are-uploading-too-fast/). So "
+"how about trying to help?"