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

# Andreas Jaeger <jaegerandi@gmail.com>, 2019. #zanata
# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
msgid ""
msgstr ""
"Project-Id-Version: contributor-guide\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-02-03 15:39+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2019-02-03 03:53+0000\n"
"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"

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

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

msgid "**Inline Comments**"
msgstr "**Inline Comments**"

msgid "**Reviewing Best Practices**"
msgstr "**Reviewing Best Practices**"

msgid ""
"+W: Approved. This patch will now be run through a final round of checks "
"before it is merged into the repository."
msgstr ""
"+W: Disetujui. Patch ini sekarang akan dijalankan melalui putaran "
"pemeriksaan terakhir sebelum digabungkan ke dalam repositori."

msgid ""
":ref:`launchpad` is one of the task tracking tools that the community is "
"using."
msgstr ""
":ref:`launchpad` adalah salah satu alat pelacak tugas yang digunakan "
"komunitas."

msgid ""
":ref:`storyboard` is a community-developed task tracking tool. The community-"
"wide adoption of the tool is in progress, you will find more and more "
"projects who migrated over to using StoryBoard already."
msgstr ""
":ref:`storyboard` adalah alat pelacak tugas yang dikembangkan masyarakat. "
"Adopsi alat di seluruh komunitas sedang berlangsung, Anda akan menemukan "
"semakin banyak proyek yang bermigrasi untuk menggunakan StoryBoard."

msgid ""
"A ``clean.sh`` run does the steps for ``unstack.sh`` plus additional "
"cleaning:"
msgstr ""
"Jalankan ``clean.sh`` melakukan langkah-langkah untuk ``unstack.sh`` plus "
"pembersihan tambahan:"

msgid ""
"A detailed description of the documentation tools and processes can be found "
"in the `OpenStack Documentation Contributor Guide <https://docs.openstack."
"org/doc-contrib-guide/index.html>`_."
msgstr ""
"Penjelasan terperinci tentang alat dan proses dokumentasi dapat ditemukan di "
"`OpenStack Documentation Contributor Guide <https://docs.openstack.org/doc-"
"contrib-guide/index.html>`_."

msgid "A log of the stack.sh run is kept in ``/opt/stack/logs/stack.sh.log``."
msgstr "Log run stack.sh disimpan ``/opt/stack/logs/stack.sh.log``."

msgid ""
"A more complete reference of using systemd to interact with DevStack can be "
"found on the `Using Systemd in DevStack <https://docs.openstack.org/devstack/"
"latest/systemd.html>`_ page."
msgstr ""
"Referensi yang lebih lengkap tentang penggunaan systemd untuk berinteraksi "
"dengan DevStack dapat ditemukan di halaman `Using Systemd in DevStack "
"<https://docs.openstack.org/devstack/latest/systemd.html>`_."

msgid ""
"A patch chain is easy to handle if you keep in mind a few recommendations:"
msgstr "Rantai patch mudah ditangani jika Anda mengingat beberapa rekomendasi:"

msgid "ADMIN_PASSWORD"
msgstr "ADMIN_PASSWORD"

msgid "Adding Reviewers"
msgstr "Menambahkan Reviewer"

msgid ""
"After checking out the patch, you will be switched to a new branch "
"automatically, on which you can make your changes."
msgstr ""
"Setelah memeriksa patch, Anda akan beralih ke cabang baru secara otomatis, "
"tempat Anda dapat melakukan perubahan."

msgid ""
"After proposing changes, you can track them at `Code Review <https://review."
"openstack.org>`_. After logging in, you will see a dashboard of \"Outgoing "
"reviews\" for changes you have proposed, \"Incoming reviews\" for changes "
"you are reviewing, and \"Recently closed\" changes for which you were either "
"a reviewer or owner."
msgstr ""
"Setelah mengajukan perubahan, Anda dapat melacaknya di `Code Review <https://"
"review.openstack.org>`_. Setelah masuk (log in), Anda akan melihat dasbor "
"\"Outgoing reviews\" untuk perubahan yang Anda usulkan, \"Incoming reviews\" "
"untuk perubahan yang Anda kaji, dan perubahan \"Recently closed\" di mana "
"Anda menjadi pengulas atau pemilik."

msgid ""
"After you've completed the Setup and Learn GIT section, the following "
"command configures the repository to know about Gerrit and installs the "
"``Change-Id`` commit hook. You only need to do this once per repository you "
"clone::"
msgstr ""
"Setelah Anda menyelesaikan bagian Setup dan Learn GIT , perintah berikut "
"mengonfigurasi repositori untuk mengetahui tentang Gerrit dan menginstal "
"commit hook (kait komit) ``Change-Id``. Anda hanya perlu melakukan ini "
"sekali per repositori yang Anda clone::"

msgid ""
"All the Sandbox repository and projects are identical to any other active "
"project's resources. You can find the same information and same "
"functionality as well to ensure you can practice everything you need to know "
"about the tool."
msgstr ""
"Semua repositori dan proyek Sandbox identik dengan sumber daya proyek aktif "
"lainnya. Anda dapat menemukan informasi yang sama dan fungsi yang sama juga "
"untuk memastikan Anda dapat mempraktikkan semua yang perlu Anda ketahui "
"tentang alat ini."

msgid "Allows you to:"
msgstr "Memungkinkan Anda untuk:"

msgid ""
"Always check the changes you made to each patch and be careful that you "
"applied the changes in the right one as patches still get merged "
"individually and there is no guarantee that the whole chain gets landed at "
"the same time."
msgstr ""
"Selalu periksa perubahan yang Anda buat untuk setiap patch dan berhati-"
"hatilah bahwa Anda menerapkan perubahan di patch yang tepat karena patch "
"masih dapat digabung secara individual dan tidak ada jaminan bahwa seluruh "
"rantai akan mendarat pada waktu yang sama."

msgid ""
"Always handle a chain as one block of changes by rebasing the whole chain "
"and keep it up to date when you modify a patch to fix review comments or add "
"changes to it."
msgstr ""
"Selalu tangani rantai sebagai satu blok perubahan dengan mengubah seluruh "
"rantai dan tetap perbarui saat Anda memodifikasi patch untuk memperbaiki "
"komentar ulasan atau menambahkan perubahan ke dalamnya."

msgid ""
"Always have a local branch for these changes to ensure that you don't mix it "
"together with changes related to another feature or bug fix."
msgstr ""
"Selalu memiliki cabang lokal untuk perubahan ini untuk memastikan bahwa Anda "
"tidak mencampurnya bersama dengan perubahan terkait dengan fitur lain atau "
"perbaikan bug."

msgid ""
"Always try to extract as much as you can into other patches, like "
"documentation or logical parts of the functionality that do not depend on "
"common functions in a lower layer."
msgstr ""
"Selalu mencoba mengekstrak sebanyak yang Anda bisa ke patch lain, seperti "
"dokumentasi atau bagian logis dari fungsi yang tidak bergantung pada fungsi "
"umum di lapisan bawah."

msgid ""
"An important part of development is, obviously, being able to test changes "
"you develop and ensure that they function properly. In a complicated "
"ecosystem like OpenStack there is a need to also be able to verify the "
"interoperability of your code. You may make a change to Cinder but that "
"change can also impact the way that Nova interacts with Cinder's APIs."
msgstr ""
"Bagian penting dari pengembangan, tentu saja, dapat menguji perubahan yang "
"Anda kembangkan dan memastikan bahwa mereka berfungsi dengan baik. Dalam "
"ekosistem yang rumit seperti OpenStack, ada juga kebutuhan untuk dapat "
"memverifikasi interoperabilitas kode Anda. Anda dapat membuat perubahan ke "
"Cinder tetapi perubahan itu juga dapat memengaruhi cara Nova berinteraksi "
"dengan API Cinder."

msgid ""
"Any temporary backing files needed to simulate a system are created in /opt/"
"stack/data"
msgstr ""
"File cadangan sementara yang diperlukan untuk mensimulasikan sistem dibuat "
"di /opt/stack/data"

msgid ""
"Assuming you have not added new files, you commit all your changes using::"
msgstr ""
"Dengan asumsi Anda belum menambahkan file baru, Anda melakukan semua "
"perubahan Anda using::."

msgid ""
"At this point DevStack takes over preparing your node to function as an "
"OpenStack cloud. The following is done:"
msgstr ""
"Pada titik ini DevStack mengambil alih mempersiapkan node Anda berfungsi "
"sebagai cloud OpenStack. Berikut ini dilakukan:"

msgid ""
"Beyond this you can also look into the functionality to find smaller "
"building blocks and make your changes smaller. For instance changes to an "
"object can be implemented first that you will use later when you implement "
"new API functionality."
msgstr ""
"Selain itu, Anda juga dapat melihat fungsionalitas untuk menemukan blok "
"bangunan yang lebih kecil dan membuat perubahan Anda lebih kecil. Misalnya "
"perubahan pada suatu objek dapat diimplementasikan terlebih dahulu yang akan "
"Anda gunakan nanti ketika Anda menerapkan fungsionalitas API baru."

