12:00:26 #startmeeting Gluster Bug Triage 12:00:26 Meeting started Tue Jun 14 12:00:26 2016 UTC. The chair is Saravanakmr. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:26 The meeting name has been set to 'gluster_bug_triage' 12:00:37 #info agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 12:00:49 #topic Roll call 12:00:56 * kkeithley is here 12:01:30 * partner here but bg 12:01:31 Hi to kkeithley :) 12:01:38 hi 12:02:05 jiffin, skoduri hgowtham 12:02:10 * jiffin is here 12:02:15 * skoduri is here 12:02:15 * hgowtham is here 12:02:25 please feel free to ping others ;) 12:02:46 ndevos, :) 12:02:52 manikandan is not here 12:03:00 hgowtham, ok 12:03:14 rafi, 12:04:44 ok..lets start 12:04:59 #topic kkeithley Saravanakmr will set up Coverity, clang, etc on public facing machine and run it regularly 12:05:36 * ndevos _o/ 12:05:37 let's move this to the community meeting where it will get more visibility. waiting for misc and nigelb to set up the jenkins slave for this 12:05:59 kkeithley, I have setup clang locally and verified 12:06:43 coverity seems to be a commercial one (with my limited knowledge) .. correct if I am wrong. 12:06:53 okay. I have them running nightly on an internal lab machine, and the results are posted at http://download.gluster.org/pub/gluster/glusterfs/static-analysis/ 12:07:09 yes, coverity is commercial/proprietary 12:07:34 but it's preferable to have it be public and run under the jenkins framework 12:07:59 kkeithley, hmm... 12:08:05 misc and nigelb are running as fast as they can, but moving the agenda item to community meeting will make it more visible 12:08:12 kkeithley, results seems empty here http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/ 12:08:39 http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2016-06-13-e0b057cf/cov-errors.txt looks pretty full to me 12:09:15 I wonder why you're not seeing the same thing I'm seeing 12:09:26 kkeithley, oh..ok..I checked first three directories :( 12:10:19 ah, yeah, that's probably when the previous version of coverity hit EOL. 12:10:40 kkeithley, ok 12:11:07 kkeithley, so I will remove this from action and moving to community meeting. 12:11:40 thanks 12:11:54 #topic ndevos need to decide on how to provide/use debug builds 12:12:07 still a todo 12:12:13 ok..moving on 12:12:15 and so are all other AIs on me 12:12:19 #action ndevos need to decide on how to provide/use debug builds 12:12:24 ndevos, sure 12:12:40 :) thanks 12:12:42 #action ndevos to propose some test-cases for minimal libgfapi test 12:12:58 #topic Manikandan and gem to followup with kshlm/misc/nigelb to get access to gluster-infra 12:13:39 gem, any update .. if you are there :) 12:14:15 ok..moving on 12:14:21 #action Manikandan and gem to followup with kshlm/misc/nigelb to get access to gluster-infra 12:14:30 #action Manikandan will host bug triage meeting on June 21st 2016 12:14:38 #action ndevos will host bug triage meeting on June 28th 2016 12:14:59 Now moving to Group triage 12:15:05 #topic Group Triage 12:15:12 #info you can fine the bugs to triage here in https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:15:17 #info http://www.gluster.org/community/documentation/index.php/Bug_triage 12:15:24 Bug triage guidelines can be found here ^^ 12:15:38 #link https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:17:15 are we reminding people that they can triage their own bugs. IOW when they open a bug they can assign it (to themselves) and set the Triaged keyword? 12:18:21 I hope we do... but I must admit I do not always do so, only when I know the irc nick and the person is online 12:18:45 ndevos, agree with ndevos ..mostly we do..sometimes get missed :) 12:20:08 I've added it as a topic to the community meeting 12:20:34 kkeithley, ok 12:20:59 so bug triage is over? 12:21:16 kkeithley: with that, we probably should remind developers+maintainers to setup notifications/rssfeeds for triaged bugs 12:21:54 yeah 12:22:02 that was fast 12:22:03 ;-) 12:22:14 super fast ! 12:22:32 ok..moving on 12:22:32 yay! 12:22:36 think how fast it would be if everyone triaged their own bugs! 12:22:49 no need for this meeting too :) 12:23:40 #topic Open Floor 12:24:51 do we know if anyone uses http://bugs.cloud.gluster.org/ ? 12:25:25 it is not really correct, because the "review status" column is parsed from bugzilla comments... 12:25:30 didn't know it existed 12:26:02 I remember seeing this from ndevos mail 12:26:59 kkeithley: improvements welcome, send a pull-request to https://github.com/gluster/gluster-bugs-webui :) 12:27:19 maybe I knew about it once. And forgot it 12:27:32 ndevos: sure 12:29:02 will end the meeting if no other update 12:29:16 nothing from my side 12:29:27 ok..the end 12:29:29 #endmeeting