12:00:20 <jiffin> #startmeeting Gluster Bug Triage
12:00:20 <zodbot> Meeting started Tue May 31 12:00:20 2016 UTC.  The chair is jiffin. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:20 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
12:00:20 <zodbot> The meeting name has been set to 'gluster_bug_triage'
12:01:14 <jiffin> So who all present to help me here
12:01:21 * kkeithley is here
12:01:25 * ndevos _o/
12:01:29 <jiffin> #topic Roll call
12:01:34 * Saravanakmr is here
12:01:47 <jiffin> hi kkeithley ndevos Saravanakmr
12:01:59 <ndevos> hello jiffin!
12:01:59 <jiffin> Manikandan, rafi, hgowtham: ??
12:02:11 * hgowtham here
12:02:12 * rafi is here
12:02:14 * Manikandan is here
12:02:28 <ndevos> and maybe atinm, poornimag, rastar and others?
12:03:05 <jiffin> K lets start
12:03:08 <rafi> ashiq
12:03:22 * partner bg
12:03:49 <jiffin> agenda for today's meeting #link https://public.pad.fsfe.org/p/gluster-bug-triage
12:04:10 <jiffin> partner: welcom
12:04:59 <jiffin> Status of last weeks action items
12:05:12 <jiffin> #topic msvbhat    will look into lalatenduM's automated Coverity setup in  Jenkins  which  need assistance from an admin with more permissions
12:05:17 <ndevos> you can skip anything with my name next to it, I guess...
12:05:28 <jiffin> ndevos: k
12:05:31 <jiffin> msvbhat: ??
12:05:43 <ndevos> I think kkeithley took that AI over?
12:06:01 <msvbhat> jiffin: Ah, not done yet. I don't find lalatenduM in office these days.
12:06:01 <jiffin> ndevos: oh, I was not aware of that
12:06:14 <jiffin> msvbhat: hmm
12:06:20 <msvbhat> jiffin: But I appreciate if someone else takes care of this now
12:06:26 <jiffin> kkeithley: ??
12:06:37 <kkeithley> no, I run my own Coverity (on an internal lab machine)  Lala was using either Coverity's community service or another internal thing
12:07:09 <ndevos> do we need more than one coverity regular run?
12:07:23 <jiffin> kkeithley: so can we make it done?
12:07:39 <kkeithley> I'm waiting to get a public facing machine (hooked into the jenkins infra probably) so I can move Coverity, clang, and other stuff off the internal lab machine.
12:07:54 <jiffin> kkeithley: k
12:08:44 <jiffin> then I will change the action item then
12:08:48 <kkeithley> I don't know what the state of Lala's Coverity runs are.  In any event he's not part of Gluster anymore so I don't think he has a vested interest in maintaining it. (Although he may be doing it, I don't know)
12:10:11 <jiffin> can u send a mail to lalatenduM regarding that, as msvbhat mention it is vey difficult to lalatenduM these days in office
12:10:17 <ndevos> kkeithley: I think you're the lucky one that now gets the job, whatever it is, as you are our local (and remote) coverity specialist
12:10:34 <jiffin> may be ccing glusterdevel
12:11:04 <kkeithley> haha.  I'm happy to share.  Anyone want to help out?
12:11:21 <Saravanakmr> kkeithley, :) I can
12:11:33 <jiffin> Saravanakmr: great
12:11:38 <kkeithley> kewl.
12:11:51 <Saravanakmr> kkeithley, I can help to an extent :) not a jenkins/coverity expert
12:11:54 <ndevos> Saravanakmr++ nice!
12:11:56 <kkeithley> Not much to do atm, once misc and nigelb get us a machine...
12:12:11 <kkeithley> s/machine/vm/
12:12:44 <jiffin> #action kkeithley Saravanakmr will set up Coverity, clang, etc on public facing machine and run it regularly
12:13:05 <kkeithley> for now coverity, clang, cppcheck results are posted at http://download.gluster.org/pub/gluster/glusterfs/static-analysis/
12:13:30 <jiffin> #link  http://download.gluster.org/pub/gluster/glusterfs/static-analysis/
12:14:01 <kkeithley> I don't know about having an AI on us though.  We're stuck in the queue behind higher priority gerrit and jenkins work that misc and nigelb are doing.
12:14:12 <nigelb> kkeithley: Are your scripts for these published?
12:14:35 <kkeithley> they are not
12:14:36 <jiffin> kkeithley: just keeping it noted
12:14:44 <jiffin> thats all
12:14:45 <ndevos> kkeithley: maybe we should also note the availability of those results in http://gluster.readthedocs.io/en/latest/Contributors-Guide/Index/ or somewhere?
12:15:08 <nigelb> kkeithley: Please publish them, so I can look at working them into Jenkins?
12:15:08 <kkeithley> good idea
12:16:34 <jiffin> moving on
12:16:42 <jiffin> skip two of the niels Al
12:16:58 <jiffin> sorry
12:17:09 <jiffin> skipping two of the ndevos Al
12:17:26 <jiffin> #action ndevos need to decide on how to provide/use debug builds
12:17:37 <jiffin> #action ndevos to propose some test-cases for minimal libgfapi test
12:17:43 <ndevos> oh, yes everyone was confused about who this niels person is
12:17:59 <jiffin> #topic Manikandan and gem to followup with kshlm to get access to gluster-infra
12:18:08 <Manikandan> jiffin, We could not get in touch with him
12:18:17 <jiffin> including me
12:18:25 <jiffin> Manikandan: k
12:18:29 <Manikandan> We pinged him as well, but did not receive replies from him
12:18:38 <ndevos> Manikandan: nigelb might be able to help out with that too
12:19:00 <Manikandan> ndevos, we will check out with him soon
12:19:22 <nigelb> access needs misc. He has the ansible scripts/salt scripts.
12:19:34 <nigelb> (kshlm is on PTO for another week)
12:20:10 <jiffin> Manikandan: you got a lot of options now
12:20:26 <Manikandan> jiffin, yep
12:20:30 <ndevos> nigelb: its about scripts that Gerrit executes on events, but Manikandan and gem will surely discuss that with you :)
12:20:41 <jiffin> #action Manikandan and gem to followup with kshlm/misc to get access to gluster-infra
12:21:02 <Manikandan> nigelb, we will discuss this with you when you are free tomorrow
12:21:09 <nigelb> sure.
12:21:24 <Manikandan> nigelb, ndevos thanks :-)
12:22:22 <jiffin> #topic Group Triage
12:22:41 <jiffin> #link https://public.pad.fsfe.org/p/gluster-bugs-to-triage
12:23:31 <jiffin> everyone heads up pick grab ur bug
12:23:55 <jiffin> kkeithley, ndevos, rafi, Saravanakmr, Manikandan, hgowtham:
12:27:25 <jiffin> we  can triage upto line 100 for Bugs with incorrect status
12:27:30 <jiffin> ?
12:27:45 <kkeithley> okay
12:27:53 <Saravanakmr> ok
12:29:49 <jiffin> rafi, hgowtham: 1290295 1290975 1292359 are tiering related bugs, you guys know the correct status right?
12:30:27 <hgowtham> jiffin, i have took 1292945 and will take a few mre
12:30:36 <jiffin> hgowtham: okaey
12:31:11 <kkeithley> this list has some bitrot.  After the meeting I'll update it with Niels' latest list
12:32:30 <jiffin> kkeithley: okay
12:35:25 <ndevos> jiffin, kkeithley: maybe we should create that list on monday-tuesday night?
12:35:48 <jiffin> ndevos: Yeah that's right way to do it
12:36:11 <kkeithley> sure, can you send me (or post) the query you use to generate the list?
12:36:16 <kkeithley> s/list/report/
12:36:41 <jiffin> ndevos, kkeithley, rafi, hgowtham:  Saravanakmr Manikandan : we are done with triaging
12:36:43 <ndevos> kkeithley: its the check-bugs.py script in https://github.com/gluster/release-tools
12:36:58 <hgowtham> jiffin, :)
12:37:06 <ndevos> and it takes a couple of minutes to run :)
12:37:25 <jiffin> moving to next topic
12:37:34 <jiffin> #topic Get moderators for June 2016
12:38:33 <jiffin> we need host for June 7th, June 14th , June 21st, June 28th
12:39:10 <Saravanakmr> jiffin, I can host on June 14
12:39:13 <jiffin> please raise hand for ur favorite date
12:39:19 <jiffin> Saravanakmr: thanks
12:39:42 <jiffin> hgowtham, Manikandan, rafi, kkeithley, ndevos: ??
12:40:20 <jiffin> #action Saravanakmr will host bug triage meeting on June 14th 2016
12:40:24 <Manikandan> June 14 I will do
12:40:33 <ndevos> I'll be travelling next week and wont be available
12:40:40 <jiffin> Manikandan: its already picked
12:40:45 <ndevos> Saravanakmr, Manikandan: FIGHT!
12:40:49 <Manikandan> jiffin, 21st then
12:40:50 <Manikandan> :P
12:41:01 <jiffin> Manikandan: thanks
12:41:05 <Manikandan> ndevos, nope, giving chances ;-)
12:41:14 <Saravanakmr> :)
12:41:31 <jiffin> #action Manikandan will host bug triage meeting on June 21st 2016
12:41:45 <jiffin> two more slots
12:42:10 <jiffin> ndevos: you can take June 28th , right?
12:42:33 <ndevos> jiffin: just checked my calendar, yes, 28 should work
12:42:54 <jiffin> #action ndevos will host bug triage meeting on June 28th 2016
12:43:18 <ndevos> kkeithley: btw, the /topic is not correct, and you have the super powers to fix it?
12:43:43 <jiffin> it seems I need to host it for June 7th
12:43:52 <kkeithley> Next weekly community meeting 12:00 UTC  1 June 2016 | Agenda https://public.pad.fsfe.org/p/gluster-community-meetings } Minutes of all our meetings https://meetbot.fedoraproject.org/sresults/?group_id=gluster-meeting&type=channel
12:44:09 <jiffin> #action Jiffin will host bug triage meeting on June 7th 2016
12:44:25 <jiffin> Moving to next topic
12:44:27 <ndevos> kkeithley: *so* close!
12:44:39 <kkeithley> ???
12:44:43 <jiffin> #topic Open Floror
12:44:57 <jiffin> sorry again
12:45:07 <jiffin> #topic Open Floor
12:45:20 <ndevos> kkeithley: uhm, try again, but put /topic in front of that line
12:45:47 <kkeithley> Just need to try again with more coffee in my system
12:45:57 <jiffin> we have 15 more minutes, any interesting topic to discuss
12:46:21 <ndevos> jiffin: do you know if any of the component maintainers/developers use the BZ queries or RSS-feeds for the Triaged bugs?
12:46:43 <jiffin> kkeithley: coffee worked I guess
12:46:49 <jiffin> ndevos: nope
12:47:05 <jiffin> I don't think so
12:47:21 <ndevos> hmm, how could we make them more aware of that?
12:47:43 <jiffin> i usually filter bugs based on component in my mail client
12:48:13 <Saravanakmr> maybe add it here :)  http://gluster.readthedocs.io/en/latest/Contributors-Guide/Index/
12:48:27 <ndevos> we have a link to a BZ query on the bottom of http://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/
12:48:34 <Saravanakmr> ndevos, ok
12:49:10 <ndevos> Saravanakmr: yeah, we need more links, and per component somewhere
12:50:34 <jiffin> ndevos: we can spread the word out via mail
12:50:44 <ndevos> kkeithley: ah, I just came across this link http://gluster.readthedocs.io/en/latest/Developer-guide/Fixing-issues-reported-by-tools-for-static-code-analysis/
12:51:00 <jiffin> ndevos: I am not sure how much will that be effective ?
12:51:22 <ndevos> jiffin: yeah, and in that email we should point to the docs for developers - and that doc should have example links for bz-queries and rss-feeds
12:52:46 <jiffin> ndevos: so what do you suggest?
12:53:25 <ndevos> someone should start documenting what the next steps are for bugs that have been triaged
12:54:16 <ndevos> that means, explaining how to filter emails with the Triaged keyword, and a component, a BZ-query with them and RSS-feed
12:55:18 <jiffin> thats part-1 and what about part-2 how we can make sure about developers/maintainers looking into the triaged bug?
12:56:11 <ndevos> is should be part of the maintainers guidelines, and any developer working on a component should probably setup such fileters/notifications too
12:56:24 <jiffin> ndevos: K
12:57:42 <jiffin> ndevos: shall I add AI for that?
12:58:12 <ndevos> jiffin: yeah, but who would be doing that?
12:58:57 <jiffin> ndevos: IMO you have more view points on that, I strongly suggests ur name
12:59:38 <ndevos> jiffin: I feel a little like a black hole for action items...
12:59:52 <jiffin> lets take this discussion for next week
13:00:18 <jiffin> we are running out of time
13:00:37 <ndevos> sure, just put something on the agenda about it :)
13:00:52 <jiffin> #action ? decide how component maintainers/developers use the BZ queries or RSS-feeds for the Triaged bugs
13:01:02 <ndevos> :)
13:01:54 <jiffin> thats all for today, I hope partner u got some idea about bug triage works
13:02:06 <ndevos> jiffin++ thanks!
13:02:15 <jiffin> appreciates everyone's participation, bye
13:02:21 <jiffin> #endmeeting