Hi guys,
we teach about opensource at our university, and I would love to
demonstrate to my students how to do BugZapping. I have a couple of
questions:
1) There are about 50 of them. If I request each one to make a Fedora
account, it's going to be a lot of accounts and lots of potential
complications. What should I do? Can all of them work simultaneously
on one account?
2) I plan to focus on finding duplicates and triaging radeon-related
stuff, because it's quite easy to explain stuff there (KMS/UMS,
xf86-video-radeon/radeonhd, card generations etc.), but I don't want
to limit myself to that. Any other suggestions what to work on?
Regards,
--
Vedran Miletić

Hi guys,
we teach about opensource at our university, and I would love to
demonstrate to my students how to do BugZapping. I have a couple of
questions:
1) There are about 50 of them. If I request each one to make a Fedora
account, it's going to be a lot of accounts and lots of potential
complications. What should I do? Can all of them work simultaneously
on one account?
2) I plan to focus on finding duplicates and triaging radeon-related
stuff, because it's quite easy to explain stuff there (KMS/UMS,
xf86-video-radeon/radeonhd, card generations etc.), but I don't want
to limit myself to that. Any other suggestions what to work on?
Regards,
--
Vedran Miletić
--
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

each one should have their own account, there are no problems if you
have thousands of students.
--
------------
Itamar Reis Peixoto
e-mail/msn/google talk/sip: itamar(a)ispbrasil.com.br
skype: itamarjp
icq: 81053601
+55 11 4063 5033
+55 34 3221 8599

Firefox (and related apps), Evolution, Nautilus, and Rhythmbox all have
large numbers of NEW bugs, are fairly important, and should be fairly
easy for new triagers to jump in on. For links, see:
https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
This is an excellent project, by the way. I have often fantasized that
hordes of students would someday eliminate backlogs while at the same
time gaining valuable hands-on experience. 8)
-B.

This is a great initiative. If possible please write a detailed post on some
blog or create a wiki page with every possible detail so that others can
also conduct similar workshops across the globe.
2010/3/24 Vedran Miletić <rivanvx(a)gmail.com&gt;

Hi guys,
we teach about opensource at our university, and I would love to
demonstrate to my students how to do BugZapping. I have a couple of
questions:
1) There are about 50 of them. If I request each one to make a Fedora
account, it's going to be a lot of accounts and lots of potential
complications. What should I do? Can all of them work simultaneously
on one account?
2) I plan to focus on finding duplicates and triaging radeon-related
stuff, because it's quite easy to explain stuff there (KMS/UMS,
xf86-video-radeon/radeonhd, card generations etc.), but I don't want
to limit myself to that. Any other suggestions what to work on?
Regards,
--
Vedran Miletić
--
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

I have a couple of questions:
1) There are about 50 of them. If I request each one to make a Fedora
account, it's going to be a lot of accounts and lots of potential
complications. What should I do? Can all of them work simultaneously
on one account?

Just for the initial demonstration session, I'd say it's fine for you to
create a single account for the whole class to use. If they want to go
on and do some Bugzapping work after the class, though, I'd say each
should register their own account at that point. Perhaps change the
password for the demo account after the class is over, so you will still
have access to it to answer any follow-ups on any of the bugs you touch.

2) I plan to focus on finding duplicates and triaging radeon-related
stuff, because it's quite easy to explain stuff there (KMS/UMS,
xf86-video-radeon/radeonhd, card generations etc.), but I don't want
to limit myself to that. Any other suggestions what to work on?

Hi guys,
we teach about opensource at our university, and I would love to
demonstrate to my students how to do BugZapping. I have a couple of
questions:
1) There are about 50 of them. If I request each one to make a Fedora
account, it's going to be a lot of accounts and lots of potential
complications. What should I do? Can all of them work simultaneously
on one account?
2) I plan to focus on finding duplicates and triaging radeon-related
stuff, because it's quite easy to explain stuff there (KMS/UMS,
xf86-video-radeon/radeonhd, card generations etc.), but I don't want
to limit myself to that. Any other suggestions what to work on?

Hi, Vedran - in addition to my reply to the list, just thought I'd ask
off-list if there's anything I or other Fedora folks could do to help
you out with this? In the way of pre-arranging sponsoring of a FAS
account or anything like that. If you let us know when the class is, we
might be able to arrange to have someone from QA online during the class
to help you out quickly if you hit any roadblocks along the way. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

On Wed, 2010-03-24 at 10:16 +0100, Vedran Miletić wrote:
> Hi guys,
>
> we teach about opensource at our university, and I would love to
> demonstrate to my students how to do BugZapping. I have a couple of
> questions:
> 1) There are about 50 of them. If I request each one to make a Fedora
> account, it's going to be a lot of accounts and lots of potential
> complications. What should I do? Can all of them work simultaneously
> on one account?
> 2) I plan to focus on finding duplicates and triaging radeon-related
> stuff, because it's quite easy to explain stuff there (KMS/UMS,
> xf86-video-radeon/radeonhd, card generations etc.), but I don't want
> to limit myself to that. Any other suggestions what to work on?
Hi, Vedran - in addition to my reply to the list, just thought I'd ask
off-list if there's anything I or other Fedora folks could do to help
you out with this? In the way of pre-arranging sponsoring of a FAS
account or anything like that. If you let us know when the class is, we
might be able to arrange to have someone from QA online during the class
to help you out quickly if you hit any roadblocks along the way. Thanks!

