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
-------- Original Message -------- Subject: Newest Bugzappah From: Mike Chambers mike@miketc.net To: Fedora Beta fedora-test-list@redhat.com Date: 03/03/2009 04:48 AM
So hopefully I can help out on way or another.
Hey Mike, it's Mike.
I'd suggest being a "Release QA" or "Rawhide QA" person. Register a Fedora account and pull updates from "updates-testing" or rawhide and after testing the package give the updates "karma" by using "bodhi" or the Fedora admin website.
... or if you want to be a Bugzapper instead, good luck!
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.use... and http://mcepl.fedorapeople.org/scripts/greasemonkey/add_bugzappers_signature.... , 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!
On Tue, Mar 3, 2009 at 12:09 PM, Adam Williamson awilliam@redhat.com wrote: ...
2: grab the Greasemonkey scripts - https://fedorahosted.org/triage/browser/scripts/bugzilla_buttons_for_fed.use...
That script now "runs on: *", whereas the version I've installed previously only runs on "https://bugzilla.redhat.com/show_bug.cgi*". I'd prefer the latter. Thanks, jerry
On Tue, Mar 3, 2009 at 1:13 PM, Jerry Amundson jamundso@gmail.com wrote:
On Tue, Mar 3, 2009 at 12:09 PM, Adam Williamson awilliam@redhat.com wrote: ...
2: grab the Greasemonkey scripts - https://fedorahosted.org/triage/browser/scripts/bugzilla_buttons_for_fed.use...
That script now "runs on: *", whereas the version I've installed previously only runs on "https://bugzilla.redhat.com/show_bug.cgi*". I'd prefer the latter. Thanks, jerry
Ah, I see the problem now. The GM script was plopped (yes, that's the technical term for it :-) into fedorahosted in it's html form (from a web server?), not as JavaScript. So, Greasemonkey will happily install the Bugzilla Triage Buttons link on https://fedoraproject.org/wiki/BugZappers/Tools, but it's junk.
I would fix this, but I cannot login to fedorahosted. I also would have cleaned up a bit and put both scripts under https://fedorahosted.org/triage/browser/greasemonkey ...
jerry
On Thu, Mar 5, 2009 at 10:02 PM, Jerry Amundson jamundso@gmail.com wrote:
On Tue, Mar 3, 2009 at 1:13 PM, Jerry Amundson jamundso@gmail.com wrote:
On Tue, Mar 3, 2009 at 12:09 PM, Adam Williamson awilliam@redhat.com wrote: ...
2: grab the Greasemonkey scripts - https://fedorahosted.org/triage/browser/scripts/bugzilla_buttons_for_fed.use...
That script now "runs on: *", whereas the version I've installed previously only runs on "https://bugzilla.redhat.com/show_bug.cgi*". I'd prefer the latter. Thanks, jerry
Ah, I see the problem now. The GM script was plopped (yes, that's the technical term for it :-) into fedorahosted in it's html form (from a web server?), not as JavaScript. So, Greasemonkey will happily install the Bugzilla Triage Buttons link on https://fedoraproject.org/wiki/BugZappers/Tools, but it's junk.
I would fix this, but I cannot login to fedorahosted. I also would have cleaned up a bit and put both scripts under https://fedorahosted.org/triage/browser/greasemonkey ...
jerry
Jerry,
There are multiple issues with this, I need to put it in the release part of fedorahosted, it will never be able to install correctly from Trac. I will take care of this right now.
--Brennan Ashton
On Fri, Mar 6, 2009 at 12:05 AM, Brennan Ashton bashton@brennanashton.com wrote:
On Thu, Mar 5, 2009 at 10:02 PM, Jerry Amundson jamundso@gmail.com wrote:
On Tue, Mar 3, 2009 at 1:13 PM, Jerry Amundson jamundso@gmail.com wrote:
On Tue, Mar 3, 2009 at 12:09 PM, Adam Williamson awilliam@redhat.com wrote: ...
2: grab the Greasemonkey scripts - https://fedorahosted.org/triage/browser/scripts/bugzilla_buttons_for_fed.use...
That script now "runs on: *", whereas the version I've installed previously only runs on "https://bugzilla.redhat.com/show_bug.cgi*". I'd prefer the latter. Thanks, jerry
Ah, I see the problem now. The GM script was plopped (yes, that's the technical term for it :-) into fedorahosted in it's html form (from a web server?), not as JavaScript. So, Greasemonkey will happily install the Bugzilla Triage Buttons link on https://fedoraproject.org/wiki/BugZappers/Tools, but it's junk.
I would fix this, but I cannot login to fedorahosted. I also would have cleaned up a bit and put both scripts under https://fedorahosted.org/triage/browser/greasemonkey ...
jerry
Jerry,
There are multiple issues with this, I need to put it in the release part of fedorahosted, it will never be able to install correctly from Trac. I will take care of this right now.
Yes. I see now - I had I assumed I had installed the signature script from trac, but of course I had used the mcepl link on the Tools page. Sorry, my bad.
Thanks for the quick fix!
jerry
On Fri, Mar 6, 2009 at 12:12 AM, Jerry Amundson jamundso@gmail.com wrote:
On Fri, Mar 6, 2009 at 12:05 AM, Brennan Ashton bashton@brennanashton.com wrote:
There are multiple issues with this, I need to put it in the release part of fedorahosted, it will never be able to install correctly from Trac. I will take care of this right now.
Yes. I see now - I had I assumed I had installed the signature script from trac, but of course I had used the mcepl link on the Tools page. Sorry, my bad.
Thanks for the quick fix!
s/fix/response/ Didn't intend to imply any kind of rush on this. Just happy it's being looked into...
jerry