Important Announcement: Please read the latest status update for Fedora infrastructure (2008-08-22 1200 UTC). Additional details can be found in RHSA-2008-0855.
New SSH Fingerprints for Public Servers: Please verify SSH Fingerprints against https://admin.fedoraproject.org/fingerprints.
BugZappers/GettingStarted
From FedoraProject
Contents |
Getting Started
What is Bug Triaging?
Bug triagers make sure that:
- bug reports have the information developers need to reproduce and fix them.
- bugs are assigned to the right component and version
- duplicate bugs are found and labelled
- feature requests reported as bugs are properly reported
- bugs already fixed are closed
Things to Remember about Triaging
- Triaging bugs does not mean that you have to understand bugs and solve them yourself. It means you should be able to look at new bugs, and report if they are duplicates, if more information is needed, or if it is filed under the wrong component.
- There is no requirement of programming knowledge. However, a familiarity with Fedora, and Linux in general will be extremely useful.
- This is purely voluntary. We do not expect you to spend hours here everyday (though if you want to, you're more than welcome!). You can triage bugs whenever you have free time. You can spend as little as 15 minutes a week - every little bit helps!
- Be polite when triaging a bug. Here are a few sample responses to consider: Stock Responses
How Do I Start Triaging?
- Complete the steps to sign up for the mailing list and Fedora Account at the Joining Page .
- Query a list of bugs to review. Knowing how to efficienly find bugs in bugzilla is one of the keys to quickly triaging bugs
- See Finding Bugs for more instructions on finding bugs needing triage
- Review each bug and take appropriate action.
- See Taking Action
