# German translation of developers-reference: developer-duties. # This file is distributed under the same license as the # developers-reference package. # Chris Leick , 2011. # msgid "" msgstr "" "Project-Id-Version: developers-reference 3.4.4\n" "POT-Creation-Date: 2011-09-10 14:03-0400\n" "PO-Revision-Date: 2011-04-04 21:41+0100\n" "Last-Translator: Chris Leick \n" "Language-Team: German \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. type: Content of: #: developer-duties.dbk:7 msgid "Debian Developer's Duties" msgstr "Pflichten von Debian-Entwicklern" #. type: Content of: <chapter><section><title> #: developer-duties.dbk:10 msgid "Package Maintainer's Duties" msgstr "" #. type: Content of: <chapter><section><para> #: developer-duties.dbk:11 msgid "" "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 #, fuzzy #| msgid "Managing release-critical bugs" msgid "Manage release-critical bugs" msgstr "Verwalten veröffentlichungskritischer Fehler" #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:58 #, fuzzy #| 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> are " #| "considered to have an impact on whether the package can be released in " #| "the next stable release of Debian. These bugs can delay the Debian " #| "release and/or can justify the removal of a package at freeze time. " #| "That's why these bugs need to be corrected as quickly as possible." 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 "" "Sie sollten Fehlerberichte zu Ihren Paketen generell erledigen, wie es in " "<xref linkend=\"bug-handling\"/> beschrieben wird. Es gibt jedoch eine " "spezielle Fehlerkategorie, auf die Sie besonders Acht geben sollten – " "sogenannte veröffentlichungskritische Fehler (release critical bugs/RC-" "Fehler). Alle Fehlerberichte, mit den Dringlichkeiten <literal>critical</" "literal>, <literal>grave</literal> oder <literal>serious</literal> werden so " "angesehen, als ob sie einen Einfluss darauf haben, ob das Paket in der " "nächsten stabilen Veröffentlichung von Debian enthalten sein kann. Diese " "Fehler können die Debian-Veröffentlichung verzögern und/oder die Entfernung " "des Pakets zur Zeit des Einfrierens rechtfertigen. Daher müssen diese Fehler " "so schnell wie möglich behoben werden." #. 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 "Abstimmung mit Originalautoren" #. 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 "" "Ein Großteil Ihrer Arbeit als Debian-Betreuer wird darin bestehen, mit den " "Autoren des Programms Kontakt zu halten. Manchmal melden Debian-Anwender " "Fehler an die Debian-Fehlerdatenbank, die nicht Debian-spezifisch sind. Sie " "müssen diese Fehler an die Programmautoren weiterleiten, so dass die " "Programmautoren sie in einer zukünftigen Veröffentlichung beheben können." #. 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 "" "Obwohl es nicht Ihre Arbeit ist, nicht Debian-spezifische Fehler zu beheben, " "können Sie dies dennoch tun, wenn Sie dazu in der Lage sind. Wenn Sie solche " "Fehler beheben, stellen Sie sicher, dass Sie ihre Korrekturen auch an die " "ursprünglichen Betreuer weiterleiten. Debian-Anwender und -Entwickler " "werden manchmal Patche schicken, um Fehler im Ursprungsprogramm zu beheben – " "Sie sollten diese Patche auswerten und an die ursprünglichen Autoren " "weiterleiten." #. 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 "" "Falls Sie die ursprünglichen Quellen verändern müssen, um ein den " "Richtlinien entsprechendes Paket zu erstellen, dann sollten Sie freundlich " "eine Korrektur vorschlagen, die dort eingefügt werden kann, so dass Sie die " "Quellen bei der nächsten Version der Urprungsautoren nicht ändern müssen. " "Ganz gleich, welche Änderungen sie möchten – versuchen Sie ein Verzweigen " "von den ursprünglichen Quellen zu vermeiden." #. 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 "" "Wenn Sie der Ansicht sind, dass die ursprünglichen Entwickler Debian oder " "der Gemeinschaft rund um freie Software ablehnend gegenüber stehen, könnten " "Sie es sich nochmal überlegen, ob Sie die Software in Debian einbringen " "möchten. Manchmal sind es die gesellschaftlichen Kosten höher, als der " "Gewinn, den die Software mitbringt." #. 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 "Verwaltung Ihrer Debian-Informationen" #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:128 msgid "" "There's a LDAP database containing information about Debian developers at " "<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 "" "Es gibt unter <ulink url=\"&url-debian-db;\"></ulink> eine LDAP-Datenbank, " "die Informationen über Debian-Entwickler enthält. Sie sollten Ihre " "Informationen dort eintragen und bei Änderungen aktualisieren. Stellen Sie " "insbesondere sicher, dass Ihre Weiterleitungsadresse für Ihre debian.org-E-" "Mails immer aktuell ist. Das gilt auch für die Adresse, zu der Ihre »debian-" "private«-E-Mails versendet werden, wenn Sie sich auch dort angemeldet haben." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:136 msgid "" "For more information about the database, please see <xref linkend=\"devel-db" "\"/>." msgstr "" "Um weitere Informationen über die Datenbank zu erhalten, lesen Sie bitte " "<xref linkend=\"devel-db\"/>." #. type: Content of: <chapter><section><section><title> #: developer-duties.dbk:141 msgid "Maintaining your public key" msgstr "Verwalten Ihres öffentlichen Schlüssels" #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:143 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>." msgstr "" "Gehen Sie sehr vorsichtig mit Ihren privaten Schlüsseln um. Legen Sie sie " "nicht auf öffentlichen Servern oder Maschinen mit mehreren Benutzern ab, wie " "den Debian-Servern (siehe <xref linkend=\"server-machines\"/>). Sichern Sie " "Ihre Schlüssel. Behalten Sie eine Kopie offline. Lesen Sie die " "Dokumentation, die Ihrer Software beiliegt. Lesen Sie die <ulink url=\"&url-" "pgp-faq;\">PGP-FAQ</ulink>." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:150 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 " "(best also in paper form) of your revocation certificate; this is needed if " "your key is lost." msgstr "" "Sie müssen nicht nur dafür sorgen, dass Ihr Schlüssel sicher vor Diebstahl " "ist, sondern auch, dass er nicht verloren geht. Generieren Sie Ihr Widerrufs-" "Zertifikat und erstellen Sie eine Kopie davon (am besten in Papierform). " "Dies wird benötigt, wenn Sie Ihren Schlüssel verloren haben." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:156 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>&keyserver-host;</literal>." msgstr "" "Falls Sie Ihrem öffentlichen Schlüssel Signaturen oder Benutzerkennungen " "hinzufügen, können Sie den Debian-Schlüsselring aktualisieren, indem Sie " "Ihren Schlüssel an den Schlüsselserver unter <literal>&keyserver-host;</" "literal> senden." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:161 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>." msgstr "" "Wenn Sie einen komplett neuen Schlüssel hinzufügen oder einen alten " "entfernen möchten, benötigen Sie den durch einen anderen Entwickler neu " "signierten Schlüssel. Falls der alte Schlüssel kompromittiert oder ungültig " "ist, müssen Sie außerdem das Widerrufs-Zertifikat hinzufügen. Falls es " "keinen vernünftigen Grund für einen neuen Schlüssel gibt, können die " "Betreuer des Schlüsselrings den neuen Schlüssel ablehnen. Details finden Sie " "unter <ulink url=\"http://&keyserver-host;/replacing_keys.html\"></ulink>." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:169 msgid "" "The same key extraction routines discussed in <xref linkend=\"registering\"/" "> apply." msgstr "" "Es werden die gleichen Schlüssel-Extrahierungsroutinen angewandt, wie sie " "unter <xref linkend=\"registering\"/> besprochen wurden." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:173 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." msgstr "" "Eine weiterreichende Erörterung der Debian-Schlüsselverwaltung können Sie in " "der Dokumentation des Pakets <systemitem role=\"package\">debian-keyring</" "systemitem> finden." #. type: Content of: <chapter><section><section><title> #: developer-duties.dbk:180 msgid "Voting" msgstr "Abstimmungen" # http://www.debian.org/devel/constitution #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:182 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>." msgstr "" "Obwohl Debian nicht wirklich demokratisch ist, werden demokratische Prozesse " "benutzt, um das Führungspersonal auszuwählen und generellen Entschlüssen " "zuzustimmen. Diese Prozeduren sind durch die <ulink url=\"&url-constitution;" "\">Debian-Verfassung</ulink> definiert." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:188 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; mailing list and it requires several endorsements before " "the project secretary starts the voting procedure." msgstr "" "Im Gegensatz zur jährlichen Wahl des Projektleiters werden keine " "regelmäßigen Abstimmungen abgehalten und wenn doch, dann nicht einfach so. " "Jeder Vorschlag wird zuerst auf der Mailingliste &email-debian-vote; " "besprochen und benötigt mehrere Befürworter, bevor der Projektsekretär die " "Abstimmungsprozedur in Gang setzt." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:194 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 " "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 "" "Sie müssen vor der Abstimmung nicht alle Diskussionen verfolgen, da der " "Sekretär mehrere Aufrufe zur Abstimmung auf &email-debian-devel-announce; " "herausgibt (Und von allen Entwicklern wird erwartet, das sie diese Liste " "abonniert haben). Demokratie funktioniert nicht richtig, wenn die Leute " "nicht an Abstimmungen teilnehmen, daher wird allen Entwicklern empfohlen " "abzustimmen. Die Abstimmung wird mittels GPG-signierte/verschlüsselte E-" "Mails durchgeführt." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:202 msgid "" "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 "" "Die Liste aller(früheren und aktuellen) Vorschläge ist auf der Seite <ulink " "url=\"&url-vote;\">Debian-Abstimmungs-Informationen</ulink> verfügbar, " "ebenso die Informationen, wie Vorschläge gemacht und unterstützt werden und " "darüber abgestimmt wird." #. type: Content of: <chapter><section><section><title> #: developer-duties.dbk:209 msgid "Going on vacation gracefully" msgstr "Elegant Urlaub machen" #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:211 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 " "to notice is that other developers need to know that you're on vacation so " "that they can do whatever is needed if a problem occurs with your packages " "or other duties in the project." msgstr "" "Es ist bei Entwicklern üblich, dass es Zeiten gibt, in denen sie abwesend " "sind, entweder wegen geplanten Ferien oder einfach, weil sie unter anderer " "Arbeit begraben sind. Am wichtigsten ist, dass Sie daran denken, andere " "Entwickler über Ihren Urlaub zu informieren, damit diese bei Problemen mit " "Ihren Paketen oder anderweitigen Pflichten im Projekt die erforderlichen " "Maßnahmen ergreifen können." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:218 msgid "" "Usually this means that other developers are allowed to NMU (see <xref " "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 "" "Üblicherweise bedeutet dies, dass andere Entwickler ein NMU (siehe <xref " "linkend=\"nmu\"/>) Ihres Pakets durchführen dürfen, weil ein großes Problem " "(veröffentlichungskritischer Fehler, Sicherheitsaktualisierung etc.) " "auftritt während Sie in Ferien sind. Manchmal ist dies etwas weniger " "kritisches, aber es ist trotzdem angemessen, andere wissen zu lassen, dass " "Sie nicht verfügbar sind." #. type: Content of: <chapter><section><section><para><footnote><para> #: developer-duties.dbk:227 msgid "" "This is so that the message can be easily filtered by people who don't want " "to read vacation notices." msgstr "" "Dies geschieht so, dass die Nachricht einfach von Leuten gefiltert werden " "kann, die keine Urlaubsbenachrichtigungen lesen möchten." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:225 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 " "problem occurs." msgstr "" "Um andere Entwickler zu informieren, gibt es zwei Dinge, die Sie tun " "sollten. Zuerst senden Sie eine E-Mail an <email>debian-private@&lists-host;" "</email> bei der Sie [VAC] vor den Betreff Ihrer Nachricht " "schreiben<placeholder type=\"footnote\" id=\"0\"/> und die Dauer angeben, " "wie lange Sie Urlaub machen. Sie können außerdem einige besondere " "Anweisungen geben, was beim Auftreten von Fehlern zu tun ist." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:234 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 " "information is only accessible to Debian developers). Don't forget to " "remove the on vacation flag when you come back!" msgstr "" "Das andere, was Sie tun sollten, ist, sich selbst in der <link linkend=" "\"devel-db\">LDAP-Entwicklerdatenbank von Debian</link> als abwesend zu " "kennzeichnen (auf diese Information können nur Debian-Entwickler zugreifen). " "Vergessen Sie nicht, die Urlaubskennzeichnung zu entfernen, wenn Sie wieder " "zurück sind." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:240 msgid "" "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 "" "Idealerweise sollten Sie sich auf den <ulink url=\"&url-gpg-coord;\">GPG-" "Koordinierungsseiten</ulink> anmelden, wenn Sie Urlaub buchen und prüfen, ob " "es dort jemanden gibt, der eine Signatur benötigt. Dies ist besonders dann " "wichtig, wenn Leute an exotische Orte fahren, an denen es noch keine " "Entwickler gibt, aber Leute, die an einer Bewerbung interessiert sind." #. type: Content of: <chapter><section><section><title> #: developer-duties.dbk:249 msgid "Retiring" msgstr "Sich zurückziehen" #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:251 msgid "" "If you choose to leave the Debian project, you should make sure you do the " "following steps:" msgstr "" "Falls Sie das Debian-Projekt verlassen wollen, sollten Sie die folgenden " "Schritte einhalten:" #. type: Content of: <chapter><section><section><orderedlist><listitem><para> #: developer-duties.dbk:257 msgid "" "Orphan all your packages, as described in <xref linkend=\"orphaning\"/>." msgstr "" "Verwaisen Sie all Ihre Pakete, wie in <xref linkend=\"orphaning\"/> " "beschrieben." #. type: Content of: <chapter><section><section><orderedlist><listitem><para> #: developer-duties.dbk:262 msgid "" "Send an gpg-signed email about why you are leaving the project to " "<email>debian-private@&lists-host;</email>." msgstr "" "Senden Sie eine GPG-signierte E-Mail mit den Gründen, weshalb Sie das " "Projekt verlassen, an <email>debian-private@&lists-host;</email>." #. type: Content of: <chapter><section><section><orderedlist><listitem><para> #: developer-duties.dbk:268 msgid "" "Notify the Debian key ring maintainers that you are leaving by opening a " "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 "" "Benachrichtigen Sie die Debian-Schlüsselverwalter über Ihren Weggang, indem " "Sie ein Ticket in Debian-RT öffnen. Dies geschieht durch Senden einer E-Mail " "an &email-keyring; mit den Wörtern »Debian RT« in der Betreffzeile (Groß- " "und Kleinschreibung spielt keine Rolle)." #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:275 msgid "" "It is important that the above process is followed, because finding inactive " "developers and orphaning their packages takes significant time and effort." msgstr "" #. type: Content of: <chapter><section><section><title> #: developer-duties.dbk:281 msgid "Returning after retirement" msgstr "" #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:283 msgid "" "A retired developer's account is marked as \"emeritus\" when the process in " "<xref linkend=\"s3.7\"/> is followed, and \"disabled\" otherwise. Retired " "developers with an \"emeritus\" account can get their account re-activated " "as follows:" msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: developer-duties.dbk:292 msgid "Contact &email-debian-account-manager;." msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: developer-duties.dbk:297 msgid "" "Go through a shortened NM process (to ensure that the returning developer " "still knows important parts of P&P and T&S)." msgstr "" #. type: Content of: <chapter><section><section><itemizedlist><listitem><para> #: developer-duties.dbk:303 msgid "" "Prove that they still control the GPG key associated with the account, or " "provide proof of identify on a new GPG key, with at least two signatures " "from other developers." msgstr "" #. type: Content of: <chapter><section><section><para> #: developer-duties.dbk:310 msgid "" "Retired developers with a \"disabled\" account need to go through NM again." msgstr "" #~ 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)." #~ msgstr "" #~ "Entwickler, die Teil der <ulink rl=\"&url-debian-qa;" #~ "\">Qualitätssicherungsgruppe</ulink> sind, verfolgen all diese Fehler und " #~ "versuchen zu helfen, wann immer dies möglich ist. Falls Sie aus " #~ "irgendeinem Grund einen RC-Fehler nicht innerhalb von zwei Wochen beheben " #~ "können, sollten Sie entweder die Qualitätssicherungsgruppe (QS) " #~ "<email>debian-qa@&lists-host;</email> um Hilfe bitten oder Ihre " #~ "Schwierigkeiten erklären und einen Plan zum Beheben per Mail an den " #~ "Fehlerbericht senden. Andernfalls könnten Leute der QS möglicherweise " #~ "einen »Non-Maintainer Upload« (siehe <xref linkend=\"nmu\"/>) " #~ "durchführen, nachdem Sie versucht haben, Sie zu kontaktieren. " #~ "(Möglicherweise warten sie nicht so lange wie üblich, bevor sie den NMU " #~ "durchführen, wenn Sie keine aktuelle Aktivität ihrerseits im BTS sehen.)"