contributor-guide/doc/source/locale/zh_CN/LC_MESSAGES/doc-code-and-documentation.po

# Andreas Jaeger <jaegerandi@gmail.com>, 2019. #zanata
# Horace Li <haoyang@openstack.org>, 2019. #zanata
msgid ""
msgstr ""
"Project-Id-Version: contributor-guide\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-03-23 13:39+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2019-12-10 10:08+0000\n"
"Last-Translator: Horace Li <haoyang@openstack.org>\n"
"Language-Team: Chinese (China)\n"
"Language: zh_CN\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"

msgid "**+/- 1 & 0**"
msgstr "**+/- 1 & 0**"

msgid "**+/- 2 & +W**"
msgstr "**+/- 2 & +W**"

msgid "**Inline Comments**"
msgstr "**行内评论**"

msgid "**Reviewing Best Practices**"
msgstr "**审阅最佳实践**"

msgid ""
"+W: Approved. This patch will now be run through a final round of checks "
"before it is merged into the repository."
msgstr ""
"+W：已批准。 现在，在将补丁合并到软件仓库之前，将对其进行最后一轮检查。"

msgid "...and *amend* the current commit"
msgstr "...和*修正（amend）*当前提交"

msgid "...and tell ``git-restack`` to proceed"
msgstr "...然后告诉 ``git-restack`` 继续"

msgid ""
":ref:`launchpad` is one of the task tracking tools that the community is "
"using."
msgstr ":ref:`launchpad` 是社区正在使用的任务跟踪工具之一。"

msgid ""
":ref:`storyboard` is a community-developed task tracking tool. The community-"
"wide adoption of the tool is in progress, you will find more and more "
"projects who migrated over to using StoryBoard already."
msgstr ""
":ref:`storyboard` 是社区开发的一个任务跟踪工具。 该工具正在社区范围内采用，您"
"将发现越来越多的项目已迁移到使用StoryBoard工具中来。"

msgid ""
"A ``clean.sh`` run does the steps for ``unstack.sh`` plus additional "
"cleaning:"
msgstr "``clean.sh`` 运行执行 ``unstack.sh`` 的步骤以及其他清理工作："

msgid "A log of the stack.sh run is kept in ``/opt/stack/logs/stack.sh.log``."
msgstr "stack.sh运行的日志会保存在/opt/stack/logs/stack.sh.log中。"

msgid ""
"A more complete reference of using systemd to interact with DevStack can be "
"found on the `Using Systemd in DevStack <https://docs.openstack.org/devstack/"
"latest/systemd.html>`_ page."
msgstr ""
"可以在 `Using Systemd in DevStack <https://docs.openstack.org/devstack/"
"latest/systemd.html>`_ 页面上找到有关使用systemd与DevStack进行交互的更完整参"
"考。"

msgid ""
"A patch chain is easy to handle if you keep in mind a few recommendations:"
msgstr "如果您牢记下面一些建议，则修补链很容易处理："

msgid "ADMIN_PASSWORD"
msgstr "ADMIN_PASSWORD"

msgid "Adding Reviewers"
msgstr "添加审核人员"

msgid "Administrator guide"
msgstr "管理员指南"

msgid ""
"After checking out the patch, you will be switched to a new branch "
"automatically, on which you can make your changes."
msgstr ""
"签出了补丁之后，您会被自动切换到一个新的分支，在这个分支上进行您的修改。"

msgid ""
"After proposing changes, you can track them at `Code Review <https://review."
"opendev.org>`_. After logging in, you will see a dashboard of \"Outgoing "
"reviews\" for changes you have proposed, \"Incoming reviews\" for changes "
"you are reviewing, and \"Recently closed\" changes for which you were either "
"a reviewer or owner."
msgstr ""
"提出更改建议后，您可以在 `Code Review <https://review.opendev.org>`_ 处进行跟"
"踪。 登录后，您将看到总控页面（Dashboard），其中包含您已建议更改的 “即将结束"
"审核(Outgoing reviews）” ，您正在进行审核的 “即将到来审核（Incoming "
"reviews）” 以及您曾经是审核人员或更改拥有者的 “最近关闭” 更改。"

msgid ""
"After you've completed the Setup and Learn GIT section, the following "
"command configures the repository to know about Gerrit and installs the "
"``Change-Id`` commit hook. You only need to do this once per repository you "
"clone::"
msgstr ""
"完成了“设置和学习GIT”章节后，以下命令将配置仓库以了解Gerrit并安装 ``Change-"
"Id`` 提交钩子（commit hook）。 您只需为每个克隆的仓库执行一次此操作："

msgid ""
"All project documentation must follow the same directory structure, which is "
"described on the `Project Guide Setup page`_."
msgstr ""
"所有项目文档都必须遵循相同的目录结构，该结构在 `Project Guide Setup page`_ 中"
"进行了描述。"

msgid ""
"All the Sandbox repository and projects are identical to any other active "
"project's resources. You can find the same information and same "
"functionality as well to ensure you can practice everything you need to know "
"about the tool."
msgstr ""
"所有沙箱仓库（Sandbox Repo）和项目都与任何其他活跃项目的资源相同。 您还可以找"
"到相同的信息和相同的功能，以确保可以练习所需的有关该工具的所有知识。"

msgid "Allows you to:"
msgstr "允许您:"

msgid ""
"Always check the changes you made to each patch and be careful that you "
"applied the changes in the right one as patches still get merged "
"individually and there is no guarantee that the whole chain gets landed at "
"the same time."
msgstr ""
"始终检查对每个补丁所做的更改，并注意将正确的更改应用到正确的位置，因为补丁仍"
"会单独合并，并且不能保证整个补丁链都可以同时合并进去。"

msgid ""
"Always handle a chain as one block of changes by rebasing the whole chain "
"and keep it up to date when you modify a patch to fix review comments or add "
"changes to it."
msgstr ""
"始终通过重新调整整个补丁链为基础，将补丁链作为一个更改整体来处理，并在修改补"
"丁以修复评论注释或向补丁添加更改时保持最新。"

msgid ""
"Always have a local branch for these changes to ensure that you don't mix it "
"together with changes related to another feature or bug fix."
msgstr ""
"始终为这些更改建立一个本地分支（local branch），以确保您不会将其与其他功能或"
"错误修复相关的更改混在一起。"

msgid ""
"Always try to extract as much as you can into other patches, like "
"documentation or logical parts of the functionality that do not depend on "
"common functions in a lower layer."
msgstr ""
"始终尝试将尽可能多的变更提取到单独的补丁中，例如文档或功能实现中不依赖于底层"
"通用功能的逻辑部分。"

msgid ""
"An important part of development is, obviously, being able to test changes "
"you develop and ensure that they function properly. In a complicated "
"ecosystem like OpenStack there is a need to also be able to verify the "
"interoperability of your code. You may make a change to Cinder but that "
"change can also impact the way that Nova interacts with Cinder's APIs."
msgstr ""
"显而易见，开发过程中很重要的一部分是能够测试您开发的更改并确保它们正常运行。 "
"在像OpenStack这样的复杂生态系统中，还需要能够验证代码的互操作性。 像是您可能"
"对Cinder进行了更改，但是这个更改可能也会影响Nova与Cinder API交互的方式。"

msgid ""
"Any temporary backing files needed to simulate a system are created in /opt/"
"stack/data"
msgstr "在/opt/stack/data中创建模拟系统所需的临时后备文件"

msgid ""
"Assuming you have not added new files, you commit all your changes using::"
msgstr "假设您还尚未添加新文件，则使用以下命令提交所有更改::"

msgid ""
"At this point DevStack takes over preparing your node to function as an "
"OpenStack cloud. The following is done:"
msgstr ""
"此时，DevStack接管了准备将节点用作OpenStack云的任务。 以下操作会被执行完成："

msgid ""
"At this point, I push my series up to gerrit. Note that it makes me confirm "
"that I really want to push two commits at once."
msgstr ""
"到此处，我将我的一系列提交推到gerrit。 请注意，这使我确认我真的想一次推送两次"
"提交。"

msgid ""
"Beyond this you can also look into the functionality to find smaller "
"building blocks and make your changes smaller. For instance changes to an "
"object can be implemented first that you will use later when you implement "
"new API functionality."
msgstr ""
"除此之外，您还可以研究该功能以找到更小的构件，并使更改量更小。 例如，可以先实"
"现对对象的更改，然后在实现新的API功能时使用它。"

msgid ""
"But I want to edit ``d76195e``, while leaving ``f17f040`` properly stacked "
"on top of it. Here I use a tool called `git-restack <https://docs.openstack."
"org/infra/git-restack/>`_ (run ``pip install git-restack`` to install it)."
msgstr ""
"但是我想编辑 ``d76195e`` ，同时将 ``f17f040`` 正确堆叠在上面。 在这里，我使用"
"了一个名为 `git-restack <https://docs.openstack.org/infra/git-restack/>`_ 的"
"工具（运行 ``pip install git-restack`` 进行安装）。"

