#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: contributor-guide\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-08-26 06:15+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../source/common/accounts.rst:3
msgid "Account Setup"
msgstr ""

#: ../../source/common/accounts.rst:8
msgid "Setup Your Open Infrastructure Foundation Account"
msgstr ""

#: ../../source/common/accounts.rst:10
msgid "An Open Infrastructure Foundation account allows you to:"
msgstr ""

#: ../../source/common/accounts.rst:12
msgid "Vote in elections."
msgstr ""

#: ../../source/common/accounts.rst:13
msgid "Run for elected positions in the OpenStack project."
msgstr ""

#: ../../source/common/accounts.rst:14
msgid "Submit presentations to OpenStack conferences."
msgstr ""

#: ../../source/common/accounts.rst:15
msgid "Vote on presentations at OpenStack conferences."
msgstr ""

#: ../../source/common/accounts.rst:18 ../../source/common/accounts.rst:85
#: ../../source/common/accounts.rst:107 ../../source/common/setup-gerrit.rst:24
msgid "Sign Up"
msgstr ""

#: ../../source/common/accounts.rst:21
msgid ""
"Make sure to use the same email address you'll want to use for code "
"contributions since it's important later that these match up."
msgstr ""

#: ../../source/common/accounts.rst:24
msgid ""
"Go to the `Open Infrastructure Foundation sign up page <https://openinfra."
"dev/join/>`_."
msgstr ""

#: ../../source/common/accounts.rst:26
msgid ""
"Under 'Participate as an Individual Member'', click the **AS AN INDIVIDUAL "
"FOUNDATION MEMBER** link."
msgstr ""

#: ../../source/common/accounts.rst:32
msgid ""
"Read through the presented individual member terms of service and our "
"`Community Code of Conduct <https://www.openstack.org/legal/community-code-"
"of-conduct/>`_."
msgstr ""

#: ../../source/common/accounts.rst:35
msgid ""
"Fill in your name, e-mail address, and gender. Use the same e-mail address "
"at every step of the registration procedure. This address will also be used "
"as your login. Your gender information is available via public API."
msgstr ""

#: ../../source/common/accounts.rst:38
msgid ""
"Add your affiliation information and statement of interest. This will be "
"visible only to foundation members."
msgstr ""

#: ../../source/common/accounts.rst:40
msgid ""
"Fill in your home address. This will be only visible to foundation members."
msgstr ""

#: ../../source/common/accounts.rst:41
msgid "Fill in your password and check the box next to 'I'm not a robot'."
msgstr ""

#: ../../source/common/accounts.rst:42
msgid "Submit your application."
msgstr ""

#: ../../source/common/accounts.rst:46
msgid "Eligibility to Vote in Elections"
msgstr ""

#: ../../source/common/accounts.rst:48
msgid ""
"Foundation Membership makes you eligible to vote in elections, for full "
"details see the `individual member policy <https://www.openstack.org/legal/"
"individual-member-policy/>`__."
msgstr ""

#: ../../source/common/accounts.rst:54
msgid "Setup Your Task Tracker Account"
msgstr ""

#: ../../source/common/accounts.rst:57
msgid ""
"The OpenStack community is currently in the process of moving from the bug "
"tracking software Launchpad to StoryBoard. Further in the project specific "
"on-boarding documentation, give special attention to if the project is using "
"Launchpad or StoryBoard. If your project is still using Launchpad you will "
"want to take notice of the Launchpad section later in this document."
msgstr ""

#: ../../source/common/accounts.rst:64
msgid "A Task Tracker account allows you to:"
msgstr ""

#: ../../source/common/accounts.rst:66
msgid "Report bugs"
msgstr ""

#: ../../source/common/accounts.rst:67
msgid "Create stories for new features (Process varies per project)"
msgstr ""

#: ../../source/common/accounts.rst:68
msgid "Track progress on bugs and new features"
msgstr ""

#: ../../source/common/accounts.rst:72
msgid "StoryBoard"
msgstr ""

#: ../../source/common/accounts.rst:75
msgid "What is StoryBoard?"
msgstr ""

#: ../../source/common/accounts.rst:76
msgid ""
"`StoryBoard <https://storyboard.openstack.org>`_ is  bug tracking software "
"the OpenStack community is `developing <https://wiki.openstack.org/wiki/"
"StoryBoard>`_, and in the progress of `migrating towards <https://superuser."
"openstack.org/articles/openstack-gerrit-storyboard-integration/>`_. Some "
"`projects are already using it <https://storyboard.openstack.org/#!/project/"
"list>`_."
msgstr ""

#: ../../source/common/accounts.rst:86
msgid ""
"Go to the `storyboard.openstack.org <https://storyboard.openstack.org>`_."
msgstr ""

#: ../../source/common/accounts.rst:87
msgid "On the top right corner, click the **login** button."
msgstr ""

#: ../../source/common/accounts.rst:88
msgid "If you already have an Ubuntu One Account, you can just login."
msgstr ""

#: ../../source/common/accounts.rst:89
msgid ""
"If you don't have a Ubuntu One Account, click the **I am a new Ubuntu One "
"user**."
msgstr ""

#: ../../source/common/accounts.rst:91
msgid ""
"Fill in your email address, name, password, and accepting the terms of "
"services."
msgstr ""

#: ../../source/common/accounts.rst:98 ../../source/common/task-tracking.rst:74
msgid "Launchpad"
msgstr ""

#: ../../source/common/accounts.rst:101
msgid "What is Launchpad?"
msgstr ""

#: ../../source/common/accounts.rst:102
msgid ""
"`Launchpad <https://launchpad.net/openstack>`_ is the legacy way the "
"OpenStack community does bug tracking since we started `moving towards "
"StoryBoard <https://superuser.openstack.org/articles/openstack-gerrit-"
"storyboard-integration>`_."
msgstr ""

#: ../../source/common/accounts.rst:108
msgid ""
"You're already signed up. Launchpad uses your Ubuntu One account for "
"authentication like StoryBoard."
msgstr ""

#: ../../source/common/communication.rst:3
msgid "Communication"
msgstr ""

#: ../../source/common/communication.rst:5
msgid "This sections allows you to:"
msgstr ""

#: ../../source/common/communication.rst:7
msgid "Ask questions and get prompt responses from the community"
msgstr ""

#: ../../source/common/communication.rst:8
msgid "Build up your persona in the community as a contributing member"
msgstr ""

#: ../../source/common/communication.rst:9
msgid "Stay up to date on the active discussions in the community"
msgstr ""

#: ../../source/common/communication.rst:12
msgid "Internet Relay Chat (IRC)"
msgstr ""

#: ../../source/common/communication.rst:13
msgid ""
"While working with OpenStack, IRC is the best way to get real time help or "
"support others. Details of how to get on IRC, channel lists, how meetings "
"are run, where to find logs, and our IRC bots are described in :ref:`setup-"
"irc`."
msgstr ""

#: ../../source/common/communication.rst:19
msgid ""
"Depending on what time zone you are based in there might be more traffic on "
"some channels than others. Have a little patience when waiting for people to "
"respond."
msgstr ""

#: ../../source/common/communication.rst:24
msgid "Wiki Pages"
msgstr ""

#: ../../source/common/communication.rst:26
msgid ""
"Each project and working group has its own `wiki page <https://wiki."
"openstack.org/wiki/Main_Page>`__. Wiki pages are a secondary source of "
"information. They hold information that is subject to more change than the "
"info provided in the project's documentation i.e. meeting agendas, team "
"members, etc."
msgstr ""

#: ../../source/common/communication.rst:33
msgid "Etherpads and Ethercalcs"
msgstr ""

#: ../../source/common/communication.rst:35
msgid ""
"Etherpad is a simple collaborative text editor. It is used as a common place "
"to have people in a project collaborate on larger projects and planning of "
"events. There is no master list of etherpads - it is harder to find what you "
"are looking for without having looked at it before or without asking for the "
"URL. It is recommended to bookmark the important etherpads for later "
"reference. The starting page of the OpenStack Etherpad is `this <https://"
"etherpad.openstack.org>`_."
msgstr ""

#: ../../source/common/communication.rst:43
msgid ""
"Ethercalc is a simple collaborative spreadsheet. It works in a similar way "
"as Etherpad, but it is more useful to facilitate distributed booking or "
"scheduling of resources. The starting page of OpenStack Ethercalc is `here "
"<https://ethercalc.openstack.org/>`_."
msgstr ""

#: ../../source/common/communication.rst:51
msgid "Mailing Lists (ML)"
msgstr ""

#: ../../source/common/communication.rst:53
msgid ""
"There are more than 40 different ML's. These are listed in the `mailman page "
"<http://lists.openstack.org/cgi-bin/mailman/listinfo>`__. Mailing lists are "
"a way for people to communicate to a larger group than those that are on IRC."
" All emails on these lists are archived and available on the `Mailing Lists "
"<https://wiki.openstack.org/wiki/Mailing_Lists>`_ wiki. The same page "
"describes how to subscribe to a list and describes some popular lists."
msgstr ""

#: ../../source/common/events.rst:3
msgid "Events"
msgstr ""

#: ../../source/common/events.rst:6
msgid "OpenStack Events"
msgstr ""

#: ../../source/common/events.rst:8
msgid ""
"The Open Infrastructure Foundation organizes multiple events per year to "
"bring together the community as well as companies and individuals interested "
"in the technology and to embrace and encourage open collaboration."
msgstr ""

#: ../../source/common/events.rst:12 ../../source/common/governance.rst:10
#: ../../source/common/i18n.rst:11 ../../source/common/releases.rst:8
#: ../../source/common/task-tracking.rst:14
#: ../../source/common/zuul-status.rst:9
msgid "This section allows you to:"
msgstr ""

#: ../../source/common/events.rst:14
msgid ""
"Understand the differences between the different in-person OpenStack events"
msgstr ""

#: ../../source/common/events.rst:15
msgid "Know which events are valuable to you"
msgstr ""

#: ../../source/common/events.rst:20
msgid "Open Infrastructure Summit"
msgstr ""

#: ../../source/common/events.rst:22
msgid ""
"The `Summits <https://www.openstack.org/summit/>`_ are annual events with "
"thousands of attendees from all around the globe. The event occasions are "
"alternating somewhere between North America, Europe and Asia."
msgstr ""

#: ../../source/common/events.rst:26
msgid ""
"The event is designed to bring together users, operators and developers to "
"discuss feedback and future plans and you will also find a lot of options to "
"collaborate with representatives from adjacent communities."
msgstr ""

#: ../../source/common/events.rst:30
msgid ""
"To see how OpenStack and further Open Infrastructure Foundation projects are "
"utilized you will find exhibitors at the Market Place area."
msgstr ""

#: ../../source/common/events.rst:33
msgid ""
"The sessions are grouped into two major parts, the conference and the Forum."
msgstr ""

#: ../../source/common/events.rst:36
msgid "Conference"
msgstr ""

#: ../../source/common/events.rst:38
msgid ""
"The conference sessions consist of 40-minute-long presentations and panel "
"discussions organized into tracks, like 'Public Clouds', 'Containers', or "
"'Telecom/NFV'."
msgstr ""

#: ../../source/common/events.rst:42
msgid ""
"There is a Call For Papers (CFP) process before each Summit where anyone can "
"propose sessions for the upcoming event. After the CFP deadline the "
"proposals go through a community vote after which a group of track chairs "
"decide about the final content for each track."
msgstr ""

#: ../../source/common/events.rst:50
msgid "Forum"
msgstr ""

