On Tue, 2009-03-03 at 04:48 -0600, Mike Chambers wrote: > Hello all, > > I am a newbie zapper to the group. I have been around awhile though, > actually using Red Hat since 5.2 or 6.0, can't remember. Was a member of > the Red Hat Beta Program group for few years before Fedora was formed > (for those of you that remember that stuff hehe). Not a developer and/or > packager/maintainer or anything, just power user I guess. Trying to > find more ways to help contribute and this should be one of them. > Besides, I hate those reports that says "this don't work, fix it" and > they don't provide info or anything, grrrrrrr! > > Anyways, I do have a day job that pays the bills, 6am-3:30pm (CST), so > that usually leaves me some time in evenings (some longer than others) > to help out and maybe weekends providing we don't work on Saturdays (as > we often do actually). So hopefully I can help out on way or another. > > Soo, thanks for having me, and um, er, do I get a zapper gun n stuff > too? :P Welcome Mike! I'm afraid there's no official gun, no. :) As of yet we don't have a really good getting-started procedure, but here's the concise version: 1: get your fedorabugs membership (I'll approve it if it's not done yet) - you need this to have privileges in bugzilla 2: grab the Greasemonkey scripts - https://fedorahosted.org/triage/browser/scripts/bugzilla_buttons_for_fed.user.js and http://mcepl.fedorapeople.org/scripts/greasemonkey/add_bugzappers_signature.user.js , and install them . The first one should give you a bunch of buttons around the Comment box on each report (including No Response, Close UPSTREAM, NEEDINFO Reminder and several more). The second should append a standard Bugzappers group signature to each comment you file in Bugzilla. You can test this in https://bugzilla.redhat.com/show_bug.cgi?id=485962 . If either script doesn't seem to work, yell. :) You need the GreaseMonkey extension for Firefox installed and you need to restart Firefox after installing the scripts. 3: go to https://fedoraproject.org/wiki/BugZappers/Components and pick a component, ideally one you're pretty familiar with and won't hate triaging reports on. Click on its name and you'll get a list of the NEW bugs for that component. Pick a bug and start triaging. For now, the page we have to explain exactly how to triage is: https://fedoraproject.org/wiki/BugZappers/How_to_Triage it's not great, we're trying to improve this whole area. Please do drop by IRC and we'll help you out with getting started. Triaging is a task with lots and lots of little wrinkles that you pick up as you go along, so it's best to get some help from people with experience already. And don't worry too much, anything you get wrong can be fixed. Always ask here or in IRC if you're unsure about anything. Hope this is helpful! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