msgid ""
"But oops, I made a mistake in my first commit. My lower constraint can't be "
"higher than my minimum in ``requirements.txt``. If I still had my branch "
"locally, I could skip this next step, but as a matter of rigor to avoid some "
"common pratfalls, I will pull the whole series afresh from gerrit by asking "
"``git-review`` to grab the *top* change:"
msgstr ""
"但是，糟糕，我在第一次提交时犯了一个错误。 我的下限不能高于 ``requirements."
"txt`` 中的下限。 如果我仍然在本地拥有分支机构，则可以跳过此下一步，但为避免某"
"些常见的困难，我会通过要求 ``git-review`` 抓住*上层*更改来重新编写整个系列 ："

msgid ""
"By default, the core services for OpenStack are installed but users can "
"configure additional services to be deployed. All services are installed "
"from source. DevStack will pull the services from git master unless "
"configured to clone from a stable branch (i.e. stable/pike)."
msgstr ""
"默认情况下，OpenStack的核心服务会被安装，但用户也可以配置需要部署的其他服"
"务。 所有服务均从源安装。 除非脚本被配置为从稳定分支（stable branch）（比如 "
"stable/pike）克隆，否则DevStack将从git master中拉取核心服务。"

msgid ""
"By grouping the changes per module you can also construct the chain or "
"dependencies by the hierarchy of the components and always keep the API "
"changes last as that will enable the new functionality and that change will "
"depend on everything else you needed to touch for your design."
msgstr ""
"通过将每个模块的更改分组，您还可以按照组件的层次结构来构建补丁链或依赖关系，"
"并始终保持API更改的最新状态，因为这将启用新功能，并且更改将取决于您需要进行设"
"计的所有其他方面。"

msgid "CLI reference"
msgstr "CLI参考"

msgid ""
"Changes that are not related to any feature implementation or bug report can "
"be uploaded but are less welcomed by reviewers."
msgstr ""
"通常来讲，可以上传与任何功能实现或错误报告无关的更改，但审核者不欢迎这些更"
"改。"

msgid "Checking Out Others' Changes"
msgstr "签出（Check Out）其他人的更改"

msgid "Cherry-picking"
msgstr "拣选（Cherry-picking）"

msgid "Cleaning up iSCSI volumes"
msgstr "清理iSCSI卷"

msgid "Clearing temporary LVM mounts"
msgstr "清除临时LVM挂载"

msgid "Code & Documentation Contributor Guide"
msgstr "代码与文档贡献者指南"

msgid "Code and Documentation Contributors"
msgstr "代码与文档贡献者"

msgid ""
"Communication is underrated, but crucial when it comes to participating in "
"an open source community. We have several tools that we use for online and "
"offline communication, which we encourage you to use."
msgstr ""
"有些情况下交流是被低估的，对于参与开源社区来说它至关重要。 我们有几种在线和离"
"线交流工具，建议您使用。"

msgid "Configuration reference"
msgstr "配置参考"

msgid "Contributor guide"
msgstr "贡献者指南"

msgid ""
"Core reviewers have additional voting choices aside from the basic set. Like "
"the basic set, the numbers map to a simple system of meaning:"
msgstr ""
"核心审阅者除了基本设置外，还有其他投票选择。 像基本值的集合一样，这些数字反映"
"了一个简单的意义系统："

msgid "DATABASE_PASSWORD"
msgstr "DATABASE_PASSWORD"

msgid "Database clean-up"
msgstr "清理数据库"

msgid "Depends-On Tag"
msgstr "Depends-On标签"

msgid "Deploying DevStack"
msgstr "部署DevStack"

msgid ""
"DevStack is a modular set of scripts that can be run to deploy a basic "
"OpenStack cloud for use as a demo or test environment. The scripts can be "
"run on a single node that is baremetal or a virtual machine. It can also be "
"configured to deploy to multiple nodes. DevStack deployment takes care of "
"tedious tasks like configuring the database and message queueing system, "
"making it possible for developers to quickly and easily deploy an OpenStack "
"cloud."
msgstr ""
"DevStack是一组模块化脚本，通过运行这些脚本来部署基本的OpenStack云，以便用作演"
"示或测试环境。 这些脚本可以在裸机或虚拟机的单个节点上运行。 也可以将其配置用"
"于部署到多个节点。 DevStack部署能够处理繁琐的任务，例如配置数据库和消息排队系"
"统，使开发人员可以快速轻松地部署OpenStack云。"

msgid ""
"DevStack uses the code in those directories to run the OpenStack services so "
"any change may be tested by making a code change in the project's directory "
"and then by restarting the project's service through systemd."
msgstr ""
"DevStack使用这些目录中的代码来运行OpenStack服务，因此可以通过更改项目目录中的"
"代码，然后通过systemd重新启动项目服务来测试任何更改。"

msgid ""
"DevStack's full documentation can be found `here <https://docs.openstack.org/"
"devstack/latest>`_."
msgstr ""
"DevStack的完整文档可以在 `here <https://docs.openstack.org/devstack/"
"latest>`_ 找到."

msgid ""
"Developers need an easy way to deploy an OpenStack cloud to do functional "
"and interoperability testing of changes. This is the purpose of DevStack."
msgstr ""
"开发人员需要一种简单的方法来部署OpenStack云以便对更改进行功能性和互操作性测"
"试。 这就是DevStack的目的。"

msgid "Documentation"
msgstr "文档"

msgid "Documents in project repositories"
msgstr "项目仓库中的文档"

msgid ""
"Each graph shows how many matches were found for that fingerprint over the "
"past 10 days. It also provides a link to both the launchpad page for the "
"bug, and the kibana dashboard for the underlying elastic-search query used "
"for the fingerprint."
msgstr ""
"每个图都显示在过去10天内针对被搜索“指纹”找到了多少个匹配项。 它还提供了指向该"
"错误的launchpad页面链接和针对该“指纹”的基础elastic-search查询的kibana "
"bashboard链接。"

msgid "Each project's database is created and populated"
msgstr "创建并填充每个项目的数据库"

msgid ""
"Enhance the automatic testing the community does on every patch submitted to "
"gerrit"
msgstr "增强社区对提交给gerrit的每个补丁所做的自动测试"

msgid ""
"Even if you have a chain of patches you still need to keep code changes and "
"related tests in one patch as you cannot guarantee that both land in time "
"for a release."
msgstr ""
"即使有一组补丁链，您仍需要将代码更改和相关测试保留在一个补丁中，因为您不能保"
"证两个部分都能及时整合进一次发布中。"

msgid "Find your project in the file."
msgstr "在文件中找到您的项目"

msgid ""
"Following is a list of the commands that you need to know for your first "
"contribution:"
msgstr "以下是您首次贡献时需要了解的命令列表："

msgid ""
"For a more in-depth look at managing patch chains, see :doc:`/code-and-"
"documentation/patch-series-tutorial`."
msgstr ""
"有关管理补丁链的更深入的信息，请参见 :doc:`/code-and-documentation/patch-"
"series-tutorial` 。"

msgid ""
"For the project documents to be linked to on the `OpenStack documentation "
"portal`_, the ``www/project-data/latest.yaml`` file in the ``openstack-"
"manuals`` repository has to be updated, following the rules of the `template "
"generator`_."
msgstr ""
"为了将项目文档链接到 `OpenStack documentation portal`_ 上，在 ``openstack-"
"manuals`` 仓库中的 ``www/project-data/latest.yaml`` 文件必须遵循 `template "
"generator`_ 的规则进行更新。"

msgid ""
"Further down the file is the ``Using milestone-proposed branches`` section. "
"These are the variables that can be changed if you wish to clone a branch "
"other than master for one or more projects."
msgstr ""
"在文件的最下方是 ``Using milestone-proposed branches`` 部分。 如果您希望为一"
"个或多个项目克隆主分支以外的分支，则可以更改这部分变量。"

msgid "General Information"
msgstr "通用信息"

msgid "Gerrit Topics"
msgstr "Gerrit标题"

msgid "Gerrit Web Editor"
msgstr "Gerrit网络编辑器"

msgid "Gerrit allows you:"
msgstr "Gerrit允许您："

msgid ""
"Gerrit also provides you options to edit the patch itself or only the commit "
"message and a few more for more advanced changes, like modifying the author."
msgstr ""
"Gerrit还为您提供了编辑补丁本身或仅提交消息的选项，还有更多选项可用于更高级的"
"更改，例如修改作者。"

msgid "Get an overview of the available projects for practice"
msgstr "获取可用于实践的项目概述"

msgid "Get guidelines on how to use them"
msgstr "获取如何使用他们的指南"

msgid "Get reviews on your changes proposed to OpenStack repositories"
msgstr "获取有关对OpenStack仓库建议的更改的审核"

msgid "Getting and Configuring DevStack"
msgstr "获取和配置DevStack"

msgid ""
"Git is a version control system that we use to track changes to our source "
"code and documentation."
msgstr "Git是一个版本控制系统，我们用于跟踪针对源代码和文档的更改。"

