From ReactOS

Bugzilla Maintainer

This page describes the work of the Bugzilla Maintainer.

Assigned Members

The current Bugzilla Maintainer is Amine Khaldi.

Responsibilities

It is under the responsibility of the Bugzilla Maintainer to carry out the following tasks:

• Check for and evaluate new bugs through the use of ros-bugs mailing list (and Deskzilla):
  1. Ensure the description is valid. If not valid, close the bug with resolution INVALID.
  2. Check that enough relevant information is given. If it is uninformative (e.g. "ReactOS BSODs when I run Vista installer on it"), further clarification is needed: providing a debug log, an environment (QEMU, VMware, real hardware. In the case of real hardware, the manufacturer and model).
  3. If the above is not given, add a comment (keeping the bug unassigned and opened) asking for more information.
  4. When there is enough information, you look over it, and make a preliminary decision who of the developers would be responsible (according to People of ReactOS). That means, you perform an assign operation in Bugzilla to a corresponding developer. It is not going to be a huge mistake if you assign to a wrong developer, since that developer is going to reassign to another if he does not feel he is closing this bug.
• Review the contents of bugs which are not touched for one (1) month or more. Add a comment about validity of the bug and if retesting is required.
• Check if modified bugs have an assigned owner. If no owner is assigned, assign it to an appropriate and available developer.