#: ../../source/common/events.rst:52
msgid ""
"The Forum sessions are also 40 minutes long, but the sessions are intended "
"to be working sessions as opposed to presentations."
msgstr ""

#: ../../source/common/events.rst:55
msgid ""
"The purpose of the Forum is to provide space for the developer and user "
"community to get together and discuss feedback and find solutions to "
"problems and new challenges and requirements."
msgstr ""

#: ../../source/common/events.rst:59
msgid ""
"The Forum sessions are proposed by the community through a proposal period "
"and the final sessions are selected by a committee."
msgstr ""

#: ../../source/common/events.rst:62
msgid ""
"You can find both the conference and Forum sessions on the Summit schedule."
msgstr ""

#: ../../source/common/events.rst:65
msgid "Project Teams Gathering (PTG)"
msgstr ""

#: ../../source/common/events.rst:67
msgid ""
"This event is created to provide space and time for developers and operators "
"to get together and have detailed technical discussions."
msgstr ""

#: ../../source/common/events.rst:70
msgid ""
"The `PTG <https://www.openstack.org/ptg/>`_ sessions are organized into "
"parallel tracks. The time is divided between Working Groups, SIGs, cross-"
"project and project team sessions and further sessions dedicated to "
"operations related discussions."
msgstr ""

#: ../../source/common/events.rst:75
msgid ""
"PTGs are scheduled at the beginning of each release cycle which makes it "
"possible to do more thorough release planning and ensure that the more "
"complicated proposals are discussed with all the affected teams."
msgstr ""

#: ../../source/common/events.rst:79
msgid ""
"This event is recommended to developers, operators and end users who are "
"already involved in community activities. If you are a new comer you might "
"want to consider one of the OpenStack Summits first where you can find "
"several sessions to help you find your way within the community."
msgstr ""

#: ../../source/common/events.rst:85
msgid "Community-organized Events"
msgstr ""

#: ../../source/common/events.rst:87
msgid ""
"There are community organized events all year all around the globe. Be sure "
"you `check <https://www.openstack.org/community/events/>`_ when the next one "
"is in your area!"
msgstr ""

#: ../../source/common/events.rst:92
msgid "OpenStack/OpenInfra Days"
msgstr ""

#: ../../source/common/events.rst:94
msgid ""
"`OpenStack Days <https://www.openstack.org/community/events/openstackdays>`_ "
"events are similar to the Open Infrastructure Summits that are organized by "
"the local community, users groups and companies."
msgstr ""

#: ../../source/common/events.rst:98
msgid ""
"The events are one or two days long and filled with mainly presentations and "
"panel discussions about the latest hot topics in the community's life. It "
"gives you a great opportunity to meet the local community and find people "
"who are interested in the same challenges and technology as you are. "
"Connecting with people in the same region where you are gives you the "
"advantage to be able to reach out easier to them later as they are in the "
"same time zone, maybe even in the same city."
msgstr ""

#: ../../source/common/events.rst:106
msgid ""
"In some cases there are training sessions and workshops as well and you may "
"see the `OpenStack Upstream Institute <https://docs.openstack.org/upstream-"
"training/>`_ training on the agenda as well."
msgstr ""

#: ../../source/common/events.rst:111
msgid ""
"OpenInfra Days are essentially the same in format and benefit to attendees, "
"but are broader in scope. OpenInfra Days are focused on being more open and "
"welcoming of adjacent infrastructure technologies."
msgstr ""

#: ../../source/common/events.rst:116
msgid "Meet-ups"
msgstr ""

#: ../../source/common/events.rst:118
msgid ""
"Meet-ups are organized by local user groups with different cadences. They "
"are a few hours long with a few presentations, discussion topics and some "
"snacks."
msgstr ""

#: ../../source/common/events.rst:121
msgid ""
"Look for `meetups in your area <http://meetup.com/pro/osf>`_  and if you "
"cannot find one you are welcome to organize one yourself!"
msgstr ""

#: ../../source/common/events.rst:125
msgid "Operators Meetup"
msgstr ""

#: ../../source/common/events.rst:127
msgid ""
"Aside from the Forum, the other operator focused event is the operator "
"meetup. You can read general information about it here :ref:`ops-meetup`. "
"It's organized by the operator community biannually in locations all over "
"the world."
msgstr ""

#: ../../source/common/git.rst:5
msgid "Setup and Learn GIT"
msgstr ""

#: ../../source/common/git.rst:9 ../../source/common/task-tracking.rst:12
msgid "This section assumes you have completed :doc:`accounts` guide."
msgstr ""

#: ../../source/common/git.rst:12
msgid "GIT"
msgstr ""

#: ../../source/common/git.rst:15
msgid "What is Git?"
msgstr ""

#: ../../source/common/git.rst:17
msgid ""
"Git is a free and open source distributed version control system that the "
"OpenStack community uses to manage changes to source code and documentation."
msgstr ""

#: ../../source/common/git.rst:20
msgid "Git allows you to:"
msgstr ""

#: ../../source/common/git.rst:22
msgid ""
"Push and test `code, docs, infrastructure changes, and CI configurations "
"<https://opendev.org/explore/repos>`_"
msgstr ""

#: ../../source/common/git.rst:23
msgid "Push `Specifications <https://specs.openstack.org>`_"
msgstr ""

#: ../../source/common/git.rst:24
msgid ""
"Push `Use cases for features <https://specs.openstack.org/openstack/"
"openstack-user-stories/>`_"
msgstr ""

#: ../../source/common/git.rst:28 ../../source/common/setup-gerrit.rst:249
msgid "Installation"
msgstr ""

#: ../../source/common/git.rst:31 ../../source/common/setup-gerrit.rst:252
msgid "Mac OS"
msgstr ""

#: ../../source/common/git.rst:33
msgid ""
"Go to the Git `download page <https://git-scm.com/downloads>`_ and click "
"**Mac OS X**."
msgstr ""

#: ../../source/common/git.rst:36
msgid ""
"The downloaded file should be a dmg in your downloads folder. Open that dmg "
"file and follow the instructions on screen."
msgstr ""

#: ../../source/common/git.rst:39
msgid ""
"If you use the package manager `Homebrew <http://brew.sh>`_, open a terminal "
"and type::"
msgstr ""

#: ../../source/common/git.rst:45 ../../source/common/setup-gerrit.rst:278
msgid "Linux"
msgstr ""

#: ../../source/common/git.rst:47 ../../source/common/setup-gerrit.rst:280
msgid ""
"For distributions like Debian, Ubuntu, or Mint open a terminal and type::"
msgstr ""

#: ../../source/common/git.rst:51 ../../source/common/setup-gerrit.rst:284
msgid ""
"For distributions like RedHat, Fedora or CentOS open a terminal and type::"
msgstr ""

#: ../../source/common/git.rst:56 ../../source/common/setup-gerrit.rst:289
msgid "For SUSE distributions open a terminal and type::"
msgstr ""

#: ../../source/common/git.rst:61
msgid "Windows"
msgstr ""

#: ../../source/common/git.rst:63
msgid ""
"`Windows Subsystem for Linux (WSL) <https://docs.microsoft.com/en-us/windows/"
"wsl/about>`_ is available in Windows 10 Anniversary Update or later (build "
"1607+). There is the possibility to install and run modern Linux Operating "
"Systems:"
msgstr ""

#: ../../source/common/git.rst:67
msgid ""
"`Ubuntu 16.04 <https://www.microsoft.com/en-us/store/p/ubuntu/"
"9nblggh4msv6>`_"
msgstr ""

#: ../../source/common/git.rst:68
msgid ""
"`openSUSE Leap 42 <https://www.microsoft.com/en-us/store/p/opensuse-leap-42/"
"9njvjts82tjx>`_"
msgstr ""

#: ../../source/common/git.rst:69
msgid ""
"`SLES 12 <https://www.microsoft.com/en-us/store/p/suse-linux-enterprise-"
"server-12/9p32mwbh6cns>`_"
msgstr ""

#: ../../source/common/git.rst:71
msgid "All common tools like bash, git, and SSH will work out of the box."
msgstr ""

#: ../../source/common/git.rst:73
msgid ""
"Although Git `download page <https://git-scm.com/downloads>`_ provides "
"Windows installation binary, most OpenStack development tools (e.g., git-"
"review) unfortunately will not work well on Windows environment."
msgstr ""

#: ../../source/common/git.rst:78
msgid "Configure Git"
msgstr ""

#: ../../source/common/git.rst:80
msgid ""
"Once you have Git installed you need to configure it. Open your terminal "
"application and issue the following commands putting in your first/last name "
"and email address. This is how your contributions will be identified::"
msgstr ""

#: ../../source/common/git.rst:89
msgid "Use the same email address that was used during the account setup."
msgstr ""

#: ../../source/common/git.rst:92
msgid "Learning Git"
msgstr ""

#: ../../source/common/git.rst:94
msgid ""
"You can use `Git Immersion <https://gitimmersion.com/index.html>`_ to work "
"through tutorials for learning git."
msgstr ""

#: ../../source/common/git.rst:97
msgid ""
"For reference, use the `Git Reference and Cheat Sheet <https://git-scm.com/"
"doc>`_."
msgstr ""

#: ../../source/common/git.rst:100
msgid "Commit Messages"
msgstr ""

#: ../../source/common/git.rst:102
msgid ""
"Commit messsages are the first things a reviewer sees and are used as "
"descriptions in the git log. They provide a description of the history of "
"changes in a repository. Commit messages cannot be modified once the patch "
"is merged."
msgstr ""

#: ../../source/common/git.rst:107
msgid "Format:"
msgstr ""

#: ../../source/common/git.rst:109 ../../source/common/git.rst:120
msgid "Summary Line"
msgstr ""

#: ../../source/common/git.rst:110 ../../source/common/git.rst:112
msgid "Empty line"
msgstr ""

#: ../../source/common/git.rst:111 ../../source/common/git.rst:127
msgid "Body"
msgstr ""

#: ../../source/common/git.rst:113 ../../source/common/git.rst:139
msgid "Footers"
msgstr ""

#: ../../source/common/git.rst:117
msgid ""
"Footers should be entered one per line with no empty lines between them."
msgstr ""

#: ../../source/common/git.rst:122
msgid ""
"The summary line briefly describes the patch content. The character limit is "
"50 characters. The summary line should not end with a period. If the change "
"is not finished at the time of the commit, start the commit message with WIP."
""
msgstr ""

#: ../../source/common/git.rst:129
msgid ""
"The body contains the explanation of the issue being solved and why it "
"should be fixed, the description of the solution, and additional optional "
"information on how it improves the code structure, or references to other "
"relevant patches, for example. The lines are limited to 72 characters. The "
"body should contain all the important information related to the problem, "
"without assuming that the reader understands the source of the problem or "
"has access to external sites."
msgstr ""

#: ../../source/common/git.rst:141
msgid ""
"Footers are lines in the final paragraph of a commit message, used to link "
"the change to other tools."
msgstr ""

#: ../../source/common/git.rst:144
msgid "The following footer is required:"
msgstr ""

#: ../../source/common/git.rst:146
msgid ""
"The ``Change-Id`` line is a unique hash describing the change, which is "
"generated automatically by a Git commit hook when you initially save a "
"commit message. This should not be changed when rebasing a commit following "
"review feedback, since it is used by Gerrit, to track versions of a patch. "
"It won't appear when you're editing a new commit message for the first time, "
"but if you ``commit --amend`` later you will see it."
msgstr ""

