No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
=== We Need You === | === We Need You === | ||
A typical BugZapper will be someone who is polite, courteous, patient and determined to make Fedora better. No particular type of background or training is required -- everyone is welcome! | A typical BugZapper will be someone who is polite, courteous, patient and determined to make Fedora better. No particular type of background or training is required -- everyone is welcome! | ||
== Communicate == | == Communicate == | ||
| Line 38: | Line 35: | ||
Keep up to date by subscribing to [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list@redhat.com] mailing list. | Keep up to date by subscribing to [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list@redhat.com] mailing list. | ||
=== How do I join? === | |||
There is a whole [[BugZappers/Joining|page]] on just this topic, but don't be intimidated. If you need help, there is someone usually around on '''[irc://irc.freenode.net/fedora-bugzappers #fedora-bugzappers]''' on freenode, or use [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list@redhat.com] for any questions you may have. | |||
== Learn More About Triage == | == Learn More About Triage == | ||
Revision as of 20:59, 17 February 2009
This is a draft for review of proposed changes to the BugZappers main wiki page. It is incomplete and not a valid source of information.
Who Are The BugZappers?
We are a dedicated group of individuals whose primary mission is to review and triage bug report submissions on bugzilla.redhat.com, acting as a bridge between users and developers to aid in fixing and closing bugs.
Responsibilities
- Review and filter bug report submissions on Bugzilla for correct component, actionable information and duplication.
- Re-assign components, mark duplicates or request further information when necessary.
- Advance Bug Status Work Flow to NEEDINFO, ASSIGNED or CLOSED when applicable.
- Assign bugs to the tracker list according to the ReleaseCriteria.
- Preform HouseKeeping necessary during release EOL (End-of-Life) transitions.
- Communicate through mailing lists and the Bugzilla to keep the Fedora community informed of upcoming or current EOL transitions, version change, etc.
Getting Involved
We Need You
A typical BugZapper will be someone who is polite, courteous, patient and determined to make Fedora better. No particular type of background or training is required -- everyone is welcome!
Communicate
BugZappers meetings are held on Tuesday's at 17:00 UTC (10 AM EDT) on freenode. Everyone is welcome, and we invite you to come and participate. Topics of discussion for the next meeting as well as IRC transcripts of previous meetings can be found here.
You can also find us on #fedora-bugzappers, stop by and say hello and feel free to ask any questions you have.
Keep up to date by subscribing to fedora-test-list@redhat.com mailing list.
How do I join?
There is a whole page on just this topic, but don't be intimidated. If you need help, there is someone usually around on #fedora-bugzappers on freenode, or use fedora-test-list@redhat.com for any questions you may have.
Learn More About Triage
| Fedora Common Bugs | ||
|---|---|---|
| Fedora 9 | Fedora 10 | |