Bug triage involves reviewing reported bugs, ensuring they are filed under the correct component, checking for duplicates, requesting more information if needed, and preparing bugs for developers to work on. It shows appreciation for reporters, improves debugging skills, and assists developers by clarifying issues. People can get involved by attending the weekly IRC meeting, reading the workflow documentation, and asking questions of developers on IRC or the mailing list. After triage, developers and maintainers track the bugs and assign them for resolution.

1. Bug Triage in Gluster
Niels de Vos
GlusterFS co-maintainer
ndevos@redhat.com

2. Gluster Summit 2015, Barcelona 2
What is Bug Triage?
● Reviewing of reported bugs
● Correcting the component a bug was filed against
● Checking for duplicate bugs
● Request more information in case of missing details
● Clone the bug for other affected versions
Prepare Bugs for developers to work on

3. Gluster Summit 2015, Barcelona 3
Why do Bug Triage?
● Show appreciation towards Bug reporters
● Learn how Gluster is deployed and (ab)used
● Improve debugging and troubleshooting skills
● Work with developers and maintainers while debugging
Assist developers and maintainers

4. Gluster Summit 2015, Barcelona 4
When to Triage a Bug?
● While reporting the Bug
● In the morning when you read your emails
● During the day while reading your RSS feeds
Untriaged bugs get handled every Tuesday

5. Gluster Summit 2015, Barcelona 5
How to get involved?
● Read the workflow:
http://gluster.org/community/documentation/index.php/Bug_triage
● Join the weekly IRC meeting:
#gluster-meeting, Tuesdays 12:00 UTC
https://public.pad.fsfe.org/p/gluster-bug-triage
● Ask questions, talk to developers and maintainers:
#gluster-devel, gluster-devel@gluster.org
Try it, do it, users will appreciate your assistance!

6. Gluster Summit 2015, Barcelona 6
What happens after the Bug Triage?
● Developers and maintainers track triaged bugs
● Bugs get assigned or taken by developers
Maintainers are responsible for their components

7. Thank you!
Niels de Vos
ndevos@redhat.com
ndevos on IRC