12:01:05 #startmeeting Gluster Bug Triage 12:01:05 Meeting started Tue Dec 1 12:01:05 2015 UTC. The chair is Manikandan. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:05 The meeting name has been set to 'gluster_bug_triage' 12:01:25 #info agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 12:02:06 #topic Roll Call 12:02:14 * ndevos is present 12:02:15 * jiffin is here 12:02:29 * Humble is here 12:02:30 kkeithley_ will be a few minutes late to bug triage 12:02:57 ashiq, around ? 12:03:13 * ashiq is here 12:03:38 Shall we wait for some more participants? 12:03:44 Manikandan: yes 12:04:18 * rafi is here 12:04:40 Manikandan: good to see you :) 12:04:52 rafi, thank you:-) 12:04:59 * ndevos o_O 12:05:07 Going on to last week action items 12:05:32 #topic skoduri and ndevos will document how people can get bug notifications for specific components 12:05:50 ndevos, any updates on this 12:06:07 Manikandan: nope, sorry 12:06:39 Moving to next week #action skoduri and ndevos will document how people can get bug notifications for specific components 12:07:20 kkeithley_ sent a mail to gluster-dev regarding target release for older bugs 12:07:41 Manikandan: I saw the mail 12:07:47 Manikandan: make sure to do the # commands at the start of the line, otherwise zodbot does not catch them 12:07:48 yes, I sent it 12:08:08 kkeithley_: oh, when? I guess I missed it 12:08:21 ndevos: last tuesday 12:08:29 #topic kkeithley_ sent a mail to gluster-dev regarding target release for older bugs 12:08:32 hm, ok, need to look for it 12:08:42 ndevos, done :-) 12:08:43 24 Nov 12:09:55 * ndevos is not looking for the email now, please dont wait for it 12:10:35 Manikandan: if it os done, may be you can go ahead with next topic 12:10:42 All other assignee's corresponding to the agenda are not present, 12:10:53 rafi, yup we will move onto group triage 12:11:07 #topic Group Triage 12:11:16 #link https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:11:55 The bug triage process is documented here #link http://gluster.readthedocs.org/en/latest/Contributors-Guide/Bug-Triage/ 12:12:37 Please enter your name in the beginning of the bug you are going to triage 12:12:51 Strike the bug out from the list once triaging is done 12:13:15 #link Bug triaging process is documented here https://gluster.readthedocs.org/en/latest/Workflow-Guide/Bug-Triage/ 12:13:52 while we're triaging.... Nobody has anything to say about Target Release. At some point I do a bulk clear and then have the field removed. 12:14:01 sorry wrong link :( 12:14:09 #link Bug triaging process is documented here https://gluster.readthedocs.org/en/latest/Contributors-Guide/Bug-Triage/ 12:14:25 Humble: the steps for the triaging itself is in the etherpad with the bugs :) 12:14:37 kkeithley_, that should be fine 12:14:41 ndevos, yeah, forgot 12:14:56 kkeithley_: yes, remove it, we should have as few fields in the bug as needed 12:15:53 ?ME sorry am late 12:16:47 skoduri, np :-) 12:16:56 ?YOU 12:17:28 skoduri, /ME :) 12:17:44 Humble, yeah realized that later :) 12:17:47 ndevos, :) 12:17:49 \o 12:17:55 typo 12:18:11 ?me uses small case irc commands 12:22:50 ndevos, okay 12:24:50 I guess we are almost done 12:26:44 * Manikandan is waiting for rafi 12:26:50 Manikandan: done 12:27:20 #topic Open Floor 12:28:56 I have one topic to bring 12:29:00 About the bug automation workflow, the patch for the first task is here #link http://review.gluster.org/#/c/12822/ and have updated in ML as well 12:29:25 rafi, always welcome :P 12:29:32 i have an AI on community meeting to setup a doodle poll for bug triage meeting 12:29:43 the poll is to decide if a new time would allow more contributors to attend bug triages 12:29:59 guys what do you think ? 12:30:06 will it really help ? 12:30:44 rafi: we can hear it from community 12:30:56 and what time would be the best 12:31:20 jiffin: my concern is about the existing active members 12:31:29 Joejulian might be person who will be interested 12:31:46 the new time should be aligned with them 12:31:53 * rafi it is my thought 12:32:02 rafi: thats right 12:32:16 ndevos, kkeithley_: ?? 12:32:30 ndevos: kkeithley_ what could be the ideal time for you ? 12:33:22 rafi: this works quite well for me 12:33:40 * Manikandan is fine with any timings :P 12:34:04 ndevos: making it bit early will find a trouble for kkeithley_ , right ? 12:34:21 later works too, but we still would want to see you guys here :) 12:34:34 rafi: yeah, earlier will be difficult 12:34:52 also, if JoeJulian wants to join, it would need to be later 12:35:10 earlier is worse. This half of the year, without daylight savings, this time is on the edge of workable 12:35:45 it is hard to make sense out of kkeithley_ on early phone calls :D 12:35:46 kkeithley_: coool 12:35:51 kkeithley_, hard for you 12:36:25 ndevos: we need kkeithley_ full brain for this meeting ;) :D 12:36:34 it's hard for me to make sense too. 12:36:39 lol 12:36:43 lol 12:36:44 I dont doubt that, kkeithley_ 12:37:06 is there ever a time when you get my full brain? /me doesn't think so. ;-) 12:37:15 * ndevos tries not to join meeting before 9:00 12:37:59 I dont think we want your full brain anyway, that'll be very confusing to us too 12:39:18 * rafi thinks about a movie 12:39:29 lucy 12:39:30 there is one action on lalatenduM in the agenda , how should we deal with that ndevos , kkeithley_, rafi, Manikandan, skoduri? 12:39:40 ndevos: kkeithley_ : I will set up a poll which starts from 12:00UTC, and four option each with 1/2 hour interval 12:40:04 Manikandan: jiffin ndevos kkeithley_ skoduri : does that make sense ? 12:40:13 rafi: sure 12:40:15 #topic lalatenduM will look into using nightly builds for automated testing, and will report issues/success to the mailinglist 12:40:17 rafi: +1 12:40:23 rafi, works for me too 12:40:32 rafi, fine :-) 12:40:43 i think the interndention was to get more people dfrom bangalore 12:41:04 *intention 12:41:12 rafi: if that is the case, we can leave kkeithley_ sleeping 12:41:41 rafi: so, before 12:00 UTC could work well too 12:41:57 Yes, make it easy/easier for more people in bangalore. If I decide to skip sleeping that's my problem 12:42:45 and mine, you'll make stupid mistakes 12:42:51 okey I will put an option before 12UTC also 12:43:20 should we make a not saying that "those who cast the vore, should try to attend the meeting" 12:43:27 ndevos: kkeithley_ ^ 12:43:34 *vote 12:43:44 rafi, that would be bit ambitious i guess :P 12:43:59 rafi: of course, if we notice people voting but not attending, we can scratch their opinion 12:44:41 i don't want to change it bit early to those who are not going to attend, we are sacrificing an active member :) 12:44:53 ndevos, rafi, yeah that could be a better option 12:45:07 coool 12:45:21 I will set up a meeting and will try to make a conclusion 12:45:37 before making a conclusion we can decide based on the resilt 12:45:41 that's all from me 12:45:44 rafi, cool 12:45:56 Any other topic to discuss? 12:46:22 rafi: just remember to include in the email that this meeting is only for the bugs that were not triaged by the component maintainers/teams yet ;-) 12:46:38 like, a safety net 12:46:51 Manikandan: yes one more thing! 12:46:56 ndevos, ? 12:46:57 ndevos: sure, I will include the doc also 12:47:22 there is one action item still pending on lalatenduM in the agenda , how should we deal with that ndevos , kkeithley_, rafi, Manikandan, skoduri? 12:47:23 Manikandan: when people file bugs (specially developers and QE), they should immediately triage the bugs 12:48:00 ndevos, should we send a mail to remind it? 12:48:14 or should we remove that item from the agenda? 12:48:27 Manikandan: maybe, but it was mainly a reminder for you ;-) 12:48:59 jiffin: depends on the item, but we might want to find someone else to do it? 12:49:05 Yeah I saw the bug, will do it 12:50:14 * ndevos does not have anything else 12:50:49 rafi, jiffin, skoduri, kkeithley_ ashiq anything else? 12:51:25 none from me 12:51:35 we should do some kind of promotional function to make bug triage more popular 12:52:12 ndevos: now we are not conducting nightly builds , so can we remove that item 12:52:14 like announcing prizes for most triage's 12:52:15 rafi: that could help, but ideally all bugs are triaged without a meeting :) 12:52:37 jiffin: we want nightly builds again, it's just broken at the moment 12:52:37 from the list 12:52:43 ndevos: K 12:52:59 ndevos: anyone looking into that? 12:53:07 jiffin: I dont think so 12:53:13 :( 12:53:49 when more number of people are attending the meeting , it could be more fun to triage 12:53:53 jiffin: I get daily emails that it fails, after the re-securing of download.gluster.org, that needs some infrastructure solution 12:54:25 rafi, yeah it would be good 12:54:45 Manikandan: you still left 6 mnts to complete ;) 12:54:47 rafi: still, users file bugs, and we should respond to users as soon as possible, a weekly interval isnt optimal 12:55:10 ndevos: agreed 12:55:31 ndevos: what about making the default assignee for a competent as mandatory 12:55:49 ndevos: so that they will get a notification, right ? 12:56:08 rafi: its not so easy to maintain that, hence the AI skoduri and I have to describe how people get the emails 12:56:33 rafi: triaging can be done by anyone, it does not need to be the component owner (which should be a team) 12:57:04 ndevos: well ya, I fear people are not so concerning about upstream :( 12:57:22 We have 3 more minutes to complete the meeting 12:57:38 rafi: that is very frightening if those people are open source developers 12:58:37 ndevos: Do you think gluster community is not reconginizing the brightest contributors/users/participant ? 12:59:20 rafi: hmmm, not sure, maybe you should check with amye about that 12:59:59 ndevos: well i was just looking for the reason 12:59:59 rafi: I think she's in your office next week or so, make sure you talk to her about it 13:00:23 rafi: it is not something I ever thought about :) 13:00:46 ndevos: I would be glad to meet her, though fear to talk ;) 13:01:36 * jiffin recollects rafi's fear in talking with managers 13:02:00 rafi: never fear to talk to people, if they dont like it, well, *shrug* and leave them with their own thoughts :) 13:03:04 thanks Manikandan for hosting the meeting! 13:03:04 ndevos: jiffin : well it is not about managers, I would like to be more optimistic 13:03:25 Manikandan: let'us conclude the meeting 13:03:51 jiffin, or anyone, anything else? 13:04:00 not from me 13:04:15 nothing form me 13:04:19 s/form/from/ 13:04:30 one more thing 13:04:38 rafi, ? 13:04:52 ah, moderator for next week? 13:04:54 ndevos, no problem :) 13:04:54 can we take decide who is going to host next meeting at the end of every meeting ? 13:04:58 * ndevos will be on holidays 13:05:14 good thinking rafi! 13:05:39 I don't like running for a person at the very last moment 13:05:54 Anyone volunteering ?^ 13:06:09 Manikandan: today was good start 13:06:23 Manikandan: Do you want more expreince ;)? 13:06:35 rafi, ahh sure :P 13:06:52 thanks Manikandan! 13:07:00 Manikandan++ 13:07:03 ndevos, np :-) 13:07:12 we should a bot also next time 13:07:14 :) 13:07:21 *bring 13:07:54 * Manikandan feels it would be better cash instead of bot :P 13:07:54 rafi: ask JoeJulian to get glusterbot in here :) 13:08:18 So shall we end the meeting? 13:08:20 sure, I will take that responsibility 13:08:21 zodbot hands out cookies if people register their IRC nick in their Fedora account 13:08:33 sure 13:08:35 zodbot: karma ndevos 13:08:36 ndevos: Karma for devos has been increased 3 times and decreased 0 times this release cycle for a total of 0 (3 all time) 13:08:56 #endmeeting