BugZappers

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(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:
{{header|bugs}}
+
__NOTOC__
  
= Fedora Bug Zappers =
+
== Who Are The BugZappers? ==
  
== Who Are We? ==
+
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.
  
{| tableclass="t1" rowclass="th" style="text-align: center; float: right; margin-left: 3em; margin-right: 5em;"
+
== Help Wanted ==
! colspan="3" | Fedora Common Bugs
+
|- 
+
| style="padding-left: 2em; padding-right: 1em; border-right: 0" | [[Bugs/F8Common| Fedora 8]] || style="padding-left: 1em; padding-right: 1em; border-left: 0; border-right: 0" | [[Bugs/F9Common| Fedora 9]] || style="padding-left: 1em; padding-right: 2em; border-left: 0" | [[Bugs/F10Common| Fedora 10]]
+
|}
+
  
* Our primary mission is to track down and shoot Fedora bugs in [https://bugzilla.redhat.com bugzilla.redhat.com] We also strive to be a bridge between users and developers that aids in fixing and closing bugs
+
Triaging bugs helps package maintainers spend more time on actually fixing bugs, and provides needed assistance to other Fedora usersNo 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]].
* See if you [[BugZappers/HelpWanted| qualify]] :-)
+
  
 +
== Responsibilities ==
  
== Contributing roles in the Bug Zappers Project ==
+
* Triage Fedora bugs in [https://bugzilla.redhat.com Bugzilla].  Request missing information, verify correct component has been chosen, and close duplicates.
{{admon/tip|Contributing roles|This is only suggestions for contributing roles. Only your imagination sets the limits. }}
+
* 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]].
  
{|class="nobordersplz"
+
== Tools and Procedures ==
|-
+
|
+
[[Image:Join_OSDeveloper.png]]<BR>
+
[[Join#OS_Developer|OS Developer]]
+
|}
+
  
== How Can I Help? ==
+
* The [[BugZappers/Tools]] page contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier.
* See [[BugZappers/Joining|Joining]] for information on what's involved and to sign up for special Bugzilla permissions.
+
* [[BugsAndFeatureRequests|Bugzilla Primer]]  
* See if you can help with a particular [[BugZappers/Goals|goal]]
+
* [[BugZappers/Components and Triagers|Components and Triagers]] - Tracking progress and who's working on what
* The [[BugZappers/Components and Triagers|Component list]] tracks progress and who's working on what.
+
* [[BugZappers/FindingBugs|Finding Bugs]] help
* Need help [[BugZappers/FindingBugs|Finding Bugs]] to work on?
+
* [[BugZappers/FindingDuplicates|How to find duplicate bugs]]
* [[BugZappers/How to Triage|How to Triage]] has a checklist you can use for each bug as you process it.
+
* [[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]]
  
== Useful Links ==
+
== Communication ==
* [[BugZappers/Tools|Tools]]
+
* [[BugZappers/HouseKeeping | Regular Release Processes]]
+
* [[BugZappers/StockBugzillaResponses|  Stock Responses]]
+
* FUDCon Boston presentations (June 21, 2008)
+
** [https://fedoraproject.org/wiki/Image:Bug-triage-getting-started-presentation-2008-jun-19.pdf pdf]
+
** [https://fedoraproject.org/w/uploads/3/34/Bug-triage-getting-started-presentation-2008-jun-19.odp odf (source)]
+
  
==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].
* Come to Triage Team [[BugZappers/Meetings|  meetings]] -- everyone is welcome!
+
'''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]].
* Stop by '''[irc://irc.freenode.net/fedora-bugzappers #fedora-bugzappers]''' and '''[irc://irc.freenode.net/fedorabot #fedorabot]''' on [http://freenode.net/ freenode]  
+
* Join the [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list@redhat.com]  mailing list.
+
* [[BugZappers/ActiveTriagers]]
+
  
[[Category:SIGs]]
+
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.
[[Category:BugTriage]]
+

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

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.