msgid ""
"By default, the core services for OpenStack are installed but users can "
"configure additional services to be deployed. All services are installed "
"from source. DevStack will pull the services from git master unless "
"configured to clone from a stable branch (i.e. stable/pike)."
msgstr ""
"Secara default, layanan inti untuk OpenStack diinstal tetapi pengguna dapat "
"mengonfigurasi layanan tambahan untuk digunakan. Semua layanan diinstal dari "
"sumber. DevStack akan menarik layanan dari git master kecuali jika "
"dikonfigurasikan untuk mengklon dari cabang stabil (misal. stable/pike)."

msgid ""
"By grouping the changes per module you can also construct the chain or "
"dependencies by the hierarchy of the components and always keep the API "
"changes last as that will enable the new functionality and that change will "
"depend on everything else you needed to touch for your design."
msgstr ""
"Dengan mengelompokkan perubahan per modul, Anda juga dapat membuat rantai "
"atau dependensi berdasarkan hierarki komponen dan selalu mempertahankan "
"perubahan API yang terakhir karena itu akan mengaktifkan fungsionalitas baru "
"dan perubahan itu akan bergantung pada segala hal lain yang perlu Anda "
"sentuh untuk desain Anda."

msgid ""
"Changes that are not related to any feature implementation or bug report can "
"be uploaded but are less welcomed by reviewers."
msgstr ""
"Perubahan yang tidak terkait dengan implementasi fitur atau laporan bug "
"dapat diunggah tetapi kurang disambut oleh pengulas."

msgid "Checking Out Others' Changes"
msgstr "Memeriksa Perubahan Lain"

msgid "Cherry-picking"
msgstr "Cherry-picking"

msgid "Cleaning up iSCSI volumes"
msgstr "Membersihkan volume iSCSI"

msgid "Clearing temporary LVM mounts"
msgstr "Menghapus mount LVM sementara"

msgid "Code & Documentation Contributor Guide"
msgstr "Code & Documentation Contributor Guide"

msgid "Code and Documentation Contributors"
msgstr "Kode dan Kontributor Dokumentasi"

msgid ""
"Communication is underrated, but crucial when it comes to participating in "
"an open source community. We have several tools that we use for online and "
"offline communication, which we encourage you to use."
msgstr ""
"Komunikasi diremehkan, tetapi penting dalam hal berpartisipasi dalam "
"komunitas open source. Kami memiliki beberapa alat yang kami gunakan untuk "
"komunikasi online dan offline, yang kami anjurkan untuk Anda gunakan."

msgid ""
"Core reviewers have additional voting choices aside from the basic set. Like "
"the basic set, the numbers map to a simple system of meaning:"
msgstr ""
"Peninjau inti memiliki pilihan suara tambahan selain dari perangkat dasar. "
"Seperti himpunan dasar, angka memetakan ke sistem makna yang sederhana:"

msgid "DATABASE_PASSWORD"
msgstr "DATABASE_PASSWORD"

msgid "Database clean-up"
msgstr "Pembersihan basis data"

msgid "Depends-On Tag"
msgstr "Depends-On Tag"

msgid "Deploying DevStack"
msgstr "Pengerahan DevStack"

msgid ""
"DevStack is a modular set of scripts that can be run to deploy a basic "
"OpenStack cloud for use as a demo or test environment. The scripts can be "
"run on a single node that is baremetal or a virtual machine. It can also be "
"configured to deploy to multiple nodes. DevStack deployment takes care of "
"tedious tasks like configuring the database and message queueing system, "
"making it possible for developers to quickly and easily deploy an OpenStack "
"cloud."
msgstr ""
"DevStack adalah sekumpulan skrip modular yang dapat dijalankan untuk "
"menggunakan cloud OpenStack dasar untuk digunakan sebagai demo atau "
"lingkungan pengujian. Skrip dapat dijalankan pada satu node yang baremetal "
"atau mesin virtual. Itu juga dapat dikonfigurasi untuk digunakan ke beberapa "
"node. Penyebaran DevStack menangani tugas-tugas yang membosankan seperti "
"mengkonfigurasi database dan sistem antrian pesan, sehingga memungkinkan "
"bagi pengembang untuk secara cepat dan mudah menggunakan cloud OpenStack."

msgid ""
"DevStack uses the code in those directories to run the OpenStack services so "
"any change may be tested by making a code change in the project's directory "
"and then by restarting the project's service through systemd."
msgstr ""
"DevStack menggunakan kode di direktori tersebut untuk menjalankan layanan "
"OpenStack sehingga setiap perubahan dapat diuji dengan membuat perubahan "
"kode di direktori proyek dan kemudian dengan me-restart layanan proyek "
"melalui systemd."

msgid ""
"DevStack's full documentation can be found `here <https://docs.openstack.org/"
"devstack/latest>`_."
msgstr ""
"Dokumentasi lengkap DevStack dapat ditemukan `here <https://docs.openstack."
"org/devstack/latest>`_."

msgid ""
"Developers need an easy way to deploy an OpenStack cloud to do functional "
"and interoperability testing of changes. This is the purpose of DevStack."
msgstr ""
"Pengembang membutuhkan cara mudah untuk menggunakan cloud OpenStack untuk "
"melakukan pengujian perubahan fungsional dan interoperabilitas. Ini adalah "
"tujuan dari DevStack."

msgid ""
"Each graph shows how many matches were found for that fingerprint over the "
"past 10 days. It also provides a link to both the launchpad page for the "
"bug, and the kibana dashboard for the underlying elastic-search query used "
"for the fingerprint."
msgstr ""
"Setiap grafik menunjukkan berapa banyak kecocokan yang ditemukan untuk "
"fingerprint itu selama 10 hari terakhir. Ini juga menyediakan tautan ke "
"halaman launchpad untuk bug, dan dasbor kibana untuk kueri elastic-search "
"yang digunakan untuk fingerprint."

msgid "Each project's database is created and populated"
msgstr "Setiap database proyek dibuat dan diisi"

msgid ""
"Enhance the automatic testing the community does on every patch submitted to "
"gerrit"
msgstr ""
"Tingkatkan pengujian otomatis yang dilakukan komunitas pada setiap patch "
"yang dikirimkan ke gerrit"

msgid ""
"Even if you have a chain of patches you still need to keep code changes and "
"related tests in one patch as you cannot guarantee that both land in time "
"for a release."
msgstr ""
"Bahkan jika Anda memiliki rantai tambalan Anda masih perlu menyimpan "
"perubahan kode dan tes terkait dalam satu patch karena Anda tidak dapat "
"menjamin bahwa keduanya tiba pada waktunya untuk rilis."

msgid ""
"Following is a list of the commands that you need to know for your first "
"contribution:"
msgstr ""
"Berikut ini adalah daftar perintah yang perlu Anda ketahui untuk kontribusi "
"pertama Anda:"

msgid ""
"Further down the file is the ``Using milestone-proposed branches`` section. "
"These are the variables that can be changed if you wish to clone a branch "
"other than master for one or more projects."
msgstr ""
"Lebih jauh ke bawah file adalah bagian ``Using milestone-proposed "
"branches``. Ini adalah variabel yang dapat diubah jika Anda ingin "
"mengkloning cabang selain master untuk satu atau lebih proyek."

msgid "General Information"
msgstr "Informasi Umum"

msgid "Gerrit Topics"
msgstr "Topik Gerrit"

msgid "Gerrit Web Editor"
msgstr "Editor Web Gerrit"

msgid "Gerrit allows you:"
msgstr "Gerrit memungkinkan Anda:"

msgid "Get an overview of the available projects for practice"
msgstr "Dapatkan ikhtisar proyek yang tersedia untuk praktik"

msgid "Get guidelines on how to use them"
msgstr "Dapatkan panduan tentang cara menggunakannya"

msgid "Get reviews on your changes proposed to OpenStack repositories"
msgstr ""
"Dapatkan ulasan tentang perubahan yang Anda usulkan ke repositori OpenStack"

msgid "Getting and Configuring DevStack"
msgstr "Mendapatkan dan Mengkonfigurasi DevStack"

msgid ""
"Git is a version control system that we use to track changes to our source "
"code and documentation."
msgstr ""
"Git adalah sistem kontrol versi yang kami gunakan untuk melacak perubahan "
"pada kode sumber dan dokumentasi kami."

msgid ""
"Here is an example of what that process would look like. In this example a "
"change is made to Cinder's LVM driver:"
msgstr ""
"Ini adalah contoh bagaimana proses itu akan terlihat. Dalam contoh ini "
"perubahan dibuat untuk driver LVM Cinder:"

