msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2008-08-08 11:33-0300\n"
+"POT-Creation-Date: 2010-05-06 17:34-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"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: ENCODING"
-# type: Content of: <chapter><title>
+#. type: Content of: <chapter><title>
#: developer-duties.dbk:7
msgid "Debian Developer's Duties"
msgstr ""
-# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:9
msgid "Maintaining your Debian information"
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:11
msgid ""
"There's a LDAP database containing information about Debian developers at "
"to subscribe there."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:19
msgid ""
"For more information about the database, please see <xref "
"linkend=\"devel-db\"/> ."
msgstr ""
-# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:25
msgid "Maintaining your public key"
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:27
msgid ""
"Be very careful with your private keys. Do not place them on any public "
"url=\"&url-pgp-faq;\">PGP FAQ</ulink>."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:34
msgid ""
"You need to ensure not only that your key is secure against being stolen, "
"your key is lost."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:40
msgid ""
"If you add signatures to your public key, or add user identities, you can "
"<literal>&keyserver-host;</literal>."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:45
msgid ""
"If you need to add a completely new key or remove an old key, you need to "
"url=\"http://&keyserver-host;/replacing_keys.html\"></ulink>."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:53
msgid ""
"The same key extraction routines discussed in <xref "
"linkend=\"registering\"/> apply."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:57
msgid ""
"You can find a more in-depth discussion of Debian key maintenance in the "
"role=\"package\">debian-keyring</systemitem> package."
msgstr ""
-# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:64
msgid "Voting"
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:66
msgid ""
"Even though Debian isn't really a democracy, we use a democratic process to "
"Constitution</ulink>."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:72
msgid ""
"Other than the yearly leader election, votes are not routinely held, and "
"the project secretary starts the voting procedure."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:78
msgid ""
"You don't have to track the pre-vote discussions, as the secretary will "
"messages."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:86
msgid ""
"The list of all proposals (past and current) is available on the <ulink "
"information on how to make, second and vote on proposals."
msgstr ""
-# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:93
msgid "Going on vacation gracefully"
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:95
msgid ""
"It is common for developers to have periods of absence, whether those are "
"or other duties in the project."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:102
msgid ""
"Usually this means that other developers are allowed to NMU (see <xref "
"that you're unavailable."
msgstr ""
-# type: Content of: <chapter><section><para><footnote>
-#: 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-host;</email> "
-"with [VAC] prepended to the subject of your message<footnote>"
-msgstr ""
-
-# type: Content of: <chapter><section><para><footnote><para>
+#. type: Content of: <chapter><section><para><footnote><para>
#: 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:113
+#
. type: Content of: <chapter><section><para>
+#: developer-duties.dbk:109
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."
+"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 "
+"problem occurs."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:118
msgid ""
"The other thing to do is to mark yourself as on vacation in the <link "
"remove the on vacation flag when you come back!"
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:124
msgid ""
"Ideally, you should sign up at the <ulink "
"developers yet but where there are people who are interested in applying."
msgstr ""
-# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><title>
#: developer-duties.dbk:133
msgid "Coordination with upstream developers"
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:135
msgid ""
"A big part of your job as Debian maintainer will be to stay in contact with "
"future upstream release."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:142
msgid ""
"While it's not your job to fix non-Debian specific bugs, you may freely do "
"patches upstream."
msgstr ""
-# type: Content of: <chapter><section><para>
+#
. type: Content of: <chapter><section><para>
#: developer-duties.dbk:149
msgid ""
"If you need to modify the upstream sources in order to build a policy "
"not to fork from the upstream sources."
msgstr ""
-# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:158
+#. type: Content of: <chapter><section><para>
+#: developer-duties.dbk:156
+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 "
+"to include the software in Debian. Sometimes the social cost to the Debian "
+"community is not worth the benefits the software may bring."
+msgstr ""
+
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:164
msgid "Managing release-critical bugs"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:160
+#
. type: Content of: <chapter><section><para>
+#: developer-duties.dbk:166
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 "
"to be corrected as quickly as possible."
msgstr ""
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:171
+#
. type: Content of: <chapter><section><para>
+#: developer-duties.dbk:177
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 "
"you in the BTS)."
msgstr ""
-# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:186
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:192
msgid "Retiring"
msgstr ""
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:188
+#
. type: Content of: <chapter><section><para>
+#: developer-duties.dbk:194
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:194
+#
. type: Content of: <chapter><section><orderedlist><listitem><para>
+#: developer-duties.dbk:200
msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
msgstr ""
-# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:199
+#
. type: Content of: <chapter><section><orderedlist><listitem><para>
+#: developer-duties.dbk:205
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:205
+#
. type: Content of: <chapter><section><orderedlist><listitem><para>
+#: developer-duties.dbk:211
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 "
~ianmdlvl / developers-reference.git / blobdiff