BugZappers

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 +
{{autolang}}
 
__NOTOC__
 
__NOTOC__
  
 
{{header|bugs}}
 
{{header|bugs}}
{autolang}
+
 
  
 
== Who Are The BugZappers? ==
 
== Who Are The BugZappers? ==

Revision as of 13:17, 4 September 2011


Image-BugZappers bugzappers-wikiheader.png


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.
  • Identify and Document Common Bugs.

Tools and Procedures

Communication

BugZappers meetings are held on every other Tuesday at 2100 UTC (4 PM EST/1 PM PST) in #fedora-meeting on freenode. See the UTC Howto for instructions to convert UTC to your local time. 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 test mailing list. Alternatively, the test-announce list carries only important event announcements, if you do not want the traffic of the full list.