msgid "How to Become a Patch Guru?"
msgstr "Bagaimana cara menjadi Patch Guru?"

msgid "How to Handle Chains?"
msgstr "Bagaimana Cara Menangani Rantai (Chains) ?"

msgid "How to Structure Your Changes?"
msgstr "Bagaimana Menyusun Perubahan Anda?"

msgid "How to Use the Sandbox Projects"
msgstr "Cara Menggunakan Proyek Sandbox"

msgid "Hypervisor clean-up"
msgstr "Pembersihan hypervisor"

msgid ""
"If OpenStack was successfully deployed by DevStack you should be able to "
"point a web browser at the IP specified by ``HOST_IP`` in ``local.conf`` and "
"access Horizon."
msgstr ""
"Jika OpenStack berhasil digunakan oleh DevStack Anda harus dapat mengarahkan "
"browser web ke IP yang ditentukan oleh ``HOST_IP`` di ``local.conf`` dan "
"mengakses Horizon."

msgid ""
"If successful, the Git response message will contain a URL you can use to "
"track your changes."
msgstr ""
"Jika berhasil, respons pesan Git akan berisi URL yang dapat digunakan untuk "
"penelusuran perubahan Anda."

msgid ""
"If you can, test the code! In some cases you may not have access to the "
"specific hardware needed, but in general you should be able to test the "
"changes or look at the zuul build of the documentation so that you are doing "
"more than just looking at the code or documentation change."
msgstr ""
"Jika bisa, uji kodenya! Dalam beberapa kasus Anda mungkin tidak memiliki "
"akses ke perangkat keras tertentu yang diperlukan, tetapi secara umum Anda "
"harus dapat menguji perubahan atau melihat zuul build dari dokumentasi "
"sehingga Anda melakukan lebih dari sekadar melihat kode atau perubahan "
"dokumentasi."

msgid ""
"If you have questions about the way something is phrased or done, or have "
"found some other issue the easiest way to let the author of the patch know "
"is to comment on that place inline. The inline comments are posted "
"collectively when you hit the 'Reply' button and add your vote on the "
"patchset."
msgstr ""
"Jika Anda memiliki pertanyaan tentang cara sesuatu diungkapkan atau "
"dilakukan, atau telah menemukan beberapa masalah lain, cara termudah untuk "
"memberi tahu pembuat patch adalah mengomentari tempat tersebut secara "
"inline. Komentar sebaris diposting secara kolektif ketika Anda menekan "
"tombol 'Reply' dan menambahkan suara Anda di patchset."

msgid ""
"If you need to make further changes to the same review, you can commit them "
"using::"
msgstr ""
"Jika Anda perlu membuat perubahan lebih lanjut pada ulasan yang sama, Anda "
"bisa mengkomitnya using::"

msgid ""
"If you only need to modify the top patch in the chain that can be done the "
"same way as you update individual patches."
msgstr ""
"Jika Anda hanya perlu memodifikasi patch teratas dalam rantai yang dapat "
"dilakukan dengan cara yang sama seperti Anda memperbarui patch individu."

msgid ""
"If you review a patch you are automatically added to the list of reviewers."
msgstr ""
"Jika Anda mengulas patch Anda secara otomatis ditambahkan ke daftar pengulas."

msgid ""
"If you're interested in more of the theory and history behind the project, "
"this talk from the Juno OpenStack Summit provides a good overview: `Elastic "
"Recheck - Tools for Finding Race Conditions in OpenStack <https://www."
"youtube.com/watch?v=Byo26Pioq1Y>`_"
msgstr ""
"Jika Anda lebih tertarik pada teori dan sejarah di balik proyek ini, ceramah "
"dari Juno OpenStack Summit ini memberikan gambaran yang bagus: `Elastic "
"Recheck - Tools for Finding Race Conditions in OpenStack <https://www."
"youtube.com/watch?v=Byo26Pioq1Y>`_"

msgid ""
"If your commit depends on a change which has been updated since you started "
"your work, and you need to get the latest patchset from that change, you can "
"cherry-pick your own changes on top of it:"
msgstr ""
"Jika komit Anda bergantung pada perubahan yang telah diperbarui sejak Anda "
"memulai pekerjaan Anda, dan Anda perlu mendapatkan patchset terbaru dari "
"perubahan itu, Anda dapat memilih perubahan sendiri di atasnya:"

msgid ""
"If your patch gets a -1 it is not bad news, it just means you need to do a "
"little more work."
msgstr ""
"Jika patch Anda mendapatkan -1, itu bukan berita buruk, itu hanya berarti "
"Anda perlu melakukan lebih banyak pekerjaan."

msgid ""
"Improvement to either the code or documentation should be part of a larger "
"effort, like if you would like to fix typos in documentation then you should "
"do it for a larger block, like a whole guide. It is also preferred to report "
"a story with tasks for a work item like this that can be tracked later."
msgstr ""
"Peningkatan baik kode atau dokumentasi harus menjadi bagian dari upaya yang "
"lebih besar, seperti jika Anda ingin memperbaiki kesalahan ketik dalam "
"dokumentasi maka Anda harus melakukannya untuk blok yang lebih besar, "
"seperti seluruh panduan. Lebih disukai melaporkan berita dengan tugas untuk "
"item pekerjaan seperti ini yang dapat dilacak nanti."

msgid ""
"In case of code refactoring work which makes the code more readable and "
"easier to maintain by restructuring methods and deleting unused code "
"snippets it is highly encouraged to consult with the project team and report "
"a story in StoryBoard first and then upload the relevant changes to Gerrit "
"for review."
msgstr ""
"Dalam kasus pekerjaan refactoring kode yang membuat kode lebih mudah dibaca "
"dan dipelihara dengan metode restrukturisasi dan menghapus snipet kode yang "
"tidak digunakan, sangat disarankan untuk berkonsultasi dengan tim proyek dan "
"melaporkan sebuah cerita di StoryBoard terlebih dahulu dan kemudian "
"mengunggah perubahan yang relevan ke Gerrit untuk ulasan."

msgid ""
"In case you use the 'Depends-On' tag you need to download all the changes "
"for a feature implementation or documentation change to test the feature or "
"build the documentation with all the changes applied. Git will not take care "
"of handling the dependencies automatically in this case."
msgstr ""
"Jika Anda menggunakan tag 'Depends-On', Anda perlu mengunduh semua perubahan "
"untuk implementasi fitur atau perubahan dokumentasi untuk menguji fitur atau "
"membuat dokumentasi dengan semua perubahan yang diterapkan. Git tidak akan "
"menangani penanganan dependensi secara otomatis dalam kasus ini."

msgid ""
"In general, its best to avoid over using this gerrit capability because each "
"interaction with the patch- new patchsets, comments, CI system votes, etc.- "
"will send an email notification to every reviewer on the patch."
msgstr ""
"Secara umum, yang terbaik untuk menghindari penggunaan kemampuan gerrit ini "
"karena setiap interaksi dengan patch - patch baru, komentar, suara sistem "
"CI, dll. - akan mengirim pemberitahuan email ke setiap pengulas di patch."

msgid ""
"In rare occasions when there is no good logical breakdown for a change and "
"your patch can grow to a thousand lines or more. In some cases it is "
"acceptable as you cannot extract the related test changes to another patch "
"for instance, but it's not highly recommended."
msgstr ""
"Dalam kesempatan yang jarang terjadi ketika tidak ada gangguan logis yang "
"baik untuk perubahan dan patch Anda dapat tumbuh hingga seribu baris atau "
"lebih. Dalam beberapa kasus itu dapat diterima karena Anda tidak dapat "
"mengekstraksi perubahan tes terkait ke patch lain misalnya, tetapi itu tidak "
"sangat dianjurkan."

msgid ""
"In some cases when you break down the required changes to smaller blocks you "
"cannot avoid having direct dependencies between them that prevents you from "
"having independent changes. You need to organize your changes in a chain to "
"maintain the dependencies which requires some additional care when you work "
"with these changes."
msgstr ""
"Dalam beberapa kasus ketika Anda memecah perubahan yang diperlukan untuk "
"blok yang lebih kecil Anda tidak dapat menghindari ketergantungan langsung "
"di antara mereka yang mencegah Anda memiliki perubahan independen. Anda "
"perlu mengatur perubahan Anda dalam rantai untuk mempertahankan dependensi "
"yang memerlukan perhatian tambahan saat Anda bekerja dengan perubahan ini."

msgid ""
"In the case of complex feature implementation work when you need to "
"introduce changes to multiple modules of the same project or multiple "
"projects you need to be very careful with managing the dependencies."
msgstr ""
"Dalam kasus kerja implementasi fitur yang kompleks ketika Anda perlu "
"memperkenalkan perubahan pada beberapa modul dari proyek yang sama atau "
"beberapa proyek, Anda harus sangat berhati-hati dalam mengelola dependensi."

msgid "Introduction"
msgstr "Pengantar"

