Melaporkan isu di Weblate

Pelacak isu Weblate dihos di GitHub.

Jangan ragu untuk melaporkan isu yang Anda alami atau menyarankan perbaikan untuk Weblate di sana. Tersedia berbagai templat yang akan memandu Anda dengan mudah dalam melaporkan isu.

Catatan

Jika yang Anda temukan adalah isu keamanan di Weblate, silakan lihat Melaporkan isu keamanan.

Jika Anda tidak yakin tentang laporan kesalahan atau permintaan fitur, Anda dapat mencoba Diskusi Weblate.

Accessibility issues

Accessibility problems should use the accessibility issue template. A good report includes the affected page or workflow, reproduction steps, expected and actual behavior, browser and operating system, assistive technology in use, and whether the problem occurs with keyboard-only navigation.

Maintainers label accessibility reports with accessibility. During triage, use the impact on core workflows and available workarounds to choose priority:

  • Blocker: a core workflow cannot be completed.

  • High: a core workflow is difficult, but a workaround exists.

  • Medium: a non-core workflow is difficult or inconsistent.

  • Low: a minor issue or polish problem that does not block the workflow.

See ACCESSIBILITY.md for Weblate's accessibility target and reporting guidance.

Menggunakan AI untuk membuat isu

Jika Anda meminta alat AI untuk menemukan masalah di Weblate atau modulnya, Anda harus memastikan untuk mengungkapkan fakta ini dalam laporan Anda.

Anda juga harus memeriksa ulang temuan dengan hati-hati sebelum melaporkannya kepada kami untuk memastikan isu tersebut memang ada dan berfungsi persis seperti yang dikatakan AI. Alat berbasis AI seringkali menghasilkan hasil yang tidak akurat atau dibuat-buat.

Jarang merupakan ide yang baik untuk sekadar menyalin dan menempelkan laporan yang dihasilkan AI ke dalam proyek. Laporan yang dihasilkan tersebut biasanya terlalu panjang dan jarang langsung ke intinya (di samping rincian yang sering dibuat-buat). Jika Anda menemukan isu dengan AI dan telah memverifikasinya sendiri, tulis laporannya sendiri dan jelaskan isunya sebagaimana yang telah Anda pelajari. Ini memastikan ketidakakuratan dan isu yang dibuat-buat oleh AI terfilter lebih awal sebelum membuang-buang waktu orang lain.

Karena kami menganggap serius laporan keamanan, kami menyelidiki setiap laporan dengan prioritas. Pekerjaan ini menyita waktu dan energi, serta menghalangi kami melakukan pekerjaan penting lainnya. Isu keamanan palsu dan rekayasa justru menghalangi kami mengerjakan proyek yang sebenarnya dan membuat kami membuang-buang waktu dan sumber daya.

Kami segera memblokir pengguna yang mengirimkan laporan palsu yang dibuat-buat ke proyek tersebut.

Siklus hidup isu

digraph "Issue lifecycle" { graph [fontname = "sans-serif", fontsize=10, ranksep=0.6, newrank=true]; node [fontname = "sans-serif", fontsize=10, margin=0.15]; edge [fontname = "sans-serif", fontsize=10]; subgraph cluster_states { graph [color=white]; "Waiting for: Triage" [shape=box, fillcolor="#1fa385", fontcolor=white, style=filled]; "Waiting for: Demand" [shape=box, fillcolor="#1fa385", fontcolor=white, style=filled]; "Waiting for: Community" [shape=box, fillcolor="#1fa385", fontcolor=white, style=filled]; "Waiting for: Milestone" [shape=box, fillcolor="#1fa385", fontcolor=white, style=filled]; "Waiting for: Implementation" [shape=box, fillcolor="#1fa385", fontcolor=white, style=filled]; "Waiting for: Release" [shape=box, fillcolor="#1fa385", fontcolor=white, style=filled]; } "Issue created" [fillcolor="#144d3f", fontcolor=white, style=filled]; "Issue closed as not planned" [fillcolor="#cccccc", style=filled]; "Issue converted to a discussion" [fillcolor="#cccccc", style=filled]; "Issue resolved" [fillcolor="#144d3f", fontcolor=white, style=filled]; "Issue created" -> "Waiting for: Triage"; "Waiting for: Triage" -> "Waiting for: Community" [label="The issue is not clearly defined"]; "Waiting for: Triage" -> "Issue closed as not planned" [label="The issue is out of scope"]; "Waiting for: Triage" -> "Issue converted to a discussion" [label="The issue is merely a support request"]; "Waiting for: Triage" -> "Waiting for: Milestone" [label="Ready to to be worked on"]; "Waiting for: Community" -> "Waiting for: Triage" [label="Community feedback received"]; "Waiting for: Community" -> "Issue closed as not planned" [label="Lack of response"]; "Waiting for: Community" -> "Waiting for: Milestone" [label="Ready to to be worked on"]; "Waiting for: Community" -> "Waiting for: Demand" [label="Too narrow use case"]; "Waiting for: Demand" -> "Waiting for: Milestone" [label="Ready to to be worked on"]; "Waiting for: Demand" -> "Issue closed as not planned" [label="The issue is out of scope"]; "Waiting for: Milestone" -> "Waiting for: Implementation" [label="Milestone assigned issue will be worked on"]; "Waiting for: Implementation" -> "Waiting for: Release" [label="Issue implemented waiting for a release"]; "Waiting for: Release" -> "Issue resolved" [label="The solution for the issue has been released"]; }