Bug management/Triage
 | This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
Bug triage refers to assuring quality of bug reports (tasks) in Wikimedia Phabricator. The process of triaging is explained in the Triage guide. The main job of triagers and the Bugsquad is to help users and developers in Phabricator. Triaging a bug report involves making sure that the bug report
- has enough information for developers and makes sense (steps to reproduce, potentially version or browser information if relevant)
- has not already been reported before (checking for duplicates)
- is filed in the correct place (associated project(s))
- has a sensible "Priority" field
We currently have a bugwrangler who triages bugs and organizes bug triage meetings to collectively prioritize, validate and assign bug reports, and to sometimes recruit developers to fix the bug or implement the enhancement. We announce the meetings ahead of time on wikitech-l and via Google Calendar and Twitter. Bug triage meetings are held in a public IRC channel, either #wikimedia-dev connect or #wikimedia-office connect. See MediaWiki on IRC for general information on IRC.
Triages currently take place about once a month, and the next triage will be announced here.
Next meeting
[edit]Currently no specific plans - propose a topic!
No technical knowledge needed, no obligations! It's a nice and easy way to get involved in the community or to give something back. See also How to triage.
Step by, say hello, and give it a try! :-)