msgid ""
"It is a good practice to group changes by modules in a project, for instance "
"virt driver changes, compute manager and api changes in case of OpenStack "
"Compute."
msgstr ""
"Ini adalah praktik yang baik untuk mengelompokkan perubahan berdasarkan "
"modul dalam suatu proyek, misalnya perubahan virt driver, manajer komputasi "
"dan perubahan api dalam kasus OpenStack Compute."

msgid ""
"It is possible to check out other contributors' patches from Gerrit and even "
"`make changes to them <https://docs.openstack.org/project-team-guide/review-"
"the-openstack-way.html#modifying-a-change>`_; however, you should always "
"discuss any changes with the contributor before you start working on their "
"patch."
msgstr ""
"Dimungkinkan untuk memeriksa patch kontributor lain dari Gerrit dan bahkan "
"`make changes to them <https://docs.openstack.org/project-team-guide/review-"
"the-openstack-way.html#modifying-a-change>`_; namun, Anda harus selalu "
"mendiskusikan perubahan apa pun dengan kontributor sebelum mulai mengerjakan "
"tambalannya."

msgid ""
"It is possible to edit your patch in the gerrit web interface and publish "
"the change without making the change locally. This is not generally advised "
"for larger code updates since it doesn't automatically update your local "
"working branch. In some cases, where the patch is basically ready to merge "
"aside from a small pep8 failure- whitespace at the end of line, needing to "
"wrap a line, etc- this gerrit feature can be convenient to make a quick edit "
"and publish the change without having to go through the entire 'git add', "
"'git commit --amend', 'git review' process."
msgstr ""
"Dimungkinkan untuk mengedit patch Anda di antarmuka web gerrit dan "
"menerbitkan perubahan tanpa membuat perubahan secara lokal. Ini biasanya "
"tidak disarankan untuk pembaruan kode yang lebih besar karena tidak secara "
"otomatis memperbarui cabang kerja lokal Anda. Dalam beberapa kasus, di mana "
"patch pada dasarnya siap untuk bergabung selain dari small pep8 failure- "
"whitespace di akhir baris, perlu untuk membungkus sebuah garis (wrap a "
"line), fitur gerrit etc- ini dapat memudahkan untuk melakukan edit cepat dan "
"menerbitkan perubahan tanpa harus melalui seluruh proses 'git add', 'git "
"commit --amend', 'git review'."

msgid ""
"It is recommended before proceeding further to set-up passwords and IP "
"addresses for the environment in which you are running DevStack. This is "
"done by configuring the ``local.conf`` file in DevStack."
msgstr ""
"Disarankan sebelum melanjutkan lebih jauh untuk mengatur kata sandi dan "
"alamat IP untuk lingkungan di mana Anda menjalankan DevStack. Ini dilakukan "
"dengan mengkonfigurasi file ``local.conf`` di DevStack."

msgid ""
"It is similar for code improvements. As the community is large and world-"
"wide we have coding guidelines, but the style of each individual can still "
"be very different. We don't enforce a particular coding style, therefore "
"changes related to fix that are less welcomed and are sources of very "
"opinionated arguments that should be avoided."
msgstr ""
"Ini serupa untuk peningkatan kode. Karena komunitasnya besar dan luas di "
"dunia, kami memiliki pedoman pengkodean, tetapi gaya masing-masing individu "
"masih bisa sangat berbeda. Kami tidak menerapkan gaya pengkodean tertentu, "
"oleh karena itu perubahan yang terkait dengan perbaikan yang kurang disambut "
"dan merupakan sumber argumen yang sangat beralasan yang harus dihindari."

msgid ""
"Know how to structure a patch that is easier for community members to review"
msgstr ""
"Ketahui cara menyusun patch yang lebih mudah bagi anggota komunitas untuk "
"meninjau"

msgid ""
"Know how to structure a patch that makes it easier to maintain throughout "
"the review process"
msgstr ""
"Ketahui cara menyusun patch yang membuatnya lebih mudah untuk dipertahankan "
"selama proses peninjauan"

msgid "Launchpad is deprecated and will be superseeded by StoryBoard."
msgstr "Launchpad sudah usang dan akan digantikan oleh StoryBoard."

msgid ""
"Logs for the running services are also able to be viewed through systemd. To "
"display the logs for the Cinder Volume service the following command could "
"be used:"
msgstr ""
"Log untuk layanan yang berjalan juga dapat dilihat melalui systemd. Untuk "
"menampilkan log untuk layanan Cinder Volume, perintah berikut dapat "
"digunakan:"

msgid ""
"Longer patches require more time to review; wherever you can, keep the "
"length reasonable. And where you can't, you can help the reviewers by adding "
"code comments and writing a detailed commit message to describe the changes "
"you introduced in your patch."
msgstr ""
"Patch yang lebih lama membutuhkan lebih banyak waktu untuk meninjau; "
"dimanapun Anda bisa, pertahankan panjang yang wajar. Dan di mana Anda tidak "
"bisa, Anda dapat membantu pengulas dengan menambahkan komentar kode dan "
"menulis pesan komit rinci untuk menggambarkan perubahan yang Anda "
"perkenalkan di patch Anda."

msgid "Make quick changes to your patches in the webui"
msgstr "Buat perubahan cepat ke patch Anda di webui"

msgid ""
"Most often, some deadline has passed and since no more changes are being "
"accepted till the new release development begins, the patch is `being held "
"<https://docs.openstack.org/project-team-guide/review-the-openstack-way."
"html#procedural-minus-2>`_."
msgstr ""
"Paling sering, beberapa tenggat waktu telah berlalu dan karena tidak ada "
"lagi perubahan yang diterima sampai pengembangan rilis baru dimulai, patch "
"itu `being held <https://docs.openstack.org/project-team-guide/review-the-"
"openstack-way.html#procedural-minus-2>`_."

msgid ""
"On some distributions you may need to also set the ``HOST_IP``. Whether this "
"is necessary will depend on what naming convention is used for network "
"interfaces in your operating system."
msgstr ""
"Pada beberapa distribusi Anda mungkin perlu mengatur ``HOST_IP``. Apakah ini "
"perlu tergantung pada konvensi penamaan apa yang digunakan untuk antarmuka "
"jaringan di sistem operasi Anda."

msgid ""
"Once testing and development of your code change is complete you will want "
"to push your code change to Gerrit for review. Since the projects in ``/opt/"
"stack`` are already synced to their respective git repository you can "
"configure `git review <https://docs.openstack.org/contributors/code-and-"
"documentation/using-gerrit.html>`_, commit your change and upload the "
"changes to Gerrit."
msgstr ""
"Setelah pengujian dan pengembangan perubahan kode Anda selesai, Anda akan "
"ingin mendorong perubahan kode Anda ke Gerrit untuk ditinjau. Karena proyek-"
"proyek di ``/opt/stack`` sudah disinkronkan ke repositori git masing-masing, "
"Anda dapat mengonfigurasi `git review <https://docs.openstack.org/"
"contributors/code-and-documentation/using-gerrit.html>`_, komit perubahan "
"Anda dan unggah perubahan ke Gerrit."

msgid ""
"Once you have your ``local.conf`` file configured executing DevStack is "
"quite easy."
msgstr ""
"Setelah Anda memiliki file ``local.conf`` Anda yang dikonfigurasikan saat "
"menjalankan DevStack cukup mudah."

msgid ""
"Once you've constructed a query and checked in on elastic-search you should "
"create a yaml file in the queries directory of the elastic-recheck git repo. "
"The file name is the launchpad bug number for the bug and the contents are "
"the elastic-search query."
msgstr ""
"Setelah Anda membuat kueri dan memeriksa elastic-search, Anda harus membuat "
"file yaml di direktori kueri repo git elastic-rechecki. Nama file adalah "
"nomor bug launchpad untuk bug dan isinya adalah permintaan elastic-recheck."

msgid ""
"Once you've identified a message in the logs that can be used for "
"fingerprinting you need to turn that into an elastic-search query. You can "
"use any of the existing fingerprints as an example: `openstack-infra/elastic-"
"recheck <https://git.openstack.org/cgit/openstack-infra/elastic-recheck/tree/"
"queries>`_"
msgstr ""
"Setelah Anda mengidentifikasi pesan dalam log yang dapat digunakan untuk "
"fingerprint, Anda harus mengubahnya menjadi permintaan elastic-search. Anda "
"dapat menggunakan salah satu fingerprints yang ada sebagai contoh: "
"`openstack-infra/elastic-recheck <https://git.openstack.org/cgit/openstack-"
"infra/elastic-recheck/tree/queries>`_"

msgid ""
"Once your changes have been saved to local.conf you are ready to deploy an "
"OpenStack cloud with DevStack."
msgstr ""
"Setelah perubahan Anda disimpan ke local.conf, Anda siap untuk deploy "
"(mengerahkan)  cloud OpenStack dengan DevStack."