msgid ""
"Here is an example of what that process would look like. In this example a "
"change is made to Cinder's LVM driver:"
msgstr "这是上面流程的一个示例。 在示例中，对Cinder的LVM驱动程序进行了更改："

msgid "Here we go."
msgstr "我们开始吧!"

msgid "How to Become a Patch Guru?"
msgstr "如何成为补丁大师？"

msgid "How to Handle Chains?"
msgstr "如何处理补丁链"

msgid "How to Structure Your Changes?"
msgstr "如何组织您的更改？"

msgid "How to Use the Sandbox Projects"
msgstr "如何使用沙箱项目"

msgid "Hypervisor clean-up"
msgstr "清理Hypervisor"

msgid "I fix ``lower-constraints.txt``:"
msgstr "我修复了 ``lower-constraints.txt`` ："

msgid ""
"I just made commit ``d76195e`` on top of ``3d008a3``. You'll notice my "
"branch name (``bp/nova-cyborg-interaction``) came along with me."
msgstr ""
"我刚刚在 ``3d008a3`` 之上提交了 ``d76195e`` 。 您会注意到我的分支名称（ ``bp/"
"nova-cyborg-interaction`` ）与我一同出现了。"

msgid "I want to fix the first one, so I change ``pick`` to ``edit``:"
msgstr "我想修复第一个，因此将 ``pick`` 更改为 ``edit`` ："

msgid ""
"If I had a taller series, and I had changed ``pick`` to ``edit`` for more "
"than one commit, I would now be sitting on the next one I needed to edit. As "
"it is, that was the only thing I needed to do, so I'm done and sitting on "
"the top of my series again."
msgstr ""
"如果我有一个更高的系列，并且已经为超过一次提交将 ``pick`` 更改成了 "
"``edit`` ，那么我现在可能处于我需要编辑的下一个提交上。 实际上，这是我唯一需"
"要做的事情，所以我已经完成并再次处于我的系列的顶部。"

msgid ""
"If OpenStack was successfully deployed by DevStack you should be able to "
"point a web browser at the IP specified by ``HOST_IP`` in ``local.conf`` and "
"access Horizon."
msgstr ""
"如果OpenStack已由DevStack成功部署，则您应该能够用网络浏览器登录 ``local."
"conf`` 中 ``HOST_IP`` 所指定的IP并访问Horizon。"

msgid ""
"If successful, the Git response message will contain a URL you can use to "
"track your changes."
msgstr "如果成功，则Git响应消息将包含一个URL，您可以使用该URL来跟踪您的更改。"

msgid ""
"If the above structure exists in the project repository and the ``latest."
"yaml`` file is updated, the ``publish-openstack-sphinx-docs`` job in the "
"``project-config`` repo automatically includes the document in the published "
"documentation. For detailed instructions, see the `Project guide setup`_."
msgstr ""
"如果项目仓库中存在上述结构，并且 ``latest.yaml`` 文件已更新，则 ``project-"
"config`` 仓库中的 ``publish-openstack-sphinx-docs`` 作业会自动将文档包含在已"
"发布的文档。 有关详细说明，请参见 `Project guide setup`_ 。"

msgid ""
"If you can, test the code! In some cases you may not have access to the "
"specific hardware needed, but in general you should be able to test the "
"changes or look at the zuul build of the documentation so that you are doing "
"more than just looking at the code or documentation change."
msgstr ""
"如果可以，请测试代码！ 在某些情况下，您可能无权访问所需的特定硬件，但总的来"
"说，您应该能够测试所做的更改或查看文档的zuul构建版本，因此您要做的不仅仅是查"
"看代码或文档的更改。"

msgid ""
"If you have questions about the way something is phrased or done, or have "
"found some other issue the easiest way to let the author of the patch know "
"is to comment on that place inline. The inline comments are posted "
"collectively when you hit the 'Reply' button and add your vote on the "
"patchset."
msgstr ""
"如果您对补丁的某些措辞或完成方式有疑问，或者发现了其他问题，让补丁的作者知道"
"的最简单方法是在行内的该位置上进行评论。 当您单击“答复”按钮并在补丁集上添加投"
"票时，这些行内评论会集体发布。"

msgid ""
"If you need to make further changes to the same review, you can commit them "
"using::"
msgstr "如果您需要对同一审核进行进一步的更改，则可以使用::"

msgid ""
"If you only need to modify the top patch in the chain that can be done the "
"same way as you update individual patches."
msgstr "如果只需要修改补丁链中的顶层补丁，可以用更新单个补丁的方式来完成。"

msgid ""
"If you review a patch you are automatically added to the list of reviewers."
msgstr "如果您审阅了一个补丁，则会自动被添加到审阅者列表中。"

msgid ""
"If you're interested in more of the theory and history behind the project, "
"this talk from the Juno OpenStack Summit provides a good overview: `Elastic "
"Recheck - Tools for Finding Race Conditions in OpenStack <https://www."
"youtube.com/watch?v=Byo26Pioq1Y>`_"
msgstr ""
"如果您对Elastic Recheck项目背后的更多理论和历史感兴趣，那么Juno OpenStack峰会"
"的演讲将提供很好的概述： `Elastic Recheck - Tools for Finding Race "
"Conditions in OpenStack <https://www.youtube.com/watch?v=Byo26Pioq1Y>`_"

msgid ""
"If your commit depends on a change which has been updated since you started "
"your work, and you need to get the latest patchset from that change, you can "
"cherry-pick your own changes on top of it:"
msgstr ""
"如果您的提交依赖于自您开始工作以来已更新的更改，并且您需要从该更改中获取最新"
"的补丁集，则可以在该更改之上拣选您自己的更改："

msgid ""
"If your patch gets a -1 it is not bad news, it just means you need to do a "
"little more work."
msgstr "如果您的补丁得到了-1，这不是一个坏消息，这仅意味着您需要做更多的修改。"

msgid ""
"Improvement to either the code or documentation should be part of a larger "
"effort, like if you would like to fix typos in documentation then you should "
"do it for a larger block, like a whole guide. It is also preferred to report "
"a story with tasks for a work item like this that can be tracked later."
msgstr ""
"改进代码或文档应该是更广范围工作的一部分，例如，如果您想修正文档中的错别字，"
"则应该在较大范围的代码块框架下进行改进，比如修正整份指南。 同时最好报告一个背"
"景描述包含类似这样的工作项的任务，以便稍后进行跟踪。"

msgid ""
"In case of code refactoring work which makes the code more readable and "
"easier to maintain by restructuring methods and deleting unused code "
"snippets it is highly encouraged to consult with the project team and report "
"a story in StoryBoard first and then upload the relevant changes to Gerrit "
"for review."
msgstr ""
"在进行代码重构的情况下，通过重构方法和删除未使用的代码段使代码更易读且更易于"
"维护，强烈建议您与项目团队协商，并先在StoryBoard中报告一个背景，然后将相关更"
"改上传到Gerrit，以便评论。"

msgid ""
"In case you use the 'Depends-On' tag you need to download all the changes "
"for a feature implementation or documentation change to test the feature or "
"build the documentation with all the changes applied. Git will not take care "
"of handling the dependencies automatically in this case."
msgstr ""
"如果您使用'Depends-On'标签，则需要下载为功能实现或者文档更改所做的所有更改，"
"以测试集成了这些更改后的功能或构建集成了这些更改后的文档。 在这种情况下，Git"
"将不会自动处理依赖项。"

msgid ""
"In general, its best to avoid over using this gerrit capability because each "
"interaction with the patch- new patchsets, comments, CI system votes, etc.- "
"will send an email notification to every reviewer on the patch."
msgstr ""
"通常情况，最好避免过度使用这项gerrit功能，因为与补丁的每次交互操作（新的补丁"
"集，注释，CI系统的投票等）都会向该补丁的每位审阅者发送电子邮件通知。"

msgid ""
"In rare occasions when there is no good logical breakdown for a change and "
"your patch can grow to a thousand lines or more. In some cases it is "
"acceptable as you cannot extract the related test changes to another patch "
"for instance, but it's not highly recommended."
msgstr ""
"在极少数情况下，当没有很好的逻辑分解依据时，您的补丁可能会增长到一千行或更"
"多。 在某些情况下，这是可以接受的，例如因为您无法将相关的测试变更提取到另一个"
"补丁中，但不建议这样做。"

msgid ""
"In some cases when you break down the required changes to smaller blocks you "
"cannot avoid having direct dependencies between them that prevents you from "
"having independent changes. You need to organize your changes in a chain to "
"maintain the dependencies which requires some additional care when you work "
"with these changes."
msgstr ""
"在某些情况下，当您将所需更改分解为较小的补丁时，它们之间将不可避免地具有直接"
"依赖性，从而使得您无法进行独立更改。 您需要将更改组织成一个链来维护依赖关系，"
"当您使用这些更改时，需要格外小心。"

