m (1 revision(s)) |
(→BugZapper Skills: fixed up formatting for MW) |
||
| Line 32: | Line 32: | ||
* Determination | * Determination | ||
* Writing | * Writing | ||
*# Being polite and courteous in your responses | |||
*# Communicating complex information clearly | |||
There you have the basic skills, the more advanced skills include: | There you have the basic skills, the more advanced skills include: | ||
* Bug reproduction | * Bug reproduction | ||
* Coding (optional) | * Coding ('''optional''') | ||
* Technical writing (detailed) | * Technical writing (detailed) | ||
Revision as of 02:42, 27 May 2008
Help Wanted
Welcome
We welcome help from just about anyone willing join in and learn
Who are the BugZappers?
The BugZappers are a group of dedicated individuals from around the world who have come together to form a community whose purpose is to triage incoming bug reports to the Fedora Project. This may entail linking up duplicate bug report reports (there are a lot of these), flagging bug reports for insufficient information and requesting more information.
Our goal is to make sure package maintainers have helpful, actionable bug reports--and get all the other bug reports out of their way by requesting more information or closing them!
A typical BugZapper may be someone like a(n):
- Doctor
- System Administrator
- User
- Enthusiast
- Student
- Lawyer
- Mr. T
In other words, don't think that any particular type of background or training is required, anyone is welcome!
BugZapper Skills
A typical BugZapper will possess skills similar to the following:
- Patience
- Determination
- Writing
- Being polite and courteous in your responses
- Communicating complex information clearly
There you have the basic skills, the more advanced skills include:
- Bug reproduction
- Coding (optional)
- Technical writing (detailed)
Not all of these skills are mandatory to be an effective BugZapper, the most important detail is your commitment to success which will grow over time.
It's especially important to note that coding/programming skills are not required - you are NOT expected to fix the bugs that you touch, or even to fully understand them. All that is required is the ability to determine that the bug has sufficient information to be reproduced or fixed, and that it is not a duplicate of an already reported bug.
How do I join?
There is a whole page on just that topic, but don't be intimidated. If you need help, there is either the mailing list or somone is usually around on IRC in #fedora-qa on freenode .