12:00:37 <ndevos> #startmeeting
12:00:38 <zodbot> Meeting started Tue Dec 16 12:00:37 2014 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:38 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:00:47 <ndevos> agenda for today: https://public.pad.fsfe.org/p/gluster-bug-triage
12:00:52 <ndevos> #topic Roll Call
12:00:58 <partner_> _o/
12:00:59 * kkeithley_ is here
12:01:03 <ndevos> good morning, afternoon and evening!
12:01:22 * hagarth is partially here
12:01:36 <ndevos> oh, pranithk joins too?
12:01:38 * jdarcy is half here too.
12:02:17 <ndevos> Humble: you're here? seen Lala round?
12:02:33 * Humble is here
12:02:42 <ndevos> #chair partner_ kkeithley_ hagarth jdarcy Humble
12:02:42 <zodbot> Current chairs: Humble hagarth jdarcy kkeithley_ ndevos partner_
12:03:22 <ndevos> #topic Status of last weeks action items
12:03:33 <ndevos> #topic hagarth will look for somebody that can act like a bug assigner manager kind of person
12:03:43 <ndevos> hagarth: still in progress?
12:04:19 * ndevos assumes "yes
12:04:21 <ndevos> #topic pranithk to report how his team is assigning triaged bugs
12:04:22 <hagarth> ndevos: yes
12:04:29 <ndevos> :)
12:05:02 <ndevos> well, pranithk may not really be here after all?
12:05:04 <ndevos> #topic hagarth should update the MAINTAINERS file, add current maintainers and new components like Snapshot
12:05:34 <ndevos> hagarth: did you see http://review.gluster.org/9266 from Humble?
12:05:56 <ndevos> it adds the current sub-maintainers, so it is a start...
12:05:59 <hagarth> ndevos: yes, I think I have a review comment on that
12:06:09 <hagarth> to be passed on i.e.
12:06:37 <ndevos> ah, yes, it would be good to have that comment in Gerrit at one point
12:07:02 <ndevos> #topic lalatenduM will send a reminder to the users- and devel- ML about (and how to) fixing Coverity defects
12:07:17 <ndevos> did anyone see an email about this from lala?
12:07:33 <ndevos> I did not see one, but I could have missed it...
12:08:58 <ndevos> okay, nobody has an email about it, we'll keep it on the agenda for next week
12:09:11 <ndevos> #topic     lalatenduM will send a reminder to the users- and devel- ML about (and how to) fixing Coverity defects
12:09:17 <ndevos> ugh..
12:09:25 <ndevos> #topic Group Triage
12:09:57 <ndevos> no bugs proposed to discuss here
12:10:09 <ndevos> but we have some new bugs that we need to triage: http://goo.gl/0IqF2q\
12:10:48 <ndevos> please have a go at triaging some, and mention here which one you are doing
12:11:04 * ndevos mumblemumble irc_lock()
12:11:20 * ndevos takes 1173953
12:11:37 <hagarth> right URL - goo.gl/0IqF2q
12:11:55 <hagarth> rather - http://goo.gl/0IqF2q
12:13:39 * hagarth locks 1173437
12:15:08 * Humble locks 1174625
12:17:02 * ndevos locks 1172458
12:19:08 <gothos> o/
12:26:23 * Humble locks 1173909
12:26:43 <ndevos> hey, I just wanted to take 1173909!
12:27:21 * ndevos try_irc_lock(1172348)
12:28:08 <soumya> looking at 1173732
12:29:12 <Humble> ndevos, I have put a comment and set the keyword
12:29:24 <Humble> but if u have anything to add , please feel free
12:29:32 <Humble> I am releasing the lock
12:30:25 <ndevos> Humble: I got an -EWOULDBLOCK and moved on
12:30:47 <Humble> ignore (-EWOULDBLOCK) :)
12:32:28 <Humble> list is empty .. Isnt it?
12:34:14 <kkeithley_> 1172348 is still there
12:35:34 <ndevos> no its not
12:36:19 <kkeithley_> indeed, not now
12:36:33 <ndevos> thanks all, the new bugs have been done!
12:36:51 <ndevos> now, we still have some time, and we can still triage some older bugs, yay!
12:37:43 <ndevos> these are *all* the older bugs that still need some form of triaging: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=keywords&keywords=Triaged%2CFutureFeature&keywords_type=nowords&list_id=3014117&o1=nowords&product=GlusterFS&query_format=advanced&v1=Triaged
12:38:45 <ndevos> or, you can have a look at some bugs for a particular version
12:38:55 <ndevos> like for 3.5: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&product=GlusterFS&f1=keywords&f2=version&o1=nowords&o2=regexp&v1=Triaged&v2=^3.5
12:39:20 <ndevos> if you want a different version, just replace the 3.5 at the end of the url to 3.6, mainline or 3.4
12:39:45 <ndevos> and please do lock the bugs that you want to triage again :)
12:40:45 <ndevos> oh, and as a reminder, the https://public.pad.fsfe.org/p/gluster-bug-triage contains some example urls to list bugs per component to
12:40:48 <ndevos> o
12:41:46 * ndevos locks 1065620
12:51:13 <hagarth> ndevos: how about making this asynchronous?
12:51:35 <hagarth> i.e. sending out an email with the list of bugs to be triaged by next week?
12:55:19 <ndevos> hagarth: we can do, but I very much doubt things get done that way :-/
12:55:51 <hagarth> ndevos: I was thinking of trying that out for the backlog
12:55:58 <ndevos> hagarth: a limited list of bugs in a webapp would still be very attractive :)
12:56:05 <hagarth> live triage can continue to happen for newer bugs here
12:57:18 <ndevos> hmm, still, I would like to be able to send a URL that lists 5-10 bugs that need triaging...
12:57:38 <hagarth> ndevos: yeah
12:57:40 * ndevos needs to think about it a little more
12:57:47 <ndevos> #topic Open Floor
12:58:01 <ndevos> so, its almost time to finish the meeting
12:58:21 <ndevos> but, now you can bring other topics - like hagarth did :)
12:58:29 <hagarth> ndevos: sorry for being OT then :)
12:58:32 <ndevos> :P
12:58:43 <hagarth> ndevos: any progress on the webapp / dashboard?
12:59:05 <ndevos> hagarth: no, I did not have time for that, and I did not hear about it from others either
12:59:46 <ndevos> #agreed We need some way or form to show the bug triage backlog and make it easier for others to triage some bugs
12:59:52 <hagarth> ndevos: let me check back on that thread. It would be cool to have one such page.
13:00:26 <ndevos> hagarth: definitely! and it's almost holiday season here, so I actually may find some time to look at it :)
13:00:37 <hagarth> ndevos: are we better off discussing coverity bugs in tomorrow's meeting?
13:00:53 <hagarth> I would like to pull down the outstanding coverity defects by 3.7
13:00:59 <ndevos> hagarth: we discussed it last week, Lala had an action item for it
13:01:36 <hagarth> ndevos: ok! I think a weekly outstanding coverity analysis report would be good to have in gluster-devel
13:02:03 <ndevos> hagarth: that was my suggestion too... but they already get sent :D
13:02:18 <ndevos> well, not completely weekly, but regulary
13:02:22 <hagarth> ndevos: no, we need a better breakup I think
13:02:37 <hagarth> like glusterd has XX defects, nfs has YY defects & so on
13:02:50 <hagarth> the reports that we send contains results from the latest scan only
13:03:19 <hagarth> gothos: just approved your coverity scan request
13:03:27 <ndevos> hagarth: hmm, okay, I'm not sure what we discussed last week, maybe we mentioned something like that to
13:03:29 <gothos> hagarth: thx
13:03:30 <ndevos> o
13:04:07 <hagarth> ndevos: maybe having something like https://scan.coverity.com/projects/987?tab=overview out for everybody's attention
13:04:57 <ndevos> hagarth: yes, something like that would be good
13:06:13 <hagarth> that's all I have for now
13:06:35 <ndevos> #action hagarth will speak with LalatenduM about the Coverity Scan emails and a new format
13:06:51 <hagarth> ndevos: cool, will do.
13:06:54 <ndevos> I guess lala will get in touch with you for some ideas :)
13:06:58 <ndevos> #endmeeting