msgid ""
"In the case of complex feature implementation work when you need to "
"introduce changes to multiple modules of the same project or multiple "
"projects you need to be very careful with managing the dependencies."
msgstr ""
"对于复杂的功能实现工作，当您需要对同一项目或多个项目的多个模块进行更改时，在"
"管理依赖项时需要格外小心。"

msgid "Installation guide"
msgstr "安装指南"

msgid "Introduction"
msgstr "引言"

msgid ""
"It is a good practice to group changes by modules in a project, for instance "
"virt driver changes, compute manager and api changes in case of OpenStack "
"Compute."
msgstr ""
"一个优良作法是按项目中的模块将更改分组，在OpenStack Compute服务中有例如virt "
"driver相关的改变，compute manager相关的改变和api相关的改变"

msgid ""
"It is possible to check out other contributors' patches from Gerrit and even "
"`make changes to them <https://docs.openstack.org/project-team-guide/review-"
"the-openstack-way.html#modifying-a-change>`_; however, you should always "
"discuss any changes with the contributor before you start working on their "
"patch."
msgstr ""
"从gerrit中签出（check out）其他贡献者的补丁是可以的，有时候甚至可以 `make "
"changes to them <https://docs.openstack.org/project-team-guide/review-the-"
"openstack-way.html#modifying-a-change>`_ ; 但是，在开始着手修改他们的补丁之"
"前，您应该始终与贡献者讨论任何要做的更改。"

msgid ""
"It is possible to edit your patch in the gerrit web interface and publish "
"the change without making the change locally. This is not generally advised "
"for larger code updates since it doesn't automatically update your local "
"working branch. In some cases, where the patch is basically ready to merge "
"aside from a small pep8 failure- whitespace at the end of line, needing to "
"wrap a line, etc- this gerrit feature can be convenient to make a quick edit "
"and publish the change without having to go through the entire 'git add', "
"'git commit --amend', 'git review' process."
msgstr ""
"在gerrit web界面中编辑补丁并发布更改是可以的，而且无需在本地进行更改。 通常不"
"建议进行较多的代码更新，因为它不会自动更新本地工作分支。 在某些情况下，除了一"
"个小的pep8故障外，生成的补丁基本上已经准备好合并了 - 行末尾有空白，需要换行，"
"等等 - 这项gerrit功能可以方便地进行快速编辑和发布更改而没有必要通过整个'git "
"add', 'git commit --amend', 'git review'流程。"

msgid ""
"It is recommended before proceeding further to set-up passwords and IP "
"addresses for the environment in which you are running DevStack. This is "
"done by configuring the ``local.conf`` file in DevStack."
msgstr ""
"建议在进一步设置运行DevStack的环境的密码和IP地址之前完成克隆。 设置是通过在"
"DevStack中配置 ``local.conf`` 文件来完成的。"

msgid ""
"It is similar for code improvements. As the community is large and world-"
"wide we have coding guidelines, but the style of each individual can still "
"be very different. We don't enforce a particular coding style, therefore "
"changes related to fix that are less welcomed and are sources of very "
"opinionated arguments that should be avoided."
msgstr ""
"代码改进也是类似的。 由于社区很大且遍布全球，所以我们有编码准则，但是每个人的"
"风格仍然可以有很大不同。 我们不强制执行特定的编码样式，因此请尽量避免不那么受"
"欢迎的修订相关的更改的编码方式，以及应避免使用一些自以为是的参数定义方法。"

msgid ""
"Know how to structure a patch that is easier for community members to review"
msgstr "知道如何构建补丁，易于社区成员查看"

msgid ""
"Know how to structure a patch that makes it easier to maintain throughout "
"the review process"
msgstr "知道如何构建补丁，以便在整个审核过程中更容易维护"

msgid "Launchpad is deprecated and will be superceded by StoryBoard."
msgstr "Launchpad已过时，并将由StoryBoard取代。"

msgid ""
"Logs for the running services are also able to be viewed through systemd. To "
"display the logs for the Cinder Volume service the following command could "
"be used:"
msgstr ""
"也可以通过systemd查看正在运行的服务的日志。 要显示Cinder Volume服务的日志，可"
"以使用以下命令："

msgid ""
"Longer patches require more time to review; wherever you can, keep the "
"length reasonable. And where you can't, you can help the reviewers by adding "
"code comments and writing a detailed commit message to describe the changes "
"you introduced in your patch."
msgstr ""
"补丁越长，需要花费审核的时间越多； 尽可能保持长度合理。 在无法做到的地方，您"
"可以通过添加代码注释并编写详细的提交消息来描述您在补丁中引入的变更，从而帮助"
"审阅者。"

msgid "Make quick changes to your patches in the webui"
msgstr "在webui里进行你的补丁的快速更改"

msgid ""
"Most often, some deadline has passed and since no more changes are being "
"accepted till the new release development begins, the patch is `being held "
"<https://docs.openstack.org/project-team-guide/review-the-openstack-way."
"html#procedural-minus-2>`_."
msgstr ""
"多数情况下，可能是截止日期已经过去，并且由于直到新版本开发开始之前都没有接受"
"更多更改，所以这个补丁正在 `being held <https://docs.openstack.org/project-"
"team-guide/review-the-openstack-way.html#procedural-minus-2>`_ 。"

msgid ""
"Notice that the commit hashes have changed for *both* commits (but not for "
"``master``). The top one changed because it got rebased onto the new version "
"of the middle one."
msgstr ""
"请注意，两个提交都已更改了提交哈希值（但对于 ``master`` 则没有）。 顶层的一个"
"发生了变化，因为它重新基于了中间版本的新版本。"

msgid ""
"Now I'm going to make another change, but just part of it, a work-in-"
"progress commit:"
msgstr "现在，我将进行另一项更改，但其中一部分是正在进行的提交："

msgid ""
"Now I'm sitting on the top change (which you'll notice happens to be exactly "
"the same as before I pushed it - again, meaning I could technically have "
"just worked from where I was, but see above):"
msgstr ""
"现在，我处在最上层更改上了（您会发现它恰好与我推送它之前完全相同 - 再次，这意"
"味着从技术上讲我可以从原来的位置继续工作，但请参见上文）："

msgid ""
"Now commit ``f17f040`` is on top of ``d76195e``, which is still on top of "
"``3d008a3`` (aka ``master``). Note that my branch name came with me again."
msgstr ""
"现在提交 ``f17f040`` 在 ``d76195e`` 之上，而 ``d76195e`` 仍然在 ``3d008a3`` "
"（也就是 ``master`` ）之上。 请注意，我的分支名称又来了。"

msgid ""
"Now if I push the series back up to gerrit, I get the same confirmation "
"prompt, and both changes get a new patch set. If you look at the top patch "
"in gerrit, you'll see that patch set 2 shows up as just a rebase."
msgstr ""
"现在，如果我将该系列备份回gerrit，则会得到相同的确认提示，并且两个更改都将获"
"得一个新的补丁集。 如果您查看gerrit中最顶层的补丁，您会看到补丁集2只是一个更"
"新基础代码而已。"

msgid ""
"Now if you go to either of those links - e.g. https://review.opendev.org/#/"
"c/635342/ - you'll see that the patches are stacked up in series on the top "
"right."
msgstr ""
"现在，如果您转到这些链接中的任何一个-例如 https://review.opendev.org/#/"
"c/635342/-您会在右上角看到补丁被堆叠在一起。"

msgid ""
"On some distributions you may need to also set the ``HOST_IP``. Whether this "
"is necessary will depend on what naming convention is used for network "
"interfaces in your operating system."
msgstr ""
"在某些发行版中，您可能还需要设置 ``HOST_IP`` 。 是否需要这样做将取决于操作系"
"统中网络接口使用的命名约定。"

msgid ""
"Once testing and development of your code change is complete you will want "
"to push your code change to Gerrit for review. Since the projects in ``/opt/"
"stack`` are already synced to their respective git repository you can "
"configure `git review <https://docs.openstack.org/contributors/code-and-"
"documentation/using-gerrit.html>`_, commit your change and upload the "
"changes to Gerrit."
msgstr ""
"一旦完成代码更改的测试和开发，您将需要将代码更改推送给Gerrit进行审查。 考虑"
"到 ``/opt/stack`` 中的项目已经同步到其各自的git仓库中，因此您可以配置 `git "
"review <https://docs.openstack.org/contributors/code-and-documentation/using-"
"gerrit.html>`_ , 提交您的更改并将更改上传到Gerrit。"

msgid ""
"Once you have your ``local.conf`` file configured executing DevStack is "
"quite easy."
msgstr "一旦配置了 ``local.conf`` 文件，执行DevStack是非常容易的。"

msgid ""
"Once you've constructed a query and checked in on elastic-search you should "
"create a yaml file in the queries directory of the elastic-recheck git repo. "
"The file name is the launchpad bug number for the bug and the contents are "
"the elastic-search query."
msgstr ""
"当构建了查询并将其检入Elastic-Search之后，您应该在elastic-recheck git repo的"
"查询目录中创建一个yaml文件。 文件名是该错误的launchpad错误号码，内容是弹性搜"
"索查询。"

