Author: matakagi
Date: Tue Aug  7 04:07:02 2007
New Revision: 890

Log:
- merge r811, r812, r816, r817, and r818.


Modified:
   trunk/ja/ch06.xml

Modified: trunk/ja/ch06.xml
==============================================================================
--- trunk/ja/ch06.xml   (original)
+++ trunk/ja/ch06.xml   Tue Aug  7 04:07:02 2007
@@ -52,9 +52,11 @@
 mechanisms a priority for everyone in the project.<footnote><para>There
 has been some interesting academic research on this topic; for example,
 see <citetitle>Group Awareness in Distributed Software
-Development</citetitle> by Gutwin, Penner, and Schneider (this used to
-be available online, but seems to have disappeared, at least
-temporarily; use a search engine to find it).</para></footnote></para>
+Development</citetitle> by Gutwin, Penner, and Schneider.  This paper
+was online for a while, then unavailable, then online again at <ulink
+url="http://www.st.cs.uni-sb.de/edu/empirical-se/2006/PDFs/gutwin04.pdf"/>.
+So try there first, but be prepared to use a search engine if it moves
+again.</para></footnote></para>
 
 </simplesect>
 
@@ -1819,13 +1821,14 @@
 partly because the target audience is always ill-defined: given that
 most or all posts are publicly accessible, the project doesn't have
 full control over the impression the world gets.  Someone&mdash;say, a
-<ulink url="slashdot.org"/> editor&mdash;may draw millions of readers'
-attention to a post that no one ever expected to be seen outside the
-project.  This is a fact of life that all open source projects live
-with, but in practice, the risk is usually small.  In general, the
-announcements that the project most wants publicized are the ones that
-will be most publicized, assuming you use the right mechanisms to
-indicate relative newsworthiness to the outside world.</para>
+<ulink url="http://slashdot.org/";>slashdot.org</ulink>
+editor&mdash;may draw millions of readers' attention to a post that no
+one ever expected to be seen outside the project.  This is a fact of
+life that all open source projects live with, but in practice, the
+risk is usually small.  In general, the announcements that the project
+most wants publicized are the ones that will be most publicized,
+assuming you use the right mechanisms to indicate relative
+newsworthiness to the outside world.</para>
 
 <para>For major announcements, there tend to be four or five main
 channels of distribution, on which announcements should be made as
@@ -1872,7 +1875,7 @@
             entry, that entry goes onto the Freshmeat change list
             for the day.  The change list is updated not only on
             Freshmeat itself, but on various portal sites (including
-            <ulink url="slashdot.org"/>) which are watched eagerly by
+            <ulink url="http://slashdot.org"/>) which are watched eagerly by
             hordes of people.  Freshmeat also offers the same data via
             RSS feed, so people who are not subscribed to your
             project's own RSS feed might still see the announcement

_______________________________________________
Producingoss-translators mailing list
Producingoss-translators@red-bean.com
http://www.red-bean.com/mailman/listinfo/producingoss-translators

Reply via email to