Bug management



Wikimedia's Bugzilla installation is used to track problem reports and feature requests related to MediaWiki code, other Wikimedia-specific components (such as extensions or tools), and Wikimedia wikis (such as Wikipedia).

Sorting and solving bug reports is a collaborative effort by users and developers of the community together with Wikimedia's bugwrangler.

Activity scope
Bug management is a perennial activity. Anyone can contribute! Activities include:
 * coordinating, triaging, and organizing the current bug reports in Bugzilla
 * writing documentation for bug management
 * coordinating MediaWiki deployments
 * consider developing a friendly way (perhaps an extension) to allow Wikipedia users to report problems and record them in Bugzilla

Documentation
Note that this is work in progress.

For Bug Reporters

 * How to report a bug / Also see Bugzilla's own documentation

For Module Maintainers

 * How to add/edit products, components, versions, and default bugmail CCs in Bugzilla

For Developers

 * Annoying little bugs to start with
 * Getting developer access

For Triagers / Bugsquad Community

 * Project:WikiProject Bug Squad
 * Triage: Definition of "triaging" and information on bug triage sessions
 * Triage guide: How you can help to improve bug reports, and tools to save time triaging
 * Easy tasks and entry points to start triaging in Bugzilla
 * Bugsquad meeting / Bugday preparations
 * Places (Village Pumps, forums) to regularly check for bug reports
 * List of upstream bugtrackers and URLs

For Bugzilla Administrators / the Bugwrangler

 * Admins: Please file a report when changing products/components/keywords to avoid work duplication and entropy and to understand reasonings. This excludes trivial changes like component descriptions or assignees/CC lists.
 * Status updates of the Bugwrangler (Note: The bugwrangler is employed by the Wikimedia Foundation to do bug management, see scope above)
 * Plans and ideas of things to do in bug management - help welcome!
 * How to run IRC office hours on bug management
 * TODO: Instructions on how to create new products/components in Bugzilla
 * Technical information on our Bugzilla instance
 * Bugzilla backup procedure
 * Andre Klapper keeps an eye on upstream Bugzilla security updates, Daniel Zahn helps deploying them.

For everybody (General / Misc)

 * An introduction to Bug report management in Wikipedia
 * Bug report life cycle: The status changes of bug reports, from reporting to closing them.
 * Fields in the Bugzilla interface
 * TODO: Bug management/Bug access restrictions: When and why some reports (often Security issues) have restricted access
 * Workflow: Proposal for a new workflow on problem entry that would lead the user to OTRS, RT, or Bugzilla as appropriate