msgid ""
"Once you've identified a message in the logs that can be used for "
"fingerprinting you need to turn that into an elastic-search query. You can "
"use any of the existing fingerprints as an example: `opendev/elastic-recheck "
"<https://opendev.org/opendev/elastic-recheck/src/queries>`_"
msgstr ""
"当在日志中识别出可用于“指纹”鉴定的消息后，您将需要将其转换为弹性搜索查询。 您"
"可以使用任何现有的“指纹”作为示例： `opendev/elastic-recheck <https://opendev."
"org/opendev/elastic-recheck/src/queries>`_"

msgid ""
"Once your changes have been saved to local.conf you are ready to deploy an "
"OpenStack cloud with DevStack."
msgstr ""
"一旦将更改保存到 ``local.conf`` 后，就可以使用DevStack部署OpenStack云了。"

msgid ""
"Only the person that voted the -2 can remove the vote and it will persist on "
"all new patchsets."
msgstr "只有投票了“-2”的人才能删除投票，并且投票将保留在所有新补丁集上。"

msgid "OpenStack Documentation Contributor Guide"
msgstr "OpenStack文档贡献者指南"

msgid "Patch Chains"
msgstr "补丁链"

msgid "Patch Chains, Depends-On Tag and Gerrit Topics"
msgstr "补丁链，Depends-On标签和Gerrit标题"

msgid ""
"Project services are all registered with systemd. Each service is prefixed "
"with ``devstack@``. Therefore you may verify through systemd that the Cinder "
"Volume process is working with a command like:"
msgstr ""
"项目服务都已在systemd中注册。 每个服务都以 ``devstack @`` 为前缀。 因此，您可"
"以通过systemd使用以下命令验证Cinder Volume进程是否正在运行："

msgid "Publishing documents in project repositories"
msgstr "发布项目仓库中的文档"

msgid "Pushing A Change"
msgstr "推进一个更改"

msgid "RABBIT_PASSWORD"
msgstr "RABBIT_PASSWORD"

msgid ""
"Read the `Summary of Git commit message structure <https://wiki.openstack."
"org/wiki/GitCommitMessages?%22Summary%20of%20Git%20commit%20message"
"%20structure%22#Summary_of_Git_commit_message_structure>`_ for best "
"practices on writing the commit message. When you are ready to send your "
"changes for review use::"
msgstr ""
"阅读 `Summary of Git commit message structure <https://wiki.openstack.org/"
"wiki/GitCommitMessages?%22Summary%20of%20Git%20commit%20message%20structure"
"%22#Summary_of_Git_commit_message_structure>`_ 以获取编写提交消息的最佳实"
"践。 当您准备好将您的更改发送以供审核时使用时："

msgid "Reference documents"
msgstr "参考文档"

msgid "Removal of .pyc files"
msgstr "删除.pyc文件"

msgid "Removing configuration files for projects from /etc"
msgstr "从/etc删除项目的配置文件"

msgid "Removing log files"
msgstr "删除日志文件"

msgid "Report recurring bugs so that you don't need to manually 'recheck'"
msgstr "报告重复出现的错误，是的您无需手动'重新检查'"

msgid "Request reviews from specific community members"
msgstr "请求指定社区成员的审核"

msgid "Required packages (like mysql and rabbitmq) are installed"
msgstr "安装必需的软件包（例如mysql和rabbitmq）"

msgid "Reviewing Changes"
msgstr "审阅更改"

msgid ""
"Reviewing changes is often suggested as a way to get started on a project. "
"Whether this is how you choose to get started or not, it's an important "
"community activity. See `How to Review Changes the OpenStack Way <https://"
"docs.openstack.org/project-team-guide/review-the-openstack-way.html>`_ for "
"more detailed guidance on when to use which votes on a change review."
msgstr ""
"审阅更改通常被建议为开始项目的一种方法。 无论您是选择开始还是不选择，这都是一"
"项重要的社区活动。 请参阅 `How to Review Changes the OpenStack Way <https://"
"docs.openstack.org/project-team-guide/review-the-openstack-way.html>`_ 以获取"
"有关何时在审阅更改中使用哪种投票的更详细指导。 "

msgid ""
"Reviewing large patches is very inconvenient and time consuming therefore we "
"always suggest to break down your changes into smaller blocks."
msgstr ""
"审核大型补丁非常不方便且耗时，因此我们始终建议您将变更分解为较小的补丁。"

msgid ""
"Running ``unstack.sh`` is the first thing to try in the case that a DevStack "
"run fails. If subsequent runs fail a more thorough removal of DevStack "
"components may be done with the following command:"
msgstr ""
"在DevStack运行失败的情况下，首先要尝试运行 ``unstack.sh`` 。 如果后续运行失"
"败，则可以使用以下命令更彻底地删除DevStack组件："

msgid "Sandbox Git Repository"
msgstr "沙箱Git仓库"

msgid "Sandbox Project on Launchpad"
msgstr "Launchpad上的沙箱项目"

msgid "Sandbox Project on StoryBoard"
msgstr "在StoryBoard上的沙箱项目"

msgid "Save and quit the editor, and I see:"
msgstr "保存并退出编辑器，我会看到："

msgid "Set to 'true' all document options that apply. For example::"
msgstr "将所有适用的文档选项设置为'true'。 例如::"

msgid ""
"Since systemd accepts wildcards, the status of all services associated with "
"DevStack can be displayed with:"
msgstr ""
"由于systemd接受通配符，因此与DevStack关联的所有服务的状态都可以显示为："

msgid "So let's say I make an edit for my first patch and commit it:"
msgstr "假设我对第一个补丁进行了编辑并提交："

msgid ""
"Sometimes there might be people you need to weigh in on your patch because "
"they have a vested interest or are helping mentor you. The easiest way of "
"letting them know you have uploaded a new patch or patchset is to add them "
"as reviewers in the gerrit web-ui. You can look them up by name, gerrit "
"email address, ssh user name, or gerrit id."
msgstr ""
"有时候，您可能需要有人帮助权衡您的补丁，因为他们有相关的关键考量或正处于帮助"
"指导您开发基础的阶段。 让他们知道您已上传新补丁或补丁集的最简单方法是将他们添"
"加为gerrit web-ui中的审阅者（reviewer）。 您可以通过名字，gerrit电子邮件地"
"址，ssh用户名或gerrit ID来查找它们。"

msgid "Start on a freshly-``pull``\\ed master branch:"
msgstr "从一个新 ``pull`` 出来的主分支开始："

msgid "Stopping DevStack"
msgstr "停止DevStack"

msgid "Stopping the project services, mysql and rabbitmq"
msgstr "停止项目服务，mysql和rabbitmq"

msgid "Testing Changes with DevStack"
msgstr "使用DevStack测试更改"

msgid ""
"The 'Depends-On' tag is a marker on your changes and when used a patch "
"cannot be merged until all its dependencies are landed."
msgstr ""
"'Depends-On'标签是您所做更改的标记，当使用标签时，除非提交更改的所有依赖项均"
"已获得，否则补丁将无法合并。"

msgid "The OpenStack Services are registered and started"
msgstr "注册并启动OpenStack服务"

msgid "The OpenStack projects are cloned into /opt/stack/"
msgstr "克隆OpenStack项目到/opt/stack/"

msgid "The Right Content"
msgstr "合适的内容"

msgid "The Right Size"
msgstr "合适的大小"

msgid ""
"The Sandbox repository and projects are maintained by community members with "
"occasional cleanup. Please help us with the housekeeping and clean up your "
"work, when you are finished with your practice and feel comfortable using "
"the tool."
msgstr ""
"沙箱仓库（Sandbox Repo）和项目由社区成员维护，并偶尔进行清理。 完成练习后，请"
"帮助我们在完整这些实践练习并感觉会用这些工具了以后进行环境整理并清理您的工"
"作。"

msgid ""
"The `OpenStack Documentation Contributor Guide <https://docs.openstack.org/"
"doc-contrib-guide/index.html>`_ describes how to contribute to OpenStack "
"documentation. It contains information on `writing <https://docs.openstack."
"org/doc-contrib-guide/writing-docs.html>`_, `building <https://docs."
"openstack.org/doc-contrib-guide/docs-builds.html>`_, and `reviewing <https://"
"docs.openstack.org/doc-contrib-guide/docs-review.html>`_ documents, as well "
"as best practices and `API documentation guidelines <https://docs.openstack."
"org/doc-contrib-guide/api-guides.html>`_."
msgstr ""
"`OpenStack Documentation Contributor Guide <https://docs.openstack.org/doc-"
"contrib-guide/index.html>`_ 描述了如何为OpenStack文档做出贡献。 它包含有关如"
"何 `writing <https://docs.openstack.org/doc-contrib-guide/writing-docs."
"html>`_, `building <https://docs.openstack.org/doc-contrib-guide/docs-builds."
"html>`_, 和 `reviewing <https://docs.openstack.org/doc-contrib-guide/docs-"
"review.html>`_ 文档的相关信息，以及最佳做法和 `API documentation guidelines "
"<https://docs.openstack.org/doc-contrib-guide/api-guides.html>`_ 。"