#: ../../source/common/git.rst:153
msgid "StoryBoard specific footers:"
msgstr ""

#: ../../source/common/git.rst:155
msgid ""
"``Task: 1234``: the number of the task in Storyboard implemented by the "
"change. This will auto update the task to 'Review' status and assign it to "
"you when you push the patch."
msgstr ""

#: ../../source/common/git.rst:158
msgid ""
"``Story: 1234567``: the number of the story in Storyboard to which the task "
"being implemented belongs. This will post a comment on the story with a link "
"to your patch."
msgstr ""

#: ../../source/common/git.rst:162
msgid "Launchpad specific footers:"
msgstr ""

#: ../../source/common/git.rst:164
msgid ""
"``Closes-Bug: #123456789``: use ``Closes-Bug`` if the commit is intended to "
"fully fix and close the bug being referenced. Use the Launchpad ID of the "
"bug for the number; Gerrit automatically creates a link to the bug."
msgstr ""

#: ../../source/common/git.rst:167
msgid ""
"``Partial-Bug: #123456789``: use ``Partial-Bug`` if the commit is only a "
"partial fix and more work is needed. Use the Launchpad ID of the bug for the "
"number; Gerrit automatically creates a link to the bug."
msgstr ""

#: ../../source/common/git.rst:170
msgid ""
"``Related-Bug: #12456789``: use ``Related-Bug`` if the commit is merely "
"related to the referenced bug. Use the Launchpad ID of the bug for the "
"number; Gerrit automatically creates a link to the bug."
msgstr ""

#: ../../source/common/git.rst:173
msgid ""
"``Partial-Implements``: Use this footer if the change partially implements a "
"Launchpad blueprint. Use the name of the blueprint as an ID."
msgstr ""

#: ../../source/common/git.rst:175
msgid ""
"``Implements``: Use this footer if the change fully implements a Launchpad "
"blueprint. Use the name of the blueprint as an ID."
msgstr ""

#: ../../source/common/git.rst:178
msgid ""
"The following footers are optional; however, their use is recommended if "
"they are applicable to the patch:"
msgstr ""

#: ../../source/common/git.rst:181
msgid ""
"The ``DocImpact`` footer contains a comment about why the change impacts "
"documentation. Put DocImpact on a line by itself. Use this footer to "
"indicate that documentation is either contained in the patch or has "
"documentation impact. When this footer is included in a commit message, "
"Gerrit creates a bug for the project affected by the change for task "
"tracking, or move to the openstack-api-site as needed."
msgstr ""

#: ../../source/common/git.rst:188
msgid ""
"The ``APIImpact`` footer contains a comment about why the change impacts a "
"public HTTP API. Put APIImpact on a line by itself. Use this footer to "
"indicate that the patch impacts a public HTTP API. When this footer is "
"included in a commit message, the API_Working_Group can use it to help find "
"relevant reviews."
msgstr ""

#: ../../source/common/git.rst:193
msgid ""
"The ``SecurityImpact`` footer is used to indicate that a change has security "
"implications and should be reviewed by the OpenStack Security Group."
msgstr ""

#: ../../source/common/git.rst:195
msgid ""
"The ``UpgradeImpact`` footer contains a comment about why the change impacts "
"upgrades. It is used to indicate that a change has upgrade implications for "
"those doing continuous deployment or N to N+1 upgrades. Also consider "
"updating the 'Upgrade Notes' section in the release notes for the affected "
"project."
msgstr ""

#: ../../source/common/git.rst:200
msgid ""
"The ``Depends-On``: <gerrit-change-url> footer is used to refer to a change "
"the current one depends on. Use the permalink of the change."
msgstr ""

#: ../../source/common/governance.rst:3
msgid "OpenStack Governance"
msgstr ""

#: ../../source/common/governance.rst:5
msgid ""
"The OpenStack community has a few different groups and roles for `governance "
"<https://governance.openstack.org/>`_, leadership, and community "
"participation. Each operates in a different sector of the community but "
"being aware of each of them is useful."
msgstr ""

#: ../../source/common/governance.rst:12
msgid "Understand the governance model of OpenStack"
msgstr ""

#: ../../source/common/governance.rst:13
msgid ""
"Know how to participate in groups that interest you and influence the future "
"of OpenStack"
msgstr ""

#: ../../source/common/governance.rst:17
msgid "Committees"
msgstr ""

#: ../../source/common/governance.rst:20
msgid "Foundation Board of Directors"
msgstr ""

#: ../../source/common/governance.rst:22
msgid ""
"The Open Infrastructure Foundation is a non-profit \"whose purpose is to "
"develop, support, protect, and promote\" OpenStack. It has a set of `bylaws "
"<https://www.openstack.org/legal/bylaws-of-the-openstack-foundation/>`_ and "
"a board of directors. The Foundation has three types of members, defined by "
"the bylaws. Each of the types -- Platinum, Gold and Individual -- are "
"represented on a Board of Directors. The maximum numbers of members of each "
"type are eight, twenty four, and unlimited, respectively."
msgstr ""

#: ../../source/common/governance.rst:30
msgid ""
"Individual members of the foundation vote once a year (usually near the "
"start of the calendar year) for the individual directors. Individuals who "
"wish to join the Foundation can learn more at :ref:`foundation account`."
msgstr ""

#: ../../source/common/governance.rst:35
msgid "Technical Committee"
msgstr ""

#: ../../source/common/governance.rst:37
msgid ""
"The `OpenStack Technical Committee <https://governance.openstack.org/tc/>`_ "
"(TC) provides governance and technical oversight of the open development of "
"OpenStack. They validate projects applying to be part of the official "
"OpenStack project and provide an ultimate appeals board for technical "
"decisions. The `Technical Committee Charter <https://governance.openstack."
"org/tc/reference/charter.html>`_ describes the TC in more detail."
msgstr ""

#: ../../source/common/governance.rst:45
msgid ""
"The 13 Members of the TC are elected for one year terms, six at one "
"election, seven at another election six months later. They are elected by :"
"ref:`Active Technical Contributors <atc>`."
msgstr ""

#: ../../source/common/governance.rst:50
msgid "User Committee"
msgstr ""

#: ../../source/common/governance.rst:52
msgid ""
"The `OpenStack User Committee <https://governance.openstack.org/uc/>`_ (UC) "
"serves the users of OpenStack, representing them to the rest of the "
"OpenStack community. The `User Committee Charter <https://governance."
"openstack.org/uc/reference/charter.html>`_ describes the UC in more detail."
msgstr ""

#: ../../source/common/governance.rst:58
msgid ""
"The 5 members of the UC are elected to one year terms, three at one "
"election, two at another election six months later. They are elected by :ref:"
"`Active User Contributors <auc>`."
msgstr ""

#: ../../source/common/governance.rst:63
msgid "Official OpenStack projects"
msgstr ""

#: ../../source/common/governance.rst:65
msgid ""
"Official OpenStack projects are the projects under the governance of the "
"Technical Commitee. Official OpenStack projects are listed in the `OpenStack "
"Project Teams page <https://governance.openstack.org/tc/reference/projects/"
"index.html>`_. Most well-known official OpenStack projects are listed in the "
"`project navigator <https://www.openstack.org/software/project-navigator>`_. "
"It is not mandatory for a project to become an official OpenStack project."
msgstr ""

#: ../../source/common/governance.rst:73
msgid ""
"Requirements for the official OpenStack projects are listed `in the wiki of "
"the Technical Commitee <https://governance.openstack.org/tc/reference/new-"
"projects-requirements.html>`_."
msgstr ""

#: ../../source/common/governance.rst:77
msgid "Benefits for official OpenStack projects:"
msgstr ""

#: ../../source/common/governance.rst:79
msgid "Contributors get to vote in the Technical Committee election"
msgstr ""

#: ../../source/common/governance.rst:80
msgid ""
"Can publish to `docs.openstack.org <https://docs.openstack.org/>`_ and "
"`developer.openstack.org <https://developer.openstack.org/>`_"
msgstr ""

#: ../../source/common/governance.rst:82
msgid ""
"The teams get space at `Open Infrastructure Summits <https://www.openstack."
"org/summit/>`_ and `Project Team Gatherings (PTG) <https://www.openstack.org/"
"ptg/>`_"
msgstr ""

#: ../../source/common/governance.rst:85
msgid "Get marketing from the Open Infrastructure Foundation"
msgstr ""

#: ../../source/common/governance.rst:86
msgid ""
"Can participate in common programs, like `mentoring <https://wiki.openstack."
"org/wiki/Mentors>`_ and `internship <https://wiki.openstack.org/wiki/"
"Outreachy>`_ to help with on boarding"
msgstr ""

#: ../../source/common/governance.rst:89
msgid "Get guidance from community members and leaders"
msgstr ""

#: ../../source/common/governance.rst:90
msgid "Its activities are under the oversight of the Technical Committee"
msgstr ""

#: ../../source/common/governance.rst:92
msgid ""
"To propose a project to be an official OpenStack project the project's "
"information should be added to the *reference/projects.yaml* file of the "
"*openstack/governance* repository. Anyone can propose changes to the file."
msgstr ""

#: ../../source/common/governance.rst:97
#: ../../source/common/introduction.rst:74
msgid "Groups"
msgstr ""

#: ../../source/common/governance.rst:100
msgid ""
"You can reference `Comparison of Official Group Structures page <https://"
"governance.openstack.org/tc/reference/comparison-of-official-group-"
"structures.html>`_ to see the difference between group structures."
msgstr ""

#: ../../source/common/governance.rst:107
msgid "Special Interest Groups"
msgstr ""

#: ../../source/common/governance.rst:109
msgid ""
"OpenStack `Special Interest Groups <https://governance.openstack.org/sigs/"
">`_ are working groups that operate within the entire OpenStack community to "
"address interests and concerns of all participants with a shared interest."
msgstr ""

#: ../../source/common/governance.rst:114
msgid "Roles"
msgstr ""

#: ../../source/common/governance.rst:119
msgid "Active Technical Contributor (ATC)"
msgstr ""

#: ../../source/common/governance.rst:121
msgid ""
"Individual Members of the Foundation who have contributed to any of the "
"official OpenStack project repositories over the last two 6-month release "
"cycles are automatically considered as ATCs."
msgstr ""

#: ../../source/common/governance.rst:125
msgid ""
"In specific cases you can apply for an exception to become an ATC, for "
"further information please see the `relevant section of the Technical "
"Committee Charter <https://governance.openstack.org/tc/reference/charter."
"html#voters-for-tc-seats-atc>`_."
msgstr ""

#: ../../source/common/governance.rst:130
msgid "Active Project Contributor (APC)"
msgstr ""

#: ../../source/common/governance.rst:132
msgid ""
"If you have the ATC status, in the official OpenStack project where you "
"contributed over the last two 6-month release cycles you are considered to "
"be an Active Project Contributor."
msgstr ""

#: ../../source/common/governance.rst:136
msgid ""
"Only APCs can participate in the election process to vote for the next PTL "
"of the team."
msgstr ""

#: ../../source/common/governance.rst:140
msgid "Project Team Lead (PTL)"
msgstr ""

#: ../../source/common/governance.rst:142
msgid ""
"Official project teams within OpenStack have a `Project Team Lead <https://"
"governance.openstack.org/tc/reference/charter.html#project-team-leads>`_. "
"These individuals coordinate the day to day operation of the project, "
"resolve technical disputes within the project, and operate as the "
"spokesperson and ambassador for the project."
msgstr ""

