-# 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-2011.
+#
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-07-01 21:18+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.4\n"
+"POT-Creation-Date: 2011-09-10 14:03-0400\n"
+"PO-Revision-Date: 2011-06-15 06:04+0900\n"
+"Last-Translator: Hideki Yamane <henrich@debian.org>\n"
+"Language-Team: Debian JP Project <debian-doc@debian.or.jp>\n"
+"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: ENCODING\n"
+"Content-Transfer-Encoding: 8bit\n"
# type: Content of: <chapter><title>
+#. type: Content of: <chapter><title>
#: developer-duties.dbk:7
msgid "Debian Developer's Duties"
+msgstr "Debian 開発者の責務"
+
+#. 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 ""
+"あなたはパッケージメンテナとして、システムにうまく適合し、Debian ポリシーに"
+"しっかり則っている高品質のパッケージを提供していることでしょう。"
+
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:16
+msgid "Work towards the next <literal>stable</literal> release"
+msgstr "次期<literal>安定版 (stable)</literal> リリースへの作業"
+
+#. 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 ""
+"高品質のパッケージを<literal>不安定版 (unstable)</literal> へ提供するだけでは"
+"十分ではありません。多くのユーザは、パッケージが次期<literal>安定版 (stable)"
+"</literal> の一部としてリリースされた時にのみ、その恩恵を受けるからです。"
+"ですから、パッケージが次期の<literal>安定版 (stable)</literal> に含まれるように"
+"リリースチームと上手く共同で作業することが期待されています。"
+
+#. 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 ""
+"より具体的には、パッケージが<literal>テスト版 (testing)</literal> に移行して"
+"いるかどうかを見守る必要があります (<xref linkend=\"testing\"/> 参照) 。テス"
+"ト期間後に移行が行われない場合は、その理由を分析してこれを修正する必要があり"
+"ます。(リリースクリティカルバグや、いくつかのアーキテクチャでビルドに失敗する"
+"場合) あなたのパッケージを修正するのが必要な場合もありますし、依存関係でパッ"
+"ケージが絡まっている状態からの移行を完了する手助けとして、他のパッケージを更"
+"新 (あるいは修正、または<literal>テスト版 (testing)</literal> からの削除) が"
+"必要な事を意味する場合もあります。障害となる理由 (blocker) を判別できない場合"
+"は、リリースチームが先の移行に関する現在の障害に関する情報を与えてくれること"
+"でしょう。"
+
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:37
+msgid "Maintain packages in <literal>stable</literal>"
+msgstr "<literal>安定版 (stable)</literal> にあるパッケージをメンテナンスする"
+
+#. 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 ""
+"パッケージメンテナの作業の大半は、パッケージの更新されたバージョンを<literal>"
+"不安定版 (unstable)</literal> へ放り込むことですが、現状の<literal>安定版 "
+"(stable)</literal> リリースのパッケージの面倒をみることも伴っています。"
+
+#. 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 ""
+"<literal>安定版 (stable)</literal> への変更は推奨されてはいませんが、可能で"
+"す。セキュリティ問題が報告された時はいつでも、セキュリティチームと修正版を提"
+"供するように協力する必要があります (<xref linkend=\"bug-security\"/> 参照)。"
+"important (あるいはそれ以上) な重要度のバグが<literal>安定版 (stable)</"
+"literal> のバージョンのパッケージに報告されたら、対象のとなる修正の提供を検討"
+"する必要があります。<literal>安定版 (stable)</literal> リリースマネージャに、"
+"そのような更新を受け入れられるかどうかを尋ね、それから<literal>安定版 (stable)</"
+"literal> のアップロードを準備するなどができます (<xref linkend=\"upload-"
+"stable\"/> 参照)。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:9
-msgid "Maintaining your Debian information"
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:56
+msgid "Manage release-critical bugs"
+msgstr "リリースクリティカルバグに対処する"
+
+# type: Content of: <chapter><section><para>
+#. 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 ""
+"大抵の場合、パッケージに対するバグ報告については <xref linkend=\"bug-handling"
+"\"/>で記述されているように対応する必要があります。しかしながら、注意を必要と"
+"する特別なカテゴリのバグがあります—リリースクリティカルバグ (RC bug) と呼ばれ"
+"るものです。<literal>critical</literal>、<literal>grave</literal>、"
+"<literal>serious</literal> の重要度が付けられている全てのバグ報告によって、"
+"そのパッケージは次の<literal>安定版 (stable)</literal> リリースに含めるのには"
+"適切ではないとされます。"
+"そのため、(<literal>テスト版 (testing)</literal> にあるパッケージ"
+"に影響する場合に) Debian のリリースを遅らせたり、(<literal>不安定版 "
+"(unstable)</literal> にあるパッケージにのみ影響する場合に) <literal>テスト版 "
+"(testing)</literal> への移行をブロックする可能性があります。最悪の場合は、パッ"
+"ケージの削除を招きます。これが RC バグを可能な限り素早く修正する必要が"
+"ある理由です。"
+
+#. 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 ""
+"もし、何らかの理由で 2 週間以内に RC バグを修正できない場合 (例えば時間の制約"
+"上、あるいは修正が難しいなど)、明示的にバグ報告にそれを述べて、他のボランティ"
+"アを招き入れて参加してもらうためにバグに <literal>help</literal> タグを打って"
+"ください。大量のパッケージが<literal>テスト版 (testing)</literal> へ移行する"
+"のを妨げることがあるので、RC バグは頻繁に Non-Maintainer Upload の対象になる"
+"ことに注意してください (<xref linkend=\"nmu\"/> 参照)。"
+
+#. 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 ""
+"RC バグへの関心の無さは、しばしば QA チームによって、メンテナが正しくパッケー"
+"ジをみなしご化せずに消えてしまったサインとして判断されます。MIA チームが関わ"
+"ることもあり、その場合はパッケージがみなしご化されます (<xref linkend=\"mia-"
+"qa\" /> 参照)。"
+
+# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:87
+msgid "Coordination with upstream developers"
+msgstr "開発元/上流 (upstream) の開発者との調整"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:11
+#. 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 ""
+"Debian メンテナとしての仕事のうちで重要な位置を占めるのは、開発元/上流 (upstream) "
+"の開発者との窓口であることです。Debian ユーザは、時折バグ報告システムに Debian 特"
+"有ではないバグを報告する事があります。Debian メンテナは、いつか上流のリリース"
+"で修正できるようにする為、このようなバグ報告を上流の開発者に転送しなくてはな"
+"りません。"
+
+# type: Content of: <chapter><section><para>
+#. 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 ""
+"Debian 固有ではないバグの修正はあなたの義務ではないとはいえ、できるなら遠慮な"
+"く修正してください。そのような修正を行った際は、上流の開発者にも送ってくださ"
+"い。時折 Debian ユーザ／開発者が上流のバグを修正するパッチを送ってくる事があ"
+"ります。その場合は、あなたはパッチを確認して上流へ転送する必要があります。"
+
+# type: Content of: <chapter><section><para>
+#. 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 ""
+"開発元の開発者らが Debian やフリーソフトウェアコミュニティに対して敵対的であ"
+"る、あるいは敵対的になってきているのを見つけた場合は、ソフトウェアを Debian "
+"に含める必要があるかを再考しなければならなくなるでしょう。時折 Debian コミュ"
+"ニティに対する社会的なコストは、そのソフトウェアがもたらすであろう利益に見合"
+"わない場合があります。"
+
+#. 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 ""
+"Debian のような大きさのプロジェクトは、あらゆる事を追いかけられる管理者用の"
+"インフラに依っています。プロジェクトメンバーとして、あらゆる物事が滞り無く"
+"進むように、あなたにはいくつかの義務があります。"
+
+# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:126
+msgid "Maintaining your Debian information"
+msgstr "あなたの Debian に関する情報をメンテナンスする"
+
+# type: Content of: <chapter><section><para>
+#. 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 "
"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:19
+#. 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 ""
+"データベースについての詳細は <xref linkend=\"devel-db\"/> を参照してくださ"
+"い。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:25
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:141
msgid "Maintaining your public key"
-msgstr ""
+msgstr "公開鍵をメンテナンスする"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:27
+#. 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 "
+"\"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:34
+#. 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 ""
+"鍵が盗難に対してだけではなく、紛失についても安全であることを保証する必要があ"
+"ります。失効証明書 (revocation certificate) を生成してコピーを作って下さい "
+"(紙にも出力しておくのがベストです)。これは鍵を紛失した場合に必要になります。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:40
+#. 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 ""
+"公開鍵に対して、署名したり身元情報を追加したりなどしたら、鍵を "
+"<literal>&keyserver-host;</literal> の鍵サーバに送付することで Debian key "
+"ring を更新できます。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:45
+#. 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 "
"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:53
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:169
msgid ""
"The same key extraction routines discussed in <xref linkend=\"registering\"/"
"> apply."
msgstr ""
+"同様に鍵の取り出し方について <xref linkend=\"registering\"/> で説明されていま"
+"す。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:57
+#. 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 ""
+"Debian での鍵のメンテナンスについて、より突っ込んだ議論を <systemitem role="
+"\"package\">debian-keyring</systemitem> パッケージ中のドキュメントで知ること"
+"ができます。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:64
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:180
msgid "Voting"
-msgstr ""
+msgstr "投票をする"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:66
+#. 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 ""
+"Debian は本来の意味での民主主義ではありませんが、我々はリーダーの選出や一般投票"
+"の承認において民主主義的なプロセスを利用しています。これらの手続きについて"
+"は、<ulink url=\"&url-constitution;\">Debian 憲章</ulink>で規程されています。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:72
+#. 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 ""
+"毎年のリーダー選挙以外には、投票は定期的には実施されず、軽々しく提案されるも"
+"のではありません。提案はそれぞれ &email-debian-vote; メーリングリストでまず議"
+"論され、プロジェクトの書記担当者が投票手順を開始する前に複数のエンドースメン"
+"トを必要とします。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:78
+#. 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 "
"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:86
+#. 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 ""
+"(過去と現在の) 全ての提案リストが <ulink url=\"&url-vote;\">Debian 投票情報</"
+"ulink>ページで閲覧できます。提案について、どの様に起案され、支持され、投票が"
+"行われたのかという関連情報の確認が可能になっています。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:93
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:209
msgid "Going on vacation gracefully"
-msgstr ""
+msgstr "優雅に休暇を取る"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:95
+#. 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 "
"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:102
+#. 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, "
+"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>
-#: 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 ""
+"通常、これはあなたが休暇中にあなたのパッケージが大きな問題 (リリースクリティ"
+"カルバグやセキュリティ更新など) となっている場合に、他の開発者に対して NMU "
+"(<xref linkend=\"nmu\"/> 参照) を許可することを意味しています。大抵の場合はそ"
+"れほど致命的なことはおきませんが、他の開発者に対してあなたが作業できない状態"
+"であることを知らせるのは重要です。"
# type: Content of: <chapter><section><para><footnote><para>
-#: developer-duties.dbk:111
+#. 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 ""
+"これは、休暇のメッセージを読みたくない人がメッセージを簡単に振り分け可能にす"
+"るためです。"
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:113
+# type: Content of: <chapter><section><para><footnote>
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:225
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 ""
+"他の開発者に通知するために行わなければならないことが 2 つあります。まず、"
+"<email>debian-private@&lists-host;</email> にサブジェクトの先頭に [VAC] と付"
+"けたメールを送り<placeholder type=\"footnote\" id=\"0\"/>、いつまで休暇なのか"
+"を示しておきます。何か問題が起きた際への特別な指示を書いておくこともできま"
+"す。"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:118
+#. 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 ""
+"他に行うべき事は <link linkend=\"devel-db\">Debian developers' LDAP "
+"database</link> 上 であなたを vacation とマークする事です (この情報は Debian "
+"開発者のみがアクセスできます)。休暇から戻った時には vacation フラグを削除する"
+"のを忘れないように!"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:124
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:240
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 "
+"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 ""
+"理想的には、休暇にあわせて <ulink url=\"&url-gpg-coord;\">GPG coordination "
+"pages</ulink> に登録して、誰かサインを希望している人がいるかどうかをチェック"
+"します。開発者がまだ誰もいないけれども応募に興味を持っている人がいるようなエ"
+"キゾチックな場所に行く場合、これは特に重要です。"
# type: Content of: <chapter><section><title>
-#: developer-duties.dbk:133
-msgid "Coordination with upstream developers"
-msgstr ""
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:249
+msgid "Retiring"
+msgstr "脱退について"
# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:135
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:251
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."
+"If you choose to leave the Debian project, you should make sure you do the "
+"following steps:"
msgstr ""
+"Debian プロジェクトから去るのを決めた場合は、以下の手順に従ってください:"
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:142
+# type: Content of: <chapter><section><orderedlist><listitem><para>
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: developer-duties.dbk:257
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."
+"Orphan all your packages, as described in <xref linkend=\"orphaning\"/>."
msgstr ""
+"<xref linkend=\"orphaning\"/> の記述に従って、全てのパッケージをみなしご"
+"化 (orphan) してください。"
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:149
+# type: Content of: <chapter><section><orderedlist><listitem><para>
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: developer-duties.dbk:262
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><title>
-#: developer-duties.dbk:158
-msgid "Managing release-critical bugs"
+"Send an gpg-signed email about why you are leaving the project to "
+"<email>debian-private@&lists-host;</email>."
msgstr ""
+"何故プロジェクトを去るのかについて GPG でサインされたメールを <email>debian-"
+"private@&lists-host;</email> に投げてください。"
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:160
+# type: Content of: <chapter><section><orderedlist><listitem><para>
+#. type: Content of: <chapter><section><section><orderedlist><listitem><para>
+#: developer-duties.dbk:268
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 "
-"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."
+"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 ""
+"'Debian RT' という単語 (大文字小文字は関係なし) がサブジェクトのどこかに入っ"
+"たメールを &email-keyring; に投げて Debian RT でチケットをオープンして、あな"
+"たがプロジェクトを去るのを Debian key ring メンテナに知らせてください。"
-#
type: Content of: <chapter><section><para>
-#: developer-duties.dbk:171
+#
. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:275
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)."
+"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><title>
-#: developer-duties.dbk:186
-msgid "Retiring"
-msgstr ""
+#. type: Content of: <chapter><section><section><title>
+#: developer-duties.dbk:281
+msgid "Returning after retirement"
+msgstr "リタイア後に再加入する"
-# type: Content of: <chapter><section><para>
-#: developer-duties.dbk:188
+#. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:283
+#, fuzzy
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
+"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 ""
+"リタイアした開発者のアカウントは、<xref linkend=\"s3.7\"/> の手続きが開始される"
+"と「emeritus」であるとマークされ、それ以外の場合は「disabled」となります。"
+"「emeritus」アカウントになっているリタイアした開発者は、以下のようにすれば"
+"アカウントを再度有効にできます: "
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: developer-duties.dbk:292
+msgid "Contact &email-debian-account-manager;."
+msgstr "&email-debian-account-manager; に連絡を取ります"
+
+#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: developer-duties.dbk:297
msgid ""
-"Orphan all your packages, as described in <xref linkend=\"orphaning\"/> ."
+"Go through a shortened NM process (to ensure that the returning developer "
+"still knows important parts of P&P and T&S)."
msgstr ""
+"短縮された NM プロセスを通過します (リタイアした開発者が P&P および "
+"T&S の肝心な部分を覚えているのを確認するためです)。"
-#
type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:199
+#
. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
+#: developer-duties.dbk:303
msgid ""
-"Send an gpg-signed email about why you are leaving the project to "
-"<email>debian-private@&lists-host;</email>."
+"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 ""
+"アカウントに紐付けられた GPG 鍵を今でも管理していることを証明する、あるいは"
+"新しい GPG 鍵について、他の開発者から少なくとも 2 つの書名を受けることにより"
+"身分証明を行う。"
-#
type: Content of: <chapter><section><orderedlist><listitem><para>
-#: developer-duties.dbk:205
+#
. type: Content of: <chapter><section><section><para>
+#: developer-duties.dbk:310
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)."
+"Retired developers with a \"disabled\" account need to go through NM again."
msgstr ""
+"リタイアした開発者で「disabled」アカウントの人は、NM をもう一度通り抜ける"
+"必要があります。"
+
+# type: Content of: <chapter><section><para>
+#~ 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 ""
+#~ "<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><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