msgid ""
"The ``cli`` directory contains command line tool reference documentation "
"which can be automatically generated with cliff’s sphinx integration, or "
"manually written when auto-generation is not possible. For more information, "
"see `cliff Sphinx Integration`_."
msgstr ""
"``cli`` 目录包含命令行工具参考文档，这些文档可以通过cliff的sphinx集成自动生"
"成，或者在无法自动生成时手动编写。 有关更多信息，请参见 `cliff Sphinx "
"Integration`_ 。"

msgid ""
"The ``configuration`` directory contains configuration reference information "
"that is either automatically generated (if the project uses ``oslo.config``) "
"or manually written (if ``oslo.config`` is not used). For more information, "
"see `Sphinx Integration`_."
msgstr ""
"``configuration`` 目录包含配置参考信息，这些信息可以自动生成（如果项目使用 "
"``oslo.config`` ）或手动编写（如果不使用 ``oslo.config`` ）。 有关更多信息，"
"请参见 `Sphinx Integration`_ 。"

msgid ""
"The ``reference`` directory contains reference information not included in "
"the other directories, for instance, automatically generated class "
"documentation in library projects."
msgstr ""
"``reference`` 目录包含其他目录中未包含的参考信息，例如库项目中自动生成的类文"
"档。"

msgid ""
"The ``user`` directory contains information targeted at end-users, for "
"instance, concept guides, tutorials, step-by-step instructions for using the "
"CLI or the project's API, and such."
msgstr ""
"``user`` 目录包含针对最终用户的信息，例如概念指南，教程，使用CLI或项目API的分"
"步说明等。"

msgid ""
"The above command and subsequent command examples assume you are still in "
"the root directory of your DevStack clone."
msgstr "以上命令和后续命令示例假定您仍位于DevStack克隆的根目录下。"

msgid ""
"The admin guide can be found in the ``admin`` directory. It contains "
"information on the configuration and operation of the software. The "
"project's administrator guide is included in the `OpenStack Administrator "
"Guides`_."
msgstr ""
"管理员指南可以在 ``admin`` 目录中找到。 它包含有关软件配置和操作的信息。 项目"
"的管理员指南包含在 `OpenStack Administrator Guides`_ 中。"

msgid ""
"The basic set of values contributors have to vote with on a patch is: -1, 0, "
"or +1. These values correspond to a relatively simple system."
msgstr ""
"贡献者必须对补丁进行投票的基本值的集合是：-1、0或+1。 这些值对应了一个相对简"
"单的系统。"

msgid "The change ID can be found on the web UI of Gerrit:"
msgstr "更改ID可以在gerrit的网络界面找到："

msgid "The change ID is the same as in the previous case."
msgstr "更改ID则和前面的情况是一致的。"

msgid ""
"The contributor guide can be found in the ``contributor`` directory. It "
"contains project-specific information on contributing to the project and on "
"team management. This guide appears only in the project's documentation."
msgstr ""
"贡献者指南可在 ``contributor`` 目录中找到。 它包含有关项目贡献和团队管理的特"
"定于项目的信息。 贡献者指南仅出现在项目的文档中。"

msgid "The documentation directory structure is the following::"
msgstr "文档目录结构如下::"

msgid ""
"The following command needs to be run as a user with sudo access and "
"NOPASSWD configured."
msgstr "以下命令需要以具有sudo访问权限和NOPASSWD配置的用户身份运行。"

msgid ""
"The heart of open source is the people who are participating in a community "
"and it is no different in case of OpenStack either."
msgstr "开源的核心是参与社区的人们，对于OpenStack来说也是如此。"

msgid ""
"The installation guide can be found in the ``install`` directory. It "
"contains information on anything to do with installing a project from "
"packages, for instance, software necessary for installing the project, like "
"database installation and configuration, or what parameters should be set in "
"the project's config file. If everything is configured properly (described "
"below), the project's installation guide is included in the `OpenStack "
"Installation Guides`_. The installation guide is not intended to be used for "
"production system installations."
msgstr ""
"安装指南可以在 ``install`` 目录中找到。 它包含关于从软件包安装项目的任何信"
"息，例如，安装项目所需的软件，例如数据库安装和配置，或需要在项目的配置文件中"
"设置哪些参数等等。 如果一切都配置正确（如下所述），则项目的安装指南包含在 "
"`OpenStack Installation Guides`_ 中。 本安装指南不适用于生产系统安装。"

msgid ""
"The patch submitted is a duplicate or at odds with another patch submitted."
msgstr "提交的补丁是重复的，或者与提交的另一个补丁不一致。"

msgid ""
"The tag can be applied to patches proposed for the same repository as well. "
"In that case the changes are separate enough to be kept independent which "
"means that if you need to fix changes from review comments you can do it on "
"a per patch basis. It is also true for rebasing each patch."
msgstr ""
"该标签也可以应用于为同一项目仓库建议的补丁。 在这种情况下，更改是可以彼此分"
"隔，独立维护的。这意味着，如果您需要修复评论注释中的更改，则可以在每个补丁的"
"基础上进行更改。 对于为每个补丁重新设置基准代码也是同样适用。"

msgid ""
"The tools that we are using in the community can look complicated if you are "
"not familiar with them. To help you practice before you use them in action "
"we are providing sandbox environments for you where you can practice all the "
"steps we describe in this guide."
msgstr ""
"如果不熟悉社区中使用的工具，它们可能会看起来很复杂。 为了帮助您在实际使用它们"
"之前进行练习，我们为您提供了沙箱环境，您可以在其中练习本指南中介绍的所有步"
"骤。"

msgid ""
"There are multiple options to choose from depending on the structure of your "
"design. You can either organize the changes in patch chains or you can use "
"the 'Depends-On' tag."
msgstr ""
"根据设计的结构，有多种选择。 您可以在补丁链中组织你的更改，也可以使"
"用'Depends-On'标签。"

msgid ""
"There is an issue with the approach taken in the patch and it needs to be "
"discussed with a larger group, likely in a meeting."
msgstr "补丁中采用的方法存在问题，需要与更大的小组讨论，例如在会议中。"

msgid ""
"This chapter will guide you through of all the tools and processes that we "
"are using to develop, test, maintain, and document the projects in OpenStack."
msgstr ""
"本章将指导您了解所有用于开发，测试，维护和记录OpenStack中项目的工具和过程。"

msgid ""
"This command cleans up the OpenStack installation that was performed on the "
"node.  This includes:"
msgstr "此命令清除在节点上执行的OpenStack安装。 这包括："

msgid ""
"This guide won't go into the details of tracing through the logs of a run "
"and finding a good fingerprint, since that's quite involved, dependent on "
"the job you're looking at, and already documented in a few places including:"
msgstr ""
"本指南将不涉及跟踪运行日志和查找良好“指纹”的详细信息，因为这会根据您要查找的"
"工作涉及很多，并且已经在一些地方进行了记录，包括："

msgid ""
"This is a good way to help tracking related changes, let that be a feature "
"implementation, bugfix or documentation work."
msgstr ""
"这是帮助跟踪相关更改的好方法，可以将其用作功能实现，错误修复或文档工作。"

msgid ""
"This pops me into an editor showing me all the commits between wherever I am "
"and the main branch (now they're in top-first order):"
msgstr ""
"这使我进入编辑器，向我显示任何我所处位置与主分支之间的所有提交（现在，它们处"
"于最高优先顺序）："

msgid "This section allows you to:"
msgstr "本章节允许您："

msgid ""
"This section assumes you have completed :doc:`../common/setup-gerrit` guide."
msgstr "本章节假设您已完成 :doc:`../common/setup-gerrit` 指南。"

msgid "This section assumes you have completed :doc:`/common/zuul-status`"
msgstr "本部分假设您已完成 :doc:`/common/zuul-status`"

msgid ""
"This section contains information necessary to contributing to OpenStack "
"documentation."
msgstr "本部分包含有助于OpenStack文档的信息。"

msgid ""
"This section will guide you through how to create patches that people will "
"want to review."
msgstr "本节将指导您了解如何创建人们想查看的补丁。"

msgid ""
"This will commit the changes under the same set of changes you issued "
"earlier. Notice that in order to send your latest version for review, you "
"will still need to call::"
msgstr ""
"这将在您之前发起的同一组更改下提交更改。 请注意，要发送最新版本以供审核，您仍"
"然需要调用::"

msgid ""
"To access the Gerrit Web Editor click on the icon that looks like a pencil "
"writing on paper next to the patch set number at the top of a Gerrit Code "
"Review page for a file."
msgstr ""
"要访问Gerrit网络编辑器以编辑文件，请单击Gerrit Code Review页面顶部的补丁集编"
"号旁边的看起来像铅笔在纸上写字的那个图标。"

msgid "To check the differences between your branch and the repository::"
msgstr "要检查您的分支和仓库之间的差异::"