#: ../../source/common/governance.rst:148
msgid ""
"Project Team Leads are `elected <https://governance.openstack.org/tc/"
"reference/charter.html#election-for-ptl-seats>`_ for each release cycle by "
"Active Project Contributors: individuals who have contributed to the project "
"in the last two release cycles."
msgstr ""

#: ../../source/common/governance.rst:154
msgid "Core Reviewer"
msgstr ""

#: ../../source/common/governance.rst:156
msgid ""
"Official OpenStack projects have a project team consisting of core reviewers "
"and contributors."
msgstr ""

#: ../../source/common/governance.rst:159
msgid "Core reviewers are responsible for:"
msgstr ""

#: ../../source/common/governance.rst:161
msgid "Defining and maintaining the project mission"
msgstr ""

#: ../../source/common/governance.rst:162
msgid "Reviewing bug reports and deciding about their priority"
msgstr ""

#: ../../source/common/governance.rst:163
msgid ""
"Reviewing changes and approving them when it meets the design and coding or "
"documentation standards of the project"
msgstr ""

#: ../../source/common/governance.rst:166
msgid ""
"Core reviewers have '+/-2' and 'W+1' rights in Gerrit that is required for "
"blocking or approving a patch."
msgstr ""

#: ../../source/common/governance.rst:169
msgid ""
"New core reviewers are nominated by someone from the existing team on the "
"Discuss Mailing List and/or in Gerrit and elected by voting from the members "
"of the core team of the project."
msgstr ""

#: ../../source/common/governance.rst:176
msgid "Active User Contributor (AUC)"
msgstr ""

#: ../../source/common/governance.rst:178
msgid ""
"The user community is crucial for OpenStack and their participation is "
"highly encouraged."
msgstr ""

#: ../../source/common/governance.rst:182
msgid ""
"Community members who have engaged in community functions listed in the "
"`related section of the User Committee Charter <https://governance.openstack."
"org/uc/reference/charter.html#active-user-contributors-auc>`_ are considered "
"to be Active User Contributors."
msgstr ""

#: ../../source/common/governance.rst:187
msgid "The User Committee chairs are elected from and by the group of AUCs."
msgstr ""

#: ../../source/common/i18n.rst:3
msgid "Contribute as a Translator"
msgstr ""

#: ../../source/common/i18n.rst:5
msgid ""
"If English is not your native language, you may wish to contribute as a "
"translator. All services and documents that are visible to the user are "
"translated by the I18n team. It does not matter which language you speak. We "
"already have a lot of language teams who are very active. Our claim is more "
"diversity, to support us in our work at I18n."
msgstr ""

#: ../../source/common/i18n.rst:13
msgid "Help translate OpenStack, making it more available for users worldwide"
msgstr ""

#: ../../source/common/i18n.rst:16
msgid "Translation Platform"
msgstr ""

#: ../../source/common/i18n.rst:18
msgid ""
"We use `Zanata <http://zanata.org/>`_ as the platform for translating "
"strings in software projects and documentation. Zanata provides web user "
"interfaces: you only need a web browser to start your translation "
"contribution. Our translation platform is reachable on `translate.openstack."
"org <https://translate.openstack.org/>`_"
msgstr ""

#: ../../source/common/i18n.rst:28
msgid "Zanata Usage"
msgstr ""

#: ../../source/common/i18n.rst:30
msgid ""
"For registration and login you need an :doc:`Open Infrastructure Foundation "
"Account <accounts>`. Click on *LogIn* on `translate.openstack.org <https://"
"translate.openstack.org/>`_ and follow the process for applying your Zanata "
"profile."
msgstr ""

#: ../../source/common/i18n.rst:38
msgid "Once registered, you can join a language team."
msgstr ""

#: ../../source/common/i18n.rst:43
msgid ""
"Your membership application must be confirmed by the language coordinator. "
"This may take some time. An e-mail with your request will be sent "
"automatically."
msgstr ""

#: ../../source/common/i18n.rst:47
msgid ""
"Choose a project where you want to contribute with translating. Usually "
"there is a translation plan with priorities on the start page."
msgstr ""

#: ../../source/common/i18n.rst:53
msgid ""
"This is the view of the Zanata workspace. On the left side you have the "
"original text string, while you can enter the translation on the right."
msgstr ""

#: ../../source/common/i18n.rst:57
msgid "Reference"
msgstr ""

#: ../../source/common/i18n.rst:59
msgid ""
"For more information please visit the `OpenStack I18n Guide <https://docs."
"openstack.org/i18n/latest/index.html>`_. This guide is also translatable."
msgstr ""

#: ../../source/common/introduction.rst:3
msgid "Introduction"
msgstr ""

#: ../../source/common/introduction.rst:6
msgid "What is OpenStack?"
msgstr ""

#: ../../source/common/introduction.rst:9
msgid "Software"
msgstr ""

#: ../../source/common/introduction.rst:11
msgid ""
"OpenStack is a software package that provides a cloud platform for Public "
"and Private cloud covering various use cases including Enterprise and "
"Telecom. The main focus is on Infrastructure as a Service (IaaS) cloud and "
"additional services built upon IaaS. The Technical Committee maintains an "
"evolving `vision for OpenStack clouds <https://governance.openstack.org/tc/"
"reference/technical-vision.html>`_ describing the overall design scope for "
"an OpenStack cloud and the principles of cloud platforms in general, and "
"OpenStack in particular, that each service within OpenStack is expected to "
"follow."
msgstr ""

#: ../../source/common/introduction.rst:22
msgid ""
"As a software, OpenStack is built from a set of microservices which can be "
"combined into different setups based on the actual need. The services "
"provide REST APIs for their users. These can be the cloud operators or other "
"services. To make the usage of the APIs easier it is possible to use "
"Software Development Kits (SDKs) which are also developed as projects inside "
"the OpenStack community."
msgstr ""

#: ../../source/common/introduction.rst:29
msgid ""
"Documentation is very important for the community so you can find guidelines "
"about how to install and use the services developed by the project teams on "
"the `documentation website for OpenStack <https://docs.openstack.org>`_."
msgstr ""

#: ../../source/common/introduction.rst:33
msgid ""
"The services developed by the community are available as tarballs to install "
"them from source and are also picked up and packaged to make it available "
"for different Linux distributions or as part of OpenStack distributions."
msgstr ""

#: ../../source/common/introduction.rst:38
msgid "Map of OpenStack projects"
msgstr ""

#: ../../source/common/introduction.rst:44
msgid "Community"
msgstr ""

#: ../../source/common/introduction.rst:46
msgid "OpenStack is a community working towards one mission:"
msgstr ""

#: ../../source/common/introduction.rst:48
msgid ""
"To produce a ubiquitous Open Source Cloud Computing platform that **is** "
"easy to use, simple to implement, interoperable between deployments, works "
"well at **all** scales, **and** meets the needs of users and operators of "
"both public **and** private clouds."
msgstr ""

#: ../../source/common/introduction.rst:53
msgid ""
"OpenStack provides an ecosystem for collaboration. It has infrastructure for"
msgstr ""

#: ../../source/common/introduction.rst:55
msgid "Code review"
msgstr ""

#: ../../source/common/introduction.rst:56
msgid "Testing"
msgstr ""

#: ../../source/common/introduction.rst:57
msgid "CI"
msgstr ""

#: ../../source/common/introduction.rst:58
msgid "Version control"
msgstr ""

#: ../../source/common/introduction.rst:59
msgid "Documentation"
msgstr ""

#: ../../source/common/introduction.rst:60
msgid ""
"a set of collaboration tools, like a wiki, IRC chanels, Etherpad and "
"Ethercalc."
msgstr ""

#: ../../source/common/introduction.rst:64
msgid "The four opens"
msgstr ""

#: ../../source/common/introduction.rst:66
msgid "The basic princinples of the OpenStack community are the four opens."
msgstr ""

#: ../../source/common/introduction.rst:68
msgid ""
"`Open source <https://governance.openstack.org/tc/reference/opens.html#open-"
"source>`_"
msgstr ""

#: ../../source/common/introduction.rst:69
msgid ""
"`Open design <https://governance.openstack.org/tc/reference/opens.html#open-"
"design>`_"
msgstr ""

#: ../../source/common/introduction.rst:70
msgid ""
"`Open development <https://governance.openstack.org/tc/reference/opens."
"html#open-development>`_"
msgstr ""

#: ../../source/common/introduction.rst:71
msgid ""
"`Open Community <https://governance.openstack.org/tc/reference/opens."
"html#open-community>`_"
msgstr ""

#: ../../source/common/introduction.rst:76
msgid ""
"There are lots of people working on OpenStack organized into different "
"groups. These are described in the :ref:`special-interest-groups` section of "
"the Governance chapter."
msgstr ""

#: ../../source/common/introduction.rst:81
msgid "What is a contribution?"
msgstr ""

#: ../../source/common/introduction.rst:83
msgid ""
"In open source projects a contribution can be anything which helps the "
"project to accomplish its mission. In addition to code contribution it can "
"be testing, documentation, requirements gathering, bug reporting and so "
"forth."
msgstr ""

#: ../../source/common/irc.rst:5
msgid "Setup IRC"
msgstr ""

#: ../../source/common/irc.rst:8
msgid "IRC"
msgstr ""

#: ../../source/common/irc.rst:11
msgid "What is IRC?"
msgstr ""

#: ../../source/common/irc.rst:13
msgid ""
"The OpenStack community uses `Internet Relay Chat (IRC) <https://en."
"wikipedia.org/wiki/IRC>`_, an open source protocol, as its primary chat "
"service."
msgstr ""

#: ../../source/common/irc.rst:16
msgid "IRC allows you to:"
msgstr ""

#: ../../source/common/irc.rst:18
msgid ""
"Communicate with project teams, the technical committee, SIGs, and other "
"Working Groups."
msgstr ""

#: ../../source/common/irc.rst:20
msgid "Participate in regular meetings with the above groups."
msgstr ""

#: ../../source/common/irc.rst:23
msgid "What IRC network we use"
msgstr ""

#: ../../source/common/irc.rst:25
msgid "The OpenStack Community is using the OFTC IRC network."
msgstr ""

#: ../../source/common/irc.rst:28
msgid "Set up IRC on Linux & Windows"
msgstr ""

#: ../../source/common/irc.rst:31
msgid "Install an IRC Program"
msgstr ""

#: ../../source/common/irc.rst:33
msgid ""
"This section explains how you can install an IRC program called Hexchat."
msgstr ""

#: ../../source/common/irc.rst:35
msgid ""
"For a Linux distributions like Debian, Ubuntu, or Mint open a terminal and "
"type::"
msgstr ""

#: ../../source/common/irc.rst:40
msgid ""
"For Linux distributions like Redhat, Fedora, or CentOS open a terminal and "
"type::"
msgstr ""

#: ../../source/common/irc.rst:45
msgid ""
"For a Windows environment, download the latest Hexchat installation binary "
"from `Hexchat download <https://hexchat.github.io/downloads.html>`__ and "
"install it."
msgstr ""

#: ../../source/common/irc.rst:49
msgid ""
"Now open the hexchat program just like you would for any Linux program."
msgstr ""

#: ../../source/common/irc.rst:53
msgid "Edit Nick Name Settings"
msgstr ""

#: ../../source/common/irc.rst:55
msgid ""
"Lets first fill out the **Nick name** and **User name** field with our "
"choice of a nickname:"
msgstr ""

