On Tue, 2009-06-02 at 09:08 -0800, Jeff Spaleta wrote: > On Tue, Jun 2, 2009 at 8:53 AM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: > > It could do, but on the other hand, we're mostly getting to the point > > where the components that lack coverage are ones which need a triager > > who's already knowledgeable about that component: we can't just > > parachute someone in. (see e.g. anaconda and kernel). > > How short is that list of components? Can you visualize that? Just > identifying that finite list could help motivate exactly that sort of > recruitment effort needed to fill the need. If we identify the short > list accurately, can we then advertise the short list as a rewarding > challenge to undertake? Our very own elite highly trained > specialists..our 00's..our A-team. So highly prized they even get > codenames and catch phrases. Anything on the Components and Triagers page where there's no-one under "Active Triagers". :) (oh, and "Need help?" is not set to No). Currently that list is: PackageKit firstboot gdm glibc gtk2 mkinitrd upstart as I said, these are bits that you kinda need decent expertise on to be able to triage properly. PackageKit might be the lowest-hanging fruit on that list. you can add: pulseaudio anaconda kernel each of these currently isn't really being triaged by any triagers. Lennart is happy to have triage for PA, but only from someone who already knows what they're talking about when it comes to PA in quite some detail (which is quite a small pool). I'm currently working with the anaconda / kernel folks to see what we can do about setting down the requirements for triage for those components. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