msgid ""
"Only the person that voted the -2 can remove the vote and it will persist on "
"all new patchsets."
msgstr ""
"Hanya orang yang memilih -2 yang dapat menghapus suara dan itu akan tetap "
"ada pada semua patchset baru."

msgid "OpenStack Documentation Contributor Guide"
msgstr "Panduan Kontributor Dokumentasi OpenStack"

msgid "Patch Chains"
msgstr "Rantai patch"

msgid "Patch Chains, Depends-On Tag and Gerrit Topics"
msgstr "Patch Chains, Depends-On Tag dan Gerrit Topics"

msgid ""
"Project services are all registered with systemd. Each service is prefixed "
"with ``devstack@``. Therefore you may verify through systemd that the Cinder "
"Volume process is working with a command like:"
msgstr ""
"Layanan proyek semuanya terdaftar dengan systemd. Setiap layanan diawali "
"dengan ``devstack@``.  Karena itu Anda dapat memverifikasi melalui systemd "
"bahwa proses Cinder Volume bekerja dengan perintah seperti:"

msgid "Pushing A Change"
msgstr "Mendorong Perubahan"

msgid "RABBIT_PASSWORD"
msgstr "RABBIT_PASSWORD"

msgid ""
"Read the `Summary of Git commit message structure <https://wiki.openstack."
"org/wiki/GitCommitMessages?%22Summary%20of%20Git%20commit%20message"
"%20structure%22#Summary_of_Git_commit_message_structure>`_ for best "
"practices on writing the commit message. When you are ready to send your "
"changes for review use::"
msgstr ""
"Membaca `Summary of Git commit message structure <https://wiki.openstack.org/"
"wiki/GitCommitMessages?%22Summary%20of%20Git%20commit%20message%20structure"
"%22#Summary_of_Git_commit_message_structure>`_ untuk praktik terbaik dalam "
"menulis pesan komit. Saat Anda siap mengirim perubahan untuk ulasan use::"

msgid "Removal of .pyc files"
msgstr "Penghapusan file .pyc"

msgid "Removing configuration files for projects from /etc"
msgstr "Menghapus file konfigurasi untuk proyek dari /etc"

msgid "Removing log files"
msgstr "Menghapus file log"

msgid "Report recurring bugs so that you don't need to manually 'recheck'"
msgstr ""
"Laporkan bug berulang sehingga Anda tidak perlu 'recheck' secara manual"

msgid "Request reviews from specific community members"
msgstr "Minta ulasan dari anggota komunitas tertentu"

msgid "Required packages (like mysql and rabbitmq) are installed"
msgstr "Paket yang diperlukan (seperti mysql dan rabbitmq) diinstal"

msgid "Reviewing Changes"
msgstr "Meninjau Perubahan"

msgid ""
"Reviewing changes is often suggested as a way to get started on a project. "
"Whether this is how you choose to get started or not, it's an important "
"community activity. See `How to Review Changes the OpenStack Way`_ for more "
"detailed guidance on when to use which votes on a change review."
msgstr ""
"Meninjau perubahan sering disarankan sebagai cara untuk memulai suatu "
"proyek. Apakah ini cara Anda memilih untuk memulai atau tidak, ini merupakan "
"kegiatan komunitas yang penting. Lihat `How to Review Changes the OpenStack "
"Way`_  untuk petunjuk lebih rinci tentang kapan harus menggunakan suara mana "
"pada tinjauan perubahan."

msgid ""
"Reviewing large patches is very inconvenient and time consuming therefore we "
"always suggest to break down your changes into smaller blocks."
msgstr ""
"Meninjau patch besar sangat merepotkan dan makan waktu karena itu kami "
"selalu menyarankan untuk memecah perubahan Anda menjadi blok yang lebih "
"kecil."

msgid ""
"Running ``unstack.sh`` is the first thing to try in the case that a DevStack "
"run fails. If subsequent runs fail a more thorough removal of DevStack "
"components may be done with the following command:"
msgstr ""
"Menjalankan ``unstack.sh`` adalah hal pertama yang harus dicoba jika "
"DevStack run gagal. Jika proses selanjutnya gagal, penghapusan komponen "
"DevStack yang lebih menyeluruh dapat dilakukan dengan perintah berikut:"

msgid "SandBox Git Repository"
msgstr "SandBox Git Repository"

msgid "SandBox Project on Launchpad"
msgstr "Proyek SandBox di Launchpad"

msgid "Sandbox Project on StoryBoard"
msgstr "Proyek Sandbox di StoryBoard"

msgid ""
"Since systemd accepts wildcards, the status of all services associated with "
"DevStack can be displayed with:"
msgstr ""
"Karena systemd menerima wildcard, status semua layanan yang terkait dengan "
"DevStack dapat ditampilkan dengan:"

msgid ""
"Sometimes there might be people you need to weigh in on your patch because "
"they have a vested interest or are helping mentor you. The easiest way of "
"letting them know you have uploaded a new patch or patchset is to add them "
"as reviewers in the gerrit web-ui. You can look them up by name, gerrit "
"email address, ssh user name, or gerrit id."
msgstr ""
"Terkadang mungkin ada orang yang perlu Anda pertimbangkan di patch Anda "
"karena mereka memiliki minat pribadi atau membantu mentor Anda. Cara "
"termudah untuk memberi tahu mereka bahwa Anda telah mengunggah patch atau "
"patch baru adalah dengan menambahkannya sebagai pengulas di gerrit web-ui. "
"Anda dapat mencarinya berdasarkan nama, alamat email gerrit, nama pengguna "
"ssh, atau id gerrit."

msgid "Stopping DevStack"
msgstr "Menghentikan DevStack"

msgid "Stopping the project services, mysql and rabbitmq"
msgstr "Menghentikan layanan proyek, mysql dan rabbitmq"

msgid "Testing Changes with DevStack"
msgstr "Testing Changes dengan DevStack"

msgid ""
"The 'Depends-On' tag is a marker on your changes and when used a patch "
"cannot be merged until all its dependencies are landed."
msgstr ""
"Tag 'Depends-On' adalah penanda pada perubahan Anda dan ketika digunakan "
"patch tidak dapat digabungkan hingga semua dependensinya mendarat (landed)."

msgid "The OpenStack Services are registered and started"
msgstr "Layanan OpenStack terdaftar dan dimulai"

msgid "The OpenStack projects are cloned into /opt/stack/"
msgstr "Proyek OpenStack dikloning ke /opt/stack/"

msgid "The Right Content"
msgstr "Konten yang Tepat"

msgid "The Right Size"
msgstr "Ukuran yang Tepat"

msgid ""
"The Sandbox repository and projects are maintained by community members with "
"occasional cleanup. Please help us with the housekeeping and clean up your "
"work, when you are finished with your practice and feel comfortable using "
"the tool."
msgstr ""
"Repositori dan proyek Sandbox dikelola oleh anggota masyarakat dengan "
"pembersihan sesekali. Tolong bantu kami dengan tata housekeeping dan "
"membersihkan pekerjaan Anda, ketika Anda selesai dengan latihan Anda dan "
"merasa nyaman menggunakan alat ini."

msgid ""
"The `OpenStack Documentation Contributor Guide <https://docs.openstack.org/"
"doc-contrib-guide/index.html>`_ describes how to contribute to OpenStack "
"documentation. It contains information on `writing <https://docs.openstack."
"org/doc-contrib-guide/writing-docs.html>`_, `building <https://docs."
"openstack.org/doc-contrib-guide/docs-builds.html>`_, and `reviewing <https://"
"docs.openstack.org/doc-contrib-guide/docs-review.html>`_ documents, as well "
"as best practices and `API documentation guidelines <https://docs.openstack."
"org/doc-contrib-guide/api-guides.html>`_."
msgstr ""
"The `OpenStack Documentation Contributor Guide <https://docs.openstack.org/"
"doc-contrib-guide/index.html>`_ menjelaskan cara berkontribusi pada "
"dokumentasi OpenStack. Ini berisi informasi tentang dokumen `writing "
"<https://docs.openstack.org/doc-contrib-guide/writing-docs.html>`_, "
"`building <https://docs.openstack.org/doc-contrib-guide/docs-builds.html>`_, "
"and `reviewing <https://docs.openstack.org/doc-contrib-guide/docs-review."
"html>`_, serta praktik terbaik dan `API documentation guidelines <https://"
"docs.openstack.org/doc-contrib-guide/api-guides.html>`_."

msgid ""
"The ``admin`` password will be set to the value you put in your ``local."
"conf`` file for ``ADMIN_PASSWORD``"
msgstr ""
"Kata sandi ``admin`` akan ditetapkan ke nilai yang Anda masukkan dalam file "
"``local.conf`` Anda untuk ``ADMIN_PASSWORD``"