#: ../../source/common/irc.rst:57
msgid "From the list of **Networks** you should select OFTC network."
msgstr ""

#: ../../source/common/irc.rst:59
msgid ""
"ircs://irc.oftc.net:6697 for SSL (alternative port: 9999), IPv4 and IPv6."
msgstr ""

#: ../../source/common/irc.rst:60
msgid ""
"irc://irc.oftc.net:6667 for non-SSL (alternative ports: 6668-6670, 7000), "
"IPv4 and IPv6."
msgstr ""

#: ../../source/common/irc.rst:65
msgid "Edit Server Settings"
msgstr ""

#: ../../source/common/irc.rst:67
msgid "Click the **edit** button and"
msgstr ""

#: ../../source/common/irc.rst:68
msgid ""
"Make sure that **Use SSL for all the servers on this network** is checked."
msgstr ""

#: ../../source/common/irc.rst:72
msgid "Troubleshooting"
msgstr ""

#: ../../source/common/irc.rst:74
msgid ""
"If you get a notice that the nick name is already taken, quit and go back to "
"the first set of steps to pick a different nickname."
msgstr ""

#: ../../source/common/irc.rst:78
msgid "Register Your Nick Name"
msgstr ""

#: ../../source/common/irc.rst:80
msgid ""
"If you don’t already have an account, you can register one with ``/msg "
"NickServ REGISTER <password> <e-mail>``. `The OFTC Guide <https://www.oftc."
"net/Services/#nickserv>`_ will guide you through the rest of the "
"registration process.  Make sure to follow the instructions and complete the "
"verification process."
msgstr ""

#: ../../source/common/irc.rst:86
msgid ""
"When you login to the server for the first time with your nickname, it will "
"be used by you, but it's still not registered yet."
msgstr ""

#: ../../source/common/irc.rst:89
msgid ""
"In order to register you need to send a message to nickserv on OFTC, which "
"is a bot that allows you to register and identify yourselves as the owner of "
"a nick name."
msgstr ""

#: ../../source/common/irc.rst:93
msgid ""
"If all goes well you should receive a message back instantly that the nick "
"name is registered by you and an activation email will be sent to the email "
"address you provided."
msgstr ""

#: ../../source/common/irc.rst:98
msgid "Auto-Login On Connecting To OFTC"
msgstr ""

#: ../../source/common/irc.rst:100
msgid ""
"In order to identify yourselves that you own the nick name upon logging in, "
"you need to tell Hexchat to communicate your password upon connecting."
msgstr ""

#: ../../source/common/irc.rst:104
msgid ""
"Click **Hexchat** from the menu and then click **Network List**. You will "
"see a familiar first screen of servers listed. Make sure OFTC is highlighted "
"and click **edit**."
msgstr ""

#: ../../source/common/irc.rst:107
msgid ""
"In the **Password** put in the password you picked in the previous step and "
"click close."
msgstr ""

#: ../../source/common/irc.rst:111
msgid ""
"In case of more question about OFTC, read `these FAQs <https://www.oftc.net/"
"FAQ/Services/>`_"
msgstr ""

#: ../../source/common/irc.rst:115
msgid "Done"
msgstr ""

#: ../../source/common/irc.rst:117
msgid ""
"Congratulations you're now ready to communicate with the OpenStack community "
"and have a registered nick name on OFTC! From here on out when you connect "
"to OFTC with Hexchat you will be identified with your nickname."
msgstr ""

#: ../../source/common/irc.rst:121
msgid ""
"A good channel to join right away is the ``#openstack-dev`` channel. A lot "
"of people hang around in that channel so come on in and say hello! If there "
"is a specific project you are also interested in working on, feel free to "
"join that one as well and introduce yourself there. Interested in joining "
"more channels or need to look up what one is called? Check out :ref:`irc-"
"channels` for more information."
msgstr ""

#: ../../source/common/irc.rst:128
msgid ""
"It's also important to note that contributors are located all over the world "
"across different time zones, so channels may be quieter outside of their "
"work hours. Be patient when asking questions, and it might be a while before "
"someone responds. Additionally, keep in mind that IRC does not natively "
"support a message backlog, so you may miss messages sent while you were "
"disconnected. Many contributors keep a persistent IRC session to avoid "
"missing important communications, and :ref:`irc-archives` can be helpful for "
"catching up on missed messages."
msgstr ""

#: ../../source/common/irc.rst:138
msgid "Set up IRC on Mac OS"
msgstr ""

#: ../../source/common/irc.rst:140
msgid ""
"`#irchelp <https://www.irchelp.org/clients/mac/>`__ describes available IRC "
"client programs for Mac OS environment. `LimeChat <https://github.com/psychs/"
"limechat>`__ provides an installation binary for you to download, install, "
"and configure to connect to OFTC."
msgstr ""

#: ../../source/common/irc.rst:146
msgid "IRC Chatting with Matrix"
msgstr ""

#: ../../source/common/irc.rst:148
msgid ""
"You can also use IRC chat with Matrix. The Zuul community described how to "
"use Matrix to bridge into OFTC IRC. If you want to use Matrix as a IRC "
"client, please follow this link:"
msgstr ""

#: ../../source/common/irc.rst:152
msgid "`<https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html>`__."
msgstr ""

#: ../../source/common/irc.rst:157
msgid "IRC Channels"
msgstr ""

#: ../../source/common/irc.rst:159
msgid ""
"Each project and working group has its own IRC channel. The common syntax "
"for naming the IRC channels is: ``#openstack-<name-of-project>``, but there "
"are some exceptions. See the contributor guide for each project for specific "
"information. If you fail to find a reference there, don't hesitate to ask in "
"the general ``#openstack-dev`` channel."
msgstr ""

#: ../../source/common/irc.rst:167
msgid "IRC Meetings"
msgstr ""

#: ../../source/common/irc.rst:169
msgid ""
"In OpenStack all the meetings are happening either on generic meeting "
"channels channels like #openstack-meeting, or on specific project channels. "
"Check the `list of meetings <https://meetings.opendev.org/#meetings>`__ for "
"meeting times, IRC channels, and archives of meetings."
msgstr ""

#: ../../source/common/irc.rst:177
msgid "IRC Archives"
msgstr ""

#: ../../source/common/irc.rst:179
msgid ""
"Most IRC channels are archived, you can read the logs on `IRC channel logs "
"<https://meetings.opendev.org/irclogs/>`__."
msgstr ""

#: ../../source/common/irc.rst:183
msgid "IRC bots"
msgstr ""

#: ../../source/common/irc.rst:185
msgid ""
"IRC allows different programs to listen to the IRC channels and do some "
"actions. These programs are called IRC bots. There are several bots used in "
"the OpenStack IRC channels, this section contains the ones which are useful "
"from the first days of OpenStack development. A more comprehensive list can "
"be found in the `OpenDev team IRC page <https://docs.opendev.org/opendev/"
"system-config/latest/irc.html>`__."
msgstr ""

#: ../../source/common/irc.rst:193
msgid "Thanksbot"
msgstr ""

#: ../../source/common/irc.rst:195
msgid ""
"This bot allows people to recognize each other and be thankful. Anyone can "
"post a message in the OpenStack IRC channels to say thanks. The way to say "
"thanks is:"
msgstr ""

#: ../../source/common/irc.rst:203
msgid ""
"The irc_nick is the IRC nick of the person who is receiving the thanks. The "
"message is a short text to explain the reason for the thanks. The bot "
"collects all thanks to a `wiki page <https://wiki.openstack.org/wiki/"
"Thanks>`__."
msgstr ""

#: ../../source/common/irc.rst:209
msgid "Statusbot"
msgstr ""

#: ../../source/common/irc.rst:211
msgid ""
"Statusbot is used to distribute urgent information from the OpenDev team to "
"OpenStack channels."
msgstr ""

#: ../../source/common/irc.rst:215
msgid "Successbot"
msgstr ""

#: ../../source/common/irc.rst:217
msgid ""
"Successbot is an IRC bot to express small successes in OpenStack development."
" To celebrate in the OpenStack IRC channel way just type:"
msgstr ""

#: ../../source/common/irc.rst:225
msgid ""
"to any OpenStack IRC channel where the Statusbot is listening. The message "
"will be posted to the `Successes wiki page <https://wiki.openstack.org/wiki/"
"Successes>`__."
msgstr ""

#: ../../source/common/mentoring.rst:5
msgid "Mentoring"
msgstr ""

#: ../../source/common/mentoring.rst:8
msgid "The Cohorts"
msgstr ""

#: ../../source/common/mentoring.rst:10
msgid "As it stands right now, there are 4 mentoring cohorts:"
msgstr ""

#: ../../source/common/mentoring.rst:12
msgid ""
"Get your first patch merged: Mentors will assist mentees with crafting a "
"change, understanding and adhering to the Developers Guide, submitting to "
"Gerrit, responding to reviews, and ultimately having their change accepted."
msgstr ""

#: ../../source/common/mentoring.rst:16
msgid ""
"First CFP submission or Give your first talk: Mentors will assist mentees "
"with submitting a CFP and  preparing to give a talk. This could be for "
"OpenStack Summit, OpenStack Days, a local meetup, or another conference or "
"event."
msgstr ""

#: ../../source/common/mentoring.rst:20
msgid ""
"Deploy your first Cloud: Mentors will provide assistance to mentees "
"deploying OpenStack for the first time. This could involve analysis of "
"available deployment tools, configuration, or troubleshooting."
msgstr ""

#: ../../source/common/mentoring.rst:23
msgid ""
"Become COA certified or study for COA: Mentors will provide support and "
"guidance to mentees as they prepare for the COA exam."
msgstr ""

#: ../../source/common/mentoring.rst:26
msgid ""
"If there is a topic you are interested in mentoring someone in, or being "
"mentored in, the organizers are always looking for new ideas! Please fill "
"out the form below that corresponds to your roll and let them know!"
msgstr ""

#: ../../source/common/mentoring.rst:31
msgid "Participating as a Mentor"
msgstr ""

#: ../../source/common/mentoring.rst:33
msgid ""
"The first thing you'll want to do is sign up using this `mentor form <https:/"
"/openstackfoundation.formstack.com/forms/mentoring_cohorts_mentors>`_. This "
"will get you into our spreadsheet of mentors so that we can keep track of "
"who is working with which group so when we need to help bolster certain "
"cohorts with calls for mentors, we can see who is already involved."
msgstr ""

#: ../../source/common/mentoring.rst:40
msgid "Participating as a Mentee"
msgstr ""

#: ../../source/common/mentoring.rst:42
msgid ""
"Similar to being a mentor, the first thing you'll want to do is sign up "
"using this `mentee form <https://openstackfoundation.formstack.com/forms/"
"mentoring_cohorts_menteess>`_. This will help us know who is participating "
"and what their goals are."
msgstr ""

#: ../../source/common/mentoring.rst:47
msgid "Join the Mailing List & IRC Channel"
msgstr ""

#: ../../source/common/mentoring.rst:51
msgid ""
"This section assumes you have completed the :doc: '/common/irc' section of "
"the contributor guide. It might also be helpful to cover the more generic "
"information about mailing lists in the Communication page's :ref:"
"`communication-mailing-lists` section as well."
msgstr ""

#: ../../source/common/mentoring.rst:57
msgid "Mentoring Mailing List"
msgstr ""

#: ../../source/common/mentoring.rst:59
msgid ""
"The mailing list is where most day to day asynchronous interactions happen. "
"Here is where you can get  `subscribed and view ML archives <http://lists."
"openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring>`_."
msgstr ""

