msgid ""
msgstr ""
"Project-Id-Version: developers-reference 3.4.2\n"
-"POT-Creation-Date: 2010-11-21 07:59-0400\n"
+"POT-Creation-Date: 2011-03-03 11:21-0400\n"
"PO-Revision-Date: 2010-10-01 08:04+0900\n"
"Last-Translator: Hideki Yamane <henrich@debian.org>\n"
"Language-Team: Japanese <debian-japanese@lists.debian.org>\n"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:328
+#, fuzzy
+#| msgid ""
+#| "Sponsoring a package means uploading a package for a maintainer who is "
+#| "not able to do it on their own, a new maintainer applicant. Sponsoring a "
+#| "package also means accepting responsibility for it."
msgid ""
"Sponsoring a package means uploading a package for a maintainer who is not "
-"able to do it on their own, a new maintainer applicant. Sponsoring a "
-"package also means accepting responsibility for it."
+"able to do it on their own. It's not a trivial matter, the sponsor must "
+"verify the packaging and ensure that it is of the high level of quality that "
+"Debian strives to have."
msgstr ""
"パッケージのスポンサーになるというのは自分の権限ではパッケージをアップロード"
"できない、新規メンテナ応募者のパッケージをアップロードするということです。ま"
"た、パッケージのスポンサーを行うことはそれに伴う責任を引き受けることを意味し"
"ます。"
-# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:339
+#: beyond-pkging.dbk:334
+msgid "Debian Developers can sponsor packages. Debian Maintainers can't."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
+#: beyond-pkging.dbk:340
msgid ""
-"New maintainers usually have certain difficulties creating Debian packages — "
-"this is quite understandable. That is why the sponsor is there, to check "
-"the package and verify that it is good enough for inclusion in Debian. "
-"(Note that if the sponsored package is new, the ftpmasters will also have to "
-"inspect it before letting it in.)"
+"The maintainer prepares a source package (<filename>.dsc</filename>) and "
+"puts it online somewhere (like on <ulink url=\"http://mentors.debian.net/cgi-"
+"bin/welcome\">mentors.debian.net</ulink>) or even better, provides a link to "
+"a public VCS repository (see <xref linkend=\"servers-vcs\"/>) where the "
+"package is maintained."
msgstr ""
-"新たなメンテナは大抵 Debian パッケージの作成する際に何らかの困難に会いますー"
-"これは非常に理解できることです。これはなぜスポンサーがいてパッケージをチェッ"
-"クし Debian に含めるのに充分良いものであるかどうかを確認するのかの根拠です。"
-"(注記: スポンサーされたパッケージが新規の場合、Debian に入れる前に ftpmaster "
-"らがそのパッケージをチェックする必要があります)。"
-# type: Content of: <chapter><section><section><para>
-#. type: Content of: <chapter><section><section><para>
+#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
#: beyond-pkging.dbk:346
+msgid "The sponsor downloads (or checkouts) the source package."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
+#: beyond-pkging.dbk:349
msgid ""
-"Sponsoring merely by signing the upload or just recompiling is <emphasis "
-"role=\"strong\">definitely not recommended</emphasis>. You need to build "
-"the source package just like you would build a package of your own. "
-"Remember that it doesn't matter that you left the prospective developer's "
-"name both in the changelog and the control file, the upload can still be "
-"traced to you."
+"The sponsor reviews the source package. If she finds issues, she informs the "
+"maintainer and asks her to provide a fixed version (the process starts over "
+"at step 1)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para><orderedlist><listitem><para>
+#: beyond-pkging.dbk:354
+msgid ""
+"The sponsor could not find any remaining problem. She builds the package, "
+"signs it, and uploads it to Debian."
msgstr ""
-"単にサインしてアップロードするや、再コンパイルするだけのスポンサー作業は"
-"<emphasis role=\"strong\">全く推奨されません</emphasis>。ソースパッケージを自"
-"分自身がパッケージをビルドするようにビルドする必要があります。changelog と "
-"control ファイルに開発候補者の名前を残してあろうとも、アップロード誰がしたか"
-"は遡及できることを忘れないでください。"
-# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:353
+#: beyond-pkging.dbk:337
msgid ""
-"If you are an application manager for a prospective developer, you can also "
-"be their sponsor. That way you can also verify how the applicant is "
-"handling the 'Tasks and Skills' part of their application."
+"The process of sponsoring a package is: <placeholder type=\"orderedlist\" id="
+"\"0\"/>"
msgstr ""
-"もしあなたが開発候補者の応募管理者であれば、彼らのスポンサーとなることもでき"
-"ます。こうすることで応募者が応募作業の 'Tasks and Skills' 部分をどう取り扱え"
-"るかを判断できます。"
-# type: Content of: <chapter><section><section><title>
-#. type: Content of: <chapter><section><section><title>
+#. type: Content of: <chapter><section><section><para>
#: beyond-pkging.dbk:360
-msgid "Managing sponsored packages"
-msgstr "スポンサーされたパッケージを取り扱う"
+msgid ""
+"Before delving in the details of how to sponsor a package, you should ask "
+"yourself whether adding the proposed package is beneficial to Debian."
+msgstr ""
-# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:362
+#: beyond-pkging.dbk:364
msgid ""
-"By uploading a sponsored package to Debian, you are certifying that the "
-"package meets minimum Debian standards. That implies that you must build "
-"and test the package on your own system before uploading."
+"There's no simple rule to answer this question, it can depend on many "
+"factors: is the upstream codebase mature and not full of security holes? Are "
+"there pre-existing packages that can do the same task and how do they "
+"compare to this new package? Has the new package been requested by users and "
+"how large is the user base? How active are the upstream developers?"
msgstr ""
-"スポンサーされたパッケージを Debian にアップロードすることは、Debian の標準に"
-"ついて最低限は合致していることを保証することです。つまり、アップロード前に自"
-"分自身のシステムでパッケージをビルド、テストしなくてはいけないという意味で"
-"す。"
-# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:367
-msgid ""
-"You cannot simply upload a binary <filename>.deb</filename> from the "
-"sponsoree. In theory, you should only ask for the diff file and the "
-"location of the original source tarball, and then you should download the "
-"source and apply the diff yourself. In practice, you may want to use the "
-"source package built by your sponsoree. In that case, you have to check "
-"that they haven't altered the upstream files in the <filename>.orig.tar.{gz,"
-"bz2,lzma}</filename> file that they're providing."
-msgstr ""
-"あなたは、スポンサー対象者からの <filename>.deb</filename> バイナリを単にアッ"
-"プロードすることはできません。通常、diff ファイルとオリジナルのソース tar "
-"ファイルを要求して、それから自分でソースをダウンロードして diff を適用する必"
-"要があります。実際には、スポンサー対象者が生成したソースパッケージを使うとい"
-"うことです。この場合、彼らが提供した <filename>.orig.tar.{gz,bz2,lzma}</"
-"filename> ファイル中の開発元 (upstream) を改変していないことをチェックする必"
-"要があります。"
+#: beyond-pkging.dbk:371
+msgid ""
+"You should also ensure that the prospective maintainer is going to be a good "
+"maintainer. Does she already have some experience with other packages? If "
+"yes, is she doing a good job with them (check out some bugs)? Is she "
+"familiar with the package and its programming language? Does she have the "
+"skills needed for this package? If not, is she able to learn them?"
+msgstr ""
-# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:376
+#: beyond-pkging.dbk:379
msgid ""
-"Do not be afraid to write the sponsoree back and point out changes that need "
-"to be made. It often takes several rounds of back-and-forth email before "
-"the package is in acceptable shape. Being a sponsor means being a mentor."
+"It's also a good idea to know where she stands towards Debian: does she "
+"agree with Debian's philosophy and does she intend to join Debian? Given how "
+"easy it is to become a Debian Maintainer, you might want to only sponsor "
+"people who plan to join. That way you know from the start that you won't "
+"have to act as a sponsor indefinitely."
msgstr ""
-"スポンサー対象者に必要な変更点を指摘の連絡するのを恐れないでください。パッ"
-"ケージが受け入れ可能な形になる前に何度もメールのやりとりが起こるのはよくある"
-"ことです。スポンサーになるということはメンター (mentor) になるということで"
-"す。"
+
+# type: Content of: <chapter><section><section><title>
+#. type: Content of: <chapter><section><section><section><title>
+#: beyond-pkging.dbk:386
+#, fuzzy
+#| msgid "Sponsoring packages"
+msgid "Sponsoring a new package"
+msgstr "パッケージのスポンサーを行う"
# type: Content of: <chapter><section><section><para>
-#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:381
-msgid "Once the package meets Debian standards, build and sign it with"
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:388
+#, fuzzy
+#| msgid ""
+#| "New maintainers usually have certain difficulties creating Debian "
+#| "packages — this is quite understandable. That is why the sponsor is "
+#| "there, to check the package and verify that it is good enough for "
+#| "inclusion in Debian. (Note that if the sponsored package is new, the "
+#| "ftpmasters will also have to inspect it before letting it in.)"
+msgid ""
+"New maintainers usually have certain difficulties creating Debian packages — "
+"this is quite understandable. They will do mistakes. That's why sponsoring a "
+"brand new package into Debian requires a thorough review of the Debian "
+"packaging. Sometimes several iterations will be needed until the package is "
+"good enough to be uploaded to Debian. Thus being a sponsor implies being a "
+"mentor."
msgstr ""
-"一旦 Debian の標準に合致するようになったら、incoming ディレクトリにアップロー"
-"ドする前にパッケージを以下の様にしてビルドして署名してください"
+"新たなメンテナは大抵 Debian パッケージの作成する際に何らかの困難に会いますー"
+"これは非常に理解できることです。これはなぜスポンサーがいてパッケージをチェッ"
+"クし Debian に含めるのに充分良いものであるかどうかを確認するのかの根拠です。"
+"(注記: スポンサーされたパッケージが新規の場合、Debian に入れる前に ftpmaster "
+"らがそのパッケージをチェックする必要があります)。"
-# type: Content of: <chapter><section><section><screen>
-#. type: Content of: <chapter><section><section><screen>
-#: beyond-pkging.dbk:384
-#, no-wrap
-msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
-msgstr "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:396
+msgid ""
+"Don't ever sponsor a new package without reviewing it. The review of new "
+"packages done by ftpmasters mainly ensures that the software is really free. "
+"Of course, it happens that they stumble on packaging problems but they "
+"really should not. It's your task to ensure that the uploaded package "
+"complies with the Debian Free Software Guidelines and is of good quality."
+msgstr ""
-# type: Content of: <chapter><section><section><para>
-# FIXME devided articles
-#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:387
+#. type: Content of: <chapter><section><section><section><para><footnote><para>
+#: beyond-pkging.dbk:409
+msgid ""
+"You can find more checks in the wiki where several developers share their "
+"own <ulink url=\"http://wiki.debian.org/SponsorChecklist\">sponsorship "
+"checklists</ulink>."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:404
+msgid ""
+"Building the package and testing the software is part of the review, but "
+"it's also not enough. The rest of this section contains a non-exhaustive "
+"list of points to check in your review. <placeholder type=\"footnote\" id="
+"\"0\"/>"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:416
+msgid ""
+"Verify that the upstream tarball provided is the same that has been "
+"distributed by the upstream author (when the sources are repackaged for "
+"Debian, generate the modified tarball yourself)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:421
+msgid ""
+"Run <command>lintian</command> (see <xref linkend=\"lintian\"/>). It will "
+"catch many common problems. Be sure to verify that any <command>lintian</"
+"command> overrides setup by the maintainer is fully justified."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:426
+msgid ""
+"Run <command>licensecheck</command> (part of <xref linkend=\"devscripts\"/>) "
+"and verify that <filename>debian/copyright</filename> seems correct and "
+"complete. Look for license problems (like files with “All rights reserved” "
+"headers, or with a non-DFSG compliant license). <command>grep -ri</command> "
+"is your friend for this task."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:433
+msgid ""
+"Build the package with <command>pbuilder</command> (or any similar tool, see "
+"<xref linkend=\"pbuilder\"/>) to ensure that the build-dependencies are "
+"complete."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:438
msgid ""
-"before uploading it to the incoming directory. Of course, you can also use "
-"any part of your <replaceable>KEY-ID</replaceable>, as long as it's unique "
-"in your secret keyring."
+"Proofread <filename>debian/control</filename>: does it follow the best "
+"practices (see <xref linkend=\"bpp-debian-control\"/>)? Are the dependencies "
+"complete?"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:443
+msgid ""
+"Proofread <filename>debian/rules</filename>: does it follow the best "
+"practices (see <xref linkend=\"bpp-debian-rules\"/>)? Do you see some "
+"possible improvements?"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:448
+msgid ""
+"Proofread the maintainer scripts (<filename>preinst</filename>, "
+"<filename>postinst</filename>, <filename>prerm</filename>, <filename>postrm</"
+"filename>, <filename>config</filename>): will the <filename>preinst</"
+"filename>/<filename>postrm</filename> work when the dependencies are not "
+"installed? Are all the scripts idempotent (i.e. can you run them multiple "
+"times without consequences)?"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:456
+msgid ""
+"Review any change to upstream files (either in <filename>.diff.gz</"
+"filename>, or in <filename>debian/patches/</filename> or directly embedded "
+"in the <filename>debian</filename> tarball for binary files). Are they "
+"justified? Are they properly documented (with <ulink url=\"&url-dep3;"
+"\">DEP-3</ulink> for patches)?"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:462
+msgid ""
+"For every file, ask yourself why the file is there and whether it's the "
+"right way to achieve the desired result. Is the maintainer following the "
+"best packaging practices (see <xref linkend=\"best-pkging-practices\"/>)?"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><itemizedlist><listitem><para>
+#: beyond-pkging.dbk:468
+msgid ""
+"Build the packages, install them and try the software. Ensure you can remove "
+"and purge the packages. Maybe test them with <command>piuparts</command>."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:474
+msgid ""
+"If the audit did not reveal any problem, you can build the package and "
+"upload it to Debian. Remember that even if you're not the maintainer, the "
+"sponsor is still responsible of what he uploaded to Debian. That's why "
+"you're encouraged to keep up with the package through the <xref linkend="
+"\"pkg-tracking-system\"/>."
msgstr ""
-"もちろん、秘密鍵のキーリング中で唯一である限り、どの <replaceable>KEY-ID</"
-"replaceable> も使うことができます。"
# type: Content of: <chapter><section><section><para>
-#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:392
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:481
+#, fuzzy
+#| msgid ""
+#| "The <literal>Maintainer</literal> field of the <filename>control</"
+#| "filename> file and the <filename>changelog</filename> should list the "
+#| "person who did the packaging, i.e., the sponsoree. The sponsoree will "
+#| "therefore get all the BTS mail about the package."
msgid ""
-"The <literal>Maintainer</literal> field of the <filename>control</filename> "
-"file and the <filename>changelog</filename> should list the person who did "
-"the packaging, i.e., the sponsoree. The sponsoree will therefore get all "
-"the BTS mail about the package."
+"Note that you should not need to modify the source package to put your name "
+"in the <filename>changelog</filename> or in the <filename>control</filename> "
+"file. The <literal>Maintainer</literal> field of the <filename>control</"
+"filename> file and the <filename>changelog</filename> should list the person "
+"who did the packaging, i.e. the sponsoree. That way she will get all the BTS "
+"mail."
msgstr ""
"<filename>control</filename> ファイルの<literal>Maintainer</literal> 欄と"
"<filename>changelog</filename> にはパッケージ作業を行った人を記載する必要があ"
"ります。つまりはスポンサー対象者、ということです。そうすることで、スポンサー"
"対象者がパッケージに対する BTS メールを受け取れるようになります。"
-# type: Content of: <chapter><section><section><para>
-#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:398
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:487
msgid ""
-"If you prefer to leave a more evident trace of your sponsorship job, you can "
-"add a line stating it in the most recent changelog entry."
+"Instead you should instruct <command>dpkg-buildpackage</command> to use your "
+"key for the signature. You do that with the <literal>-k</literal> option:"
msgstr ""
-"スポンサーを行ったという状況証拠を残しておいて後から確認したいという場合は、"
-"最も新しい changelog のエントリにそのような記述を追加できます。"
-# type: Content of: <chapter><section><section><para>
-# FIXME keep tabs?
-#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:402
+# type: Content of: <chapter><section><section><screen>
+#. type: Content of: <chapter><section><section><section><screen>
+#: beyond-pkging.dbk:490
+#, no-wrap
+msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
+msgstr "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:492
+msgid ""
+"If you use <command>debuild</command> and <command>debsign</command>, you "
+"can even configure it permanently in <filename>~/.devscripts</filename>:"
+msgstr ""
+
+# type: Content of: <chapter><section><section><screen>
+#. type: Content of: <chapter><section><section><section><programlisting>
+#: beyond-pkging.dbk:495
+#, fuzzy, no-wrap
+#| msgid "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
+msgid "DEBSIGN_KEYID=<replaceable>KEY-ID</replaceable>\n"
+msgstr "dpkg-buildpackage -k<replaceable>KEY-ID</replaceable>\n"
+
+#. type: Content of: <chapter><section><section><section><title>
+#: beyond-pkging.dbk:500
+msgid "Sponsoring an update of an existing package"
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:502
+msgid ""
+"You will usually assume that the package has already gone through a full "
+"review. So instead of doing it again, you will carefully analyze the "
+"difference between the current version and the new version prepared by the "
+"maintainer. If you have not done the initial review yourself, you might "
+"still want to have a more deeper look just in case the initial reviewer was "
+"sloppy."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:510
+msgid ""
+"To be able to analyze the difference you need both versions. Download the "
+"current version of the source package (with <command>apt-get source</"
+"command>) and rebuild it (or download the current binary packages with "
+"<command>aptitude download</command>). Download the source package to "
+"sponsor (usually with <command>dget</command>)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:517
+msgid ""
+"Read the new changelog entry, it should tell you what to expect during the "
+"review. The main tool you will use is <command>debdiff</command> (provide by "
+"the <systemitem role=\"package\">devscripts</systemitem> package), you can "
+"run it with two source packages (<filename>.dsc</filename> files), or two "
+"binary packages, or two <filename>.changes</filename> files (it will then "
+"compare all the binary packages listed in the <filename>.changes</filename>)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:524
+msgid ""
+"If you compare the source packages (excluding upstream files in the case of "
+"a new upstream version, for example by filtering the output of "
+"<command>debdiff</command> with <command>filterdiff -i '*/debian/*'</"
+"command>), you must understand all the changes you see and they should be "
+"properly documented in the Debian changelog."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:531
msgid ""
-"You are encouraged to keep tabs on the package you sponsor using <xref "
-"linkend=\"pkg-tracking-system\"/>."
+"If everything is fine, build the package and compare the binary packages to "
+"verify that the changes on the source package have no unexpected "
+"consequences (like some files dropped by mistake, missing dependencies, "
+"etc.)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:537
+msgid ""
+"You might want to check out the Package Tracking System (see <xref linkend="
+"\"pkg-tracking-system\"/>) to verify if the maintainer has not missed "
+"something important. Maybe there are translations updates sitting in the BTS "
+"that could have been integrated. Maybe the package has been NMUed and the "
+"maintainer forgot to integrate the changes from the NMU in his package. "
+"Maybe there's a release critical bug that he has left unhandled and that's "
+"blocking migration to <literal>testing</literal>. Whatever. If you find "
+"something that she could have done (better), it's time to tell her so that "
+"she can improve for next time, and so that she has a better understanding of "
+"her responsibilities."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><section><para>
+#: beyond-pkging.dbk:549
+msgid ""
+"If you have found no major problem, upload the new version. Otherwise ask "
+"the maintainer to provide you a fixed version."
msgstr ""
-"<xref linkend=\"pkg-tracking-system\"/> を使って、スポンサーしたパッケージの"
-"状況を把握するのをお勧めします。"
# type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:408
+#: beyond-pkging.dbk:556
msgid "Advocating new developers"
msgstr "新たな開発者を支持する (advocate)"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:410
+#: beyond-pkging.dbk:558
msgid ""
"See the page about <ulink url=\"&url-newmaint-advocate;\">advocating a "
"prospective developer</ulink> at the Debian web site."
# type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><title>
-#: beyond-pkging.dbk:417
+#: beyond-pkging.dbk:565
msgid "Handling new maintainer applications"
msgstr "新規メンテナ申請 (new maintainer applications) を取り扱う"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: beyond-pkging.dbk:419
+#: beyond-pkging.dbk:567
msgid ""
"Please see <ulink url=\"&url-newmaint-amchecklist;\">Checklist for "
"Application Managers</ulink> at the Debian web site."
"Debian のウェブサイトにある <ulink url=\"&url-newmaint-amchecklist;\">申請管"
"理者用チェックリスト (Checklist for Application Managers)</ulink> を参照して"
"ください。"
+
+# type: Content of: <chapter><section><section><para>
+#~ msgid ""
+#~ "Sponsoring merely by signing the upload or just recompiling is <emphasis "
+#~ "role=\"strong\">definitely not recommended</emphasis>. You need to build "
+#~ "the source package just like you would build a package of your own. "
+#~ "Remember that it doesn't matter that you left the prospective developer's "
+#~ "name both in the changelog and the control file, the upload can still be "
+#~ "traced to you."
+#~ msgstr ""
+#~ "単にサインしてアップロードするや、再コンパイルするだけのスポンサー作業は"
+#~ "<emphasis role=\"strong\">全く推奨されません</emphasis>。ソースパッケージ"
+#~ "を自分自身がパッケージをビルドするようにビルドする必要があります。"
+#~ "changelog と control ファイルに開発候補者の名前を残してあろうとも、アップ"
+#~ "ロード誰がしたかは遡及できることを忘れないでください。"
+
+# type: Content of: <chapter><section><section><para>
+#~ msgid ""
+#~ "If you are an application manager for a prospective developer, you can "
+#~ "also be their sponsor. That way you can also verify how the applicant is "
+#~ "handling the 'Tasks and Skills' part of their application."
+#~ msgstr ""
+#~ "もしあなたが開発候補者の応募管理者であれば、彼らのスポンサーとなることもで"
+#~ "きます。こうすることで応募者が応募作業の 'Tasks and Skills' 部分をどう取り"
+#~ "扱えるかを判断できます。"
+
+# type: Content of: <chapter><section><section><title>
+#~ msgid "Managing sponsored packages"
+#~ msgstr "スポンサーされたパッケージを取り扱う"
+
+# type: Content of: <chapter><section><section><para>
+#~ msgid ""
+#~ "By uploading a sponsored package to Debian, you are certifying that the "
+#~ "package meets minimum Debian standards. That implies that you must build "
+#~ "and test the package on your own system before uploading."
+#~ msgstr ""
+#~ "スポンサーされたパッケージを Debian にアップロードすることは、Debian の標"
+#~ "準について最低限は合致していることを保証することです。つまり、アップロード"
+#~ "前に自分自身のシステムでパッケージをビルド、テストしなくてはいけないという"
+#~ "意味です。"
+
+# type: Content of: <chapter><section><section><para>
+#~ msgid ""
+#~ "You cannot simply upload a binary <filename>.deb</filename> from the "
+#~ "sponsoree. In theory, you should only ask for the diff file and the "
+#~ "location of the original source tarball, and then you should download the "
+#~ "source and apply the diff yourself. In practice, you may want to use the "
+#~ "source package built by your sponsoree. In that case, you have to check "
+#~ "that they haven't altered the upstream files in the <filename>.orig.tar."
+#~ "{gz,bz2,lzma}</filename> file that they're providing."
+#~ msgstr ""
+#~ "あなたは、スポンサー対象者からの <filename>.deb</filename> バイナリを単に"
+#~ "アップロードすることはできません。通常、diff ファイルとオリジナルのソース "
+#~ "tar ファイルを要求して、それから自分でソースをダウンロードして diff を適用"
+#~ "する必要があります。実際には、スポンサー対象者が生成したソースパッケージを"
+#~ "使うということです。この場合、彼らが提供した <filename>.orig.tar.{gz,bz2,"
+#~ "lzma}</filename> ファイル中の開発元 (upstream) を改変していないことを"
+#~ "チェックする必要があります。"
+
+# type: Content of: <chapter><section><section><para>
+#~ msgid ""
+#~ "Do not be afraid to write the sponsoree back and point out changes that "
+#~ "need to be made. It often takes several rounds of back-and-forth email "
+#~ "before the package is in acceptable shape. Being a sponsor means being a "
+#~ "mentor."
+#~ msgstr ""
+#~ "スポンサー対象者に必要な変更点を指摘の連絡するのを恐れないでください。パッ"
+#~ "ケージが受け入れ可能な形になる前に何度もメールのやりとりが起こるのはよくあ"
+#~ "ることです。スポンサーになるということはメンター (mentor) になるということ"
+#~ "です。"
+
+# type: Content of: <chapter><section><section><para>
+#~ msgid "Once the package meets Debian standards, build and sign it with"
+#~ msgstr ""
+#~ "一旦 Debian の標準に合致するようになったら、incoming ディレクトリにアップ"
+#~ "ロードする前にパッケージを以下の様にしてビルドして署名してください"
+
+# type: Content of: <chapter><section><section><para>
+# FIXME devided articles
+#~ msgid ""
+#~ "before uploading it to the incoming directory. Of course, you can also "
+#~ "use any part of your <replaceable>KEY-ID</replaceable>, as long as it's "
+#~ "unique in your secret keyring."
+#~ msgstr ""
+#~ "もちろん、秘密鍵のキーリング中で唯一である限り、どの <replaceable>KEY-ID</"
+#~ "replaceable> も使うことができます。"
+
+# type: Content of: <chapter><section><section><para>
+#~ msgid ""
+#~ "If you prefer to leave a more evident trace of your sponsorship job, you "
+#~ "can add a line stating it in the most recent changelog entry."
+#~ msgstr ""
+#~ "スポンサーを行ったという状況証拠を残しておいて後から確認したいという場合"
+#~ "は、最も新しい changelog のエントリにそのような記述を追加できます。"
+
+# type: Content of: <chapter><section><section><para>
+# FIXME keep tabs?
+#~ msgid ""
+#~ "You are encouraged to keep tabs on the package you sponsor using <xref "
+#~ "linkend=\"pkg-tracking-system\"/>."
+#~ msgstr ""
+#~ "<xref linkend=\"pkg-tracking-system\"/> を使って、スポンサーしたパッケージ"
+#~ "の状況を把握するのをお勧めします。"
~ianmdlvl / developers-reference.git / blobdiff