故障管理/Phabricator禮儀

From mediawiki.org
This page is a translated version of the page Bug management/Phabricator etiquette and the translation is 14% complete.

請遵照以下的指引來使Phabricator 成爲一個具有生產力、和諧的代碼錯誤管理及願望請求平臺。

You must also follow the 行为准则 .

  • Comments should be directly related to reporting, confirming, evaluating the severity, or fixing the bug. Thoughts unrelated to the topic of the report (for example, meta-level discussions on priorities in general or on whether a new extension is wanted at all) should go to the appropriate mailing lists, wiki talk pages, or separate reports.
    • Criticize ideas, not people.[1] A healthy amount of constructive criticism and vibrant debate helps to improve our software and is encouraged.
    • Act in public. Unless you are reporting a security issue or you were asked to email somebody with specific information, place all technical information relating to a bug report in the report itself.
  • Report status and priority fields summarize and reflect reality and do not cause it. Read about the meaning of the Priority field values and, when in doubt, do not change them, but add a comment suggesting the change and convincing reasons for it.
  • Only manually assign a task to someone if they have given their prior agreement. It is up to developers (or their product managers) what they plan to work on.
  • Prefer using Phabricator usernames (e.g. @username) over a person's real name or other personal identifiers. To address both concerns regarding privacy and unnecessary confusion, when communicating on various tasks, pastes, phame posts, etc, please use Phabricator usernames. Even if you know individuals on a personal level (real name, etc.) they may not wish to have that information associated with their Phabricator username. It also presents a layer of confusion for other Phabricator users who are not aware of someone's real name or other personal identifiers.

如果您發現有人沒有遵照指引,請

  1. The first step is to contact them. This can be done through private email in minor cases, or in public in major cases to avoid any later assumptions of tolerated behavior.
    • Be informativeTell what they are doing what they should not do. If pertinent, make them aware of this document.
    • Be catalyticTell what they should do instead. Occasionally this may be encouraging and motivating, better than a dense list of "rules".
  2. In the case of persistent disregard of these guidelines, ping a Phabricator administrator in #wikimedia-releng connect on Wikimedia IRC or contact the bugwrangler and ask them to look into it. In case the disregard can be seen as unacceptable behavior defined by the Code of Conduct, the Code of Conduct committee will be informed.

文档声明

參見

参考资料