#: ../../source/common/mentoring.rst:62
msgid ""
"When sending emails to the ML, if your subject is specific to one cohort, "
"please use the relevant tag:"
msgstr ""

#: ../../source/common/mentoring.rst:65
msgid "[first-patch] for getting your first patch merged"
msgstr ""

#: ../../source/common/mentoring.rst:66
msgid "[first-cfp] for giving your first conference talk"
msgstr ""

#: ../../source/common/mentoring.rst:67
msgid "[first-cloud] for deploying your first cloud"
msgstr ""

#: ../../source/common/mentoring.rst:68
msgid "[coa] for becoming a Certified OpenStack Administrator"
msgstr ""

#: ../../source/common/mentoring.rst:70
msgid ""
"**Both mentors and mentees should subscribe to stay up to date with "
"conversations.**"
msgstr ""

#: ../../source/common/mentoring.rst:74
msgid "#openstack-mentoring"
msgstr ""

#: ../../source/common/mentoring.rst:76
msgid ""
"On IRC, we also have a dedicated channel for the topics our cohorts focus on."
" Please join #openstack-mentoring whenever you are online to stay in the "
"loop and meet other people that have overlapping timezones- both mentors and "
"mentees."
msgstr ""

#: ../../source/common/mentoring.rst:82
msgid "General Information"
msgstr ""

#: ../../source/common/mentoring.rst:84
msgid ""
"The cohort program is hosted under the `Diversity and Inclusion Working "
"Group <https://wiki.openstack.org/wiki/Diversity>`_. For more information "
"about the cohort program, you can check out their `wiki <https://wiki."
"openstack.org/wiki/Mentoring#Long_Term_Mentoring>`_."
msgstr ""

#: ../../source/common/releases.rst:3
msgid "Releases"
msgstr ""

#: ../../source/common/releases.rst:5
msgid ""
"OpenStack has a 6-month long release cadence with different release models "
"that projects can choose to follow."
msgstr ""

#: ../../source/common/releases.rst:10
msgid ""
"Understand the different release models that OpenStack components follow"
msgstr ""

#: ../../source/common/releases.rst:11
msgid ""
"Know the structure of the different release models and how to work "
"effectively in those to influence the future of OpenStack"
msgstr ""

#: ../../source/common/releases.rst:15
msgid "Release Models"
msgstr ""

#: ../../source/common/releases.rst:17
msgid ""
"OpenStack consists of a large number of projects that form the main "
"components of an OpenStack cloud, from client libraries to lifecycle "
"management services. The different projects are different in nature which "
"implies different `release models <https://releases.openstack.org/reference/"
"release_models.html>`_ to follow."
msgstr ""

#: ../../source/common/releases.rst:23
msgid "The currently available options are the following:"
msgstr ""

#: ../../source/common/releases.rst:25
msgid ""
"`cycle-with-rc <https://releases.openstack.org/reference/release_models."
"html#cycle-with-rc>`_"
msgstr ""

#: ../../source/common/releases.rst:27
msgid ""
"`cycle-with-intermediary <https://releases.openstack.org/reference/"
"release_models.html#cycle-with-intermediary>`_"
msgstr ""

#: ../../source/common/releases.rst:29
msgid ""
"`cycle-trailing <https://releases.openstack.org/reference/release_models."
"html#cycle-trailing>`_"
msgstr ""

#: ../../source/common/releases.rst:31
msgid ""
"`cycle-automatic <https://releases.openstack.org/reference/release_models."
"html#cycle-automatic>`_"
msgstr ""

#: ../../source/common/releases.rst:33
msgid ""
"`independent <https://releases.openstack.org/reference/release_models."
"html#independent>`_"
msgstr ""

#: ../../source/common/releases.rst:35
msgid ""
"`untagged <https://releases.openstack.org/reference/release_models."
"html#untagged>`_"
msgstr ""

#: ../../source/common/releases.rst:39
msgid "Release Schedule and Planning"
msgstr ""

#: ../../source/common/releases.rst:41
msgid ""
"The majority of the official OpenStack projects follow the release schedule "
"set by the Release Management Team."
msgstr ""

#: ../../source/common/releases.rst:44
msgid ""
"The 6-month cycle is divided into three milestones and a usually one-month "
"long stabilization period with release candidates."
msgstr ""

#: ../../source/common/releases.rst:47
msgid ""
"The first period of a cycle includes more focus on planning, which is why "
"the PTGs are scheduled right after the releases. This is the phase when you "
"should upload your specs for review and use the mailing list, project "
"channels and meetings on IRC to discuss any parts of your design that might "
"be in question."
msgstr ""

#: ../../source/common/releases.rst:52
msgid ""
"After the first milestone, some projects focus more on the development and "
"bug fixing activities, while other projects might still accept new ideas to "
"implement in that cycle."
msgstr ""

#: ../../source/common/releases.rst:56
msgid ""
"The third period of a release is focusing on finishing the implementation "
"and testing of new functionality added during the release. You need to "
"ensure to add new tests in Tempest and have documentation covered as well "
"before the third milestone. During this phase the core review team can "
"choose to focus on higher priority features only. They make their decision "
"about priorities either at the PTG or soon after, some time before the first "
"milestone of a release."
msgstr ""

#: ../../source/common/releases.rst:63
msgid ""
"Some projects also have different dates through a release cycles as "
"internal, project-specific deadlines, like spec-freeze or code-freeze. You "
"need to make sure you are aware of the freeze dates which you can find on "
"the `release schedule page <https://releases.openstack.org>`_."
msgstr ""

#: ../../source/common/releases.rst:68
msgid ""
"After the third milestone the community is focusing on stabilizing the "
"release by putting more emphasis on testing and fixing bugs. The projects "
"following the release cycle have their release candidates tagged after the "
"third milestone. There are no limits to release candidates, but the goal is "
"to keep the number low and fix all the critical issues that got identified "
"by milestone-3."
msgstr ""

#: ../../source/common/releases.rst:75
msgid ""
"Having the main projects following the release cycle ensures that all these "
"projects release at the same time so these can be picked up by downstream "
"teams to package and further distribute."
msgstr ""

#: ../../source/common/releases.rst:80
msgid "Stable Branches"
msgstr ""

#: ../../source/common/releases.rst:82
msgid ""
"Once a 6-month development cycle is completed the code for that release is "
"branched, in git, to a stable branch. For instance, when the Stein release "
"was completed a new branch in git, ``stable/stein`` was created."
msgstr ""

#: ../../source/common/releases.rst:86
msgid ""
"Stable branches are kept as a safe source of fixes for high impact bugs and "
"security issues which have been fixed, on master, since the release occurred."
" Given the stable nature of these branches, backports to stable branches "
"undergo additional scrutiny when they are proposed. Proposed changes should:"
msgstr ""

#: ../../source/common/releases.rst:92
msgid "Have a low risk of introducing a regression"
msgstr ""

#: ../../source/common/releases.rst:93
msgid "Have a user visible benefit"
msgstr ""

#: ../../source/common/releases.rst:94
msgid "Be self contained"
msgstr ""

#: ../../source/common/releases.rst:95
msgid ""
"Be included in master and backported to all releases between master and the "
"stable branch in question"
msgstr ""

#: ../../source/common/releases.rst:98
msgid ""
"Project teams do point releases off stable branches when enough changes "
"accumulate in the stable branch to justify creating another release for "
"their project."
msgstr ""

#: ../../source/common/releases.rst:102
msgid ""
"Stable branches proceed through different levels of maintenance as they age."
msgstr ""

#: ../../source/common/releases.rst:106
msgid "State"
msgstr ""

#: ../../source/common/releases.rst:106
msgid "Summary"
msgstr ""

#: ../../source/common/releases.rst:106
msgid "Time frame"
msgstr ""

#: ../../source/common/releases.rst:108
msgid "All appropriate bug fixes accepted and releases are produced."
msgstr ""

#: ../../source/common/releases.rst:108
msgid "Approximately 18 months"
msgstr ""

#: ../../source/common/releases.rst:108
msgid "Maintained"
msgstr ""

#: ../../source/common/releases.rst:111
msgid ""
"All appropriate bug fixes accepted. No releases are produced and there is "
"reduced CI commitment."
msgstr ""

#: ../../source/common/releases.rst:111
msgid "Unmaintained"
msgstr ""

#: ../../source/common/releases.rst:111
msgid "While there are community members maintaining it."
msgstr ""

#: ../../source/common/releases.rst:115
msgid "Branch is no longer accepting Changes."
msgstr ""

#: ../../source/common/releases.rst:115
msgid "End of Life (EOL)"
msgstr ""

#: ../../source/common/releases.rst:115
msgid "N/A"
msgstr ""

#: ../../source/common/releases.rst:119
msgid ""
"Unmaintained state is only to have a common place for cooperation for "
"interested parties to do some further maintenance of a given stable release "
"after its maintained phase, but as its name says, it's not officially "
"considered maintained."
msgstr ""

#: ../../source/common/releases.rst:124
msgid ""
"The state of all OpenStack releases may be seen on the `OpenStack Releases "
"<https://releases.openstack.org>`_ web page."
msgstr ""

#: ../../source/common/releases.rst:127
msgid ""
"For more detailed information on Stable Branches and their maintenance "
"phases see the `Stable Branches <https://docs.openstack.org/project-team-"
"guide/stable-branches.html>`_ page."
msgstr ""

#: ../../source/common/setup-gerrit.rst:3
msgid "Setting Up Your Gerrit Account"
msgstr ""

#: ../../source/common/setup-gerrit.rst:7
msgid "This section assumes you have completed :doc:`git` guide."
msgstr ""

#: ../../source/common/setup-gerrit.rst:12
msgid "What is Gerrit?"
msgstr ""

#: ../../source/common/setup-gerrit.rst:14
msgid "This is the review system the OpenStack community uses."
msgstr ""

#: ../../source/common/setup-gerrit.rst:16
msgid "Gerrit allows you to review:"
msgstr ""

#: ../../source/common/setup-gerrit.rst:18
msgid ""
"`Code, docs, infrastructure changes, and CI configurations <https://opendev."
"org/explore/repos>`_"
msgstr ""

#: ../../source/common/setup-gerrit.rst:19
msgid "`Specifications <https://specs.openstack.org>`_"
msgstr ""

#: ../../source/common/setup-gerrit.rst:20
msgid "`Translations <https://opendev.org/openstack/i18n/>`_"
msgstr ""

#: ../../source/common/setup-gerrit.rst:21
msgid ""
"`Use cases for features <https://specs.openstack.org/openstack/openstack-"
"user-stories/>`_"
msgstr ""

#: ../../source/common/setup-gerrit.rst:26
msgid ""
"Visit `OpenStack's Gerrit page <https://review.opendev.org>`_ and click the "
"**sign in** link."
msgstr ""

#: ../../source/common/setup-gerrit.rst:28
msgid ""
"You will be prompted to select a username. You can enter the same one you "
"did for Launchpad, or something else."
msgstr ""

#: ../../source/common/setup-gerrit.rst:33
msgid ""
"Choose and type your username carefully. Once it is set, you cannot change "
"the username."
msgstr ""

#: ../../source/common/setup-gerrit.rst:38
msgid ""
"From here on out when you sign into Gerrit, you'll be prompted to enter your "
"Launchpad login info. This is because Gerrit uses it as an OpenID single "
"sign on."
msgstr ""

