[00:01] <grmls> hi
[17:21] <alo21> hi all
[18:29] <alo21> could someone help me on triaging bug?
[18:30] <alo21> htorque: can you help me?
[18:35] <alo21> JackyAlcine_: can you help me?
[18:35] <JackyAlcine_> Depends, what's up?
[18:40] <alo21> JackyAlcine_: I am a new triaging, and I am a little bit unsecure
[18:40] <alo21> JackyAlcine_: so... I would ask you if I am doing the right things
[18:41] <alo21> JackyAlcine_: could follow me for two easy bugs?
[18:42] <JackyAlcine_> Well, I haven't really triaged a bug before, so I'd most definitely you astray.
[18:43] <JackyAlcine_> I hang out here to see if there's a bug that someone reports that I could fix.
[18:44] <Laibsch> alo21: the first mistake you are making is asking if it's OK to ask intead of simply laying out the problem/question you have.
[18:44] <alo21> Laibsch: ok...
[18:44] <JackyAlcine_> Yeah, that's the way of IRC.
[18:44] <JackyAlcine_> Don't ask to ask, just ASK :)
[18:45] <alo21> Laibsch: as I sad I am little unsecure if I am doing the right things
[18:45] <alo21> JackyAlcine_: ok :)
[18:46] <JackyAlcine_> Only can be sure of yourself if you take that jump.
[18:50] <alo21> JackyAlcine_: If I will make a mistake?
[18:50] <JackyAlcine_> It isn't a problem if you do.
[18:51] <JackyAlcine_> If you think of all of the bugs on Launchpad as a bug, we've made hundred of thousands of them.
[18:51] <JackyAlcine_> Be open about it, you'll not only learn from it, but be able to tell others that might have the same question how to go about solving that problem.
[18:51] <JackyAlcine_> Sharing the wealth :)
[18:54] <alo21> JackyAlcine_: the problem is... I haven't got the wealth
[18:54] <JackyAlcine_> We'd be able to give it to you if you tell us your problem.
[18:56] <alo21> JackyAlcine_: my problem is: be not secure if is right what I am doing
[18:58] <JackyAlcine_> I don't understand.
[18:58] <JackyAlcine_> But what I'm trying to say, if you don't tell us, we can't help you.
[18:58] <JackyAlcine_> Gotta give to get.
[19:01] <alo21> JackyAlcine_: ok...
[19:02] <alo21> JackyAlcine_: I think bug 954519 should put as wishlist
[19:02] <ubot2`> Launchpad bug 954519 in overlay-scrollbar "Wishlist: Enable resizing with the thumb in nautilus 'Extra Pane' mode" [Undecided,New] https://launchpad.net/bugs/954519
[19:02] <alo21> JackyAlcine_: right?
[19:03] <JackyAlcine_> It's already marked as a wishlist, though.
[19:06] <tsimpson> it's [Undecided,New]
[19:07] <Laibsch> the wishlist is in the title, not the actual priority setting
[19:08] <Laibsch> alo21: I'd say that generally you shouldn't worry too much about setting priorities.
[19:08] <alo21> Laibsch: ok..
[19:08] <Laibsch> priorities are up to the developers, unless they are on a paid contract nobody can force anybody to do anything
[19:09] <Laibsch> alo21: how come you picked that bug?
[19:09] <yofel> Laibsch: the bug importance should be set as soon as possible using the criteria on https://wiki.ubuntu.com/Bugs/Importance
[19:09] <yofel> alo21: ^
[19:10] <yofel> but you don't usually set it by itself, except when it's the only thing to do for a bug (like needs-packaging bugs, etc...)
[19:11] <alo21> yofel: so my work is only check if bugs are well written?
[19:11] <Laibsch> well, I guess I'm known no to always go d'accord with whatever is the latest fashion in the wiki.  I still think that importance is not so important ;-)
[19:12] <Laibsch> alo21: not only that
[19:12] <Laibsch> but also
[19:12] <Laibsch> a) can you reproduce the bug
[19:12] <yofel> alo21: it's to make sure that the bug has all information on it to be fixed and the people that know how to fix it know about the bug
[19:12] <Laibsch> b) is the bug assigned to the right package
[19:12] <Laibsch> c) should the bug be dealt with upstream
[19:13] <Laibsch> d) does the bug have all the information, in a concise and easy to digest manner
[19:13] <Laibsch> the whole reason for triaging is to leverage the time of the devs better
[19:13] <yofel> overlay-scrollbar is what provides that modified scrollbar for unity, right?
[19:13] <Laibsch> to make sure they can dive right in and fix the problem
[19:18] <alo21> Laibsch: yofel how did you triage your fist bug
[19:19] <Laibsch> it's been so long, I don't remember
[19:19] <yofel> me neither, that was like 3 years ago ^^
[19:19] <Laibsch> I think maybe you should stop thinking of "I am triaging" and simply think of what you can do to improve the status of the bug
[19:19] <Laibsch> I've given a number of examples up above
[19:19] <yofel> IIRC I looked for duplicates back then
[19:20] <yofel> yeah, as Laibsch said
[19:20] <Laibsch> yes, get yourself an angle and then attack from that vector
[19:21] <Laibsch> alo21: one thing you could do is to start with one package that is not so widely used but that you like
[19:21] <Laibsch> go through all the bug, merge dupes and either confirm or reject (after discusion with the reporter)
[19:21] <Laibsch> then the bugs for that package are in picture perfect shape
[19:22] <Laibsch> I quite often do that when I am playing around with a new software package
[19:22] <Laibsch> gives me a good feeling about well-maintained the software is, too
[19:34] <jalcine> See how productive that was, alo21? :) Don't be afraid to speak up next time.
[19:34] <jalcine> I was wrong here, but I learned a bit here too.
[19:59] <alo21> lifeless: an easy package?
[20:03] <alo21> can someone suggest me an esy package to triage?
[20:08] <alo21> mythos: hi
[20:41] <hggdh> alo21: when you start triaging, everything will be overwhelming. This is normal. The best way to start is to look at packages you yourself also use. Then you browse the bugs list for this package, and
[20:41] <hggdh> alo21: try to find one you understand (or do not completely fail to understand)
[20:42] <hggdh> then you follow Laibsch's, yofel's and other's suggestions. And ask for help :-)
[20:43] <alo21> hggdh: most of thunderbird's bugs are commented yet
[20:43] <hggdh> are, or are not?
[20:44] <hggdh> I would strongly suggest to keep clear of complex packages -- Thunderbird, firefox, Chromium-browser, Java, GCC, linux (the kernel itself), sound issues, display (X) issues, etc
[20:45] <hggdh> these usually require a more detailed knowledge of package internals (or even hardware)
[20:47] <alo21> hggdh: do you know an easy package?
[20:48] <hggdh> hum. Easy is in the eyes of the beholder. What applications you usually run on your machine?
[20:50] <hggdh> alo21: also (if you do not mind saying it) what is your background? Sciences, programming, whatever
[20:53] <alo21> hggdh: usaully is use firefox, thunderbird, skype and sometimes gcc
[20:53] <alo21> hggdh: my background is sciences and a little bit of programming
[20:53] <hggdh> OK
[20:54] <hggdh> skype is closed-source, so there is nothing we can do about it
[20:55] <alo21> yep
[20:55] <hggdh> GCC, and other languages' bugs are usually extremely complex if you do not have a background on languages, parsing, optimisation, etc
[20:56] <alo21> you right
[20:56]  * hggdh did a bit of it a looong time ago, and found the theory of parsing, translation and compiling to be a PITA
[20:57] <alo21> hggdh: with what package did you start?
[20:59] <hggdh> alo21: I do not quite remember, but I was very involved on Evolution (the previous default email client for Ubuntu)
[20:59] <hggdh> but what I actually did was what I suggested -- started browsing thru the bugs, looking for something that I could understand
[20:59] <hggdh> alo21: gotta go, back in ~ 2 hours
[21:18] <lifeless> alo21: ?
[21:18] <alo21> lifeless: yes?
[21:19] <lifeless> alo21: you said '08:59 < alo21> lifeless: an easy package?'
[21:19] <lifeless> alo21: what did you mean ?
[21:19] <alo21> lifeless: I asked if you know an easy package
[21:20] <alo21> in this way I can practice triaging
[21:20] <lifeless> as hggdh says
[21:23] <alo21> lifeless: is very hard
[21:27] <alo21> lifeless: could you give me link where to look for new bug?
[21:28] <lifeless> sorry, I'm in the middle of a bunch of other things
[21:28] <lifeless> follow hggdh's suggestions
[21:28] <lifeless> or Laibsch's whom you were talking to before
[21:28] <alo21> lifeless: ok thanks