msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-06 17:34-0400\n"
+"POT-Creation-Date: 2011-03-03 11:18-0400\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"
"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: 8bit\n"
#. type: Content of: <chapter><title>
#: developer-duties.dbk:7
#. type: Content of: <chapter><section><para>
#: 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:25
+#: developer-duties.dbk:24
msgid "Maintaining your public key"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:27
+#: developer-duties.dbk:26
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=\"&url-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:34
+#: developer-duties.dbk:33
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:40
+#: developer-duties.dbk:39
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 "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:45
+#: developer-duties.dbk:44
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://&keyserver-host;/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:53
+#: developer-duties.dbk:52
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:57
+#: developer-duties.dbk:56
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:64
+#: developer-duties.dbk:63
msgid "Voting"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:66
+#: developer-duties.dbk:65
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=\"&url-constitution;\">Debian "
-"Constitution</ulink>."
+"defined by the <ulink url=\"&url-constitution;\">Debian Constitution</ulink>."
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:72
+#: developer-duties.dbk:71
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 "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:78
+#: developer-duties.dbk:77
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; (and all "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:86
+#: developer-duties.dbk:85
msgid ""
-"The list of all proposals (past and current) is available on the <ulink "
-"url=\"&url-vote;\">Debian Voting Information</ulink> page, along with "
+"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:93
+#: developer-duties.dbk:92
msgid "Going on vacation gracefully"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:95
+#: developer-duties.dbk:94
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:102
+#: developer-duties.dbk:101
msgid ""
"Usually this means that other developers are allowed to NMU (see <xref "
-"linkend=\"nmu\"/> ) your package if a big problem (release critical bug, "
+"linkend=\"nmu\"/>) your package if a big problem (release critical bug, "
"security update, etc.) occurs while you're on vacation. Sometimes it's "
"nothing as critical as that, but it's still appropriate to let others know "
"that you're unavailable."
msgstr ""
#. type: Content of: <chapter><section><para><footnote><para>
-#: developer-duties.dbk:111
+#: developer-duties.dbk:110
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:109
+#: developer-duties.dbk:108
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-host;</email> "
-"with [VAC] prepended to the subject of your message<placeholder "
-"type=\"footnote\" id=\"0\"/> 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 "
+"with [VAC] prepended to the subject of your message<placeholder type="
+"\"footnote\" id=\"0\"/> 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:118
+#: developer-duties.dbk:117
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:124
+#: developer-duties.dbk:123
msgid ""
-"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."
+"Ideally, you should sign up at the <ulink url=\"&url-gpg-coord;\">GPG "
+"coordination pages</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:133
+#: developer-duties.dbk:132
msgid "Coordination with upstream developers"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:135
+#: developer-duties.dbk:134
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:142
+#: developer-duties.dbk:141
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:149
+#: developer-duties.dbk:148
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><para>
-#: developer-duties.dbk:156
+#: developer-duties.dbk:155
msgid ""
"If you find that the upstream developers are or become hostile towards "
"Debian or the free software community, you may want to re-consider the need "
msgstr ""
#. type: Content of: <chapter><section><title>
-#: developer-duties.dbk:164
+#: developer-duties.dbk:163
msgid "Managing release-critical bugs"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:166
+#: developer-duties.dbk:165
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 "
+"<xref linkend=\"bug-handling\"/>. However, there's a special category of "
"bugs that you need to take care of — the so-called release-critical bugs (RC "
"bugs). All bug reports that have severity <literal>critical</literal>, "
"<literal>grave</literal> or <literal>serious</literal> are considered to "
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:177
+#: developer-duties.dbk:176
msgid ""
"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-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)."
+"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:192
+#: developer-duties.dbk:191
msgid "Retiring"
msgstr ""
#. type: Content of: <chapter><section><para>
-#: developer-duties.dbk:194
+#: developer-duties.dbk:193
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:200
-msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
+#: developer-duties.dbk:199
+msgid ""
+"Orphan all your packages, as described in <xref linkend=\"orphaning\"/>."
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:205
+#: developer-duties.dbk:204
msgid ""
"Send an gpg-signed email about why you are leaving the project to "
"<email>debian-private@&lists-host;</email>."
msgstr ""
#. type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:211
+#: developer-duties.dbk:210
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)."
+"ticket in Debian RT by sending a mail to &email-keyring; with the words "
+"'Debian RT' somewhere in the subject line (case doesn't matter)."
msgstr ""
~ianmdlvl / developers-reference.git / blobdiff