12:01:08 #startmeeting 12:01:08 Meeting started Wed Jul 15 12:01:08 2015 UTC. The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:19 Roll-Call 12:01:57 * obnox here 12:02:00 * kkeithley is here 12:02:10 * raghu is here 12:02:11 * poornimag is here 12:02:13 * overclk is here 12:02:14 * msvbhat is here 12:02:38 * kshlm is here chairing for the first time. 12:02:52 Okay looks like enough people. 12:02:53 kshlm, a big thank you 12:02:57 * spot is here 12:02:59 kshlm++ 12:02:59 Let's start the meeting. 12:03:11 #topic Last week's action items 12:03:27 #topic spot will ask about a potential Justin replacement 12:03:31 spot? 12:04:42 In the short term, there is going to be a team out of Bangalore that is going to take over the most important infrastructure tasks. 12:05:04 OSAS infrastructure team is also going to help out 12:05:15 * hchiramm is here 12:05:20 * jiffin1 is here 12:05:24 * anoopcs is here 12:05:32 * RaSTar is here 12:05:44 * jdarcy is 12:05:48 We should have more specific details on that in the next few weeks. 12:06:23 #note Short term infra maintainence to be done by a team from Bangalore. OSAS to help. More details in coming weeks. 12:06:27 Thanks spot. 12:06:45 #topic hchiramm to update about packaging emails 12:06:55 hchiramm, has already updated it as TBD 12:07:00 kshlm, yep :) 12:07:04 #action hchiramm to update about packaging emails 12:07:27 Oops forgot this. The agenda as always is at https://public.pad.fsfe.org/p/gluster-community-meetings 12:07:40 #topic tigert summarize options for integrating a calendar on the website, call for feedback 12:07:50 Is tigert here? 12:08:30 Doesn't seem so. 12:08:32 No, he's not. 12:08:34 in vacation 12:08:37 #action tigert summarize options for integrating a calendar on the website, call for feedback 12:09:03 #topic hagarth shoudl have completed the roadmap planning for the next gluster releases 12:09:26 hagarth isn't here, but he informed me of his update. 12:09:53 hagarth sent out a note on 3.8 plans to the mailing list. 12:10:04 So this item is completed. 12:10:17 #topic hagarth should have published the 4.0 roadmap to gluster.org last week 12:10:36 hagarth said he'd be doing this, this week. 12:10:44 #action hagarth should have published the 4.0 roadmap to gluster.org last week 12:11:02 #topic csim/misc to pickup the requesting of public IPs and those kind of things for our new servers (or VPN) 12:11:14 csim you're up. 12:11:35 well, VPN is up, I am now setting firewall and routing so it doesn't break after reboot 12:11:39 (as i found out à 12:11:56 so far, I have 1 fedora builder, but adding a few more should be easy once the fireone is going 12:12:09 * rjoseph arrived late 12:12:11 Cool. 12:12:44 So when can we expect to get jenkins slaves from this new setup? 12:12:56 I would say end of the week 12:13:06 Awesome! 12:13:19 but after, I am in europython for 1 week, so if I cannot finish in time, it will be in 2 weeks 12:13:50 Please keep us updated on your progress. 12:14:09 kshlm: when there is, yes, but this month, it was mostly PTO :) 12:14:10 csim: what about using CentOS's jenkins? 12:15:01 kkeithley: did look yet, I was focusing on getting our infra ready, in the end, that's jenkins slaves no matter the underlying hardware 12:15:50 did _not_ look?? But yes, a jenkins slave is a jenkins slave. ;-) 12:15:59 yeah, did not look 12:16:10 yup, but the amount of setup would be the same in both case 12:16:17 so I rather finish the one I started :) 12:16:21 yup 12:16:26 csim, any plans on when/if you're planning to look at the CentOS infra? 12:17:01 kshlm: I plan to do, but nope, do not have a planning 12:17:11 Cool. 12:17:14 likely once the ci.gluster;org is in use 12:18:07 #note csim will look at the CentOS Jenkins infra once ci.gluster.org is up and running. 12:18:23 Thanks csim. 12:18:44 #topic overclk should have created a feature page about lockdep 12:18:52 overclk, you here? 12:18:58 kshlm: that's what I'm doing at the moment. 12:18:59 * surabhi is here 12:19:12 * ira is here. 12:19:16 kshlm: but the team in bangalore that should help can also look, i do not have magic access to the ci.centos infra :) 12:19:23 kshlm: should be done by the time meeting ends :) 12:19:42 overclk, okay. I'll get back to this towards the end. 12:19:49 kshlm: sure. 12:20:02 #topic hchiramm should have come up with suggestions on how/where to post work-in-progress documentation 12:20:25 hchiramm, ? 12:20:39 we have enough inputs now :) 12:20:50 me or anjana will send a mail 12:20:56 tomorrow about the same 12:20:58 Awesome. 12:21:06 cool 12:21:22 #action hchiramm will send an update on WIP documentation issue 12:21:33 Thanks hchiramm 12:21:43 yw ! 12:21:47 #topic atinm will start a schedule for office hours in #gluster 12:22:21 atinm sent out a mail with a link to an etherpad with the schedules. 12:23:08 #link https://public.pad.fsfe.org/p/gluster-office-hours 12:23:39 Several community members have already penned themselves in. 12:23:57 There a lot more who haven't (me included). 12:24:05 * msvbhat is updating now 12:24:47 #action kshlm to add himself to the gluster-office-hours schedule. 12:25:04 does anyone mind if I restructure the etherpad to be sorted as per time? 12:25:05 so what is that really about: guaranteed presence and responsiveness on #gluster 12:25:08 ? 12:25:18 But what if sometime I am not available on the time I mentioned? 12:25:44 obnox, I think so. 12:25:52 ok, wow 12:26:06 But I wasn't in last weeks meeting, so could anyone confirm? 12:26:18 RaSTar: I think the sorting makes sense 12:26:27 RaSTar: I think that's a good proposal to sort it by time 12:26:41 Does etherpad have tables? Tables would be good for this. 12:27:23 etherpad does not have tables.. 12:27:26 But I can not commit to the same time always. Sometimes I can't be online for many reasons 12:28:10 I agree with msvbhat I also want to be there but sometimes I may not. 12:28:32 But I *try* to be online most the time which I mentioned. Sometimes I may not be though 12:28:41 I don't think this is meant to be a rigid schedule. 12:29:17 kshlm: reading from last week's log, the idea is as reliable presence and coverage in #gluster and #gluster-devel. term office-hours was not strictly definde 12:29:21 defined 12:29:39 (#gluster-dev that is) 12:31:13 thanks obnox. 12:32:02 Cool, Having people spread across different time zones will be helpful here :) To have more presence coverage 12:33:14 Anyways, let's move on. 12:33:20 #topic HELP: maintainers can volunteer to become release manager for 3.7.3 12:33:50 What's the difference between a release-maintainer and a release-manager? 12:33:56 I don't get this. 12:34:47 kshlm: it mostly refers to module mainatainers 12:34:56 I don't remember seeing any request for volunteers being sent out on the lists this week. 12:35:51 So this doesn't seem like it's been done. Carrying it forward to next week. 12:36:33 kshlm: there i no mention of *release-*maintainers, just maintainers. (gluster component maintainers?) It seems they are eligible for being release-manager for a given release? 12:36:53 * obnox is just learning gluster communit and trying to understand... :) 12:37:05 #action to Send a request to mailing list requesting for volunteers to be release-manager for 3.7.3 12:37:15 obnox, I don't understand that either. 12:37:34 kshlm: hagarth is currently assigned with 3.7.3 release.. 12:37:53 #note hagarth is release manager for 3.7.3 12:37:54 he said he would be happy if any of the maintainers take it up 12:37:56 kshlm: it seems gluster has varying release managers for different releases. so one needs volunteers for a release, no? 12:38:17 * obnox thinks this is a very interesting concept 12:38:58 obnox, All I know is hagarth handles the master branch. The release branches upto release-3.6 have release maintainers who maintain that branch and do releases. 12:39:13 release-3.7 seems to be in a unique position currently. 12:39:32 It doesn't have a release-maintiner (AFAIK) 12:40:04 hagarth could probably answer better about this if he were here. 12:40:21 kshlm: ah, so hagarth is in charge but looking for someone to help out because he is overloaded (or so) 12:40:31 obnox, seeems like it. 12:40:43 * obnox shuts up now with speculations ;) 12:41:10 #action Get hagarth to clear up the speculations about "release-manager' 12:41:20 Onto the next topic. 12:41:33 #topic HELP: propose a roster/schedule for hosting the weekly meeting (all maintainers should participate) 12:41:45 atinm did it. So this is done. 12:42:53 #topic GlusterFS 3.7 12:43:21 hagarth, just in time. 12:43:31 kshlm: for ? 12:43:37 The current topic is GlusterFS 3.7 12:44:04 kshlm: hagarth can also clarify ... ;) 12:44:06 Do you have an update on 3.7.3 plans 12:44:44 obnox, Yes. But I don't think we'll have time. 12:44:56 right. sorry 12:44:59 * kshlm is running the meeting really slowly. 12:45:17 kshlm: yes 12:45:30 the plan is to release 3.7.3 later this week or in a week from now 12:45:57 hagarth, Who is doing the release? 12:46:11 kshlm: in all probability I will release 3.7.3 12:46:33 There was an earlier action item on calling for volunteer to be release-manager for 3.7.3. We were speculating on what release-manager means. 12:46:42 Cool. Thanks hagarth. 12:46:45 kshlm: basically how we did 3.7.x releases 12:47:03 #note hagarth will be releasing 3.7.3 in 1 or 2 weeks time. 12:47:18 if there is somebody interested to push 3.7.3 out as KP did it for 3.7.1 and atinm for 3.7.2, I am happy to let them take over 12:47:33 I'll volunteer. 12:48:03 kshlm: ok, 3.7.3 is yours then :) 12:48:19 #note kshlm will be releasing 3.7.3 in 1 or 2 weeks time. 12:48:30 Anything else on 3.7? 12:49:06 Doesn't seem to be. Onto the next topic. 12:49:13 #topic GlusterFS 3.6 12:49:19 raghu, You're up. 12:49:30 I have made 3.6.4 and announced it in the mailing list also. 12:49:39 There are some patches sent for 3.6 branch. I will be considering them for 3.6.5 12:50:10 For 3.6.5 I am planning not to make any beta releases and directly go ahead with GA 12:50:25 Any timeline for 3.6.5? 12:50:43 Since no beta, 2-3 weeks. 12:51:05 Thanks raghu 12:51:06 If suffecient amount of patches are merged, then 2 weeks. Otherwise I will wait for 1 more week 12:51:40 #note raghu will do the 3.6.5 release directly in 2-3 weeks depending on patch merge rates. 12:51:52 Anything else on 3.6? 12:52:12 nope. 12:52:16 Ok. 12:52:20 #topic GlusterFS 3.5 12:52:32 kkeithley, anything to say? 12:52:42 3.5.5 was released last week 12:52:56 Oh sorry, ndevos is the maintainer for 3.5 right? 12:53:36 Thanks hagarth 12:53:46 Anything else w.r.t 3.5? 12:54:02 #topic Gluster 4.0 12:54:15 jdarcy, hagarth Anything you want to add. 12:54:42 Did some experiments to validate the brick-multiplexing infrastructure idea. 12:55:01 kshlm: nothing new from me, I have an AI to publish the roadmap for 4.0 this week. Will do so in consultation with jdarcy and others. 12:55:03 Experiment was successful, but in the process I uncovered a few minor issues in glusterd-land. 12:55:04 correct, ndevos has 3.5 12:55:40 jdarcy, That's good news. 12:56:00 Next week I'll be trying to revive NSR. 12:56:03 #note jdarcy experimented with brick multiplexing. The experiment was a success. 12:56:38 #note jdarcy will experiment with NSR next. 12:57:08 #action hagarth will publish 4.0 roadmap this week 12:57:14 Thanks hagarth and jdarcy. 12:57:22 Anything else to add? 12:58:11 #topic overclk should have created a feature page about lockdep 12:58:30 kshlm: nope not yet. 12:58:32 overclk, We're back to you. Are you done? Or should we move this to next week? 12:58:42 Okay. moving to next week. 12:58:43 kshlm: still slow on it, move it to next week. 12:58:50 #action overclk should have created a feature page about lockdep 12:58:56 kshlm: and perhaps feature pages should be in readthedocs now? 12:58:57 #topic Open Floor 12:59:30 * RaSTar just managed to get a text table for etherpad 12:59:34 overclk: possibly so, I don't think we converged on a decision on that one 13:00:02 kshlm: OK, because the feature page template in gluster.org says that it locked. 13:00:02 Weekly reminder on community members attending events. 13:00:26 Please keep https://public.pad.fsfe.org/p/gluster-events updated with events you are attending. 13:00:42 overclk, Yes. The wiki is in RO mode now. 13:00:57 And as hagarth said we haven't converged on any decision yet. 13:01:28 Anyone have a topic they'd like to discuss now? 13:01:33 kshlm: yeh, so where can I put up the feature page now? anyone has a link from readthedocs (I couldn't find it there). 13:01:50 hchiramm: ^^ ? 13:02:06 overclk, hchiramm should be able to help you. 13:02:28 kshlm: ok, thanks! I'll disturb him :) 13:02:30 kshlm, https://github.com/gluster/glusterdocs/tree/master/Features 13:02:50 https://github.com/gluster/glusterdocs/tree/master/Feature%20Planning overclk 13:03:12 hchiramm: thanks. and send the pull request perhaps... 13:03:20 Thanks hchiramm 13:03:23 overclk, yep 13:03:31 hchiramm: okies. 13:03:38 There don't seem to be anymore topics left to discuss. 13:03:51 Thanks for attending the meeting everyone. 13:04:03 kshlm: thanks for hosting today! 13:04:04 #endmeeting