From Fedora Project Wiki
Line 10: Line 10:
== Responsibilities ==
== Responsibilities ==


*Review and filter bug report submissions on [https://bugzilla.redhat.com Bugzilla] for correct component, actionable information and duplication.
* 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]].
*Advance [[BugZappers/BugStatusWorkFlow|Bug Status Work Flow]] to NEEDINFO, ASSIGNED or CLOSED when applicable.
* Perform [[BugZappers/HouseKeeping|housekeeping]] during release EOL ("End of Life") transitions in coordination with [[ReleaseEngineering]].
 
*Add bugs to the [[BugZappers/HouseKeeping/Trackers#Current_Tracker_Bugs|tracker]] list according to the [[QA/ReleaseCriteria|ReleaseCriteria]].
 
*Perform necessary [[BugZappers/HouseKeeping|HouseKeeping]] 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 changes, etc.


== Communicate ==
== Communicate ==

Revision as of 15:36, 10 March 2009


Note.png
Note
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.
Image-BugZappers bugzappers-wikiheader.png


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

  • 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.

Communicate

BugZappers meetings are held on Tuesday's at 15:00 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.

Getting Involved

We Need You

A typical BugZapper will be someone who is courteous, patient and determined to make Fedora better. No particular type of background or training is required, just a willingness to learn and be part of a team -- everyone is welcome!

Want to help? Getting Started is easy.