Probably you fell victum to reply-to munging. If you usually use reply to list,
reply to all or reply to recipients to respond to messages when you want the
list copied and want reply to sender to work as intended, then consider using
something like maildrop and reformail to strip reply-to headers pointing
to the Fedora lists at mail delivery. This makes the lists work more sanely.

On Wed, Mar 24, 2010 at 11:21:51 -0700,
Adam Williamson <awilliam(a)redhat.com&gt; wrote:
>
> Well hey, clearly I fail at sending off-list. =) Oh well!
Probably you fell victum to reply-to munging. If you usually use reply to list,
reply to all or reply to recipients to respond to messages when you want the
list copied and want reply to sender to work as intended, then consider using
something like maildrop and reformail to strip reply-to headers pointing
to the Fedora lists at mail delivery. This makes the lists work more sanely.

Hello Christopher,
I have since last year wanted to get involved in triaging/bug zapping, but was overwhelmed
on where to begin, I read this email and felt like I may have a starting point.mYou
suggested Rhythmbox as a place to start for Vedran Miletić's students, and since I use
Rhythmbox, I was thinking I could start there as well. The link you provided doesn't
directly show Rhythmbox? How would I find it? You also mention Nautilus?
Thank you for your time
Pats
----- Original Message ----
From: Christopher Beland <beland(a)alum.mit.edu&gt;
To: For testers of Fedora development releases <test(a)lists.fedoraproject.org&gt;
Sent: Wed, March 24, 2010 8:07:21 AM
Subject: Re: Students learning BugZapping
On Wed, 2010-03-24 at 10:16 +0100, Vedran Miletić wrote:

Hello Christopher,
I have since last year wanted to get involved in triaging/bug zapping,
but was overwhelmed on where to begin, I read this email and felt like
I may have a starting point.mYou suggested Rhythmbox as a place to
start for Vedran Miletić's students, and since I use Rhythmbox, I was
thinking I could start there as well. The link you provided doesn't
directly show Rhythmbox? How would I find it?

You can find all open bugs on Rhythmbox by using the handy
http://bugz.fedoraproject.org/ system:
http://bugz.fedoraproject.org/rhythmbox
or by doing a search in Bugzilla. Go to http://bugzilla.redhat.com/ ,
click Search. Selection Fedora under Classification, and Fedora under
Product, then hit 'Refresh Components/Versions/Milestones'. Then scroll
down the Component box and select rhythmbox. You can also change Status
to include MODIFIED, ON_DEV, ON_QA, VERIFIED, RELEASE_PENDING and POST
if you like, but for triaging purposes it may be best not to. Then just
hit the Search button.

On Wed, 2010-03-24 at 10:16 +0100, Vedran Miletić wrote:
> Hi guys,
>
> we teach about opensource at our university, and I would love to
> demonstrate to my students how to do BugZapping. I have a couple of
> questions:
> 1) There are about 50 of them. If I request each one to make a Fedora
> account, it's going to be a lot of accounts and lots of potential
> complications. What should I do? Can all of them work simultaneously
> on one account?
> 2) I plan to focus on finding duplicates and triaging radeon-related
> stuff, because it's quite easy to explain stuff there (KMS/UMS,
> xf86-video-radeon/radeonhd, card generations etc.), but I don't want
> to limit myself to that. Any other suggestions what to work on?
Hi, Vedran - in addition to my reply to the list, just thought I'd ask
off-list if there's anything I or other Fedora folks could do to help
you out with this? In the way of pre-arranging sponsoring of a FAS
account or anything like that. If you let us know when the class is, we
might be able to arrange to have someone from QA online during the class
to help you out quickly if you hit any roadblocks along the way. Thanks!

First off, thank you for your offer. I hoped someone from Fedora
Community will offer to jump in.
The class is held in two groups, one starts at 4pm, and other at 6pm
on monday, April 26 (CET). I believe it translates to 10am and 12pm in
EST.
It would above all be great if we could speed-up account creation and
getting privileges process.
--
Vedran Miletić

Just for the initial demonstration session, I'd say it's fine
for you to
create a single account for the whole class to use. If they want to go
on and do some Bugzapping work after the class, though, I'd say each
should register their own account at that point. Perhaps change the
password for the demo account after the class is over, so you will still
have access to it to answer any follow-ups on any of the bugs you touch.

We did it for the time being without accounts, they were offline and
posted info about bugs to Moodle.

> 2) I plan to focus on finding duplicates and triaging
radeon-related
> stuff, because it's quite easy to explain stuff there (KMS/UMS,
> xf86-video-radeon/radeonhd, card generations etc.), but I don't want
> to limit myself to that. Any other suggestions what to work on?
Beland's reply to this looks good to me.