#: ../../source/common/setup-gerrit.rst:45
msgid "Individual Contributor License Agreement (ICLA)"
msgstr ""

#: ../../source/common/setup-gerrit.rst:48
#: ../../source/common/setup-gerrit.rst:237
msgid "What is it?"
msgstr ""

#: ../../source/common/setup-gerrit.rst:50
msgid ""
"An agreement to clarify intellectual property rights granted with "
"contributions from a person or entity. `Preview the full agreement <https://"
"review.opendev.org/static/cla.html>`_."
msgstr ""

#: ../../source/common/setup-gerrit.rst:55
msgid "Signing it"
msgstr ""

#: ../../source/common/setup-gerrit.rst:58
msgid "Individual Contributors"
msgstr ""

#: ../../source/common/setup-gerrit.rst:60
msgid ""
"In Gerrit's `settings <https://review.opendev.org/#/settings/agreements>`_ "
"click the **New Contributor Agreement** link and sign the agreement. You "
"need this to contribute code & documentation. You will not be able to push "
"patches to Gerrit without this."
msgstr ""

#: ../../source/common/setup-gerrit.rst:70
msgid "Contributors From a Company or Organization"
msgstr ""

#: ../../source/common/setup-gerrit.rst:72
msgid ""
"If you are contributing on behalf of a company or organization, please make "
"sure that you sign the ICLA **AND** also get added to the list of "
"contributors on your company's Corporate Contributor License Agreement "
"(CCLA). You will need to complete both of these steps before being able to "
"contribute."
msgstr ""

#: ../../source/common/setup-gerrit.rst:78
msgid ""
"In Gerrit's `settings <https://review.opendev.org/#/settings/agreements>`_ "
"click the **New Contributor Agreement** link and sign the agreement."
msgstr ""

#: ../../source/common/setup-gerrit.rst:85
msgid ""
"An employer with the appropriate signing rights of the company or "
"organization needs to sign the `Corporate Contributor License Agreement "
"<https://secure.echosign.com/public/hostedForm?formid=56JUVGT95E78X5>`_."
msgstr ""

#: ../../source/common/setup-gerrit.rst:88
msgid ""
"If the CCLA only needs to be extended follow `this <https://wiki.openstack."
"org/wiki/HowToUpdateCorporateCLA>`_ procedure."
msgstr ""

#: ../../source/common/setup-gerrit.rst:93
msgid ""
"Employers can update the list of authorized employees by filling out and "
"signing an `Updated Schedule A Form <https://openstack.echosign.com/public/"
"hostedForm?formid=56JUVP6K4Z6P4C>`_."
msgstr ""

#: ../../source/common/setup-gerrit.rst:99
msgid "Contributors From the U.S. Government"
msgstr ""

#: ../../source/common/setup-gerrit.rst:101
msgid ""
"Someone of authority needs to sign the `U.S. Government Contributor License "
"Agreement <https://wiki.openstack.org/wiki/GovernmentCLA>`_. Contact the "
"`Open Infrastructure Foundation <mailto:communitymngr@openstack.org>`_ to "
"initiate this process."
msgstr ""

#: ../../source/common/setup-gerrit.rst:107
msgid "Setup SSH Keys"
msgstr ""

#: ../../source/common/setup-gerrit.rst:110
msgid "What are they?"
msgstr ""

#: ../../source/common/setup-gerrit.rst:112
msgid ""
"In order to push things to `Gerrit <https://review.opendev.org>`_ we need to "
"have a way to identify ourselves. We will do this using SSH keys which "
"allows us to have our machine we're pushing a change from to perform a "
"`challenge-response authentication <https://en.wikipedia.org/wiki/Challenge-"
"response_authentication>`_ with the Gerrit server."
msgstr ""

#: ../../source/common/setup-gerrit.rst:119
msgid "SSH keys are always generated in pairs:"
msgstr ""

#: ../../source/common/setup-gerrit.rst:121
msgid "**Private key** - Only known to you and it should be safely guarded."
msgstr ""

#: ../../source/common/setup-gerrit.rst:122
msgid ""
"**Public key** - Can be shared freely with any SSH server you wish to "
"connect to."
msgstr ""

#: ../../source/common/setup-gerrit.rst:125
msgid ""
"In summary, you will be generating a SSH key pair, and providing the Gerrit "
"server with your public key. With your system holding the private key, it "
"will have no problem replying to Gerrit during the challenge-response "
"authentication."
msgstr ""

#: ../../source/common/setup-gerrit.rst:130
msgid ""
"Some people choose to use one SSH key pair to access many systems while "
"others prefer to use separate key pairs. Both options are covered in the "
"following sections."
msgstr ""

#: ../../source/common/setup-gerrit.rst:135
msgid "Check For Existing Keys"
msgstr ""

#: ../../source/common/setup-gerrit.rst:137
msgid "Open your terminal program and type::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:141
msgid "Typically public key filenames will look like:"
msgstr ""

#: ../../source/common/setup-gerrit.rst:143
msgid "id_dsa.pub"
msgstr ""

#: ../../source/common/setup-gerrit.rst:144
msgid "id_ecdsa.pub"
msgstr ""

#: ../../source/common/setup-gerrit.rst:145
msgid "id_ed25519.pub"
msgstr ""

#: ../../source/common/setup-gerrit.rst:146
msgid "id_rsa.pub"
msgstr ""

#: ../../source/common/setup-gerrit.rst:148
msgid ""
"If you don't see .pub extension file or want to generate a specific set for "
"OpenStack Gerrit, you need to generate keys."
msgstr ""

#: ../../source/common/setup-gerrit.rst:153
msgid "Generate SSH Key Pairs"
msgstr ""

#: ../../source/common/setup-gerrit.rst:157
msgid ""
"This guide recommends using ``ed25519`` keys because it has been found that "
"this type works well across all operating systems."
msgstr ""

#: ../../source/common/setup-gerrit.rst:161
msgid "Generating The Default Or Initial SSH Key Pair"
msgstr ""

#: ../../source/common/setup-gerrit.rst:163
msgid ""
"You can generate a new SSH key pair using the provided email as a label by "
"going into your terminal program and typing::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:168
msgid ""
"When you're prompted to \"Enter a file in which to save the key\" press "
"Enter. This accepts the default location::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:173
#: ../../source/common/setup-gerrit.rst:192
msgid ""
"At the prompt, type a secure passphrase, you may enter one or press Enter to "
"have no passphrase::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:180
msgid "Generating A Separate Key Pair For OpenStack Gerrit (optional)"
msgstr ""

#: ../../source/common/setup-gerrit.rst:182
msgid ""
"You can generate a new SSH key using the provided email as a label by going "
"into your terminal program and typing::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:187
msgid ""
"When you're prompted to \"Enter a file in which to save the key\" you must "
"specify the name of the new key pair and then press Enter::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:198
msgid ""
"Finally you need to tell ssh what host(s) to associate SSH keys with. To do "
"this open \"~/.ssh/config\" in an editor, create the file if it doesn't "
"exist and add something like::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:209
msgid "Copy Public Key"
msgstr ""

#: ../../source/common/setup-gerrit.rst:212
msgid "Mac OS & Linux"
msgstr ""

#: ../../source/common/setup-gerrit.rst:214
msgid "From your terminal type::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:218
msgid ""
"Or if you created a separate key pair, assuming the example name above::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:223
msgid "Select and copy the output."
msgstr ""

#: ../../source/common/setup-gerrit.rst:226
msgid "Import Public Key Into Gerrit"
msgstr ""

#: ../../source/common/setup-gerrit.rst:228
msgid ""
"Go to `Gerrit's SSH Keys section in User Settings <https://review.opendev."
"org/settings/#SSHKeys>`_."
msgstr ""

#: ../../source/common/setup-gerrit.rst:230
msgid "Paste the public key into the **New SSH Key** text box."
msgstr ""

#: ../../source/common/setup-gerrit.rst:231
msgid "Click the 'ADD NEW SSH KEY' button."
msgstr ""

#: ../../source/common/setup-gerrit.rst:234
msgid "Git Review"
msgstr ""

#: ../../source/common/setup-gerrit.rst:239
msgid ""
"Git review is a tool maintained by the OpenStack community. It adds an "
"additional sub-command to 'git' like so::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:244
msgid ""
"When you have changes in an OpenStack project repository, you can use this "
"sub-command to have the changes posted to `Gerrit <https://review.opendev."
"org/>`__ so that they can be reviewed."
msgstr ""

#: ../../source/common/setup-gerrit.rst:254
msgid "In a terminal type::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:258
msgid ""
"If you don't have pip installed already, follow the `installation "
"documentation <https://pip.pypa.io/en/stable/installing/#installing-with-get-"
"pip-py>`_ for pip."
msgstr ""

#: ../../source/common/setup-gerrit.rst:264
msgid ""
"Mac OS X El Capitan and Mac OS Sierra users might see an error message like "
"\"Operation not permitted\" when installing with the command. In this case, "
"there are two options to successfully install git-review."
msgstr ""

#: ../../source/common/setup-gerrit.rst:268
msgid "Option 1: install using pip with more options::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:272
msgid ""
"Option 2: Use the package manager `Homebrew <https://brew.sh>`_, and type in "
"a terminal::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:294
msgid "Configuration"
msgstr ""

#: ../../source/common/setup-gerrit.rst:296
msgid ""
"Git review assumes the user you're running it as is the same as your Gerrit "
"username. If it's not, you can tell it by setting this git config setting::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:301
msgid ""
"If you don't know what your Gerrit username is, you can check the `Gerrit "
"settings <https://review.opendev.org/#/settings/>`_."
msgstr ""

#: ../../source/common/setup-gerrit.rst:305
msgid "Preparing to Send a Review"
msgstr ""

#: ../../source/common/setup-gerrit.rst:307
msgid ""
"Before doing **git commit** on your patch it is important to initialize git "
"review. Use the following command to do the initial git review configuration "
"in your repository::"
msgstr ""

#: ../../source/common/setup-gerrit.rst:313
msgid ""
"The command sets up the necessary remote hosts and commit hooks to enable "
"pushing changes to Gerrit."
msgstr ""

#: ../../source/common/setup-gerrit.rst:318
msgid "Git review only needs to be initialized once in a repository."
msgstr ""

#: ../../source/common/task-tracking.rst:3
msgid "Task Tracking"
msgstr ""

#: ../../source/common/task-tracking.rst:5
msgid ""
"This section provides information on Storyboard and Launchpad task trackers. "
"You can learn about Storyboard stories and tasks, boards and worklists, and "
"Launchpad blueprints and bugs."
msgstr ""

#: ../../source/common/task-tracking.rst:16
msgid "Understand the different tools OpenStack uses for task management"
msgstr ""

#: ../../source/common/task-tracking.rst:17
msgid "Know how to report bugs and propose features"
msgstr ""

#: ../../source/common/task-tracking.rst:20
msgid "What Task Trackers does OpenStack use?"
msgstr ""

#: ../../source/common/task-tracking.rst:22
msgid ""
"Each project is different in the process of reporting bugs and planning new "
"features. There are however two main tools that projects use: Launchpad and "
"Storyboard."
msgstr ""

#: ../../source/common/task-tracking.rst:28
msgid ""
"Before raising a bug, story or feature request it's important to note that "
"not all projects do the same thing. It's best to go check with the project "
"to see how they handle these requests. For details on how to contact a "
"project check the `project list <https://governance.openstack.org/tc/"
"reference/projects/index.html>`_."
msgstr ""

