# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+# Copyright (C) 2007 Free Software Foundation, Inc.
+# <>, 2007.
+# , fuzzy
+#
#
-#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-06-26 16:13+0000\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"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2007-07-01 21:16+0000\n"
+"PO-Revision-Date: 2007-07-01 23:10+0000\n"
+"Last-Translator: <>\n"
+"Language-Team: \n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: ENCODING"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: "
# type: Content of: <chapter><title>
-#: developer-duties.dbk:5
+#: developer-duties.dbk:7
msgid "Debian Developer's Duties"
-msgstr ""
+msgstr "Les charges du responsable Debian"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:7
+#: developer-duties.dbk:9
msgid "Maintaining your Debian information"
-msgstr ""
+msgstr "Mise à jour de vos références Debian"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:9
+#: developer-duties.dbk:11
msgid ""
"There's a LDAP database containing information about Debian developers at "
-"<ulink url=\"https://db.debian.org/\"></ulink>. You should enter your "
-"information there and update it as it changes. Most notably, make sure that "
-"the address where your debian.org email gets forwarded to is always up to "
-"date, as well as the address where you get your debian-private subscription "
-"if you choose to subscribe there."
+"<ulink url=\"&url-debian-db;\"></ulink>. You should enter your information "
+"there and update it as it changes. Most notably, make sure that the address "
+"where your debian.org email gets forwarded to is always up to date, as well "
+"as the address where you get your debian-private subscription if you choose "
+"to subscribe there."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:17
+#: developer-duties.dbk:19
msgid ""
-"For more information about the database, please see <xref "
-"linkend=\"devel-db\"/> ."
+"For more information about the database, please see <xref linkend=\"devel-db"
+"\"/> ."
msgstr ""
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:23
+#: developer-duties.dbk:25
msgid "Maintaining your public key"
-msgstr ""
+msgstr "Gérer votre clé publique"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:25
+#: developer-duties.dbk:27
msgid ""
"Be very careful with your private keys. Do not place them on any public "
-"servers or multiuser machines, such as the Debian servers (see <xref "
-"linkend=\"server-machines\"/> ). Back your keys up; keep a copy offline. "
-"Read the documentation that comes with your software; read the <ulink "
-"url=\"http://www.cam.ac.uk.pgp.net/pgpnet/pgp-faq/\">PGP FAQ</ulink>."
+"servers or multiuser machines, such as the Debian servers (see <xref linkend="
+"\"server-machines\"/> ). Back your keys up; keep a copy offline. Read the "
+"documentation that comes with your software; read the <ulink url=\"&url-pgp-"
+"faq;\">PGP FAQ</ulink>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:32
+#: developer-duties.dbk:34
msgid ""
"You need to ensure not only that your key is secure against being stolen, "
"but also that it is secure against being lost. Generate and make a copy "
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:38
+#: developer-duties.dbk:40
msgid ""
"If you add signatures to your public key, or add user identities, you can "
"update the Debian key ring by sending your key to the key server at "
-"<literal>keyring.debian.org</literal>."
+"<literal>&keyserver-host;</literal>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:43
+#: developer-duties.dbk:45
msgid ""
"If you need to add a completely new key or remove an old key, you need to "
"get the new key signed by another developer. If the old key is compromised "
"or invalid, you also have to add the revocation certificate. If there is no "
"real reason for a new key, the Keyring Maintainers might reject the new "
-"key. Details can be found at <ulink "
-"url=\"http://keyring.debian.org/replacing_keys.html\"></ulink>."
+"key. Details can be found at <ulink url=\"http://&keyserver-host;/"
+"replacing_keys.html\"></ulink>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:51
+#: developer-duties.dbk:53
msgid ""
-"The same key extraction routines discussed in <xref "
-"linkend=\"registering\"/> apply."
+"The same key extraction routines discussed in <xref linkend=\"registering\"/"
+"> apply."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:55
+#: developer-duties.dbk:57
msgid ""
"You can find a more in-depth discussion of Debian key maintenance in the "
-"documentation of the <systemitem "
-"role=\"package\">debian-keyring</systemitem> package."
+"documentation of the <systemitem role=\"package\">debian-keyring</"
+"systemitem> package."
msgstr ""
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:62
+#: developer-duties.dbk:64
msgid "Voting"
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:64
+#: developer-duties.dbk:66
msgid ""
"Even though Debian isn't really a democracy, we use a democratic process to "
"elect our leaders and to approve general resolutions. These procedures are "
-"defined by the <ulink "
-"url=\"http://www.debian.org/devel/constitution\">Debian "
-"Constitution</ulink>."
+"defined by the <ulink url=\"&url-constitution;\">Debian Constitution</ulink>."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:70
+#: developer-duties.dbk:72
msgid ""
"Other than the yearly leader election, votes are not routinely held, and "
"they are not undertaken lightly. Each proposal is first discussed on the "
-"<email>debian-vote@lists.debian.org</email> mailing list and it requires "
-"several endorsements before the project secretary starts the voting "
-"procedure."
+"&email-debian-vote; mailing list and it requires several endorsements before "
+"the project secretary starts the voting procedure."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:76
+#: developer-duties.dbk:78
msgid ""
"You don't have to track the pre-vote discussions, as the secretary will "
-"issue several calls for votes on "
-"<email>debian-devel-announce@lists.debian.org</email> (and all developers "
-"are expected to be subscribed to that list). Democracy doesn't work well if "
-"people don't take part in the vote, which is why we encourage all developers "
-"to vote. Voting is conducted via GPG-signed/encrypted email messages."
+"issue several calls for votes on &email-debian-devel-announce; (and all "
+"developers are expected to be subscribed to that list). Democracy doesn't "
+"work well if people don't take part in the vote, which is why we encourage "
+"all developers to vote. Voting is conducted via GPG-signed/encrypted email "
+"messages."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:84
+#: developer-duties.dbk:86
msgid ""
-"The list of all proposals (past and current) is available on the <ulink "
-"url=\"http://www.debian.org/vote/\">Debian Voting Information</ulink> page, "
-"along with information on how to make, second and vote on proposals."
+"The list of all proposals (past and current) is available on the <ulink url="
+"\"&url-vote;\">Debian Voting Information</ulink> page, along with "
+"information on how to make, second and vote on proposals."
msgstr ""
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:91
+#: developer-duties.dbk:93
msgid "Going on vacation gracefully"
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:93
+#: developer-duties.dbk:95
msgid ""
"It is common for developers to have periods of absence, whether those are "
"planned vacations or simply being buried in other work. The important thing "
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:100
+#: developer-duties.dbk:102
msgid ""
"Usually this means that other developers are allowed to NMU (see <xref "
"linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
msgstr ""
# type: Content of: <chapter><section><para><footnote>
-#: developer-duties.dbk:107
+#: developer-duties.dbk:109
msgid ""
"In order to inform the other developers, there are two things that you "
-"should do. First send a mail to "
-"<email>debian-private@lists.debian.org</email> with [VAC] prepended to the "
-"subject of your message<footnote>"
+"should do. First send a mail to <email>debian-private@&lists-host;</email> "
+"with [VAC] prepended to the subject of your message<footnote>"
msgstr ""
# type: Content of: <chapter><section><para><footnote><para>
-#: developer-duties.dbk:109
+#: developer-duties.dbk:111
msgid ""
"This is so that the message can be easily filtered by people who don't want "
"to read vacation notices."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:111
+#: developer-duties.dbk:113
msgid ""
"</footnote> and state the period of time when you will be on vacation. You "
"can also give some special instructions on what to do if a problem occurs."
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:116
+#: developer-duties.dbk:118
msgid ""
"The other thing to do is to mark yourself as on vacation in the <link "
"linkend=\"devel-db\">Debian developers' LDAP database</link> (this "
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:122
+#: developer-duties.dbk:124
msgid ""
-"Ideally, you should sign up at the <ulink "
-"url=\"http://nm.debian.org/gpg.php\">GPG coordination site</ulink> when "
-"booking a holiday and check if anyone there is looking for signing. This is "
-"especially important when people go to exotic places where we don't have any "
-"developers yet but where there are people who are interested in applying."
+"Ideally, you should sign up at the <ulink url=\"&url-newmaint-db;gpg.php"
+"\">GPG coordination site</ulink> when booking a holiday and check if anyone "
+"there is looking for signing. This is especially important when people go "
+"to exotic places where we don't have any developers yet but where there are "
+"people who are interested in applying."
msgstr ""
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:131
+#: developer-duties.dbk:133
msgid "Coordination with upstream developers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:133
+#: developer-duties.dbk:135
msgid ""
"A big part of your job as Debian maintainer will be to stay in contact with "
"the upstream developers. Debian users will sometimes report bugs that are "
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:140
+#: developer-duties.dbk:142
msgid ""
"While it's not your job to fix non-Debian specific bugs, you may freely do "
"so if you're able. When you make such fixes, be sure to pass them on to the "
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:147
+#: developer-duties.dbk:149
msgid ""
"If you need to modify the upstream sources in order to build a policy "
"compliant package, then you should propose a nice fix to the upstream "
msgstr ""
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:156
+#: developer-duties.dbk:158
msgid "Managing release-critical bugs"
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:158
+#: developer-duties.dbk:160
msgid ""
"Generally you should deal with bug reports on your packages as described in "
"<xref linkend=\"bug-handling\"/> . However, there's a special category of "
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:169
+#: developer-duties.dbk:171
msgid ""
-"Developers who are part of the <ulink url=\"http://qa.debian.org/\">Quality "
+"Developers who are part of the <ulink url=\"&url-debian-qa;\">Quality "
"Assurance</ulink> group are following all such bugs, and trying to help "
"whenever possible. If, for any reason, you aren't able fix an RC bug in a "
"package of yours within 2 weeks, you should either ask for help by sending a "
-"mail to the Quality Assurance (QA) group "
-"<email>debian-qa@lists.debian.org</email>, or explain your difficulties and "
-"present a plan to fix them by sending a mail to the bug report. Otherwise, "
-"people from the QA group may want to do a Non-Maintainer Upload (see <xref "
-"linkend=\"nmu\"/> ) after trying to contact you (they might not wait as long "
-"as usual before they do their NMU if they have seen no recent activity from "
-"you in the BTS)."
+"mail to the Quality Assurance (QA) group <email>debian-qa@&lists-host;</"
+"email>, or explain your difficulties and present a plan to fix them by "
+"sending a mail to the bug report. Otherwise, people from the QA group may "
+"want to do a Non-Maintainer Upload (see <xref linkend=\"nmu\"/> ) after "
+"trying to contact you (they might not wait as long as usual before they do "
+"their NMU if they have seen no recent activity from you in the BTS)."
msgstr ""
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:184
+#: developer-duties.dbk:186
msgid "Retiring"
msgstr ""
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:186
+#: developer-duties.dbk:188
msgid ""
"If you choose to leave the Debian project, you should make sure you do the "
"following steps:"
msgstr ""
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:192
-msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
+#: developer-duties.dbk:194
+msgid ""
+"Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
msgstr ""
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:197
+#: developer-duties.dbk:199
msgid ""
"Send an gpg-signed email about why you are leaving the project to "
-"<email>debian-private@lists.debian.org</email>."
+"<email>debian-private@&lists-host;</email>."
msgstr ""
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:203
+#: developer-duties.dbk:205
msgid ""
"Notify the Debian key ring maintainers that you are leaving by opening a "
"ticket in Debian RT by sending a mail to keyring@rt.debian.org with the "
"words 'Debian RT' somewhere in the subject line (case doesn't matter)."
msgstr ""
+
~ianmdlvl / developers-reference.git / blobdiff