12:00:04 #startmeeting Gluster Bug Triage 12:00:04 Meeting started Tue Jan 10 12:00:04 2017 UTC. The chair is hgowtham. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:04 The meeting name has been set to 'gluster_bug_triage' 12:00:08 #topic Roll call 12:00:15 #info agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 12:00:34 * Saravanakmr is here 12:00:41 * ankitraj here 12:00:58 * ndevos _o/ 12:01:50 Hi everyone. 12:01:52 hgowtham: just a reminder, but when you send out the meeting minutes, please include the full text of the generated minutes too, not only the links 12:02:09 yes sure ndevos . im aware of it :) 12:02:32 ankitraj: I noticed you sent the links only, but I do not expect anyone to open the URLs, if the text is included more people will read it :) 12:02:38 we shall start with the Action Items. so that other can join when they are here 12:02:51 ndevos, ok i got it. 12:03:00 i have talked with ankitraj regarding sending the whole thing from next time 12:03:11 #topic Action items 12:03:31 #topic ndevos need to decide on how to provide/use debug builds 12:03:45 thats still todo 12:03:55 #action ndevos need to decide on how to provide/use debug builds 12:04:07 if anyone has ideas or suggestions about it, tell me! (by email) 12:04:14 #topic jiffin will try to add an error for bug ownership to check-bugs.py 12:04:26 hgowtham: its done 12:04:42 jiffin, the link to thread would be good 12:04:43 i have given pr link in previous meeting 12:04:50 wait give a sec 12:04:55 jiffin: oh, wow, I did not know! 12:04:56 jiffin++ 12:05:00 jiffin, sure 12:05:22 https://github.com/thotz/glusterfs-patch-acceptance-tests/commit/9759f7848ef10be5cd847294b05f305fac1a0b55 12:06:36 jiffin: wait, that is not for check-bugs.py from the release-tools repo? 12:07:46 jiffin: https://github.com/gluster/release-tools/blob/master/check-bugs.py 12:08:25 #link https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/74 12:08:46 #link https://github.com/thotz/glusterfs-patch-acceptance-tests/commit/9759f7848ef10be5cd847294b05f305fac1a0b55 12:09:07 ndevos: it not merged 12:09:07 hgowtham: link ^^ 12:09:07 ndevos: no I guess 12:09:07 it is part of smoke test 12:09:27 #info Jiffin done with the changes on check-bugs.py 12:09:27 jiffin, thanks 12:09:27 #topic Group Triage 12:09:28 #info you can find the bugs to triage here in https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:09:29 #info http://www.gluster.org/community/documentation/index.php/Bug_triage 12:09:34 jiffin i made a note of the link 12:10:10 #link https://github.com/thotz/glusterfs-patch-acceptance-tests/commit/9759f7848ef10be5cd847294b05f305fac1a0b55 from jiffin for the check-bug.py 12:11:25 ndevos: do I need to revert above change and make a similar change in check-bugs.py 12:11:54 jiffin: I think the change is a good addition, but we also need it in check-bugs.py 12:11:54 * jiffin will logging from meeting in 5mins 12:12:02 ndevos: okay 12:12:14 ndevos: will do that 12:13:34 #action jiffin needs to send the changes to check-bugs.py also 12:16:36 done! 12:17:00 yes moving on to the next topic 12:17:11 #topic Next week’s meeting host 12:17:23 I will do 12:17:33 Saravanakmr, thanks :) 12:18:06 #info Saravanakmr to host the bug triage on 17th Jan 12:18:21 moving to next topic 12:18:23 #topic Open Floor 12:18:45 we need to start using other etherpads for bug triage too 12:19:01 ah, yes 12:19:09 so how do we transfer stuff from this one to other? 12:19:10 final date 1 february 12:19:27 I already did - moved to gluster github wiki 12:19:27 maybe also use hackmd.io like we do for the community meeting? 12:20:07 hackmd looks good 12:20:08 yup - I think from next week we can try hackmod.io 12:20:27 can you provide the link? 12:20:33 #link https://github.com/gluster/glusterfs/wiki 12:20:43 thanks 12:20:58 is it ok for everybody to host in hackmod.io ? 12:21:05 from next week 12:21:09 #info Triage meetings to use https://github.com/gluster/glusterfs/wiki instead of etherpad 12:21:19 sorry decided in a hurry 12:21:31 is everyone fine with it from next week? 12:22:39 * Saravanakmr why so silent? :) 12:22:49 okie then ill confirm it 12:22:57 anything else to discuss? 12:23:12 nothing more 12:23:13 hgowtham, send it on mailing list.. 12:23:16 uh, the wiki is bad for online editing 12:23:19 ankitraj, sure 12:23:33 um okie. which one shall we opt? 12:23:41 we mark the bugs we triage immediately, and the wiki needs a [commit] click 12:24:07 the hackmd.io site allows etherpad like editing 12:24:07 yes. thats going to be a bit annoying 12:24:32 annoying because we will most likely have conflicting edits all the time :) 12:24:43 For Triaging we use hackmod.io - then the contents are moved to wiki for every week 12:24:53 if everyone is fine with hackmd.io. we will use it 12:25:32 Saravanakmr: I do not think we need the agenda/logs in the wiki, having it in the email archives is probably sufficient? 12:26:23 but, I do not care *that* much, if there is value in having it in the wiki, then we'll just copy it there too 12:26:37 So what are the final thought? 12:26:42 ndevos, make sense - why to have two different copy 12:26:54 ndevos, but for community meeting it is maintained. 12:27:09 okie then we will use hackmd.io instead of etherpad and continue the same mechanism there 12:27:18 ndevos, what you say make sense - why to pollute wiki with these contents. 12:27:43 ndevos, maybe we can discuss it tomorrow community meeting too. 12:27:53 * ankitraj thinks let's see how hackmd works for community meeting. If it works for them then we will switch. 12:28:09 I'm also not sure why we need the community meeting results in the wiki... I would just link to the archived email if we need that 12:28:22 ndevos, agree :) 12:29:02 #info use hackmd.io instead of etherpad 12:29:17 ankitraj, hackmd used in community meeting already 12:29:51 oh.. I wasn't aware of that. I haven't attended last few meetings 12:30:34 hgowtham, you can end the meeting :) 12:30:45 Saravanakmr, sure 12:30:54 endmeeting 12:30:57 #endmeeting