This page lists active triagers, sorted by component. Check the below list to see which components need help, and use the links to get lists of bugs that need triage.
If you are unfamiliar with a component and someone is very active there, it is probably a good idea to pick a different component or talk to that person and see if you can work together. As you start work on a component, communicating with other triagers working on the same component or the developer can help make your working relationship more productive. The Component information column in the table will help you identify the maintainer(s) of any component. Where it links to the Fedora Package Database entry for a package, the person listed as Owner for the Fedora devel collection is likely the primary maintainer for that component, and those listed as Users will be co-maintainers. You should be able to contact any of these by adding @fedoraproject.org to the alias given on the page.
Set Components
Any Component
Triagers willing to work on any component:
- Christopher D. Stover (quantumburnz)
- Brennan Ashton (comphappy)
- Paul W. Frields (stickster)
- Jerry Amundson (jamundso)
- Marco Crosio (TopoMorto)
- Chedi Toueiti (douda)
- Jon Dufresne (bigdufstuff)
- Mike Chambers (MikeC)
- Christopher Beland (beland)
Non-key Components
People working on non-key components:
- François Cami (fcami): kvm, dm [1]
- Edward Kirk (TK009): Desktop Gnome
- Keiran Smith (Affix): Web Development
- iarly selbir (iarlyy): Kpackagekit [2]
- Steve Grubb (sgrubb): aide, amtu, audit, libprelude, libpreludedb, libsafe, openssh, openswan, pads, prelude-correlator, prelude-lml, prelude-manager, prelude-notify, prewikka, shadow-utils, usermode, xguest.[3] (No further assistance is needed for these packages.)
See also
- BugZappers/FindingBugs for alternate ways to get lists of bugs.
- BugZappers/Goals for component bug levels
- BugZappers/Metrics for automated statistics (soon to replace stats tracking on this page)