msgid "To check the files that have been updated in your branch::"
msgstr "要检查您的分支中已更新的文件::"

msgid "To clone a copy of some repository::"
msgstr "克隆某个仓库的拷贝::"

msgid ""
"To create your development branch (substitute branch_name for a name of your "
"choice). It's better to create a new branch for each patch than working from "
"master::"
msgstr ""
"创建您的开发分支（用您选择的名称替换branch_name）。 最好为每个补丁创建一个新"
"分支，而不是使用主分支::"

msgid ""
"To download the full chain you need to download the top patch and Git will "
"automatically download all the dependent patches in the chain."
msgstr ""
"要下载完整的补丁链，您需要下载顶层补丁，Git会自动下载补丁链中的所有相关补丁。"

msgid ""
"To modify a patch within a chain you will need to use interactive rebase:"
msgstr "要修改补丁链中的补丁，您将需要使用交互式复位基础（rebase）："

msgid ""
"To shutdown a DevStack instance running on a node the following command "
"should be used:"
msgstr "要关闭在节点上运行的DevStack实例，应使用以下命令："

msgid ""
"To simplify future interaction with your deployment you will want to set the "
"following variables:"
msgstr "为了简化将来与部署的交互，您将需要设置以下变量："

msgid "Tracking a new bug in elastic-recheck"
msgstr "在elastic-recheck中跟踪一个新错误"

msgid "Tracking your Changes"
msgstr "跟踪您的更改"

msgid "Tutorial: Developing Changes In A Series"
msgstr "教程：开发一系列变更"

msgid ""
"Until you click 'Reply' and vote on the patch, any inline comments you've "
"made exist as drafts."
msgstr ""
"在您单击“答复”并对补丁进行投票之前，您所做的任何行内评论都将作为草稿存在。"

msgid "User guide"
msgstr "用户指南"

msgid ""
"Using DevStack to develop and test changes is easy. Development can be done "
"in the project clones under ``/opt/stack/<project name>``. Since the "
"projects are clones of the project's git repository a branch can be made and "
"development can take place."
msgstr ""
"使用DevStack开发和测试更改很容易。 可以在项目克隆中的 ``/opt/stack/<project "
"name>`` 下进行开发。 考虑到项目是项目git仓库的克隆，因此可以创建分支并进行开"
"发。"

msgid "Using Elastic Recheck"
msgstr "使用Elastic Recheck"

msgid "Using Gerrit"
msgstr "使用Gerrit"

msgid "Verifying Your DevStack Deployment"
msgstr "验证您的DevStack部署"

msgid ""
"We do not differentiate between the different types of contributions such as "
"code or documentation therefore you will find guidance in this chapter for "
"all types."
msgstr ""
"我们不会区分代码或文档等不同类型的贡献，因此您将在本章中找到所有类型的贡献指"
"南。"

msgid "What is DevStack"
msgstr "什么是DevStack"

msgid "What is elastic-recheck"
msgstr "什么是elastic-recheck"

msgid "What to do if a test job fails"
msgstr "如果测试作业失败该怎么办"

msgid ""
"When you ``git commit`` (without ``--amend``), you're creating a new commit "
"on top of whatever commit you started at. If you started with a clean, "
"freshly ``pull``\\ed master branch, that'll be whatever the most recently "
"merged commit in the master branch was. In this example, that's commit "
"``3d008a3``."
msgstr ""
"当您执行 ``git commit`` （不带 ``--amend`` 选项）时，您将在开始的任何提交之上"
"创建一个新的提交。 如果您从一个干净的，新的 ``pull`` 出来的主分支开始，那将是"
"主分支中最新合并的提交。 在此示例中，是提交 ``3d008a3`` 。"

msgid ""
"When you are working on implementing a new feature or adding documentation "
"to an already existing one it is easy to get carried away by the work itself "
"and forget about the unwritten rules of constructing your changes."
msgstr ""
"当您在实现一项新功能或向现有功能添加文档时，很容易被这些任务本身所牵扯住，而"
"忽略了构建变更的一些不成文规则。"

msgid ""
"When you encounter a failure that's not being tracked by elastic-recheck and "
"you've looked through the logs to determine that it's not being caused by "
"the proposed change and is affecting other changes you can propose a new "
"elastic-recheck fingerprint."
msgstr ""
"当您遇到无法通过elastic-recheck进行跟踪的故障，并且查看了日志以确定该故障不是"
"由建议的更改引起的并且正在影响其他更改时，可以提出新的elastic-recheck“指纹”。"

msgid ""
"When you have a chain Gerrit helps you by listing all the commit titles in "
"the 'Related Changes' column on the top right corner of the Gerrit UI. The "
"titles are also links which help you navigate between the changes to review "
"them when you upload a new version."
msgstr ""
"当有一组补丁链后，Gerrit可以通过在Gerrit UI右上角的“相关联变更（Related "
"Changes）”中列出所有提交标题来帮助您。 标题也是链接，可帮助您在更改之间导览，"
"以在上载新版本时查看它们。"

msgid ""
"When you have changes in multiple project repositories you can mark "
"dependent patches with the 'Depends-On' tag. The tag will appear as a link "
"in the commit message which helps you and also the reviewers to track and "
"navigate between the dependencies of your changes."
msgstr ""
"当您在多个项目仓库中进行更改时，可以使用'Depends-On'标签标记相关依赖的补丁。 "
"该标记将作为链接显示在提交消息中，该链接可以帮助您以及审阅者在更改的依赖关系"
"之间进行跟踪和导览。"

msgid ""
"When you submit a patch to gerrit and zuul returns the test results for the "
"jobs it ran, sometimes one of those tests fails. Most of the time this "
"indicates there is an issue with your proposed change and the tests are "
"catching it. Sometimes the test run might have tripped over an underlying "
"pre-existing bug in OpenStack. Additionally, some times the infrastructure "
"for running the tests might have had a failure. To figure this out you'll "
"always need to look at the logs from the failed job to understand what's "
"happening."
msgstr ""
"当您向gerrit提交补丁时，zuul返回其运行的测试结果，有时其中一项测试失败。 在大"
"多数情况下，这表明您建议的更改存在问题，并且测试正在找出问题。 有时，测试运行"
"可能会因OpenStack中潜在的预先存在的错误而跳闸。 此外，有时运行测试的基础设施"
"可能会出现故障。 为了弄清楚这一点，您始终需要查看失败作业的日志以了解发生了什"
"么。"

msgid ""
"When you upload changes in a chain only the patches that got updated will be "
"uploaded. This also means that the review scores on lower patches in the "
"chain will be untouched."
msgstr ""
"当您上传补丁链中的更改时，只会上传被更新的补丁。 这也意味着补丁链中较低层的补"
"丁的评论得分数将保持不变。"

msgid ""
"When you're working on a blueprint, you want to name your local branch after "
"the blueprint. For this example, we'll use ``bp/nova-cyborg-interaction``."
msgstr ""
"在工作在一个蓝图（bp）上时，您可能会想要在蓝图后命名本地分支。 在此示例中，我"
"们将使用 ``bp/nova-cyborg-interaction`` 。"

msgid ""
"When your work item grows above a particular size and you need to upload "
"multiple patches it is crucial to structure it well in case of both patch "
"chains and independent changes."
msgstr ""
"当您的工作项增长到特定大小以上并且您需要上传多个补丁时，至关重要的是，在补丁"
"链或是独立更改的情况下，合理地组织它。"

msgid ""
"While there is no magic number try to **keep the size of your changes as "
"small as possible**, but under a few hundreds of lines changed total. "
"Patches that are test heavy with little code change require as much effort "
"as code heavy changes."
msgstr ""
"虽然没有一个神奇的数字规范**使变更量的大小保持尽可能小**，但最好总变更量要少"
"于几百行。 少量代码变更但是进行大量测试的补丁与大量代码变更所需的工作量相同。"

msgid ""
"You can find a `Sandbox <https://storyboard-dev.openstack.org/#!/"
"project/2>`_ project in the tool that provides all the functionalities to "
"you as any of the other active projects."
msgstr ""
"您可以在工具中找到一个 `Sandbox <https://storyboard-dev.openstack.org/#!/"
"project/2>`_ 项目，该项目可以像其他任何活跃项目一样为您提供所有功能。"

msgid "You can find instructions on how to use Git in the :ref:`git` section."
msgstr "您可以在 :ref:`git` 章节中找到有关如何使用Git的说明。"

msgid ""
"You can find the same repositories using the search function here: `OpenDev "
"git repository browser <https://opendev.org/explore/repos>`_"
msgstr ""
"您可以在此处使用搜索功能找到相同的仓库： `OpenDev git repository browser "
"<https://opendev.org/explore/repos>`_"

msgid "You can find these pages at:"
msgstr "你可以在下面找到这些页面："

