Author: mumumu Date: Wed Aug 15 06:55:47 2007 New Revision: 985 Log: - translated only titles in chapter 04.
Modified: trunk/ja/ch04.xml Modified: trunk/ja/ch04.xml ============================================================================== --- trunk/ja/ch04.xml (original) +++ trunk/ja/ch04.xml Wed Aug 15 06:55:47 2007 @@ -1,6 +1,6 @@ <chapter id="social-infrastructure"> -<title>Social and Political Infrastructure</title> +<title>プロジェクトの政治構造と社会構造</title> <simplesect> @@ -41,7 +41,7 @@ few bad apples can spoil the whole barrel, at least for a while.</para> <sect1 id="forkability"> -<title>Forkability</title> +<title>forkできること</title> <para>The indispensable ingredient that binds developers together on a free software project, and makes them willing to compromise when @@ -99,7 +99,7 @@ <!-- ======================== SECTION ============================== --> <sect1 id="benevolent-dictator"> -<title>Benevolent Dictators</title> +<title>優しい独裁者</title> <para>The <firstterm>benevolent dictator</firstterm> model is exactly what it sounds like: final decision-making authority rests with one @@ -127,7 +127,7 @@ role.</para> <sect2 id="benevolent-dictator-qualifications"> -<title>Who Can Be a Good Benevolent Dictator?</title> +<title>誰がよき「優しい独裁者」となれるか?</title> <para>Being a BD requires a combination of traits. It needs, first of all, a well-honed sensitivity to one's own influence in the project, @@ -194,7 +194,7 @@ <!-- ======================== SECTION ============================== --> <sect1 id="consensus-democracy"> -<title>Consensus-based Democracy</title> +<title>合意に基づく民主主義</title> <para>As projects get older, they tend to move away from the benevolent dictatorship model and toward more openly democratic @@ -253,7 +253,7 @@ the next section.</para> <sect2 id="version-control-relaxation"> -<title>Version Control Means You Can Relax</title> +<title>バージョン管理を行なうと堅くならずに済む</title> <para>The fact that the project's source code is kept under version control means that most decisions can be easily unmade. The most @@ -299,7 +299,7 @@ </sect2> <sect2 id="voting"> -<title>When Consensus Cannot Be Reached, Vote</title> +<title>合意に至らなければ投票する</title> <para>Inevitably, some debates just won't consense. When all other means of breaking a deadlock fail, the solution is to vote. But @@ -360,7 +360,7 @@ </sect2> <sect2 id="when-to-vote"> -<title>When To Vote</title> +<title>いつ投票を行なうべきか?</title> <para>The hardest thing about voting is determining when to do it. In general, taking a vote should be very rare—a last resort for @@ -415,7 +415,7 @@ </sect2> <sect2 id="electorate"> -<title>Who Votes?</title> +<title>誰が投票するのか?</title> <para>Having a voting system raises the question of electorate: who gets to vote? This has the potential to be a sensitive issue, because @@ -482,7 +482,7 @@ </sect2> <sect2 id="polls"> -<title>Polls Versus Votes</title> +<title>世論調査 v.s 投票</title> <para>For certain kinds of votes, it may be useful to expand the electorate. For example, if the developers simply can't figure out @@ -499,7 +499,7 @@ </sect2> <sect2 id="veto"> -<title>Vetoes</title> +<title>拒否権</title> <para>Some projects allow a special kind of vote known as a <firstterm>veto</firstterm>. A veto is a way for a developer to put a @@ -548,7 +548,7 @@ <!-- ======================== SECTION ============================== --> <sect1 id="written-rules"> -<title>Writing It All Down</title> +<title>全てを記録しておく</title> <para>At some point, the number of conventions and agreements floating around in your project may become so great that you need to record it _______________________________________________ Producingoss-translators mailing list [email protected] http://www.red-bean.com/mailman/listinfo/producingoss-translators
