在 Weblate 中回報問題

Weblate 問題追蹤器 託管於 Github。

歡迎報告任何問題,或提出改進建議。我們準備了各種範本,可以輕鬆地指導您完成問題報告。

備註

如果您在 Weblate 中發現了安全問題,請查閱下方的 產品漏洞報告 部分。

如果您不確定您的缺陷報告或功能請求,您可以嘗試 Weblate 討論

無障礙性問題

無障礙問題應使用無障礙問題範本。良好的回報應包含受影響的頁面或工作流程、重現步驟、預期及實際行為、瀏覽器與作業系統、使用中的輔助技術,以及問題是否會在純鍵盤導覽時發生。

維護者會以 accessibility 標示無障礙問題回報。分流處理時,請依核心工作流程受到的影響及可用的替代方案選擇優先程度:

  • 阻斷:無法完成核心工作流程。

  • 高:核心工作流程難以完成,但有替代方案。

  • 中:非核心工作流程難以完成或行為不一致。

  • 低:不會阻礙工作流程的輕微問題或細節改善問題。

Weblate 的無障礙目標及回報指引請參閱 ACCESSIBILITY.md

使用 AI 建立 issues

若您要求 AI 工具尋找 Weblate 或其模組的問題,則 必須 在回報中揭露此事。

向我們回報前,您也必須仔細再次確認結果,驗證問題確實存在,且運作情況與 AI 所述一致。AI 工具經常產生不準確或虛構的結果。

直接複製貼上 AI 產生的報告,通常 不是好主意。這類報告往往過度冗長、未切中要點,也常包含虛構細節。若您確實透過 AI 發現問題,並親自驗證為真,請自行撰寫報告,依您的理解說明問題。如此可及早過濾 AI 產生的不準確內容與捏造問題,避免浪費更多人的時間。

我們嚴肅看待安全性回報,因此會優先調查每一份回報。這項工作耗費時間與心力,也會排擠其他有意義的工作。虛假或捏造的安全性問題會妨礙真正的專案工作,浪費我們的時間與資源。

對專案提交捏造虛假報告的使用者會立即遭到停權。

問題生命週期

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"]; }