This part is interesting. To get familiar with clicking around
bugzilla, I assigned them to looking into Xorg logs attached to bugs
and finding out details about graphics cards and KMS. Over 70% of
reports were usable, and I could go over them afterwards and change
summary on each bug.
I would like to push this further, as I discussed today with Matej on
IRC. Can we arrange it all somehow for next monday 1530 CET? I have
only one group of students, not two as planned earlier.
--
Vedran Miletić

2010/3/24 Adam Williamson <awilliam(a)redhat.com&gt;:
> Great idea!
I did an experimental class with this last week (a bit later than
planned, indeed), information below. Students reacted very well and
figured out how to do things pretty quickly.
> Just for the initial demonstration session, I'd say it's fine for you to
> create a single account for the whole class to use. If they want to go
> on and do some Bugzapping work after the class, though, I'd say each
> should register their own account at that point. Perhaps change the
> password for the demo account after the class is over, so you will still
> have access to it to answer any follow-ups on any of the bugs you touch.
We did it for the time being without accounts, they were offline and
posted info about bugs to Moodle.
>> 2) I plan to focus on finding duplicates and triaging radeon-related
>> stuff, because it's quite easy to explain stuff there (KMS/UMS,
>> xf86-video-radeon/radeonhd, card generations etc.), but I don't want
>> to limit myself to that. Any other suggestions what to work on?
>
> Beland's reply to this looks good to me.
This part is interesting. To get familiar with clicking around
bugzilla, I assigned them to looking into Xorg logs attached to bugs
and finding out details about graphics cards and KMS. Over 70% of
reports were usable, and I could go over them afterwards and change
summary on each bug.
I would like to push this further, as I discussed today with Matej on
IRC. Can we arrange it all somehow for next monday 1530 CET? I have
only one group of students, not two as planned earlier.

I'm glad to hear this went ahead, and sorry I wasn't around to help out
- I wrote it down in my Tasks list, but forgot that I'd be out of the
country at that time and didn't transfer it to the list I had in the UK.
D'oh!
I could be around next Monday, sure - I'll put it in my calendar this
time so I definitely don't lose it. =) Matej actually integrated a
function into the triage scripts at one point which automatically
extracted the correct card details from the first Xorg.0.log attached to
the bug and dumped them in the Whiteboard field, but I think it may be
broken at the moment; that's definitely a good way to handle that,
though. Could you outline what you want to do next week for the rest of
us, who weren't around for the IRC conversation? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

I'm glad to hear this went ahead, and sorry I wasn't around
to help out
- I wrote it down in my Tasks list, but forgot that I'd be out of the
country at that time and didn't transfer it to the list I had in the UK.
D'oh!
I could be around next Monday, sure - I'll put it in my calendar this
time so I definitely don't lose it. =) Matej actually integrated a
function into the triage scripts at one point which automatically
extracted the correct card details from the first Xorg.0.log attached to
the bug and dumped them in the Whiteboard field, but I think it may be
broken at the moment; that's definitely a good way to handle that,
though. Could you outline what you want to do next week for the rest of
us, who weren't around for the IRC conversation? Thanks!

Well, we didn't go into details, so nothing is set in stone. I would
actually run them by the concepts from the wiki pages linked at [1],
and then I would leave it to you to decide what to work on.
--
Vedran Miletić
[1] http://fedoraproject.org/wiki/BugZappers

Datuma 31. svibnja 2010. 17:18 Adam Williamson
<awilliam(a)redhat.com&gt;
je napisao/la:
> I'm glad to hear this went ahead, and sorry I wasn't around to help out
> - I wrote it down in my Tasks list, but forgot that I'd be out of the
> country at that time and didn't transfer it to the list I had in the UK.
> D'oh!
>
> I could be around next Monday, sure - I'll put it in my calendar this
> time so I definitely don't lose it. =) Matej actually integrated a
> function into the triage scripts at one point which automatically
> extracted the correct card details from the first Xorg.0.log attached to
> the bug and dumped them in the Whiteboard field, but I think it may be
> broken at the moment; that's definitely a good way to handle that,
> though. Could you outline what you want to do next week for the rest of
> us, who weren't around for the IRC conversation? Thanks!
Well, we didn't go into details, so nothing is set in stone. I would
actually run them by the concepts from the wiki pages linked at [1],
and then I would leave it to you to decide what to work on.

Cool. Is the time flexible at all? 3:30pm CET appears to be 6:30am PDT,
which is not when you'll find me at my brightest =)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

Datuma 31. svibnja 2010. 19:11 Adam Williamson
<awilliam(a)redhat.com&gt;
je napisao/la:
> Cool. Is the time flexible at all? 3:30pm CET appears to be 6:30am PDT,
> which is not when you'll find me at my brightest =)
I checked and we could indeed make it 4:00pm CET, but not adjust it
much more since it's not the last class in schedule that day. Would
that help?