12:08:17 <ndevos> #startmeeting
12:08:18 <zodbot> Meeting started Tue Aug  4 12:08:17 2015 UTC.  The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:08:18 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:08:29 * jiffin is here
12:08:33 <ndevos> #info agenda: https://public.pad.fsfe.org/p/gluster-bug-triage
12:08:40 <ndevos> #toptic Roll Call
12:08:48 <ndevos> #toptc Roll Call
12:08:55 <ndevos> #topic Roll Call
12:09:08 <ndevos> okay, so, who's there?
12:09:32 * pranithk is here
12:09:34 <kdhananjay> me is here
12:09:46 * kdhananjay is here
12:10:03 * skoduri is here for half an hour :)
12:10:11 * kkeithley_ is here
12:10:39 <ndevos> #topic Status of last weeks action items
12:10:58 <ndevos> #topic need to discuss about a new locking mechanism
12:11:18 * ndevos skips the topics where the assignee is not online
12:11:41 <ndevos> kdhananjay: can you explain what the issue is with the current locking?
12:11:59 <ndevos> do you mean the irc-locks that we use for the triage?
12:12:06 <kdhananjay> ndevos: Yes :)
12:12:26 <kdhananjay> ndevos: I participated in the bug triage meeting for the first time last week,
12:12:26 <ndevos> kdhananjay: how does an etherpad make it easier?
12:13:00 <kdhananjay> kdhananjay: I had to constantly look at two places: The IRC window to see who is locking what and refresh the bugzilla page.
12:13:17 <ndevos> kdhananjay: right, that is indeed not optimal
12:13:55 <kdhananjay> ndevos: I had to mentally delete those bug ids in my head which were locked by the participants.
12:14:11 <kdhananjay> ndevos: And focus on the ones which hadn't been locked at that point.
12:14:23 <ndevos> kdhananjay: how do you suggest using an etherpad?
12:15:48 <kdhananjay> ndevos: I was thinking maybe 1) put out the list on an etherpad, 2) each lockee "strikes" out the bug he/she wants to triage, 3) anytime you want to lock you look at the lines that have not been struck out
12:16:17 <ndevos> kdhananjay: sounds good to me :)
12:16:20 <pranithk> kdhananjay++
12:16:31 <skoduri> +!
12:16:33 <skoduri> +1
12:16:33 <kdhananjay> ndevos: Each participant could optionally write their names too beside their choice
12:18:01 <ndevos> #agreed we'll try to use an etherpad for triaging bugs today, see how it works
12:18:07 <kdhananjay> So the updates would be atomic. ;)
12:18:43 <ndevos> yeah, should be easy enough :)
12:18:56 <ndevos> #topic <someone> will send a reminder to the users- and devel- ML about (and how to) fixing Coverity defects
12:19:10 <ndevos> do we have anyone that wants to take this up?
12:19:28 <ndevos> remind newcomers how to find easyfix bugs and send patches?
12:20:04 <ndevos> ... I guess we'll try again next week?
12:20:57 <pranithk> ndevos: I will take that up. The easybugs thing
12:21:09 <ndevos> pranithk: thanks!
12:21:47 <ndevos> #action pranithk will send a reminder on how to find and fix bugs, attract new contributors
12:21:53 <ndevos> #topic Group Triage
12:22:54 <ndevos> #info 10 new bugs that have not been triaged yet
12:23:03 <ndevos> for lockung, we'll use  https://public.pad.fsfe.org/p/gluster-bugs-to-triage
12:23:09 <ndevos> *locking even
12:23:25 <ndevos> when you are going to triage a bug, strike the line through :)
12:23:45 <kkeithley_> http://goo.gl/WuDQun ?
12:23:52 <kkeithley_> Oh, sorry, nm
12:28:25 <skoduri> have to quit the meeting now :( ..bbye !
12:37:13 <ndevos> kdhananjay: are you almost done with triaging bug 1248123 ?
12:38:03 <ndevos> and who is triaging Bug 1248669 - all: Make all the xlator fops static to avoid incorrect symbol resolution ?
12:38:25 <kdhananjay> ndevos: done
12:39:02 <ndevos> kkeithley_: did you want to triage 1248669 ?
12:39:59 <ndevos> well, I guess either Soumya or kkeithley_ will have a look at it soon
12:40:08 <ndevos> #topic Open Floor
12:40:26 <ndevos> #info reminder, bugs and the status of their patches in Gerrit: http://bugs.cloud.gluster.org/
12:40:42 <ndevos> does anyone else have topics for today?
12:40:44 <pranithk> ndevos: how is the new way of doing bug-triage? I quite like the new method :-)
12:40:44 <kkeithley_> Soumya did the strike-through on 1248669, but I can do it if she didn't finish
12:41:10 <ndevos> kkeithley_: yeah, have a look, and fix the commit message of the patch you sent
12:41:25 <pranithk> ndevos: how do we do follow ups if the bugs are being looked up by the respective owners?
12:41:53 <ndevos> pranithk: the etherpad works for me, it should be easy enough to upate it too
12:42:24 <kkeithley_> oh, are we ready to say that my change-set is the correct fix for 1248669?
12:42:45 <pranithk> ndevos: how do we do follow ups if the bugs are being looked up by the respective owners?
12:43:13 <jiffin> ndevos: its better  to mention our name while striking out the bugs in etherpad as a must
12:43:27 <pranithk> jiffin: +1
12:44:35 <pranithk> ndevos: how do we do follow ups if the bugs are being looked up by the respective owners?
12:44:47 <ndevos> kkeithley_: yeah, I think it addresses the point
12:45:22 <ndevos> pranithk: the bugs are listed in the next 4 weeks, as long as you set a needinfo
12:45:46 <pranithk> ndevos: Sorry, didn't get you?
12:46:12 <pranithk> ndevos: we add people in CC, but what if someone forgot to follow up. How do we remind them again?
12:46:26 <ndevos> pranithk: if you need to follow up, set a needinfo, and the bugzilla query will list it to triage next week again
12:46:46 <pranithk> ndevos: Even if it is the developer?
12:47:03 <pranithk> ndevos: so we do CC and then set needinfo on one of the developers?
12:47:12 <ndevos> pranithk: if it is the developer, the bug should be assigned, and the developer should just work on it
12:47:57 <ndevos> pranithk: the maintainers (and the development teams) should check for triaged bugs regulary, and assign those
12:48:26 <pranithk> ndevos: hmm...
12:48:28 <pranithk> ndevos: ok
12:48:35 <ndevos> pranithk: the triage we do now, is just the pre-check if all details are in the bug, and a developer could start working on it
12:48:46 <pranithk> ndevos: got it
12:49:05 <ndevos> ok!
12:49:13 <ndevos> anything else to discuss?
12:50:00 <ndevos> oh, maybe a status update on the upcoming automated bugzilla status/assignee work
12:50:42 <ndevos> #info tasks on https://public.pad.fsfe.org/p/gluster-automated-bug-workflow have been assigned
12:51:04 <ndevos> #info automated bug status correction should be ready before the end of september
12:51:25 * ndevos does not have anything else to note
12:51:50 <ndevos> if there is nobody else that wants to mention something, we'll finish the meeting in a bit
12:53:37 <ndevos> thanks for joining, and talk to you next week again!
12:53:41 <ndevos> #endmeeting