{"title":"Saran untuk penyumbang baru","version":"6.0","locale":"id","docname":"internals/contributing/new-contributors","url":"/id/6.0/internals/contributing/new-contributors/","canonical":"https://djangodocs.dev/id/6.0/internals/contributing/new-contributors/","summary":"Peyumbang baru dan tidak yakin apa yang harus dilakukan? Ingin membantu tetapi tidak tahu bagaimana memulai? Ini adalah bagian untuk anda. Bangun dan berjalan! Jika…","html":"

Saran untuk penyumbang baruLink to this heading#

\n

Peyumbang baru dan tidak yakin apa yang harus dilakukan? Ingin membantu tetapi tidak tahu bagaimana memulai? Ini adalah bagian untuk anda.

\n\n

Halaman ini mengandung saran umum pada cara anda dapat membantu Django, dan bagaimana mencapainya.

\n

Jika anda mencari acuan pada rincian dari membuat bantuan kode, lihat dokumentasi Kode bantuan.

\n
\n

Langkah pertamaLink to this heading#

\n

Mulai dengan langkah-langkah ini untuk menemukan pengolahan pengembangan Django.

\n
\n

Tiket triaseLink to this heading#

\n

If an unreviewed ticket reports a bug, try and reproduce it. If you can\nreproduce it and it seems valid, make a note that you confirmed the bug and\naccept the ticket. Make sure the ticket is filed under the correct component\narea. Consider writing a patch that adds a test for the bug's behavior, even if\nyou don't fix the bug itself. See more at How can I help with development?.

\n
\n
\n

Tinjau tambalan tiket yang diterimaLink to this heading#

\n

This will help you build familiarity with the codebase and processes. Mark the\nappropriate flags if a patch needs docs or tests. Look through the changes a\npatch makes, and keep an eye out for syntax that is incompatible with older but\nstill supported versions of Python. Run the tests and make sure they pass.\nWhere possible and relevant, try them out on a database other than SQLite.\nLeave comments and feedback!

\n
\n
\n

Jaga agar patch lama tetap mutakhirLink to this heading#

\n

Oftentimes the codebase will change between a patch being submitted and the\ntime it gets reviewed. Make sure it still applies cleanly and functions as\nexpected. Updating a patch is both useful and important! See more on\nDaftar centang bantuan.

\n
\n
\n

Tulis beberapa dokumentasiLink to this heading#

\n

Django's documentation is great but it can always be improved. Did you find a\ntypo? Do you think that something should be clarified? Go ahead and suggest a\ndocumentation patch! See also the guide on\nMenulis dokumentasi.

\n\n
\n
\n

Tanda tangai Persetujuan Lisensi PenyumbangLink to this heading#

\n

The code that you write belongs to you or your employer. If your contribution\nis more than one or two lines of code, you have the option to sign the CLA.\nSee the Contributor License Agreement FAQ for a more thorough explanation.

\n
\n
\n
\n

PanduanLink to this heading#

\n

Sbagai seorang pendatang baru pada proyek besar, sangat mudah mengalami frustasi. Ini adalah beberapa saran untuk membuat pekerjaan anda pada Django lebih berguna dan bermanfaat.

\n
\n

Ambil kawasan subjekLink to this heading#

\n

This should be something that you care about, that you are familiar with or\nthat you want to learn about. You don't already have to be an expert on the\narea you want to work on; you become an expert through your ongoing\ncontributions to the code.

\n
\n
\n

Menganalisa kontek dan riwayat tiketLink to this heading#

\n

Trac tidak mutlak; konteks hanya sama pentingnya dengan kata-kata. Ketika membaca Trac, anda perlu memperhitungkan siapa mengatakan hal-hal, dan kapan mereka katakan. Dukungan untuk sebuah ide dua tahun lalu tidak berarti bahwa ide akan masih mempunyai dukungan. Anda juga butuh perhatian ke siapa belum bicara -- sebagai contoh, jika seorang pembantu berpengalaman belum saat ini terlibat dalam sebuah obrolan, kemudian sebuah tiket mungkin tidak memiliki dukungan yang butuhkan untuk masuk ke dalam Django.

\n
\n
\n

Mulai kecilLink to this heading#

\n

Hal ini lebih mudah mendapatkan umpanbalik pada masalah kecil daripada yang besar. Lihat easy pickings.

\n
\n
\n

Konfirmasi dukungan sebelum menarik di tugas besarLink to this heading#

\n

Ini berarti mendapatkan seseorang lain untuk menegaskan bahwa sebuah kesalahan adalah nyata sebelum anda memperbaiki masalah, dan memastikan bahwa ada pemufakatan pada fitur yang diajukan sebelum anda pergi menerapkan itu.

\n
\n
\n

Berani! Berikan masukan!Link to this heading#

\n

Terkadang itu dapat menakutkan untuk menaruh pendapat anda ke dunia dan mengatakan "tiket ini benar" atau "tambalan ini butuh bekerja", tetapi itu hanya jalan proyek maju kedepan. Sumbangan dari komunitas luas Django akhirnya mempunyai dampak yang lebih hebat daripada satu orang. Kami tidak dapat melakukannya tanpa anda!

\n
\n
\n

Waspada ketika menandai hal-hal "Ready For Check-in"Link to this heading#

\n

If you're really not certain if a ticket is ready, don't mark it as such. Leave\na comment instead, letting others know your thoughts. If you're mostly certain,\nbut not completely certain, you might also try asking on the\n#contributing-getting-started channel in the Django Discord server to\nsee if someone else can confirm your suspicions.

\n
\n
\n

Tunggu untuk umpan balik, dan tanggapi untuk umpan balik yang anda terimaLink to this heading#

\n

Jika anda tidak yakin jika tiket sudah siap, jangan menandainya. Tinggalkan komentar sebagai gantinya, membiatkan lainnya mengetahui pikiran anda. Jika anda sangat yakin, tetapi tidak sepenuhnya yakin, anda mungkin juga coba menanyakan pada IRC untuk melihat jika lainnya dapat menegaskan kecurigaan anda.

\n
\n
\n

Bersikaplah tegasLink to this heading#

\n

When we say "PEP 8, and must have docs and tests", we mean it. If a patch\ndoesn't have docs and tests, there had better be a good reason. Arguments like\n"I couldn't find any existing tests of this feature" don't carry much weight.\nWhile it may be true, that means you have the extra-important job of writing\nthe very first tests for that feature, not that you get a pass from writing\ntests altogether.

\n
\n
\n

Harap sabarLink to this heading#

\n

It's not always easy for your ticket or your patch to be reviewed quickly. This\nisn't personal. There are a lot of tickets and pull requests to get through.

\n

Keeping your patch up to date is important. Review the ticket on Trac to ensure\nthat the Needs tests, Needs documentation, and Patch needs improvement\nflags are unchecked once you've addressed all review comments.

\n

Remember that Django has an eight-month release cycle, so there's plenty of\ntime for your patch to be reviewed.

\n

Akhirnya, pengigat waktu-baik dapat membantu. Lihat contributing code FAQ untuk ide disini.

\n
\n
","rootId":"advice-for-new-contributors","toc":[{"title":"Langkah pertama","anchor":"first-steps","children":[{"title":"Tiket triase","anchor":"triage-tickets","children":[]},{"title":"Tinjau tambalan tiket yang diterima","anchor":"review-patches-of-accepted-tickets","children":[]},{"title":"Jaga agar patch lama tetap mutakhir","anchor":"keep-old-patches-up-to-date","children":[]},{"title":"Tulis beberapa dokumentasi","anchor":"write-some-documentation","children":[]},{"title":"Tanda tangai Persetujuan Lisensi Penyumbang","anchor":"sign-the-contributor-license-agreement","children":[]}]},{"title":"Panduan","anchor":"guidelines","children":[{"title":"Ambil kawasan subjek","anchor":"pick-a-subject-area","children":[]},{"title":"Menganalisa kontek dan riwayat tiket","anchor":"analyze-tickets-context-and-history","children":[]},{"title":"Mulai kecil","anchor":"start-small","children":[]},{"title":"Konfirmasi dukungan sebelum menarik di tugas besar","anchor":"confirm-support-before-engaging-in-a-big-task","children":[]},{"title":"Berani! Berikan masukan!","anchor":"be-bold-leave-feedback","children":[]},{"title":"Waspada ketika menandai hal-hal \"Ready For Check-in\"","anchor":"be-cautious-when-marking-things-ready-for-check-in","children":[]},{"title":"Tunggu untuk umpan balik, dan tanggapi untuk umpan balik yang anda terima","anchor":"wait-for-feedback-and-respond-to-feedback-that-you-receive","children":[]},{"title":"Bersikaplah tegas","anchor":"be-rigorous","children":[]},{"title":"Harap sabar","anchor":"be-patient","children":[]}]}],"breadcrumbs":[{"docname":"internals/index","title":"Dalam Django","url":"/id/6.0/internals/"},{"docname":"internals/contributing/index","title":"Membantu untuk Django","url":"/id/6.0/internals/contributing/"}],"prev":{"docname":"internals/contributing/index","title":"Membantu untuk Django","url":"/id/6.0/internals/contributing/"},"next":{"docname":"internals/contributing/sprint-quickstart","title":"Sprint quickstart guide","url":"/id/6.0/internals/contributing/sprint-quickstart/"},"formats":{"html":"/id/6.0/internals/contributing/new-contributors/","markdown":"/id/6.0/internals/contributing/new-contributors.md","json":"/id/6.0/internals/contributing/new-contributors.json"},"source":"https://github.com/django/django/blob/stable/6.0.x/docs/internals/contributing/new-contributors.txt","official":"https://docs.djangoproject.com/id/6.0/internals/contributing/new-contributors/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10","1.9"],"inLocales":["en","sv","zh-hans","ga","fr","ja","id","it","pt-br","ko","es","el","pl"]}