Author: rocksun Date: Thu Oct 9 04:06:08 2008 New Revision: 1517 Log: finish ch03.xml, need a thorough review.
Modified: trunk/zh/ch03.xml Modified: trunk/zh/ch03.xml ============================================================================== --- trunk/zh/ch03.xml (original) +++ trunk/zh/ch03.xml Thu Oct 9 04:06:08 2008 @@ -848,29 +848,11 @@ <sect1 id="irc"> <title>IRC / 实时聊天系统</title> -<para>Many projects offer real-time chat rooms using <firstterm>Internet -Relay Chat</firstterm> (<firstterm>IRC</firstterm>), forums where users -and developers can ask each other questions and get instant responses. -While you <emphasis>can</emphasis> run an IRC server from your own -web site, it is generally not worth the hassle. Instead, do what -everyone else does: run your IRC channels at Freenode -(<ulink url="http://freenode.net/"/>). Freenode gives you the control -you need to administer your project's IRC -channels,<footnote><para>There is no requirement or expectation that -you donate to Freenode, but if you or your project can afford it, -please consider a contribution. They are a tax-exempt charity in the -U.S., and they perform a valuable service.</para></footnote> while -sparing you the not-insignificant trouble of maintaining an IRC server -yourself.</para> - -<para>The first thing to do is choose a channel name. The most -obvious choice is the name of your project—if that's available -at Freenode, then use it. If not, try to choose something as close to -your project's name, and as easy to remember, as possible. Advertise -the channel's availabity from your project's web site, so a visitor -with a quick question will see it right away. For example, this -appears in a prominently placed box at the top of Subversion's home -page:</para> +<para>许多项目使用<firstterm>互联网多线交谈</firstterm>（<firstterm>IRC</firstterm>）提供实时聊天室，作为用户和开发者互相提问并得到及时答复的讨论场所。即使你<emphasis>可以</emphasis>在你的服务器运行IRC服务器时，也不必为此事麻烦。而应该象其他人一样：在Freenode（<ulink url="http://freenode.net/"/>）运行你的IRC频道。Freenode给了你足够的权利来管理你项目的IRC频道，<footnote> +<para>没有要求或期望你能够为Freenode捐献，但是如果你或你的项目能够负担，请考虑贡献一下。他们在美国有一个免税的慈善团体，提供有价值的服务 +</para></footnote>可以让你摆脱维护IRC服务器这类无意义的麻烦。</para> + +<para>首先要选择一个频道名称，最明显选择是你的项目名—如果在Freenode存在的话，就使用它。如果不存在，可以选择一个与项目名接近的名称，尽可能的易于记忆。在你的项目网站上将频道广而告之，这样期望快速提问的访问者可以立刻看到它，例如，Subversion主页上显著放置的方框中所出现的：</para> <blockquote> <para><emphasis>If you're using Subversion, we recommend that you @@ -884,30 +866,13 @@ <emphasis>channel</emphasis> <literal>#svn</literal>.</para> </blockquote> -<para>Some projects have multiple channels, one per subtopic. For -example, one channel for installation problems, another for usage -questions, another for development chat, etc. (<xref -linkend="growth"/><phrase output="printed"> in -<xref linkend="communications"/></phrase> discusses and how to -divide into multiple channels). When your project is young, there -should only be one channel, with everyone talking together. Later, as -the user-to-developer ratio increases, separate channels may become -necessary.</para> - -<para>How will people know all the available channels, let alone which -channel to talk in? And when they talk, how will they know what the -local conventions are?</para> - -<para>The answer is to tell them by setting the <firstterm>channel -topic</firstterm>.<footnote><para>To set a channel topic, use the -<literal>/topic</literal> command. All commands in IRC start with -"<literal>/</literal>". See <ulink url="http://www.irchelp.org/"/> if -you're not familiar with IRC usage and administration; in particular, -<ulink url="http://www.irchelp.org/irchelp/irctutorial.html"/> is an -excellent tutorial.</para></footnote> The channel topic is a brief -message each user sees when they first enter the channel. It gives -quick guidance to newcomers, and pointers to further information. For -example:</para> +<para>一些项目有多个频道，每个子主题一个。例如，一个频道关注安装问题，另一个是使用问题，还有一个是开发聊天，等等。（<phrase output="printed"><xref linkend="communications"/>的</phrase><xref +linkend="growth"/>讨论了如何划分多个频道）。当你的项目海年轻时，应该只有一个频道，所有人在一起讨论，之后，随着用户到开发者比率增加，也就有必要分开单独的频道。 +</para> + +<para>人们如何知道所有的已有频道，以及在哪个频道讨论？他们何时交谈，如何知道当地的习惯？</para> + +<para>答案是通过设定<firstterm>频道主题</firstterm>告诉他们。<footnote><para>使用<literal>/topic</literal>命令设定频道主题，IRC频道中的所有的命令以“<literal>/</literal>”开头。如果你不熟悉IRC的使用和管理，可以看<ulink url="http://www.irchelp.org/"/>；而<ulink url="http://www.irchelp.org/irchelp/irctutorial.html"/>是一份完美的教程。</para></footnote>频道主题是每个用户在进入频道时看到的一些信息，可以给每个新人一份快速指南，指出更进一步的信息，例如：</para> <screen> You are now talking on #svn @@ -919,116 +884,64 @@ is released, see http://svn110.notlong.com/ for details. </screen> -<para>That's terse, but it tells newcomers what they need to know. It -says exactly what the channel is for, gives the project home page (in -case someone wanders into the channel without having first been to the -project web site), mentions a related channel, and gives some guidance -about pasting.</para> +<para>内容很扼要，但是它告诉新人所必需知道的东西。它精确的说明频道的目的，提供了项目的主页（如果某人是游荡近来，而并非从项目网页过来），提及相关的频道，并给出一些表面的指导。</para> <sidebar id="paste-sites"> -<title>Paste Sites</title> +<title>粘贴站点</title> + +<para>一个IRC频道是一个共享空间：任何人可以看到每个人的谈话。通常情况下，这是一个好事情，这允许人们在感到能做出贡献时跳入谈话，也可以通过观察学习。但如果某人希望一次提供一大段信息时，例如调试会话脚本，因为会输出很多行，会扰乱其他人的对话。</para> + +<para>解决办法是使用<firstterm>pastebin</firstterm>或<firstterm>pastebot</firstterm>站点，当向某人要求一大块数据时，告知他们不要粘贴到频道中，而是去（例如）<ulink url="http://pastebin.ca/"/>，将数据粘到那里的表单中，并在IRC频道中告知结果的URL，任何人可以访问这个URL并察看数据。</para> -<para>An IRC channel is a shared space: everyone can see what everyone -else is saying. Normally, this is a good thing, as it allows people -to jump into a conversation when they think they have something to -contribute, and allows spectators to learn by watching. But it -becomes problematic when someone has to provide a large quantity of -information at once, such as a debugging session transcript, because -pasting too many lines of output into the channel will disrupt other -conversations.</para> - -<para>The solution is to use one of the -<firstterm>pastebin</firstterm> or <firstterm>pastebot</firstterm> -sites. When requesting a large amount of data from someone, ask them -not to paste it into the channel, but instead to go to (for example) -<ulink url="http://pastebin.ca/"/>, paste their data into the form -there, and tell the resulting new URL to the IRC channel. Anyone can -then visit the URL and view the data.</para> - -<para>There are a number of free paste sites available now, too many -for a comprehensive list, but here are some of the ones I've seen used: -<ulink url="http://www.nomorepasting.com/"/>, -<ulink url="http://pastebin.ca/"/>, -<ulink url="http://nopaste.php.cd/"/> -<ulink url="http://rafb.net/paste/"/> -<ulink url="http://sourcepost.sytes.net/"/>, -<ulink url="http://extraball.sunsite.dk/notepad.php"/>, -and -<ulink url="http://www.pastebin.com/"/>.</para> +<para>现在有许多免费的粘贴站点，完整地例子太多了，这里是我曾经用过的： +<ulink url="http://www.nomorepasting.com/"/>、 +<ulink url="http://pastebin.ca/"/>、 +<ulink url="http://nopaste.php.cd/"/>、 +<ulink url="http://rafb.net/paste/"/>、 +<ulink url="http://sourcepost.sytes.net/"/>、 +<ulink url="http://extraball.sunsite.dk/notepad.php"/>,、 +和 +<ulink url="http://www.pastebin.com/"/>。</para> </sidebar> <sect2 id="bots"> -<title>Bots</title> +<title>机器人（Bots）</title> -<para>Many technically-oriented IRC channels have a non-human member, -a so-called <firstterm>bot</firstterm>, that is capable of storing and -regurgitating information in response to specific commands. -Typically, the bot is addressed just like any other member of the -channel, that is, the commands are delivered by "speaking to" the bot. -For example:</para> +<para>许多面向技术的IRC频道有一个非人的成员，叫做<firstterm>机器人（bot）</firstterm>，它可以对特定的命令返回信息，通常情况下，这个机器人就像频道中的其它成员一样，命令是通过谈话传递给的机器人，例如：</para> <screen> <kfogel> ayita: learn diff-cmd = http://subversion.tigris.org/faq.html#diff-cmd <ayita> Thanks! </screen> -<para>That told the bot (who is logged into the channel as ayita) to -remember a certain URL as the answer to the query "diff-cmd". Now we -can address ayita, asking the bot to tell another user about -diff-cmd:</para> +<para>这是告诉机器人（以ayita登入了频道）记住以特定的URL回答“diff-cmd”的提问，现在其他用户可以向ayita讯问，并获取diff-cmd的信息。</para> <screen> <kfogel> ayita: tell jrandom about diff-cmd <ayita> jrandom: http://subversion.tigris.org/faq.html#diff-cmd </screen> -<para>The same thing can be accomplished via a convenient shorthand:</para> +<para>通过速记法可以得到同样的结果：</para> <screen> <kfogel> !a jrandom diff-cmd <ayita> jrandom: http://subversion.tigris.org/faq.html#diff-cmd </screen> -<para>The exact command set and behaviors differ from bot to bot. The -above example is with <literal>ayita</literal> -(<ulink url="http://hix.nu/svn-public/alexis/trunk/"/>), of which -there is usually an instance running in <literal>#svn</literal> at -freenode. Other bots include Dancer -(<ulink url="http://dancer.sourceforge.net/"/>) and Supybot -(<ulink url="http://supybot.com/"/>). Note that no special server -privileges are required to run a bot. A bot is a client program; -anyone can set one up and direct it to listen to a particular -server/channel.</para> - -<para>If your channel tends to get the same questions over and over, -I highly recommend setting up a bot. Only a small percentage of -channel users will acquire the expertise needed to manipulate the bot, -but those users will answer a disproportionately high percentage of -questions, because the bot enables them to respond so much more -efficiently.</para> +<para>准确的命令集和行为方式各不相同，以上的例子来自<literal>ayita</literal>（<ulink url="http://hix.nu/svn-public/alexis/trunk/"/>），通常在freenode的<literal>#svn</literal>运行着一个实例。其它机器人包括Dancer（<ulink url="http://dancer.sourceforge.net/"/>）和Supybot（<ulink url="http://supybot.com/"/>）。请注意，运行机器人无需服务器的权限，一个机器人就是一个客户端程序；任何人可以设置一个并监听特定的服务器/频道。</para> + +<para> +如果你的频道一次次的得到同样的问题，我强烈推荐你设置一个机器人，只有一小部分频道用户会获得需要处理机器人的专业技能，而这些用户会回答不成比例的大部分问题，因为机器人可以帮助他们有效率的回复。</para> </sect2> <sect2 id="irc-archiving"> -<title>Archiving IRC</title> +<title>归档IRC</title> + +<para>尽管可以将IRC频道发生的任何事情都归档，但这不是必要的。IRC对话名以上是公开的，但是许多用户认为这是非正式的，半私人的对话，用户会对语法不是很在意，而且经常会表达意见（例如，关于其它软件或其他程序员），这些都不是他们希望永久保存归档的。</para> -<para>Although it is possible to archive everything that happens in an -IRC channel, it's not necessarily expected. IRC conversations may be -nominally public, but many people think of them as informal, -semi-private conversations. Users may be careless with grammar, and -often express opinions (for example, about other software or other -programmers) that they wouldn't want preserved forever in an online -archive.</para> - -<para>Of course, there will sometimes be <emphasis>excerpts</emphasis> -that should be preserved, and that's fine. Most IRC clients can log a -conversation to a file at the user's request, or failing that, one can -always just cut and paste the conversation from IRC into a more -permanent forum (most often the bug tracker). But indiscriminate -logging may make some users uneasy. If you do archive everything, -make sure you state so clearly in the channel topic, and give a URL to -the archive.</para> +<para>当然，有时候<emphasis>摘要</emphasis>必须能够保存，大多数IRC客户端可以在用户要求的情况下记录对话到一个文件，如果不能，人们也可以仅仅是将对华拷贝和粘贴到固定的论坛（经常是bug跟踪系统）中。但是不加区分的归档所有内容会让某些用户不悦，如果你需要归档所有的事情，请确认你已经在频道主题明确说明，并给出了归档的URL。</para> </sect2> @@ -1038,65 +951,23 @@ <sect1 id="wikis"> <title>Wikis</title> -<para>A <firstterm>wiki</firstterm> is a web site that allows any -visitor to edit or extend its content; the term "wiki" (from a -Hawaiian word meaning "quick" or "super-fast") is also used to refer -to the software that enables such editing. Wikis were invented in -1995, but their popularity has really started to take off since 2000 -or 2001, boosted partly by the success of Wikipedia (<ulink -url="http://www.wikipedia.org/"/>), a wiki-based free-content -encyclopedia. Think of a wiki as falling somewhere between IRC and -web pages: wikis don't happen in realtime, so people get a chance to -ponder and polish their contributions, but they are also very easy to -add to, involving less interface overhead than editing a regular web -page.</para> - -<para>Wikis are not yet standard equipment for open source projects, -but they probably will be soon. As they are relatively new -technology, and people are still experimenting with different ways of -using them, I will just offer a few words of caution here—at -this stage, it's easier to analyze misuses of wikis than to analyze -their successes.</para> - -<para>If you decide to run a wiki, put a lot of effort into having a -clear page organization and pleasing visual layout, so that visitors -(i.e., potential editors) will instinctively know how to fit in their -contributions. Equally important, post those standards on the wiki -itself, so people have somewhere to go for guidance. Too often, wiki -administrators fall victim to the fantasy that because hordes of -visitors are individually adding high quality content to the site, -the sum of all these contributions must therefore also be of high -quality. That's not how web sites work. Each individual page or -paragraph may be good when considered by itself, but it will not be -good if embedded in a disorganized or confusing whole. Too often, -wikis suffer from:</para> +<para>一个<firstterm>wiki</firstterm>就是允许任何访问者都可以编辑或扩展其内容的站点；术语“wiki”（来自夏威夷词汇，意思是“快”或“非常迅速”）也用来特指支持这种编辑功能的软件。Wikis在1995年发明，但它们的流行是从2000或2001年开始的，一定程度上由维基百科（Wikipedia，<ulink +url="http://www.wikipedia.org/"/>）的成功推动，维基百科是以wiki为基础的自由内容的百科全书。可以把wiki看作介于IRC和网页之间：wikis不会实时发生，所以人们可以仔细考虑并润色他们的贡献，但是他们也可以很容易的添加，比正规的网页需要较少的界面操作。</para> + +<para>wikis还不是开源项目的标准配置，但是可能很快就会。因为它还是相对新的技术，人们还在实验使用它的多种方式，这里我只提供一些劝诫—在本阶段，更容易分析wiki的误用，而不是他们的成功。</para> + +<para>如果你决定运行wiki，需要花费很多力量在保持清洁的页面和可视化的布局上，这样访问者（也就是潜在的编辑者）才可以凭直觉知道如何提供贡献。同样重要的是，在wiki上发表这些标准，这样热门可以访问这些指导。经常是，wiki管理员成为幻想的牺牲品，他们相信因为大群访问者各自为站点添加高质量的内容，所以这些贡献的组合也是高质量的。但那不是网站工作的方式。每个单独的页面或段落可能单独看来不错，但是如果在一个没有组织的或迷惑的整体中它就不是了。wikis经常遇到的困境有： +</para> <itemizedlist> <listitem> - <para><emphasis role="bold">Lack of navigational principles.</emphasis> - A well-organized web site makes visitors feel like they know - where they are at any time. For example, if the pages are - well-designed, people can intuitively tell the difference - between a "table of contents" region and a "content" region. - Contributors to a wiki will respect such differences too, but - only if the differences are present to begin with.</para> + <para><emphasis role="bold">缺乏导航原则。</emphasis>一个组织良好的站点可以让访问者永远知道自己在哪里。例如，如果页面设计良好，用户会凭本能说出“目录”和“内容”区域的区别，wiki的贡献者会尊重这种区别，但是这要求区别出现在面前。</para> </listitem> <listitem> - <para><emphasis role="bold">Duplication of information.</emphasis> - Wikis frequently end up with different pages saying similar - things, because the individual contributors did not notice the - duplications. This can be partly a consequence of the lack of - navigational principles noted above, in that people may not find - the duplicate content if it is not where they expect it to - be.</para> + <para><emphasis role="bold">信息重复。</emphasis>wikis经常会变得很多页面讨论相似的内容，因为每个单独的贡献者不会注意到重复。这可能部分由于缺乏前面提到的导航原则，人们可能不会在预期的地方找到重复的内容。</para> </listitem> <listitem> - <para><emphasis role="bold">Inconsistent target audience.</emphasis> - To some degree this problem is inevitable when there are so many - authors, but it can be lessened if there are written guidelines - about how to create new content. It also helps to aggressively - edit new contributions at the beginning, as an example, so that - the standards start to sink in.</para> + <para><emphasis role="bold">不一致的目标读者。</emphasis>当有许多作者时，某种程度上这个问题是不可避免的，但是如果有关于创建新内容的编写指南时可以减少这种情况。如果能够首先就做出贡献作为实例也非常好，这就成为标准被理解。</para> </listitem> </itemizedlist> @@ -1109,184 +980,61 @@ prime it with well-written content, so people have a template to follow.</para> -<para>The shining example of a well-run wiki is Wikipedia, though this -may be partly -because the content (encyclopedia entries) is naturally well-suited to -the wiki format. But if you examine Wikipedia closely, you'll see -that its administrators laid a <emphasis>very</emphasis> thorough -foundation for cooperation. There is extensive documentation on how -to write new entries, how to maintain an appropriate point of view, -what sorts of edits to make, what edits to avoid, a dispute resolution -process for contested edits (involving several stages, including -eventual arbitration), and so forth. They also have authorization -controls, so that if a page is the target of repeated inappropriate -edits, they can lock it down until the problem is resolved. In other -words, they didn't just throw some templates onto a web site and hope -for the best. Wikipedia works because its founders thought carefully -about how to get thousands of strangers to tailor their writing to a -common vision. While you may not need the same level of preparedness -to run a wiki for a free software project, the spirit is worth -emulating.</para> - -<para>For more information about wikis, see -<ulink url="http://en.wikipedia.org/wiki/Wiki"/>. Also, the first -wiki remains alive and well, and contains a lot of discussion about -running wikis: see <ulink -url="http://www.c2.com/cgi/wiki?WelcomeVisitors"/>, -<ulink url="http://www.c2.com/cgi/wiki?WhyWikiWorks"/>, and -<ulink url="http://www.c2.com/cgi/wiki?WhyWikiWorksNot"/> for -various points of view.</para> +<para>一个运行良好的闪耀例子是维基百科，尽管可能是部分因为它的内容（百科条目）本身就符合wiki的格式，但是如果你深入维基百科，你会发现管理员放置了对于合作<emphasis>非常</emphasis>完整的基础。有关于如何编写新条目，如何维护合适的视角，做何种编辑，避免怎样的编辑，争议编辑解决过程（涉及许多步骤，包含最终的裁决）等问题的大量文档。他们也有授权控制，这样如果某个页面是重复不合适编辑的结果，他们会锁定它，直到问题解决。换句话说，他们不仅是在网站上抛出了几个模板就希望坐享其成。维基百科能够成功是因为它的创建者仔细思考过如何让几千陌生人调整他们的写作来实现共同的梦想。虽然对于自由软件项目，你可能不需要同样级别的准备，但是其精神值得模仿。</para> + +<para>关于wiki的更多信息可以看<ulink url="http://en.wikipedia.org/wiki/Wiki"/>。另外，第一个wiki还活得很好，包含了许多运行wiki的讨论，在<ulink +url="http://www.c2.com/cgi/wiki?WelcomeVisitors"/>、<ulink +url="http://www.c2.com/cgi/wiki?WhyWikiWorks"/>和<ulink +url="http://www.c2.com/cgi/wiki?WhyWikiWorksNot"/>有许多不同的视点。</para> </sect1> <!-- ======================== SECTION ============================== --> <sect1 id="web-site"> -<title>Web Site</title> +<title>网站</title> -<para>There is not much to say about setting up the project web site -from a technical point of view: setting up a web server and writing -web pages are fairly simple tasks, and most of the important things to -say about layout and arrangement were covered in the previous chapter. -The web site's main function is to present a clear and welcoming -overview of the project, and to bind together the other tools (the -version control system, bug tracker, etc.). If you don't have the -expertise to set up a web server yourself, it's usually not hard to -find someone who does and is willing to help out. Nonetheless, to -save time and effort, people often prefer to use one of the canned -hosting sites.</para> +<para>从技术角度上看，对于设置项目网站没有可以多说的：设置网站服务器并编写网页都是相当简单的任务，大多数需要说的重要事情如布局和安排已经在前面的章节提过。网站的主要功能是展示项目的清楚和客气的概观，并组合其他工具（版本控制系统、bug跟踪系统等等）。如果你没有设置网站的技能，通常不难能找到有能力的人乐意帮助你，虽然如此，为了节省时间和工作量，人们通常会选择一个包装主机站点。</para> <sect2 id="canned-hosting"> -<title>Canned Hosting</title> +<title>包装主机</title> + +<para>使用包装站点有两个主要的好处，首先是服务器容量和带宽：他们的服务器通常位于非常宽的管道上，无论你的项目多么成功，你都会用完你的磁盘并消耗完网络带宽。第二个好处是简单，他们已经配置好了工具，并且会小心的备份其保管的所有数据，你不需要作出任何选择，你所需要的只是填写表单，点击按钮，你就立刻得到了一个项目网站。</para> + +<para>这是很明显的益处，坏处当然也有，你必须接受<emphasis>他们的</emphasis>选择和配置，即使有时候不同的方式更适合你的项目。通常情况下，包装主站可以通过特定很少的参数进行调整，但是你永远无法得到细致的控制，就像你自己搭建站点并对服务器有完全管理权限时的那样。</para> + +<para>这里的一个完美例子是对生成文件的处理。特定项目网页可以是生成的文件—例如，有系统可以保持FAQ数据为易于编辑的原格式，而不是HTML、PDF、和其他可以生成的展示格式。<phrase output="printed">本章后的</phrase><xref linkend="version-everything"/>会有解释，你不会希望版本化这些生成格式，而只要保存原文件。但是当你的网站存放在其他人的服务器上，就不能设置一个自定义的钩子，当原格式文件变更时，来生成在线的HTML版本的FAQ。唯一的解决办法是也版本化生成的格式，这样，它们才可以在网站上展示。</para> -<para>There are two main advantages to using a canned site. The first -is server capacity and bandwidth: their servers are beefy boxes sitting -on really fat pipes. No matter how successful your project gets, -you're not going to run out of disk space or swamp the network -connection. The second advantage is simplicity. They have already -chosen a bug tracker, a version control system, a mailing list manager, -an archiver, and everything else you need to run a site. They've -configured the tools, and are taking care of backups for all the data -stored in the tools. You don't need to make many decisions. All you -have to do is fill in a form, press a button, and suddenly you've got -a project web site.</para> - -<para>These are pretty significant benefits. The disadvantage, of -course, is that you must accept <emphasis>their</emphasis> choices and -configurations, even if something different would be better for your -project. Usually canned sites are adjustable within certain narrow -parameters, but you will never get the fine-grained control you would -have if you set up the site yourself and had full administrative -access to the server.</para> - -<para>A perfect example of this is the handling of generated files. -Certain project web pages may be generated files—for example, -there are systems for keeping FAQ data in an easy-to-edit master -format, from which HTML, PDF, and other presentation formats can be -generated. As explained in -<xref linkend="version-everything"/><phrase output="printed"> -earlier in this chapter</phrase>, -you wouldn't want to version the generated formats, only the master -file. But when your web site is hosted on someone else's server, it -may be impossible to set up a custom hook to regenerate the online -HTML version of the FAQ whenever the master file is changed. The only -workaround is to version the generated formats too, so that they show -up on the web site.</para> - -<para>There can be larger consequences as well. You may not have as -much control over presentation as you would wish. Some of the canned -hosting sites allow you to customize your web pages, but the site's -default layout usually ends up showing through in various awkward -ways. For example, some projects that host themselves at SourceForge -have completely customized home pages, but still point developers to -their "SourceForge page" for more information. The SourceForge page -is what would be the project's home page, had the project not used a -custom home page. The SourceForge page has links to the bug tracker, -the CVS repository, downloads, etc. Unfortunately, a SourceForge page -also contains a great deal of extraneous noise. The top is a banner -ad, often an animated image. The left side is a vertical arrangement -of links of little relevance to someone interested in the project. -The right side is often another advertisement. Only the center of the -page is devoted to truly project-specific material, and even that is -arranged in a confusing way that often makes visitors unsure of what -to click on next.</para> - -<para>Behind every individual aspect of SourceForge's design, there is -no doubt a good reason—good from SourceForge's point of view, -such as the advertisements. But from an individual project's point of -view, the result can be a less-than-ideal web page. I don't mean to -pick on SourceForge; similar concerns apply to many of the canned -hosting sites. The point is that there's a tradeoff. You get relief -from the technical burdens of running a project site, but only at the -price of accepting someone else's way of running it.</para> - -<para>Only you can decide whether canned hosting is best for your -project. If you choose a canned site, leave open the option of -switching to your own servers later, by using a custom domain name for -the project's "home address". You can forward the URL to the canned -site, or have a fully customized home page at the public URL and hand -users off to the canned site for sophisticated functionality. Just -make sure to arrange things such that if you later decide to use a -different hosting solution, the project's address doesn't need to -change.</para> +<para>也可能有更大的后果。你可能无法控制你所展示的内容，一些包装主站允许你自定义网页，但是站点的缺省布局通常是通过许多蹩脚的方法完成。例如，一些SourceForge上的项目拥有完全的自定义主页，但仍然将开发者指向他们的“SourceForge页面”来获得进一步信息。SourceForge页面是项目的主页，使得项目不能使用自定义主页。SourceForge页面包含到bug跟踪、CVS版本库、下载等的链接。不幸的是，SourceForge页面也包含了太多外来的噪音。顶上有一个广告条，通常是一个图像动画。左面是垂直布局的是相关或某人感兴趣的其他项目链接，只有中央才是项目特定的材料，甚至让访问者无法确定下一步应该点击什么。</para> + +<para>SourceForge设计的每个方面后面，无疑有一个好的原因—从SourceForge的视点是好的，例如广告。但是从每个项目的视点，结果可能不是一个理想的网页。我不是要招惹SourceForge；类似的关注会在许多包装主站出现，关键是代价。你省去了运行项目站点的负担，但是要接受其他人运行它的代价。</para> + +<para>你唯一可以决定的是哪个包装主站适合你的项目，如果你选择了一个包装站点，可以保留将站点转移到你自己服务器的选项，通过使用自定义域名作为项目的“主地址”。你可以将URL转向到包装主站，或者你在公共URL上有完全自定义的主页，只在复杂功能时才将用户转移到包装主站。只要确保这样安排，如果之后你希望使用不同的主机方案，项目地址不需要改变。</para> <sect3 id="canned-hosting-choosing"> -<title>Choosing a canned hosting site</title> +<title>选择一个包装站点</title> -<para>The largest and most well-known hosting site is <ulink -url="http://www.sourceforge.net/";>SourceForge</ulink>. Two other -sites providing the same or similar services are <ulink -url="http://savannah.gnu.org/";>savannah.gnu.org</ulink> and <ulink -url="http://www.berlios.de/";>BerliOS.de</ulink>. A few organizations, -such as the <ulink url="http://www.apache.org/";>Apache Software -Foundation</ulink> and <ulink -url="http://www.tigris.org/";>Tigris.org</ulink><footnote><para>Disclaimer: -I am employed by <ulink -url="http://www.collab.net/";>CollabNet</ulink>, which sponsors -Tigris.org, and I use Tigris regularly.</para></footnote>, give free -hosting to open source projects that fit well with their missions and -their community of existing projects.</para> - -<para>Haggen So did a thorough evaluation of various canned hosting -sites, as part of the research for his Ph.D. thesis, -<citetitle>Construction of an Evaluation Model for Free/Open Source -Project Hosting (FOSPHost) sites</citetitle>. The results are at -<ulink url="http://www.ibiblio.org/fosphost/"/>, and see especially -the very readable comparison chart at <ulink -url="http://www.ibiblio.org/fosphost/exhost.htm"/>.</para> +<para>最大最著名的主机站点是<ulink +url="http://www.sourceforge.net/";>SourceForge</ulink>，两个站点提供的相同或类似的服务<ulink +url="http://savannah.gnu.org/";>savannah.gnu.org</ulink>和<ulink +url="http://www.berlios.de/";>BerliOS.de</ulink>。一些组织，例如<ulink url="http://www.apache.org/";>Apache Software +Foundation</ulink>和<ulink +url="http://www.tigris.org/";>Tigris.org</ulink><footnote><para>免责生命：我由<ulink +url="http://www.collab.net/";>CollabNet</ulink>雇佣，它是Tigris.org的赞助商，我经常会用Tigris。</para></footnote>也会为开源项目提供免费主机，但要符合他们的目标和他们社区已有的项目。</para> + +<para>Haggen So对于各式包装站点有一个完全的评估，作为他的博士论文研究的一部分，<citetitle>Construction of an Evaluation Model for Free/Open Source +Project Hosting (FOSPHost) sites</citetitle>。结果在<ulink url="http://www.ibiblio.org/fosphost/"/>，还可以看特别易读的比较图<ulink +url="http://www.ibiblio.org/fosphost/exhost.htm"/>。</para> </sect3> <sect3 id="anonymity"> -<title>Anonymity and involvement</title> +<title>匿名和参与</title> + +<para>一个不仅是包装主战，而且许多其他地方也能看到的问题是对于用户登录功能的滥用。这个功能本身很简单：站点允许每个访问者自己通过用户名和密码注册，此后他就保存了一份用户信息，项目管理员可以为用户赋予特定的权限，例如，提交版本库的权利。</para> + +<para>这非常有用，实际上这也是包装主站的一个好处，问题是有时候有一些附加给注册用户的任务本应该由未注册访问者执行，特别是如在bug跟踪系统发起问题和对已有问题进行回复。如果对此类活动要求输入登陆用户名，项目就为这类快速方便的任务设置了障碍。当然，人们希望可以联系到输入数据的人，但只要保留一个输入邮件地址（如果她愿意）的字段就够了。如果一个新的用户发现一个bug，并希望报告它，她会被在输入bug之前被填写帐户信息惹恼，她可能会放弃发起这个bug。</para> -<para>A problem that is not strictly limited to the canned sites, but -is most often found there, is the abuse of user login functionality. -The functionality itself is simple enough: the site allows each -visitor to register herself with a username and password. From -then on it keeps a profile for that user, and project administrators -can assign the user certain permissions, for example, the right to -commit to the repository.</para> - -<para>This can be extremely useful, and in fact it's one of the prime -advantages of canned hosting. The problem is that sometimes user -login ends up being required for tasks that ought to be permitted to -unregistered visitors, specifically the ability to file issues in the -bug tracker, and to comment on existing issues. By requiring a -logged-in username for such actions, the project raises the -involvement bar for what should be quick, convenient tasks. Of -course, one wants to be able to contact someone who's entered data -into the issue tracker, but having a field where she can enter her -email address (if she wants to) is sufficient. If a new user spots a -bug and wants to report it, she'll only be annoyed at having to fill -out an account creation form before she can enter the bug into the -tracker. She may simply decide not to file the bug at all.</para> - -<para>The advantages of user management generally outweigh the -disadvantages. But if you can choose which actions can be done -anonymously, make sure not only that <emphasis>all</emphasis> -read-only actions are permitted to non-logged-in visitors, but also -some data entry actions, especially in the bug tracker and, if you -have them, wiki pages.</para> +<para>用户管理的好处被过高估计了，但是如果你可以选择哪些动作可以匿名完成，请确保不仅只有<emphasis>所有的</emphasis>只读动作对于未登陆用户是允许的，也包括一些数据条目动作，特别是在bug跟踪系统，如果你有，还有wiki页。</para> </sect3> _______________________________________________ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
