From Fedora Project Wiki
(→How to Sign Up: move advice to /Components and Triagers) |
(update and merge from BugZappers/Why, BugZappers/HelpWanted (draft posted on BugZappers/Joining/tmp, no objections heard so far)) |
||
| Line 3: | Line 3: | ||
Bug triagers make sure that: | Bug triagers make sure that: | ||
* | * Bug reports have the information developers need to reproduce and fix them. | ||
* | * Bugs are assigned to the right component and version. | ||
* | * Duplicate bugs are found and labelled. | ||
* | * Feature requests reported as bugs are properly reported. | ||
* | * Bugs already fixed are closed. | ||
Triaging bugs does '''not''' mean that you have to understand bugs and solve them yourself. It means you should be able to look at new bugs, and report if they are duplicates, if more information is needed, or if it is filed under the wrong component. | Triaging bugs does '''not''' mean that you have to understand bugs and solve them yourself. It means you should be able to look at new bugs, and report if they are duplicates, if more information is needed, or if it is filed under the wrong component. | ||
There is no requirement of programming knowledge. However, | There is no requirement of programming knowledge. However, being familiarity with Fedora and Linux in general will be extremely useful. | ||
This is purely voluntary. We do not expect you to spend hours here | This is purely voluntary. We do not expect you to spend hours here every day. (Though if you want to, you're more than welcome!) You can triage bugs whenever you have free time. You can spend as little as 15 minutes a week - every little bit helps! | ||
== Why Triage Bugs? == | |||
* The less time package maintainers have to spend resolving duplicates, attempting to reproduce bugs, and requesting missing information, the more time they can spend fixing bugs. | |||
* Helps to identify bugs that should be fixed before release (adding to tracker and blocker lists) | |||
* Gives bug reporters the feeling that someone has acknowledged their problem | |||
* Strives to provide a level of certainty that the total number of open bugs is accurate | |||
* Closing bugs for EOL releases helps keep Bugzilla tidy and useful, and lets reporters know they need to upgrade | |||
* Identifying workarounds can help users in the meantime until a bug is fixed | |||
* Provides an idea of where problem areas are in the distribution | |||
* Good way to learn more about Fedora | |||
== How to Sign Up == | == How to Sign Up == | ||
| Line 25: | Line 36: | ||
# Fedora encourages you to sign the Contributor License Agreement (giving the project permission to use and keep contributions you make in the course of triaging), but it is not required. [[Infrastructure/AccountSystem/CLAHowTo|Here's how!]] | # Fedora encourages you to sign the Contributor License Agreement (giving the project permission to use and keep contributions you make in the course of triaging), but it is not required. [[Infrastructure/AccountSystem/CLAHowTo|Here's how!]] | ||
# After successfully obtaining a Fedora account, view the [https://admin.fedoraproject.org/accounts/group/view/fedorabugs fedorabugs group] and apply to the group by clicking the '''Apply!''' button. Your membership will need to be approved, so this process is not instantaneous. It may take several days (unfortunately) for your membership to be approved, so please be patient. After your approval, you will have additional permissions in the system which will allow you to triage bugs. | # After successfully obtaining a Fedora account, view the [https://admin.fedoraproject.org/accounts/group/view/fedorabugs fedorabugs group] and apply to the group by clicking the '''Apply!''' button. Your membership will need to be approved, so this process is not instantaneous. It may take several days (unfortunately) for your membership to be approved, so please be patient. After your approval, you will have additional permissions in the system which will allow you to triage bugs. | ||
# If you can commit to being a regular triager for the current release cycle, add your name to the [[BugZappers/ActiveTriagers|Active Triagers]] | # If you can commit to being a regular triager for the current release cycle, add your name to the [[BugZappers/ActiveTriagers|Active Triagers]] page. | ||
#* This is a simple reference so that package maintainers know who the triagers are | #* This is a simple reference so that package maintainers know who the triagers are | ||
#* It also gives us a rough idea who is triaging bugs in which components | #* It also gives us a rough idea who is triaging bugs in which components | ||
| Line 34: | Line 45: | ||
#* All announcements and conversations about bug triage happen on this list | #* All announcements and conversations about bug triage happen on this list | ||
#* https://www.redhat.com/mailman/listinfo/fedora-test-list | #* https://www.redhat.com/mailman/listinfo/fedora-test-list | ||
# Valuable communication and real time help happen in the chat channels on IRC. See | # Valuable communication and real time help happen in the chat channels on IRC. See [[Communicate/IRCSetup|IRCSetup]] and [[Communicate/IRCHowTo|IRCHowTo]] for more information on using IRC | ||
#* The main IRC channels to join are: [irc://irc.freenode.net/fedora-bugzappers #fedora-bugzappers] - where team members discuss things - and [irc://irc.freenode.net/fedorabot #fedorabot] - where you will see automated messages when new bugs are filed (among other things) | #* The main IRC channels to join are: [irc://irc.freenode.net/fedora-bugzappers #fedora-bugzappers] - where team members discuss things - and [irc://irc.freenode.net/fedorabot #fedorabot] - where you will see automated messages when new bugs are filed (among other things) | ||
#* Once you are all setup and ready to go drop by and say hello on #fedora-bugzappers | #* Once you are all setup and ready to go drop by and say hello on #fedora-bugzappers | ||
#* #fedora-bugzappers is also a good place to get help if you are having problems with the sign-up process | #* #fedora-bugzappers is also a good place to get help if you are having problems with the sign-up process | ||
# Attend a [[BugZappers/Meetings|Bug Triage Meeting]]. Details on the time and location of meetings are on that page. | # Attend a [[BugZappers/Meetings|Bug Triage Meeting]]. Details on the time and location of meetings are on that page. | ||
== How to Start Triaging == | == How to Start Triaging == | ||
Revision as of 14:58, 11 March 2009
What is Involved in Bug Triaging?
Bug triagers make sure that:
- Bug reports have the information developers need to reproduce and fix them.
- Bugs are assigned to the right component and version.
- Duplicate bugs are found and labelled.
- Feature requests reported as bugs are properly reported.
- Bugs already fixed are closed.
Triaging bugs does not mean that you have to understand bugs and solve them yourself. It means you should be able to look at new bugs, and report if they are duplicates, if more information is needed, or if it is filed under the wrong component.
There is no requirement of programming knowledge. However, being familiarity with Fedora and Linux in general will be extremely useful.
This is purely voluntary. We do not expect you to spend hours here every day. (Though if you want to, you're more than welcome!) You can triage bugs whenever you have free time. You can spend as little as 15 minutes a week - every little bit helps!
Why Triage Bugs?
- The less time package maintainers have to spend resolving duplicates, attempting to reproduce bugs, and requesting missing information, the more time they can spend fixing bugs.
- Helps to identify bugs that should be fixed before release (adding to tracker and blocker lists)
- Gives bug reporters the feeling that someone has acknowledged their problem
- Strives to provide a level of certainty that the total number of open bugs is accurate
- Closing bugs for EOL releases helps keep Bugzilla tidy and useful, and lets reporters know they need to upgrade
- Identifying workarounds can help users in the meantime until a bug is fixed
- Provides an idea of where problem areas are in the distribution
- Good way to learn more about Fedora
How to Sign Up
- Obtain a bugzilla account in Red Hat's Bugzilla
- https://bugzilla.redhat.com/bugzilla/createaccount.cgi
- Fedora's bugs are tracked in Red Hat's Bugzilla
- Note that this is all you need to start reporting bugs, but if you also want to triage, then you will also need to...
- Obtain a Fedora Account
- It is necessary that the e-mail address used for your Bugzilla and Fedora accounts are the same
- Fedora encourages you to sign the Contributor License Agreement (giving the project permission to use and keep contributions you make in the course of triaging), but it is not required. Here's how!
- After successfully obtaining a Fedora account, view the fedorabugs group and apply to the group by clicking the Apply! button. Your membership will need to be approved, so this process is not instantaneous. It may take several days (unfortunately) for your membership to be approved, so please be patient. After your approval, you will have additional permissions in the system which will allow you to triage bugs.
- If you can commit to being a regular triager for the current release cycle, add your name to the Active Triagers page.
- This is a simple reference so that package maintainers know who the triagers are
- It also gives us a rough idea who is triaging bugs in which components
Communication
- Join the fedora-test-list
- All announcements and conversations about bug triage happen on this list
- https://www.redhat.com/mailman/listinfo/fedora-test-list
- Valuable communication and real time help happen in the chat channels on IRC. See IRCSetup and IRCHowTo for more information on using IRC
- The main IRC channels to join are: #fedora-bugzappers - where team members discuss things - and #fedorabot - where you will see automated messages when new bugs are filed (among other things)
- Once you are all setup and ready to go drop by and say hello on #fedora-bugzappers
- #fedora-bugzappers is also a good place to get help if you are having problems with the sign-up process
- Attend a Bug Triage Meeting. Details on the time and location of meetings are on that page.
How to Start Triaging
- See BugZappers/FindingBugs to get a list of bugs to work on.
- See BugZappers/How to Triage for instructions.