+"As a package maintainer, you're supposed to provide high-quality packages "
+"that are well integrated in the system and that adhere to the Debian Policy."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:16
+msgid "Work towards the next <literal>stable</literal> release"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:18
+msgid ""
+"Providing high-quality packages in <literal>unstable</literal> is not "
+"enough, most users will only benefit from your packages when they are "
+"released as part of the next <literal>stable</literal> release. You are thus "
+"expected to collaborate with the release team to ensure your packages get "
+"included."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:24
+msgid ""
+"More concretely, you should monitor whether your packages are migrating to "
+"<literal>testing</literal> (see <xref linkend=\"testing\"/>). When the "
+"migration doesn't happen after the test period, you should analyze why and "
+"work towards fixing this. It might mean fixing your package (in the case of "
+"release-critical bugs or failures to build on some architecture) but it can "
+"also mean updating (or fixing, or removing from <literal>testing</literal>) "
+"other packages to help complete a transition in which your package is "
+"entangled due to its dependencies. The release team might provide you some "
+"input on the current blockers of a given transition if you are not able to "
+"identify them."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:37
+msgid "Maintain packages in <literal>stable</literal>"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:39
+msgid ""
+"Most of the package maintainer's work goes into providing updated versions "
+"of packages in <literal>unstable</literal>, but his job also entails taking "
+"care of the packages in the current <literal>stable</literal> release."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:44
+msgid ""
+"While changes in <literal>stable</literal> are discouraged, they are "
+"possible. Whenever a security problem is reported, you should collaborate "
+"with the security team to provide a fixed version (see <xref "
+"linkend=\"bug-security\"/>). When bugs of severity important (or more) are "
+"reported against the <literal>stable</literal> version of your packages, you "
+"should consider providing a targeted fix. You can ask the "
+"<literal>stable</literal> release team whether they would accept such an "
+"update and then prepare a <literal>stable</literal> upload (see <xref "
+"linkend=\"upload-stable\"/>)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:56
+msgid "Manage release-critical bugs"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:58
+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 "
+"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> make the package "
+"unsuitable for inclusion in the next <literal>stable</literal> release. "
+"They can thus delay the Debian release (when they affect a package in "
+"<literal>testing</literal>) or block migrations to "
+"<literal>testing</literal> (when they only affect the package in "
+"<literal>unstable</literal>). In the worst scenario, they will lead to the "
+"package's removal. That's why these bugs need to be corrected as quickly as "
+"possible."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:70
+msgid ""
+"If, for any reason, you aren't able fix an RC bug in a package of yours "
+"within 2 weeks (for example due to time constraints, or because it's "
+"difficult to fix), you should mention it clearly in the bug report and you "
+"should tag the bug <literal>help</literal> to invite other volunteers to "
+"chime in. Be aware that RC bugs are frequently the targets of Non-Maintainer "
+"Uploads (see <xref linkend=\"nmu\"/>) because they can block the "
+"<literal>testing</literal> migration of many packages."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:79
+msgid ""
+"Lack of attention to RC bugs is often interpreted by the QA team as a sign "
+"that the maintainer has disappeared without properly orphaning his package. "
+"The MIA team might also get involved, which could result in your packages "
+"being orphaned (see <xref linkend=\"mia-qa\" />)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:87
+msgid "Coordination with upstream developers"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:89
+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 "
+"not specific to Debian to our bug tracking system. You have to forward "
+"these bug reports to the upstream developers so that they can be fixed in a "
+"future upstream release."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:96
+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 "
+"upstream maintainers as well. Debian users and developers will sometimes "
+"submit patches to fix upstream bugs — you should evaluate and forward these "
+"patches upstream."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:103
+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 "
+"developers which can be included there, so that you won't have to modify the "
+"sources of the next upstream version. Whatever changes you need, always try "
+"not to fork from the upstream sources."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:110
+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:120
+msgid "Administrative Duties"
+msgstr ""
+
+#. type: Content of: <chapter><section><para>
+#: developer-duties.dbk:121
+msgid ""
+"A project of the size of Debian relies on some administrative infrastructure "
+"to keep track of everything. As a project member, you have some duties to "
+"ensure everything keeps running smoothly."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:126
+msgid "Maintaining your Debian information"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:128
+msgid ""