Phabricator/zh

Phabricator是一个开源的软件开发平台. 在维基媒体中，所有项目使用Phabricator用于项目管理、-{zh-hans:软件错误汇报;zh-hant:軟體臭蟲回報}-和测试请求（请参见$1）. The Wikimedia Foundation maintains its own instance of Phabricator to maintain the software for all of the Wikimedia projects and related tools.

Phabricator is similar to Github in that it is used for tracking issues and project management. It is not used for storing and maintaining code (Wikimedia uses Gerrit for this).

前往维基媒体Phabricator

Overview
Here is a general overview on how Phabricator works:
 * Phabricator consists of Tasks (similar to Github issues).
 * Tasks are not specific to one project or "repository" and instead use Tags to relate themselves with the Project(s) that are working on them.
 * Tasks can be one of three Types: Generic, Bug Report, and Feature.
 * Tasks have a Status of either: Open, Resolved, In Progress, Stalled, Declined, or Invalid.
 * Tasks have a Priority to indicate their importance. These include: Unbreak Now!, Needs Triage, High, Medium, Low, and Lowest.
 * Tasks can have Subscribers, or users that receive notifications when they are changed.
 * Tasks can be Assigned To users to indicate who is working on them.
 * Tasks can specify a Due Date they are expected to be completed.
 * Tasks have a Description to explain what they are about. Anyone with an account can edit a Task description if it needs to be updated.
 * Tasks can have Related Tasks like Subtasks and Parent Tasks. Highest-parent tasks are often named and tagged as an Epic.
 * Tasks can have Related Objects like Commits, Mocks, and Revisions.
 * Users can add Tokens to a Task to indicate their appreciation for it. These are similar to the emoji reactions you can add to issues on Github.
 * Users can discuss Tasks by Commenting on them.
 * Phabricator has Projects to organize the types of things that are worked on.
 * Projects use Workboards to organize Tasks and which they are working on
 * Projects have Members or users that are associated with the project and Watchers who receive notifications when the Tasks of a project change.
 * Projects can consist of Subprojects.
 * GerritBot posts comments to Tasks about what code is being changed on Gerrit related to a Task.

入门
如果您有问题，请查阅-{zh-hans:帮助;zh-hant:說明}-页面. 非常欢迎您提出问题.

有关Phabricator是什么，能做什么的基本概述，参看教程视频（如果您的带宽有限，）.

常见的第一个动作是：


 * 创建您的-{zh-hans:账户;zh-hant:帳號}-
 * 创建一个任务
 * 如果您管理-{zh-hans:项目;zh-hant:專案}-：创建一个-{zh-hans:项目;zh-hant:專案}-，并了解有关在Phabricator上进行-{zh-hans:项目;zh-hant:專案}-管理.
 * 礼仪
 * 了解如何使用Phabricator. 在我们的伺服器实例尽可能如您所愿的进行测试. （不保證可以百分之百運行） 在查看文檔及短片

每周更新/维护时段
Phabricator没有发布版本，并因此由我们决定我们要与上游版本有多接近. There is a weekly window for updates and other maintenance tasks on Wednesdays at 5:00PM Pacific (Thursday Midnight, 0:00 UTC) (check your timezone) and users will get redirected to Phabricator/Maintenance. 我们不是每周都必须更新Phabricator的，但我们保留该时段以便按需使用，基本上每个月两次，这取决于上游修复的显要-{zh-hans:错误;zh-hant:臭蟲}-的紧急性. 该时段的定期停机时间是0~30分钟.

有关特定-{zh-hans:错误;zh-hant:臭蟲}-与-{zh-hans:更改;zh-hant:變更}-，可查询「里程碑」下最新更新日期的已解决任务，并查阅对应的最新上游更新日志项.

参见

 * Test instance of Phabricator
 * Phabricator — technical information for administrators of Wikimedia Phabricator
 * 关键子页面
 * 关键子页面