msgid ""
"The above command and subsequent command examples assume you are still in "
"the root directory of your DevStack clone."
msgstr ""
"Perintah di atas dan contoh-contoh perintah selanjutnya menganggap Anda "
"masih berada di direktori root klon DevStack Anda."

msgid ""
"The basic set of values contributors have to vote with on a patch is: -1, 0, "
"or +1. These values correspond to a relatively simple system."
msgstr ""
"Rangkaian nilai dasar yang harus dipilih oleh kontributor pada patch adalah: "
"-1, 0, atau +1. Nilai-nilai ini sesuai dengan sistem yang relatif sederhana."

msgid "The change ID can be found on the web UI of Gerrit:"
msgstr "ID perubahan dapat ditemukan di UI web Gerrit:"

msgid "The change ID is the same as in the previous case."
msgstr "ID perubahan sama seperti pada kasus sebelumnya."

msgid ""
"The following command needs to be run as a user with sudo access and "
"NOPASSWD configured."
msgstr ""
"Perintah berikut perlu dijalankan sebagai pengguna dengan akses sudo dan "
"NOPASSWD dikonfigurasi."

msgid ""
"The heart of open source is the people who are participating in a community "
"and it is no different in case of OpenStack either."
msgstr ""
"Inti dari open source adalah orang-orang yang berpartisipasi dalam suatu "
"komunitas dan tidak ada bedanya dengan OpenStack."

msgid ""
"The patch submitted is a duplicate or at odds with another patch submitted."
msgstr ""
"Patch yang dikirimkan adalah duplikat atau bertentangan (duplicate or odd) "
"dengan patch lain yang dikirimkan."

msgid ""
"The tag can be applied to patches proposed for the same repository as well. "
"In that case the changes are separate enough to be kept independent which "
"means that if you need to fix changes from review comments you can do it on "
"a per patch basis. It is also true for rebasing each patch."
msgstr ""
"Tag dapat diterapkan ke tambalan yang diusulkan untuk repositori yang sama "
"juga. Dalam hal ini perubahannya cukup terpisah untuk tetap independen yang "
"berarti bahwa jika Anda perlu memperbaiki perubahan dari komentar ulasan "
"Anda dapat melakukannya berdasarkan setiap patch. Hal ini juga berlaku untuk "
"rebasing setiap patch."

msgid ""
"The tools that we are using in the community can look complicated if you are "
"not familiar with them. To help you practice before you use them in action "
"we are providing sandbox environments for you where you can practice all the "
"steps we describe in this guide."
msgstr ""
"Alat yang kami gunakan di komunitas bisa terlihat rumit jika Anda tidak "
"terbiasa dengannya. Untuk membantu Anda berlatih sebelum menggunakannya "
"dalam aksi, kami menyediakan lingkungan sandbox untuk Anda tempat Anda dapat "
"mempraktikkan semua langkah yang kami jelaskan dalam panduan ini."

msgid ""
"There are multiple options to choose from depending on the structure of your "
"design. You can either organize the changes in patch chains or you can use "
"the 'Depends-On' tag."
msgstr ""
"Ada beberapa opsi untuk dipilih tergantung pada struktur desain Anda. Anda "
"dapat mengatur perubahan dalam rantai patch atau Anda dapat menggunakan tag "
"'Depends-On'."

msgid ""
"There is a `Sandbox project <https://launchpad.net/openstack-dev-sandbox>`_ "
"available there which is created to track bugs and issues related to the "
"openstack-dev/sandbox repository."
msgstr ""
"Ada proyek `Sandbox project <https://launchpad.net/openstack-dev-sandbox>`_ "
"tersedia di sana yang dibuat untuk melacak bug dan masalah yang berkaitan "
"dengan repositori openstack-dev/sandbox."

msgid ""
"There is an issue with the approach taken in the patch and it needs to be "
"discussed with a larger group, likely in a meeting."
msgstr ""
"Ada masalah dengan pendekatan yang diambil dalam patch dan perlu "
"didiskusikan dengan kelompok yang lebih besar, kemungkinan dalam pertemuan."

msgid ""
"This chapter will guide you through of all the tools and processes that we "
"are using to develop, test, maintain, and document the projects in OpenStack."
msgstr ""
"Bab ini akan memandu Anda melalui semua alat dan proses yang kami gunakan "
"untuk mengembangkan, menguji, memelihara, dan mendokumentasikan proyek di "
"OpenStack."

msgid ""
"This command cleans up the OpenStack installation that was performed on the "
"node.  This includes:"
msgstr ""
"Perintah ini membersihkan instalasi OpenStack yang dilakukan pada node. Ini "
"termasuk:"

msgid ""
"This guide won't go into the details of tracing through the logs of a run "
"and finding a good fingerprint, since that's quite involved, dependent on "
"the job you're looking at, and already documented in a few places including:"
msgstr ""
"Panduan ini tidak akan membahas rincian penelusuran log dan menemukan "
"fingerprint yang baik, karena cukup terlibat, tergantung pada pekerjaan yang "
"Anda lihat, dan sudah didokumentasikan di beberapa tempat termasuk:"

msgid ""
"This is a good way to help tracking related changes, let that be a feature "
"implementation, bugfix or documentation work."
msgstr ""
"Ini adalah cara yang baik untuk membantu melacak perubahan terkait, biarkan "
"itu menjadi implementasi fitur, perbaikan bug atau pekerjaan dokumentasi."

msgid ""
"This is a quick start version. For a more in depth description of how to "
"clone, create a patch and push the change, directions can be `found here "
"<https://docs.openstack.org/infra/manual/developers.html#starting-work-on-a-"
"new-project>`_"
msgstr ""
"Ini adalah versi mulai cepat. Untuk deskripsi yang lebih mendalam tentang "
"cara mengkloning, membuat patch dan mendorong perubahan, arah bisa ditemukan "
"disini `found here <https://docs.openstack.org/infra/manual/developers."
"html#starting-work-on-a-new-project>`_"

msgid "This section allows you to:"
msgstr "Bagian ini memungkinkan Anda untuk:"

msgid ""
"This section assumes you have completed :doc:`../common/setup-gerrit` guide."
msgstr ""
"Bagian ini menganggap Anda telah menyelesaikan panduan :doc:`../common/setup-"
"gerrit`."

msgid "This section assumes you have completed :doc:`/common/zuul-status`"
msgstr ""
"Bagian ini menganggap Anda telah menyelesaikan :doc:`/common/zuul-status`"

msgid ""
"This section will guide you through how to create patches that people will "
"want to review."
msgstr ""
"Bagian ini akan memandu Anda melalui cara membuat patch yang ingin ditinjau "
"orang."

msgid ""
"This will commit the changes under the same set of changes you issued "
"earlier. Notice that in order to send your latest version for review, you "
"will still need to call::"
msgstr ""
"Ini akan melakukan perubahan di bawah set perubahan yang sama yang Anda "
"keluarkan sebelumnya. Perhatikan bahwa untuk mengirim versi terbaru Anda "
"untuk ditinjau, Anda masih perlu call::"

msgid ""
"To access the Gerrit Web Editor click on the icon that looks like a pencil "
"writing on paper next to the patch set number at the top of a Gerrit Code "
"Review page for a file."
msgstr ""
"Untuk mengakses Gerrit Web Editor klik pada ikon yang terlihat seperti "
"pensil yang menulis di atas kertas di sebelah nomor set patch di bagian atas "
"halaman Gerrit Code Review untuk sebuah file."

msgid "To check the differences between your branch and the repository::"
msgstr "Untuk memeriksa perbedaan antara cabang Anda dan  repository::"

msgid "To check the files that have been updated in your branch::"
msgstr "Untuk memeriksa file yang telah diperbarui di branch:: Anda."

msgid "To clone a copy of some repository::"
msgstr "Untuk mengkloning beberapa repositori ::"

msgid ""
"To create your development branch (substitute branch_name for a name of your "
"choice). It's better to create a new branch for each patch than working from "
"master::"
msgstr ""
"Untuk membuat cabang pengembangan Anda (gantikan branch_name dengan nama "
"pilihan Anda). Lebih baik membuat cabang baru untuk setiap patch daripada "
"bekerja dari master::"

msgid ""
"To download the full chain you need to download the top patch and Git will "
"automatically download all the dependent patches in the chain."
msgstr ""
"Untuk mengunduh rantai penuh, Anda perlu mengunduh patch teratas dan Git "
"akan secara otomatis mengunduh semua patch dependen dalam rantai."

msgid ""
"To get DevStack you will need to clone it from the ``devstack`` repository "
"under ``openstack-dev``."
msgstr ""
"Untuk mendapatkan DevStack Anda harus mengkloningnya dari repositori "
"``devstack`` di bawah ``openstack-dev``."

msgid ""
"To modify a patch within a chain you will need to use interactive rebase:"
msgstr ""
"Untuk memodifikasi patch dalam rantai Anda perlu menggunakan rebase "
"interaktif:"