msgid ""
"You can see the current status of the bugs being tracked by elastic recheck "
"at: `Elastic Recheck <http://status.openstack.org/elastic-recheck/index."
"html>`_"
msgstr ""
"您可以在以下位置查看通过elastic recheck跟踪的错误的当前状态： `Elastic "
"Recheck <http://status.openstack.org/elastic-recheck/index.html>`_"

msgid ""
"You can upload your changes to the sandbox repository and review it on "
"Gerrit as it is described in the :ref:`gerrit` section."
msgstr ""
"您可以将所做的更改上传到沙箱仓库，然后按照 :ref:`gerrit` 章节中的说明在Gerrit"
"上进行检查。"

msgid ""
"You get permissions to perform all the operations in the Sandbox project for "
"the sake of practice. When you join a project as a contributor you will have "
"limited access to the functionalities as there are actions only core "
"reviewers can perform. You can find information about these in the "
"respective sections of the Contributor Guide."
msgstr ""
"为了练习，您具有在沙箱项目中执行所有操作的权限。 当您以贡献者身份加入项目时，"
"您将只能使用部分功能，因为只有核心审核人员可以执行某些操作。 您可以在《贡献者"
"指南》的相应章节中找到有关这些内容的信息。"

msgid ""
"You have the option to specify a topic for your changes when you upload them "
"for review. While Gerrit topics will not add dependency to your patches you "
"can apply a search based on the topic that will show you all the relevant "
"changes in all the projects where there are patches with the same topic. "
"Gerrit will also show them to you in the 'Same Topic' column on the top "
"right corner of the page of a review."
msgstr ""
"当您上传更改以进行审核时，可以选择为更改指定标题。 尽管Gerrit标题不会对补丁增"
"加依赖性，但是您可以基于标题进行搜索，该搜索将向您显示所有具有相同标题的补丁"
"的所有相关更改。 Gerrit还将在评论页面右上角的“相同标题（Same Topic）”列中向您"
"显示这些标题。"

msgid ""
"You need as many '^' as the number of the patch you want to edit first from "
"the top of the chain. Alternatively you may wish to use `git-restack "
"<https://docs.openstack.org/infra/git-restack/>`_, which figures out the "
"appropriate ``git rebase`` command for you."
msgstr ""
"从补丁链顶部开始，您将需要与要编辑的补丁数量一样多的'^'。 另外，您可能希望使"
"用 `git-restack <https://docs.openstack.org/infra/git-restack/>`_ ，这会为您"
"找出合适的 ``git rebase`` 命令。"

msgid ""
"You should also check any elastic search queries using kibana at: `Logstash "
"Search <http://logstash.openstack.org/>`_"
msgstr ""
"您还应该在以下位置使用kibana检查所有弹性搜索查询： `Logstash Search <http://"
"logstash.openstack.org/>`_"

msgid ""
"`+1`_: Looks good to me, but someone else must approve. This does not mean "
"that there is nothing to comment on, just that there aren't any issues that "
"would block the merging of the patch. You can still make comments on "
"nitpicky things the patch owner can address if others find issues with the "
"patch. These comments might also be something to address in a followup patch "
"as opposed to another patchset."
msgstr ""
"`+1`_ ：对我来说不错，但其他人必须批准。 这并不意味着没有什么可评论的，只是不"
"存在任何会阻碍补丁合并的问题。 如果其他人发现补丁的问题，您仍然可以对补丁所有"
"者可能解决这个问题的一些方式发表评论。 这些评论也可能是这项补丁的后续补丁（而"
"不是另一个补丁集）中要解决的问题。"

msgid ""
"`+2`_: Looks good to me (core reviewer). Depending on the project team and "
"repository, merging a patch will require at least one +2 vote if not two +2 "
"votes."
msgstr ""
"`+2`_ ：对我来说看起来不错（核心审阅者）。 根据项目团队和软件仓库的不同，合并"
"补丁至少需要一票“+2”（如果不是两票“+2”）。"

msgid ""
"`-1`_: This patch needs further work before it can be merged. A -1 is "
"usually given when the reviewer sees some issue that needs to be fixed "
"before the patch can be merged. The issues the author needs to address "
"would, ideally, have inline comments posted on them unless there is some "
"larger issue. If there is something wrong with the overall approach, you are "
"able to leave an overall comment with the vote to raise your concerns."
msgstr ""
"`-1`_ ：这个补丁需要进一步的修改才能合并。 当审阅者发现合并补丁之前需要解决一"
"些问题时，通常会给出-1。 理想情况下，除非有更大的问题，否则作者需要解决的问题"
"应在相应的位置上添加行内评论（inline comments）。 如果总体方法有问题，您可以"
"在投票中留下总体评论，以提出您的担忧。"

msgid ""
"`-2`_: Do not merge. This score does not often appear and when it does, it's "
"for a good reason:"
msgstr ""
"`-2`_ ：不要合并。 这个分数并不经常出现，当出现时，这是有充分的理由的："

msgid ""
"`0`_: No score. This is the default score when replying to a patchset. "
"Generally it's kept as the vote when someone has a question about the "
"patchset or doesn't have a fully formed opinion of the patchset yet - it "
"requires more time, testing, or investigation."
msgstr ""
"`0`_ ：没有分数。 这是回复补丁集时的默认分数。 通常，当有人对补丁集有疑问或尚"
"未对补丁集有完整的意见时，它将保留表决权–需要更多时间，测试或调查。"

msgid ""
"`Tales From the Gate: How Debugging the Gate Helps Your Enterprise <https://"
"www.openstack.org/videos/vancouver-2015/tales-from-the-gate-how-debugging-"
"the-gate-helps-your-enterprise>`_"
msgstr ""
"`Tales From the Gate: How Debugging the Gate Helps Your Enterprise <https://"
"www.openstack.org/videos/vancouver-2015/tales-from-the-gate-how-debugging-"
"the-gate-helps-your-enterprise>`_"

msgid ""
"`Unclassified failed integrated gate jobs <http://status.openstack.org/"
"elastic-recheck/data/integrated_gate.html>`_ and `Unclassified failed jobs "
"<http://status.openstack.org/elastic-recheck/data/others.html>`_"
msgstr ""
"`Unclassified failed integrated gate jobs <http://status.openstack.org/"
"elastic-recheck/data/integrated_gate.html>`_ 和 `Unclassified failed jobs "
"<http://status.openstack.org/elastic-recheck/data/others.html>`_"

msgid ""
"`elastic-recheck queries <https://docs.openstack.org/infra/elastic-recheck/"
"readme.html#queries>`_"
msgstr ""
"`elastic-recheck queries <https://docs.openstack.org/infra/elastic-recheck/"
"readme.html#queries>`_"

msgid "depending on which jobs you're interested in."
msgstr "取决于哪些作业是你感兴趣的。"

msgid ""
"elastic-recheck also has a page to show how many failures were encountered "
"that do not have a matching fingerprint. Typically the more failures that go "
"uncategorized the more unstable the gate is (and OpenStack as a whole)."
msgstr ""
"elastic-recheck也有一个页面来显示遇到了多少个没有匹配“指纹”的故障。 通常，未"
"分类的故障越多，则门控（以及整个OpenStack）越不稳定。"

msgid ""
"elastic-recheck is a tool used to track failures in test jobs. It keeps a "
"repository of fingerprints for known bugs that are affecting jobs in the "
"gate. It is then used to both track the rates those bugs are being found and "
"also to leave comments in gerrit and in IRC when it has found a known bug "
"fingerprint in a failure."
msgstr ""
"elastic-recheck是用于跟踪测试作业中的失败的工具。 它保留了已知错误“指纹”的仓"
"库，这些“指纹”存储着正在影响门控工作的已知错误。 然后，它既可以用来跟踪发现这"
"些错误的速率，也可以在发现故障的已知错误“指纹”时在gerrit和IRC中留下注释。"

msgid ""
"elastic-recheck is built on top of an ELK (`Elastic Search <https://github."
"com/elastic/elasticsearch>`_, `Logstash <https://github.com/elastic/"
"logstash>`_, `Kibana <https://github.com/elastic/kibana>`_) stack where we "
"use Logstash to store all logs from CI jobs in an Elastic Search cluster. We "
"also host a `Kibana dashboard <http://logstash.openstack.org/>`_ which can "
"be used to run queries on the cluster and interacts with the data. elastic-"
"recheck queries the elastic-search cluster for the fingerprints."
msgstr ""
"elastic-recheck建立在ELK之上（ `Elastic Search <https://github.com/elastic/"
"elasticsearch>`_, `Logstash <https://github.com/elastic/logstash>`_, `Kibana "
"<https://github.com/elastic/kibana>`_ ），我们使用Logstash将CI作业中的所有日"
"志存储在Elastic Search集群中。 我们还托管了一个 `Kibana dashboard <http://"
"logstash.openstack.org/>`_ ，可用于在集群上运行查询并与数据进行交互。 "
"elastic-recheck在弹性搜索集群中查询“指纹”。"

msgid "etc."
msgstr "等等"

msgid "mysql and rabbitmq are configured"
msgstr "配置mysql和rabbitmq"