From Fedora Project Wiki
(→How Can I Help?: add goal link after page un-merge) |
(new bugzappers front page, as discussed & agreed on mailing list and irc group meeting) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | |||
= | == Who Are The BugZappers? == | ||
We are a group of volunteers and Red Hat employees whose primary mission is to review and triage bug report submissions on [https://bugzilla.redhat.com bugzilla.redhat.com], acting as a bridge between users and developers to aid in fixing and closing bugs. | |||
== Help Wanted == | |||
Triaging bugs helps package maintainers spend more time on actually fixing bugs, and provides needed assistance to other Fedora users. No programming knowledge is necessary, and triagers don't necessarily need to understand the bugs they are working on - just help others communicate about them. To find out more about why and how to become a BugZapper, see [[BugZappers/Joining|Joining]]. | |||
== Responsibilities == | |||
* Triage Fedora bugs in [https://bugzilla.redhat.com Bugzilla]. Request missing information, verify correct component has been chosen, and close duplicates. | |||
* Nominate "target" and "blocker" bugs ([[BugZappers/HouseKeeping/Trackers|tracked here]]) that should be fixed before the next release, according to the [[QA/ReleaseCriteria|release criteria]]. | |||
* Perform [[BugZappers/HouseKeeping|housekeeping]] during release EOL ("End of Life") transitions in coordination with [[ReleaseEngineering]]. | |||
== Tools and Procedures == | |||
* The [[BugZappers/Tools]] page contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier. | |||
* | * [[BugsAndFeatureRequests|Bugzilla Primer]] | ||
* | * [[BugZappers/Components and Triagers|Components and Triagers]] - Tracking progress and who's working on what | ||
* | * [[BugZappers/FindingBugs|Finding Bugs]] help | ||
* | * [[BugZappers/FindingDuplicates|How to find duplicate bugs]] | ||
* [[BugZappers/How to Triage|How to Triage]] | * [[BugZappers/How to Triage|How to Triage]] - Includes checklists for use when triaging bugs | ||
* [[BugZappers/HouseKeeping|Housekeeping]] processes tied to the Fedora release cycle | |||
* [[BugZappers/StockBugzillaResponses|Stock Responses]] | |||
== | == Communication == | ||
BugZappers meetings are held on '''Tuesdays''' at '''1500 UTC''' (10 AM EDT) in '''[irc://irc.freenode.net/fedora-meetings #fedora-meetings]'''on [http://freenode.net 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 [[BugZappers/Meetings|BugZappers Meetings]]. | |||
[ | You can also find us on '''[irc://irc.freenode.net/fedora-bugzappers #fedora-bugzappers]''', stop by and say hello and feel free to ask any questions you have. Also, you can keep up to date with what is going on in the BugZappers by subscribing to the [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list@redhat.com] mailing list. | ||
Revision as of 15:42, 17 March 2009
Who Are The BugZappers?
We are a group of volunteers and Red Hat employees 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.
Help Wanted
Triaging bugs helps package maintainers spend more time on actually fixing bugs, and provides needed assistance to other Fedora users. No programming knowledge is necessary, and triagers don't necessarily need to understand the bugs they are working on - just help others communicate about them. To find out more about why and how to become a BugZapper, see Joining.
Responsibilities
- Triage Fedora bugs in Bugzilla. Request missing information, verify correct component has been chosen, and close duplicates.
- Nominate "target" and "blocker" bugs (tracked here) that should be fixed before the next release, according to the release criteria.
- Perform housekeeping during release EOL ("End of Life") transitions in coordination with ReleaseEngineering.
Tools and Procedures
- The BugZappers/Tools page contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier.
- Bugzilla Primer
- Components and Triagers - Tracking progress and who's working on what
- Finding Bugs help
- How to find duplicate bugs
- How to Triage - Includes checklists for use when triaging bugs
- Housekeeping processes tied to the Fedora release cycle
- Stock Responses
Communication
BugZappers meetings are held on Tuesdays at 1500 UTC (10 AM EDT) in #fedora-meetingson 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 BugZappers Meetings.
You can also find us on #fedora-bugzappers, stop by and say hello and feel free to ask any questions you have. Also, you can keep up to date with what is going on in the BugZappers by subscribing to the fedora-test-list@redhat.com mailing list.