12:00:06 #startmeeting Gluster Community Bug Triage meeting 12:00:07 Meeting started Tue Apr 5 12:00:06 2016 UTC. The chair is hgowtham. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:07 The meeting name has been set to 'gluster_community_bug_triage_meeting' 12:00:18 hello everyone :) 12:00:24 #info agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 12:00:30 #topic Roll Call 12:00:48 * kkeithley_ is here 12:01:38 * ndevos _o/ 12:01:56 jiffin, rafi1 skoduri , there? 12:02:20 hgowtham: :) 12:02:32 Manikandan said he won't be able to join today 12:02:44 * rafi1 is here 12:03:15 okay shall we proceed? 12:03:44 #topic ndevos need to decide on how to provide/use debug builds 12:04:20 yeah, I've got an idea to get them build, but its at the idea stage... -> next week more? 12:04:25 as msvbhat_ is not here moving his AI to next week 12:04:38 yes sure ndevos 12:04:42 #action msvbhat will look into lalatenduM's automated Coverity setup in Jenkins which need assistance from an admin with more permissions 12:05:16 #action ndevos need to decide on how to provide/use debug builds (idea ready) 12:05:51 moving AI of the not available to next week 12:06:04 #action Manikandan and Nandaja will update on bug automation 12:06:25 #topic kkeithley_ will come up with a proposal to reduce the number of bugs against "mainline" in NEW state 12:06:43 #action hagarth start/sync email on regular (nightly) automated tests 12:06:54 #action msvbhat provide a simple step/walk-through on how to provide testcases for the nightly rpm tests 12:07:20 I think we should just drop that item. I don't think it's a issue any more 12:07:45 kkeithley_, yes sure will remove it :) 12:07:59 #topic ndevos to propose some test-cases for minimal libgfapi test 12:08:33 oh, more ideas! just need to share them and hope someone can assist with creating the tests 12:08:52 and test the tests for that matter 12:09:49 yes, but today we dont have much participants to volunteer. So shall we move it next week? 12:09:59 We will ask for volunteers by then 12:10:27 sure 12:10:33 #action ndevos to propose some test-cases for minimal libgfapi test 12:10:44 #topic Group Triage 12:10:50 #link https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:11:00 #info http://www.gluster.org/community/documentation/index.php/Bug_triage - The bug triage guidelines can be found here 12:12:43 * skoduri is here 12:17:43 jiffin: welcome back 12:19:47 rafi1: did i miss anything? 12:20:08 jiffin: we missed you so badly 12:20:15 jiffin, group triage is nearly over waiting for ndevos to finish 12:20:22 done! 12:20:33 yep . moving on to the next 12:20:45 topic Open Floor 12:20:50 #topic Open Floor 12:21:45 * ndevos .... bzzzzzt blip 12:22:02 we have reduced the number of bugs to a great extent. is it necessary to have triage meetings every week? 12:22:19 i mean the bugs in the new state 12:22:35 yes, we still need to do it until all developers triage bugs before this meeting 12:22:57 oh okie :) 12:23:17 gem: do you have an update on the automated bug status scripts? 12:24:19 ndevos, Hey. We were actually waiting for some access permissions. But we couldn't follow up on this with kaushal later. We have got some scripts ready that could be tested. 12:24:27 hgowtham: maybe you can convince more developers to setup notifications for their components? https://github.com/gluster/glusterdocs/blob/master/Developer-guide/Bugzilla%20Notifications.md 12:24:49 gem: great, where are the scripts located? 12:25:44 ndevos, We will push it to github and will send a PR to the main repo. We have currently it in our local machines only :) 12:26:17 gem: oh, ok, please do share them early so others can comment on them :) 12:26:26 ndevos, will do. Thanks! 12:26:43 gem: it would also be nice to share a status update and next steps on gluster-devel 12:26:46 ndevos, convince in the sense? I can send a reminder to the maintainers. Is that enough? 12:27:25 ndevos, sure. 12:27:29 hgowtham: yeah, but not only the maintainers, any of the developers working on a component (or interest in it) should do it :) 12:27:39 gem++ thanks! 12:27:39 ndevos: Karma for gem changed to 1 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 12:28:36 yea. then i'll send out a mail to the developers asking them to setup notification for the respective component 12:29:44 kkeithley_, skoduri, ndevos, rafi1, gem, anything else? 12:29:55 not from me 12:30:00 kkeithley_, :) 12:30:14 nothing from me either 12:30:15 nothing from me 12:30:34 okay then i'll end the meeting. 12:30:40 thanks for attending 12:30:44 hgowtham++ 12:30:45 rafi1: hgowtham's karma is now 3 12:30:48 #endmeeting