User:Beland/BugZappers

The BugZappers subproject has the following 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.

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.

Coordination and Communication

• Tracking - Find bugs to work on, track progress against our goals
• ActiveTriagers - Find out who's working on what

Channels of communication outside the wiki:

• fedora-test-list mailing list - Announcements and conversations about bug triage and general QA
• IRC - See How to use IRC for technical assistance getting connected.
  • Weekly meetings
  • #fedora-bugzappers - For general BugZappers discussion and help
  • #fedorabot - For automated messages produced when new bugs are filed (among other things)

Documentation

• Bugzilla Primer (TODO - ITEM 5)
• Tracking - For finding bugs to work on
• Checklist - For use when triaging bugs (TODO - ITEM 5)
• How to find duplicate bugs
• Housekeeping processes tied to the Fedora release cycle
• Tools
• Stock Responses