msgid ""
"To shutdown a DevStack instance running on a node the following command "
"should be used:"
msgstr ""
"Untuk mematikan instance DevStack yang berjalan pada node, perintah berikut "
"harus digunakan:"

msgid ""
"To simplify future interaction with your deployment you will want to set the "
"following variables:"
msgstr ""
"Untuk menyederhanakan interaksi di masa depan dengan penyebaran Anda, Anda "
"ingin mengatur variabel berikut:"

msgid "Tracking a new bug in elastic-recheck"
msgstr "Melacak bug baru di elastic-recheck"

msgid "Tracking your Changes"
msgstr "Melacak Perubahan Anda"

msgid ""
"Until you click 'Reply' and vote on the patch, any inline comments you've "
"made exist as drafts."
msgstr ""
"Sampai Anda mengklik 'Reply' dan memberi suara pada patch, setiap komentar "
"sebaris yang Anda buat ada sebagai konsep."

msgid ""
"Using DevStack to develop and test changes is easy. Development can be done "
"in the project clones under ``/opt/stack/<project name>``. Since the "
"projects are clones of the project's git repository a branch can be made and "
"development can take place."
msgstr ""
"Menggunakan DevStack untuk mengembangkan dan menguji perubahan itu mudah. "
"Pengembangan dapat dilakukan di klon proyek di bawah  ``/opt/stack/<project "
"name>``. Karena proyek adalah klon dari repositori git proyek, cabang dapat "
"dibuat dan pengembangan dapat dilakukan."

msgid "Using Elastic Recheck"
msgstr "Menggunakan Elastic Recheck"

msgid "Using Gerrit"
msgstr "Menggunakan Gerrit"

msgid "Verifying Your DevStack Deployment"
msgstr "Memverifikasi DevStack Deployment Anda"

msgid ""
"We do not differentiate between the different types of contributions such as "
"code or documentation therefore you will find guidance in this chapter for "
"all types."
msgstr ""
"Kami tidak membedakan antara berbagai jenis kontribusi seperti kode atau "
"dokumentasi karena itu Anda akan menemukan panduan dalam bab ini untuk semua "
"jenis kontribusi."

msgid "What is DevStack"
msgstr "Apa itu DevStack"

msgid "What is elastic-recheck"
msgstr "Apa itu elastic-recheck"

msgid "What to do if a test job fails"
msgstr "Apa yang harus dilakukan jika pekerjaan uji gagal"

msgid ""
"When you are working on implementing a new feature or adding documentation "
"to an already existing one it is easy to get carried away by the work itself "
"and forget about the unwritten rules of constructing your changes."
msgstr ""
"Ketika Anda sedang berupaya mengimplementasikan fitur baru atau menambahkan "
"dokumentasi ke yang sudah ada, mudah terbawa oleh karya itu sendiri dan "
"melupakan aturan tidak tertulis dalam menyusun perubahan Anda."

msgid ""
"When you encounter a failure that's not being tracked by elastic-recheck and "
"you've looked through the logs to determine that it's not being caused by "
"the proposed change and is affecting other changes you can propose a new "
"elastic-recheck fingerprint."
msgstr ""
"Ketika Anda menemukan kegagalan yang tidak dilacak oleh elastic-recheck dan "
"Anda telah memeriksa log untuk menentukan bahwa itu tidak disebabkan oleh "
"perubahan yang diajukan dan memengaruhi perubahan lain, Anda dapat "
"mengusulkan fingerprint elastic-recheck baru."

msgid ""
"When you have a chain Gerrit helps you by listing all the commit titles in "
"the 'Related Changes' column on the top right corner of the Gerrit UI. The "
"titles are also links which help you navigate between the changes to review "
"them when you upload a new version."
msgstr ""
"Ketika Anda memiliki rantai, Gerrit membantu Anda dengan mendaftar semua "
"judul komit di kolom 'Related Changes' di sudut kanan atas Gerrit UI. Judul "
"itu juga tautan yang membantu Anda menavigasi di antara perubahan untuk "
"meninjau mereka ketika Anda mengunggah versi baru."

msgid ""
"When you have changes in multiple project repositories you can mark "
"dependent patches with the 'Depends-On' tag. The tag will appear as a link "
"in the commit message which helps you and also the reviewers to track and "
"navigate between the dependencies of your changes."
msgstr ""
"Ketika Anda memiliki perubahan dalam beberapa repositori proyek, Anda dapat "
"menandai patch dependen dengan tag 'Depends-On'. Tag akan muncul sebagai "
"tautan dalam pesan komit yang membantu Anda dan juga pengulas untuk melacak "
"dan menavigasi antara dependensi perubahan Anda."

msgid ""
"When you submit a patch to gerrit and zuul returns the test results for the "
"jobs it ran, sometimes one of those tests fails. Most of the time this "
"indicates there is an issue with your proposed change and the tests are "
"catching it. Sometimes the test run might have tripped over an underlying "
"pre-existing bug in OpenStack. Additionally, some times the infrastructure "
"for running the tests might have had a failure. To figure this out you'll "
"always need to look at the logs from the failed job to understand what's "
"happening."
msgstr ""
"Ketika Anda mengirimkan patch ke gerrit dan zuul mengembalikan hasil tes "
"untuk pekerjaan yang dijalankannya, terkadang salah satu dari tes itu gagal. "
"Sebagian besar waktu ini menunjukkan ada masalah dengan perubahan yang Anda "
"usulkan dan tes menangkapnya. Kadang-kadang uji coba mungkin telah "
"tersandung bug yang sudah ada sebelumnya di OpenStack. Selain itu, beberapa "
"kali infrastruktur untuk menjalankan tes mungkin mengalami kegagalan. Untuk "
"mengetahuinya, Anda harus selalu melihat log dari pekerjaan yang gagal untuk "
"memahami apa yang terjadi."

msgid ""
"When you upload changes in a chain only the patches that got updated will be "
"uploaded. This also means that the review scores on lower patches in the "
"chain will be untouched."
msgstr ""
"Saat Anda mengunggah perubahan dalam rantai, hanya patch yang diperbarui "
"akan diunggah. Ini juga berarti bahwa skor ulasan pada patch yang lebih "
"rendah dalam rantai tidak akan tersentuh."

msgid ""
"When your work item grows above a particular size and you need to upload "
"multiple patches it is crucial to structure it well in case of both patch "
"chains and independent changes."
msgstr ""
"Ketika item pekerjaan Anda tumbuh di atas ukuran tertentu dan Anda perlu "
"mengunggah beberapa patch, sangat penting untuk menyusunnya dengan baik jika "
"terjadi perubahan patch dan perubahan independen."

msgid ""
"While there is no magic number try to **keep the size of your changes as "
"small as possible**, but under a few hundreds of lines changed total. "
"Patches that are test heavy with little code change require as much effort "
"as code heavy changes."
msgstr ""
"Meskipun tidak ada angka ajaib, cobalah untuk  **keep the size of your "
"changes as small as possible**,  tetapi di bawah beberapa ratus baris "
"berubah total. Patch yang uji berat dengan sedikit perubahan kode "
"membutuhkan usaha sebanyak perubahan berat kode."

msgid ""
"You can find a `Sandbox <https://storyboard-dev.openstack.org/#!/"
"project/2>`_ project in the tool that provides all the functionalities to "
"you as any of the other active projects."
msgstr ""
"Anda dapat menemukan proyek `Sandbox <https://storyboard-dev.openstack.org/"
"#!/project/2>`_ dalam alat yang menyediakan semua fungsi kepada Anda sebagai "
"salah satu dari proyek aktif lainnya."

msgid ""
"You can find a `sandbox Git repository <https://git.openstack.org/cgit/"
"openstack-dev/sandbox>`_ where you can practice the Git commands before you "
"put together a patch to resolve a bug or implement a new functionality."
msgstr ""
"Anda dapat menemukan `sandbox Git repository <https://git.openstack.org/cgit/"
"openstack-dev/sandbox>`_ di mana Anda bisa mempraktikkan perintah Git "
"sebelum Anda membuat patch untuk menyelesaikan bug atau mengimplementasikan "
"fungsionalitas baru."

msgid "You can find instructions on how to use Git in the :ref:`git` section."
msgstr ""
"Anda dapat menemukan petunjuk tentang cara menggunakan Git di bagian :ref:"
"`git`."

msgid ""
"You can find the same respositories using the search function here: "
"`OpenStack git repository browser <https://git.openstack.org/cgit>`_"
msgstr ""
"Anda dapat menemukan repositori yang sama menggunakan fungsi pencarian di "
"sini: `OpenStack git repository browser <https://git.openstack.org/cgit>`_"

msgid "You can find these pages at:"
msgstr "Anda dapat menemukan halaman ini di:"