#: ../../source/common/task-tracking.rst:37
msgid "Storyboard"
msgstr ""

#: ../../source/common/task-tracking.rst:39
msgid ""
"Storyboard is a kanban style task tracking system created and maintained by "
"the community. It was designed API-first and was engineered to support the "
"coordination of cross project work. Items tracked are stories and tasks. A "
"story can be a bug or a new feature, while tasks are the smaller todo's "
"required to complete the story."
msgstr ""

#: ../../source/common/task-tracking.rst:45
msgid ""
"For information on how to use storyboard, please see `the user interface "
"manual <https://docs.openstack.org/infra/storyboard/gui/tasks_stories_tags."
"html>`_."
msgstr ""

#: ../../source/common/task-tracking.rst:47
msgid ""
"For other information about the project itself, please check out `their "
"documentation <https://docs.openstack.org/infra/storyboard/>`_."
msgstr ""

#: ../../source/common/task-tracking.rst:53
msgid "Stories & Tasks"
msgstr ""

#: ../../source/common/task-tracking.rst:55
msgid ""
"A story is a desired change. Whether it is a bug or a new feature, both are "
"essentially a code change. Tasks are sub items of the story; they are tied "
"to specific projects. As an example, a story could be to invent some new "
"feature A, and tasks would be change in project X, change in project Y, and "
"change in project Z. Those changes need to merge in order to complete "
"feature A."
msgstr ""

#: ../../source/common/task-tracking.rst:63
msgid "Boards & Worklists"
msgstr ""

#: ../../source/common/task-tracking.rst:65
msgid ""
"Worklists and boards are different ways of organizing work. It is up to the "
"project team how stories are organized. They could be sorted by milestone. A "
"lane could have all the bugs or all the new features. It depends on the "
"teams way of organizing and coordinating work. Order of stories in a "
"worklist could convey priority as well."
msgstr ""

#: ../../source/common/task-tracking.rst:76
msgid ""
"Launchpad is the original task tracker used by OpenStack projects to "
"organize and target work to milestones and releases. It uses UbuntuOne for "
"authentication as it is managed by Canonical. Items tracked are either bugs "
"or blueprints."
msgstr ""

#: ../../source/common/task-tracking.rst:86
msgid "Blueprints"
msgstr ""

#: ../../source/common/task-tracking.rst:88
msgid ""
"In Launchpad, a new feature is called a blueprint. To file a new blueprint, "
"click the 'Register a blueprint' button on the right."
msgstr ""

#: ../../source/common/task-tracking.rst:91
msgid ""
"On the next screen you are prompted to add details including its name and "
"title."
msgstr ""

#: ../../source/common/task-tracking.rst:97
msgid ""
"These are different in that the name is what is used in the generated url "
"and the title is what displays when blueprints are listed out (name: "
"new_ibm_driver title: New IBM ISCSI Driver). The next most important part is "
"the summary- a description of the code change, where most of the details "
"about the implementation are. After that, there are several optional fields "
"you may wish to fill in- a specification url, assignee, drafter, and "
"approver. The last two fields before registering have default values- status "
"and propose for a sprint. For most teams, it is typical to leave the default "
"values."
msgstr ""

#: ../../source/common/task-tracking.rst:107
msgid ""
"It is possible to update all of this information except the name and title "
"after the blueprint is registered. When you have finished filling out all of "
"the information you care to include, it is good to communicate with the "
"project team lead that you have filed a blueprint."
msgstr ""

#: ../../source/common/task-tracking.rst:118
msgid ""
"Not all projects use the blueprints feature of Launchpad, you should contact "
"the project to see how they handle feature requests. For details on how to "
"contact a project check the `project list <https://governance.openstack.org/"
"tc/reference/projects/index.html>`_."
msgstr ""

#: ../../source/common/task-tracking.rst:124
msgid "Bugs"
msgstr ""

#: ../../source/common/task-tracking.rst:126
msgid ""
"Bugs are pretty self explanitory- some unexpected or unintended behavior of "
"the software. To report a bug you have found in Launchpad, click the 'Report "
"a bug' button from the project's overview page."
msgstr ""

#: ../../source/common/task-tracking.rst:130
msgid ""
"To get to the details of reporting the bug you fill in the summary line and "
"click 'next'."
msgstr ""

#: ../../source/common/task-tracking.rst:136
msgid ""
"Based on the summary line, Launchpad will do a quick query to see if there "
"has been anything reported already that might be the same issue you are "
"trying to report. It is important to look through these to avoid filing "
"duplicate bugs and creating redundancies in the bug index. If you do not see "
"a bug that sounds like the issue you are reporting, you can click the 'No, I "
"need to report a new bug' button."
msgstr ""

#: ../../source/common/task-tracking.rst:146
msgid ""
"After clicking that button, the further information field will appear along "
"with the 'This bug is a security vulnerability' radio box. You can edit the "
"summary line to differentiate it from the other bugs Launchpad thought it "
"was similar to, add details like the setup you were using, what you were "
"doing when you hit the unexpected behavior, the error codes you encountered, "
"etc."
msgstr ""

#: ../../source/common/task-tracking.rst:153
msgid ""
"If the bug is related to a security vulnerability it is important to click "
"the box to alert the Vulnerability Management Team to the issue. When you "
"feel you have added all of the information needed, go ahead and submit the "
"bug report. For more information about the full process for reporting "
"security vulnerabilties, please continue reading `this page <https://"
"security.openstack.org/vmt-process.html>`_."
msgstr ""

#: ../../source/common/task-tracking.rst:163
msgid ""
"It is a good idea to check back on the bug routinely if you aren't actively "
"working on solving it to make sure people haven't asked for more information "
"about the issue. If someone has commented on the bug, try to respond with "
"the details they need."
msgstr ""

#: ../../source/common/task-tracking.rst:168
msgid ""
"**Bug Status** All bugs have a status lifecycle. They start as 'New' and "
"move to other statuses from there depending on what all is included in the "
"description and if others can duplicate the issue. Resolved statuses, "
"meaning there is no more work to be done on the bug are: 'Fix Released', "
"'Invalid', or 'Won't Fix'."
msgstr ""

#: ../../source/common/task-tracking.rst:178
msgid "`New`"
msgstr ""

#: ../../source/common/task-tracking.rst:179
msgid "The bug was just created"
msgstr ""

#: ../../source/common/task-tracking.rst:180
msgid "`Incomplete`"
msgstr ""

#: ../../source/common/task-tracking.rst:181
msgid "The bug is waiting on input from the reporter"
msgstr ""

#: ../../source/common/task-tracking.rst:182
msgid "`Confirmed`"
msgstr ""

#: ../../source/common/task-tracking.rst:183
msgid "The bug was reproduced or confirmed as a genuine bug"
msgstr ""

#: ../../source/common/task-tracking.rst:184
msgid "`Triaged`"
msgstr ""

#: ../../source/common/task-tracking.rst:185
msgid ""
"The bug comments contain a full analysis on how to properly fix the issue"
msgstr ""

#: ../../source/common/task-tracking.rst:187
msgid "`In Progress`"
msgstr ""

#: ../../source/common/task-tracking.rst:188
msgid "Work on the fix is in progress, bug has an assignee"
msgstr ""

#: ../../source/common/task-tracking.rst:189
msgid "`Fix Committed`"
msgstr ""

#: ../../source/common/task-tracking.rst:190
msgid "Not used"
msgstr ""

#: ../../source/common/task-tracking.rst:191
msgid "`Fix Released`"
msgstr ""

#: ../../source/common/task-tracking.rst:192
msgid "The fix has been merged into an official branch"
msgstr ""

#: ../../source/common/task-tracking.rst:193
msgid "`Invalid`"
msgstr ""

#: ../../source/common/task-tracking.rst:194
msgid "This is not a bug"
msgstr ""

#: ../../source/common/task-tracking.rst:195
msgid "`Opinion`"
msgstr ""

#: ../../source/common/task-tracking.rst:196
msgid "This is a valid issue, but it is the way it should be"
msgstr ""

#: ../../source/common/task-tracking.rst:197
msgid "`Won't Fix`"
msgstr ""

#: ../../source/common/task-tracking.rst:198
msgid "This is a valid issue, but we don't intend to fix that"
msgstr ""

#: ../../source/common/zuul-status.rst:3
msgid "Checking Status in Zuul"
msgstr ""

#: ../../source/common/zuul-status.rst:7
msgid ""
"This section assumes you have completed :doc:`/code-and-documentation/using-"
"gerrit`."
msgstr ""

#: ../../source/common/zuul-status.rst:11
msgid "Monitor your patches as they get tested by Zuul"
msgstr ""

#: ../../source/common/zuul-status.rst:12
msgid ""
"Understand the underlying infrastructure and gating processes that OpenStack "
"uses"
msgstr ""

#: ../../source/common/zuul-status.rst:16
msgid "What is Zuul"
msgstr ""

#: ../../source/common/zuul-status.rst:18
msgid ""
"Zuul is a tool written and run by the OpenStack Infrastructure team that is "
"used to manage running continuous infrastructure jobs. It provides projects "
"with a way to define test jobs that will run on each proposed commit. These "
"tests are required to pass in order for any proposed patch to merge."
msgstr ""

#: ../../source/common/zuul-status.rst:23
msgid ""
"When you push a patch to gerrit zuul will automatically trigger jobs to "
"verify the patch functions properly."
msgstr ""

#: ../../source/common/zuul-status.rst:28
msgid "Tracking Changes in Zuul status page"
msgstr ""

#: ../../source/common/zuul-status.rst:30
msgid ""
"You can check the status of those jobs at any time by navigating to: https://"
"zuul.openstack.org/"
msgstr ""

#: ../../source/common/zuul-status.rst:36
msgid ""
"This will show you the status on all jobs running in zuul currently. You can "
"expand jobs running on any patch by clicking on the box for a patch."
msgstr ""

#: ../../source/common/zuul-status.rst:43
msgid ""
"To find your specific patch in zuul you can use the search bar and search "
"for the patch number. This will then filter what is displayed to just that "
"patch:"
msgstr ""

#: ../../source/common/zuul-status.rst:51
msgid "Why do changes go first in the check queue?"
msgstr ""

#: ../../source/common/zuul-status.rst:53
msgid ""
"The OpenStack project uses what's called a `clean check` approach. This is "
"designed to keep flaky changes out of the gate. A change always needs to "
"pass the check before it enters the gate. If it fails in the gate, it re-"
"enters the check pipeline."
msgstr ""

#: ../../source/common/zuul-status.rst:59
msgid ""
"If your change fails in the gate, then there is an increased chance it is "
"introducing non-deterministic failure behavior. Forcing it to go through "
"check again helps make that more apparent."
msgstr ""

#: ../../source/common/zuul-status.rst:62
msgid ""
"This avoids approving changes that have no hope of ever passing due to pep8 "
"or other trivial errors."
msgstr ""

#: ../../source/common/zuul-status.rst:64
msgid ""
"It also helps with approving changes that had been sitting around with a 6-"
"month-old passing check."
msgstr ""

#: ../../source/common/zuul-status.rst:67
msgid ""
"Changes in the gate pipeline are prioritized but also serialized. If a "
"change fails, all tests for changes behind that failing change have to be "
"restarted. If restarts after restarts happen, then resources are never freed "
"up for the check pipeline."
msgstr ""

#: ../../source/common/zuul-status.rst:72
msgid ""
"Therefore, having a stable gate pipeline is crucial and the clean check "
"requirement will help with the stable jobs."
msgstr ""