BugZappers

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (How Can I Help?: fix link)
(UTCHowto link update)
 
(46 intermediate revisions by 22 users not shown)
Line 1: Line 1:
 +
{{autolang|base=yes}}
 
{{header|bugs}}
 
{{header|bugs}}
  
= Fedora Bug Zappers =
 
  
== Who Are We? ==
+
== Who Are The BugZappers? ==
  
{| tableclass="t1" rowclass="th" style="text-align: center; float: right; margin-left: 3em; margin-right: 5em;"
+
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.
! 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
+
== Help Wanted ==
* See if you [[BugZappers/HelpWanted|  qualify]]  :-)
+
  
 +
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]].
  
== Contributing roles in the Bug Zappers Project ==
+
== Responsibilities ==
{{admon/tip|Contributing roles|This is only suggestions for contributing roles. Only your imagination sets the limts. }}
+
  
{|class="nobordersplz"
+
* 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]].
[[Image:Join_OSDeveloper.png]]<BR>
+
* Identify and Document [[Bugs/Common|Common Bugs]].
[[Join#OS_Developer|OS Developer]]
+
|}
+
  
== How Can I Help? ==
+
== Tools and Procedures ==
* See [[BugZappers/Joining|Joining]] for information on what's involved and to sign up for special Bugzilla permissions.
+
* The [[BugZappers/components|Component list]] tracks progress and has pre-formatted queries to produce bug lists
+
* Need help [[BugZappers/FindingBugs|Finding Bugs]] to work on?
+
* [[BugZappers/How to Triage|How to Triage]] has a checklist you can use for each bug as you process it.
+
  
== Useful Links ==
+
* [[Bugs_and_feature_requests|Bugzilla Primer]] : To better understand Bugzilla
* [[BugZappers/Tools|Tools]]
+
* [[BugZappers/StockBugzillaResponses|Stock Responses]] : Know the Bugzilla terminology
* [[BugZappers/HouseKeeping | Regular Release Processes]]
+
* [[BugZappers/BugStatusWorkFlow|Bug Lifecycle]] : From bug-report to closed
* [[BugZappers/StockBugzillaResponses| Stock Responses]]
+
* [[BugZappers/Tools|BugZappers' Tools]] : Contains several tools and scripts that are of use to BugZappers, including Greasemonkey scripts to make triaging quicker and easier.
* FUDCon Boston presentations (June 21, 2008_
+
* [[BugZappers/Components and Triagers|Components and Triagers]] : Tracking progress and who's working on what
** [https://fedoraproject.org/wiki/Image:Bug-triage-getting-started-presentation-2008-jun-19.pdf pdf]
+
* [[BugZappers/FindingBugs|Finding Bugs]] : Help including finding duplicate bugs
** [https://fedoraproject.org/w/uploads/3/34/Bug-triage-getting-started-presentation-2008-jun-19.odp odf (source)]
+
* [[BugZappers/How to Triage|How to Triage]] : Includes checklists for use when triaging bugs
 +
* [[BugZappers/HouseKeeping|Housekeeping]] : Processes tied to the Fedora release cycle
 +
* [[How to test updates]] : Steps to create the necessary environment
  
==Communication==
+
== Communication ==
* Come to Triage Team [[BugZappers/Meetings|  meetings]] -- everyone is welcome!
+
* 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.
+
  
[[Category:SIGs]]
+
BugZappers meetings are held on every other '''Tuesday''' at '''21:00 UTC''' (4 PM EST/1 PM PST) in {{fpchat|#fedora-meeting}} on freenode.net. See the [[UTCHowto|UTC Howto]] for instructions to convert UTC to your local time.
[[Category:BugTriage]]
+
 
 +
'''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 {{fpchat|#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 {{fplist|test}} mailing list. Alternatively, the {{fplist|test-announce}} list carries only important event announcements, if you do not want the traffic of the full list.
 +
 
 +
[[Category:QA]]
 +
[[Category:Fedora sub-projects]]

Latest revision as of 17:27, 1 May 2013

Image-BugZappers bugzappers-wikiheader.png


Contents

[edit] 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.

[edit] 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.

[edit] 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.

[edit] Tools and Procedures

[edit] Communication

BugZappers meetings are held on every other Tuesday at 21:00 UTC (4 PM EST/1 PM PST) in #fedora-meeting[?] on freenode.net. 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.