-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR Free Software Foundation, Inc.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+# Debian Developer's Reference (Japanese)
+# (C) Hideki Yamane (Debian-JP) <henrich@debian.or.jp>, 2007-2009.
+#
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"
+"Project-Id-Version: developers-reference 3.4.2\n"
+"POT-Creation-Date: 2009-09-06 02:31+0900\n"
+"PO-Revision-Date: 2009-09-06 02:04+0900\n"
+"Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
+"Language-Team: Debian JP Project <debian-doc@debian.or.jp>\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:5
+#. type: Content of: <chapter><title>
+#: developer-duties.dbk:7
msgid "Debian Developer's Duties"
-msgstr ""
+msgstr "Debian 開発者の責務"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:7
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:9
msgid "Maintaining your Debian information"
-msgstr ""
+msgstr "あなたの Debian に関する情報をメンテナンスする"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:9
+#. type: Content of: <chapter><section><para>
+#: 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."
-msgstr ""
+"<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 ""
+"Debian 開発者に関する情報が含まれた LDAP データベースが <ulink url=\"&url-"
+"debian-db;\"></ulink> にあります。ここに情報を入力して、情報に変更があった際"
+"に更新する必要があります。特に、あなたの debian.org アドレス宛メールの転送先"
+"アドレスが常に最新になっているのを必ず確認してください。debian-private の購読"
+"をここで設定した場合、そのメールを受け取るアドレスについても同様です。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:17
+#. 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 ""
+"データベースについての詳細は <xref linkend=\"devel-db\"/> を参照してくださ"
+"い。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:23
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:25
msgid "Maintaining your public key"
-msgstr ""
+msgstr "公開鍵をメンテナンスする"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:25
+#. 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 "
-"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 ""
+"秘密鍵の取扱いには十二分に注意してください。Debian サーバ (<xref linkend="
+"\"server-machines\"/> 参照) のような公開サーバや複数のユーザがいるマシンに"
+"は、どれにも置かないようにしてください。鍵をバックアップして、コピーはオフラ"
+"インな場所に置きましょう。ソフトの使い方についてはドキュメントを参照してくだ"
+"さい。<ulink url=\"&url-pgp-faq;\">PGP FAQ</ulink> を読みましょう。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:32
+#. 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, "
"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 ""
+"鍵が盗難に対してだけではなく、紛失についても安全であることを保証する必要があ"
+"ります。失効証明書 (revocation certificate) を生成してコピーを作って下さい "
+"(紙にも出力しておくのがベストです)。これは鍵を紛失した場合に必要になります。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:38
+#. 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 "
"update the Debian key ring by sending your key to the key server at "
-"<literal>keyring.debian.org</literal>."
+"<literal>&keyserver-host;</literal>."
msgstr ""
+"公開鍵に対して、署名したり身元情報を追加したりなどしたら、鍵を "
+"<literal>&keyserver-host;</literal> の鍵サーバに送付することで Debian key "
+"ring を更新できます。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:43
+#. 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 "
"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 ""
+"まったく新しい鍵を追加したりあるいは古い鍵を削除したりする必要がある時は、別"
+"の開発者に署名された新しい鍵が必要になります。以前の鍵が侵害されたり利用不可"
+"能になった場合には、失効証明書 (revocation certificate) も追加する必要があり"
+"ます。新しい鍵が本当に必要な理由が見当たらない場合は、Keyring メンテナは新し"
+"い鍵を拒否することがあります。詳細は <ulink url=\"http://&keyserver-host;/"
+"replacing_keys.html\"></ulink> で確認できます。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:51
+#. type: Content of: <chapter><section><para>
+#: 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 ""
+"同様に鍵の取り出し方について <xref linkend=\"registering\"/> で説明されていま"
+"す。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:55
+#. 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 "
-"documentation of the <systemitem "
-"role=\"package\">debian-keyring</systemitem> package."
+"documentation of the <systemitem role=\"package\">debian-keyring</"
+"systemitem> package."
msgstr ""
+"Debian での鍵のメンテナンスについて、より突っ込んだ議論が <systemitem role="
+"\"package\">debian-keyring</systemitem> パッケージ中のドキュメントで知ること"
+"ができます。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:62
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:64
msgid "Voting"
-msgstr ""
+msgstr "投票をする"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:64
+#. 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 "
"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 ""
+"Debian は本来の意味での民主主義ではありませんが、我々はリーダの選出や一般投票"
+"の承認において民主主義的なプロセスを利用しています。これらの手続きについて"
+"は、<ulink url=\"&url-constitution;\">Debian 憲章</ulink>で規程されています。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:70
+#. type: Content of: <chapter><section><para>
+#: 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 ""
+"毎年のリーダー選挙以外には、投票は定期的には実施されず、軽々しく提案されるも"
+"のではありません。提案はそれぞれ &email-debian-vote; メーリングリストでまず議"
+"論され、プロジェクトの書記担当者が投票手順を開始する前に複数のエンドースメン"
+"トを必要とします。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:76
+#. 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 "
-"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."
-msgstr ""
+"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 ""
+"書記担当者が &email-debian-devel-announce; 上で複数回投票の呼びかけを行うの"
+"で、投票前の議論を追いかける必要はありません (全開発者がこのメーリングリスト"
+"を購読することが求められています)。民主主義は、人々が投票に参加しないと正常に"
+"機能しません。これが我々が全ての開発者に投票を勧める理由です。投票は GPG に"
+"よって署名／暗号化されたメールによって行われます。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:84
+#. type: Content of: <chapter><section><para>
+#: 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 ""
+"(過去と現在の) 全ての提案リストが <ulink url=\"&url-vote;\">Debian 投票情報</"
+"ulink>ページで閲覧できます。提案について、どの様に起案され、支持され、投票が"
+"行われたのかという関連情報の確認が可能になっています。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:91
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:93
msgid "Going on vacation gracefully"
-msgstr ""
+msgstr "優雅に休暇を取る"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:93
+#. type: Content of: <chapter><section><para>
+#: 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 "
"that they can do whatever is needed if a problem occurs with your packages "
"or other duties in the project."
msgstr ""
+"予定していた休暇にせよ、それとも単に他の作業で忙しいにせよ、開発者が不在にな"
+"ることがあるのはごく普通のことです。注意すべき重要な点は、他の開発者達があな"
+"たが休暇中であることを知る必要があることと、あなたのパッケージについて問題が"
+"起こった場合やプロジェクト内での責務を果たすのに問題が生じたという様な場合"
+"は、必要なことを彼らが何であってもできるようにすることです。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:100
+#. type: Content of: <chapter><section><para>
+#: 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, "
"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>
-#: developer-duties.dbk:107
-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>"
-msgstr ""
+"通常、これはあなたが休暇中にあなたのパッケージが大きな問題 (リリースクリティ"
+"カルバグやセキュリティ更新など) となっている場合に、他の開発者に対して NMU "
+"(<xref linkend=\"nmu\"/> 参照) を許可することを意味しています。大抵の場合はそ"
+"れほど致命的なことはおきませんが、他の開発者に対してあなたが作業できない状態"
+"であることを知らせるのは重要です。"
# type: Content of: <chapter><section><para><footnote><para>
-#: developer-duties.dbk:109
+#. 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:111
+# type: Content of: <chapter><section><para><footnote>
+#. 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."
-msgstr ""
+"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 ""
+"他の開発者に通知するために行わなければならないことが 2 つあります。まず、"
+"<email>debian-private@&lists-host;</email> にサブジェクトの先頭に [VAC] と付"
+"けたメールを送ります<placeholder type=\"footnote\" id=\"0\"/>。休暇に"
+"行く際、メールの本文にいつまで休暇予定なのかを記述して送ってください。問題が"
+"起こった際にどうすれば良いのか、特別な指示を書いておくこともできます。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:116
+#. 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 "
"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 ""
+"他に行うべき事は <link linkend=\"devel-db\">Debian developers' LDAP "
+"database</link> 上 であなたを vacation とマークする事です (この情報は Debian "
+"開発者のみがアクセスできます)。休暇から戻った時には vacation フラグを削除する"
+"のを忘れないように!"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:122
+#. type: Content of: <chapter><section><para>
+#: 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 ""
+"理想的には、休暇にあわせて <ulink url=\"&url-newmaint-db;gpg.php\">GPG "
+"coordination site</ulink> に登録して、誰かサインを希望している人がいるかどう"
+"かをチェックします。開発者がまだ誰もいないけれども応募に興味を持っている人が"
+"いるようなエキゾチックな場所に行く場合、これは特に重要です。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:131
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:133
msgid "Coordination with upstream developers"
-msgstr ""
+msgstr "上流 (upstream) の開発者との調整について"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:133
+#. 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 "
"the upstream developers. Debian users will sometimes report bugs that are "
"these bug reports to the upstream developers so that they can be fixed in a "
"future upstream release."
msgstr ""
+"Debian メンテナとしての仕事のうち重要な位置を占めるのは、上流 (upstream) の開"
+"発者との窓口であることです。Debian ユーザは、時折バグ報告システムに Debian 特"
+"有ではないバグを報告する事があります。Debian メンテナは、いつか上流のリリース"
+"で修正できるようにする為、このようなバグ報告を上流の開発者に転送しなくてはな"
+"りません。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:140
+#. 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 "
"so if you're able. When you make such fixes, be sure to pass them on to the "
"submit patches to fix upstream bugs — you should evaluate and forward these "
"patches upstream."
msgstr ""
+"Debian 固有ではないバグの修正はあなたの義務ではないとはいえ、できるなら遠慮な"
+"く修正してください。そのような修正を行った際は、上流の開発者にも送ってくださ"
+"い。時折 Debian ユーザ／開発者が上流のバグを修正するパッチを送ってくる事があ"
+"ります。その場合は、あなたはパッチを確認して上流へ転送する必要があります。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:147
+#. 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 "
"compliant package, then you should propose a nice fix to the upstream "
"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><title>
+#. type: Content of: <chapter><section><para>
#: developer-duties.dbk:156
-msgid "Managing release-critical bugs"
+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 ""
+"開発元の開発者らが Debian やフリーソフトウェアコミュニティに対して敵対的であ"
+"る、あるいは敵対的になってきているのを見つけた場合は、ソフトウェアを Debian "
+"に含める必要があるかを再考しなければならなくなるでしょう。時折 Debian コミュ"
+"ニティに対する社会的なコストは、そのソフトウェアがもたらすであろう利益に見合"
+"わない場合があります。"
+
+# type: Content of: <chapter><section><title>
+#. 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:158
+#. 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 "
"bugs that you need to take care of — the so-called release-critical bugs (RC "
-"bugs). All bug reports that have severity <emphasis>critical</emphasis>, "
-"<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to "
+"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."
msgstr ""
+"大抵の場合、パッケージに対するバグ報告については <xref linkend=\"bug-handling"
+"\"/>で記述されているように対応する必要があります。しかしながら、注意を必要と"
+"する特別なカテゴリのバグがあります - リリースクリティカルバグ (RC bug) と呼ば"
+"れるものです。<literal>critical</literal>、<literal>grave</literal>、"
+"<literal>serious</literal> の重要度が付けられている全てのバグ報告は、Debian "
+"の次期安定版リリースからパッケージに含めるかどうかについての影響を持つと見な"
+"されています。これらのバグは Debian のリリースを遅らせたり、フリーズ時にパッ"
+"ケージ削除の調整に使われるなどされることがあります。これが、これらのバグを可"
+"能な限り素早く修正する必要がある理由です。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:169
+#. type: Content of: <chapter><section><para>
+#: developer-duties.dbk:177
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)."
-msgstr ""
+"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 ""
+"<ulink url=\"&url-debian-qa;\">品質保証</ulink> グループに所属している開発者"
+"はそのようなバグ全てを取扱い、何時でも可能な時に修正を試みます。どの様な理由"
+"であれ、2 週間の間でパッケージの RC バグを修正出来なかったりする場合は品質保"
+"証 (QA) グループ <email>debian-qa@&lists-host;</email> にメールを送って協力を"
+"求めるか、困難な点を説明してどうやってそれを修正するつもりなのか、バグ報告に"
+"対してメールを送ってください。そうしない場合は、QA グループのメンバーはあなた"
+"にコンタクトを試みた後で Non-Maintainer アップロード (<xref linkend=\"nmu\"/"
+"> 参照) を行おうとします (BTS 上で最近の活動が見られない場合は、彼らは NMU を"
+"行う前にいつもの様には待とうとはしないでしょう)。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:184
+#. type: Content of: <chapter><section><title>
+#: developer-duties.dbk:192
msgid "Retiring"
-msgstr ""
+msgstr "脱退について"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:186
+#. 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 ""
+"Debian プロジェクトから去るのを決めた場合は、以下の手順に従ってください:"
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:192
-msgid "Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
+#. type: Content of: <chapter><section><orderedlist><listitem><para>
+#: developer-duties.dbk:200
+msgid ""
+"Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
msgstr ""
+"<xref linkend=\"orphaning\"/> の記述にしたがって、全てのパッケージをみなしご"
+"化 (orphan) してください。"
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:197
+#. 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.debian.org</email>."
+"<email>debian-private@&lists-host;</email>."
msgstr ""
+"何故プロジェクトを去るのかについて GPG でサインされたメールを <email>debian-"
+"private@&lists-host;</email> に投げてください。"
# type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:203
+#. 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 "
"words 'Debian RT' somewhere in the subject line (case doesn't matter)."
msgstr ""
+"'Debian RT' という単語 (大文字小文字は関係なし) が入ったメールを keyring@rt."
+"debian.org に投げて Debian RT でチケットをオープンすることで、あなたがプロ"
+"ジェクトを去るのを Debian key ring メンテナに知らせてください。"
+
+# type: Content of: <chapter><section><para>
+#~ 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 ""
+#~ "</footnote>。メールの本文に、いつまで休暇予定なのかを記述して休暇に行く際"
+#~ "に送ってください。問題が起こった際にどうすれば良いのか、特別な指示を書いて"
+#~ "おくこともできます。"
~ianmdlvl / developers-reference.git / blobdiff