msgid ""
"You can see the current status of the bugs being tracked by elastic recheck "
"at: `Elastic Recheck <http://status.openstack.org/elastic-recheck/index."
"html>`_"
msgstr ""
"Anda dapat melihat status terkini dari bug yang dilacak oleh elastic recheck "
"di: `Elastic Recheck <http://status.openstack.org/elastic-recheck/index."
"html>`_"

msgid ""
"You can upload your changes to the sandbox repository and review it on "
"Gerrit as it is described in the :ref:`gerrit` section."
msgstr ""
"Anda dapat mengunggah perubahan Anda ke repositori sandbox dan memeriksanya "
"di Gerrit seperti yang dijelaskan di bagian :ref:`gerrit`."

msgid ""
"You get permissions to perform all the operations in the Sandbox project for "
"the sake of practice. When you join a project as a contributor you will have "
"limited access to the functionalities as there are actions only core "
"reviewers can perform. You can find information about these in the "
"respective sections of the Contributor Guide."
msgstr ""
"Anda mendapatkan izin untuk melakukan semua operasi di proyek Sandbox demi "
"praktik. Ketika Anda bergabung dengan sebuah proyek sebagai kontributor, "
"Anda akan memiliki akses terbatas ke fungsi karena ada tindakan yang hanya "
"dapat dilakukan oleh pengulas inti. Anda dapat menemukan informasi tentang "
"ini di bagian masing-masing Contributor Guide."

msgid ""
"You have the option to specify a topic for your changes when you upload them "
"for review. While Gerrit topics will not add dependency to your patches you "
"can apply a search based on the topic that will show you all the relevant "
"changes in all the projects where there are patches with the same topic. "
"Gerrit will also show them to you in the 'Same Topic' column on the top "
"right corner of the page of a review."
msgstr ""
"Anda memiliki opsi untuk menentukan topik untuk perubahan Anda saat Anda "
"mengunggahnya untuk ditinjau. Sementara topik Gerrit tidak akan menambah "
"ketergantungan pada patch Anda, Anda bisa menerapkan pencarian berdasarkan "
"topik yang akan menunjukkan semua perubahan yang relevan di semua proyek di "
"mana ada patch dengan topik yang sama. Gerrit juga akan menunjukkannya "
"kepada Anda di kolom 'Same Topic' di sudut kanan atas halaman ulasan."

msgid ""
"You need as many '^' as the number of the patch you want to edit first from "
"the top of the chain. Gerrit also provides you options to edit the patch "
"itself or only the commit message and a few more for more advanced changes, "
"like modifying the author."
msgstr ""
"Anda membutuhkan '^' sebanyak jumlah patch yang ingin Anda edit pertama dari "
"atas rantai. Gerrit juga menyediakan opsi untuk mengedit patch itu sendiri "
"atau hanya pesan komit dan beberapa lainnya untuk perubahan lebih lanjut, "
"seperti memodifikasi pembuat (author)."

msgid ""
"You should also check any elastic search queries using kibana at: `Logstash "
"Search <http://logstash.openstack.org/>`_"
msgstr ""
"Anda juga harus memeriksa kueri elastic search menggunakan kibana di: "
"`Logstash Search <http://logstash.openstack.org/>`_"

msgid ""
"`+1`_: Looks good to me, but someone else must approve. This does not mean "
"that there is nothing to comment on, just that there aren't any issues that "
"would block the merging of the patch. You can still make comments on "
"nitpicky things the patch owner can address if others find issues with the "
"patch. These comments might also be something to address in a followup patch "
"as opposed to another patchset."
msgstr ""
"`+ 1`_: Terlihat bagus untuk saya, tetapi orang lain harus menyetujuinya. "
"Ini tidak berarti bahwa tidak ada yang perlu dikomentari, hanya saja tidak "
"ada masalah yang akan memblokir penggabungan patch. Anda masih dapat membuat "
"komentar tentang hal-hal yang bersifat nitpicky yang bisa ditangani pemilik "
"patch jika orang lain menemukan masalah dengan patch itu. Komentar ini "
"mungkin juga sesuatu untuk diatasi dalam patch tindak lanjut sebagai lawan "
"dari patch lain."

msgid ""
"`+2`_: Looks good to me (core reviewer). Depending on the project team and "
"repository, merging a patch will require at least one +2 vote if not two +2 "
"votes."
msgstr ""
"`+2`_: Terlihat bagus untuk saya (core reviewer). Bergantung pada tim proyek "
"dan repositori, penggabungan patch akan membutuhkan setidaknya satu suara +2 "
"jika tidak dua suara +2."

msgid ""
"`-1`_: This patch needs further work before it can be merged. A -1 is "
"usually given when the reviewer sees some issue that needs to be fixed "
"before the patch can be merged. The issues the author needs to address "
"would, ideally, have inline comments posted on them unless there is some "
"larger issue. If there is something wrong with the overall approach, you are "
"able to leave an overall comment with the vote to raise your concerns."
msgstr ""
"`-1`_: Patch ini perlu kerja lebih lanjut sebelum bisa digabung. A -1 "
"biasanya diberikan ketika pengulas melihat beberapa masalah yang perlu "
"diperbaiki sebelum patch dapat digabungkan. Masalah yang penulis perlu "
"atasi, idealnya, memiliki komentar sebaris yang diposting padanya kecuali "
"ada masalah yang lebih besar. Jika ada yang salah dengan pendekatan "
"keseluruhan, Anda dapat meninggalkan komentar keseluruhan dengan suara untuk "
"meningkatkan kekhawatiran Anda."

msgid ""
"`-2`_: Do not merge. This score does not often appear and when it does, it's "
"for a good reason:"
msgstr ""
"`-2`_: Jangan gabung. Skor ini tidak sering muncul dan ketika itu terjadi, "
"itu karena alasan yang bagus:"

msgid ""
"`0`_: No score. This is the default score when replying to a patchset. "
"Generally it's kept as the vote when someone has a question about the "
"patchset or doesn't have a fully formed opinion of the patchset yet - it "
"requires more time, testing, or investigation."
msgstr ""
"`0`_: Tidak ada skor. Ini adalah skor default ketika membalas patchset. "
"Biasanya ini disimpan sebagai suara ketika seseorang memiliki pertanyaan "
"tentang patchset atau belum memiliki opini yang lengkap tentang patchset - "
"itu membutuhkan lebih banyak waktu, pengujian, atau penyelidikan."

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

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

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

msgid "depending on which jobs you're interested in."
msgstr "tergantung pada pekerjaan yang Anda minati."

msgid ""
"elastic-recheck also has a page to show how many failures were encountered "
"that do not have a matching fingerprint. Typically the more failures that go "
"uncategorized the more unstable the gate is (and OpenStack as a whole)."
msgstr ""
"elastic-recheck juga memiliki halaman untuk menunjukkan berapa banyak "
"kegagalan yang ditemui yang tidak memiliki fingerprint yang cocok. Biasanya "
"semakin banyak kegagalan yang tidak dikategorikan, semakin tidak stabil gate "
"tersebut (dan OpenStack secara keseluruhan)."

msgid ""
"elastic-recheck is a tool used to track failures in test jobs. It keeps a "
"repository of fingerprints for known bugs that are affecting jobs in the "
"gate. It is then used to both track the rates those bugs are being found and "
"also to leave comments in gerrit and in IRC when it has found a known bug "
"fingerprint in a failure."
msgstr ""
"elastic-recheck adalah alat yang digunakan untuk melacak kegagalan dalam "
"pekerjaan pengujian. Itu menyimpan repositori fingerprint untuk bug yang "
"diketahui yang mempengaruhi pekerjaan di gate. Kemudian digunakan untuk "
"melacak tingkat bug yang ditemukan dan juga untuk meninggalkan komentar di "
"gerrit dan di IRC ketika telah menemukan bug fingerprint yang diketahui "
"gagal."

msgid ""
"elastic-recheck is built on top of an ELK (`Elastic Search`_, `Logstash`_, "
"`Kibana`_) stack where we use Logstash to store all logs from CI jobs in an "
"Elastic Search cluster. We also host a `Kibana dashboard`_ which can be used "
"to run queries on the cluster and interacts with the data. elastic-recheck "
"queries the elastic-search cluster for the fingerprints."
msgstr ""
"elastic-recheck dibangun di atas stack ELK (`Elastic Search`_, `Logstash`_, "
"`Kibana`_) di mana kami menggunakan Logstash untuk menyimpan semua log dari "
"pekerjaan CI di cluster Elastic Search. Kami juga meng-host `Kibana "
"dashboard`_ yang dapat digunakan untuk menjalankan kueri di kluster dan "
"berinteraksi dengan data. elastic-recheck kueri pencarian elastis untuk "
"fingerprint."

msgid "etc."
msgstr "etc."

msgid "mysql and rabbitmq are configured"
msgstr "mysql dan rabbitmq dikonfigurasi"