12:00:38 #startmeeting 12:00:38 Meeting started Wed Mar 25 12:00:38 2015 UTC. The chair is hagarth. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:47 ndevos: I sent a reminder too on the MLs ;) 12:00:50 #topic Roll Call 12:00:52 * kkeithley is here 12:00:55 * jimjag is here 12:00:56 * Debloper is here. 12:00:58 * ndevos is here _o/ 12:00:58 * kshlm o/ 12:01:14 * partner o/ 12:01:17 * overclk is here 12:01:26 * spot is awake 12:01:29 sounds like we have quorum, let's get rolling 12:01:37 #topic Action items from the last meeting(s) 12:01:49 AI - tigert to continue investigating the blog post duplication 12:02:02 tigert: any update on this one if you are around? 12:02:28 does not look to be the case, moving on 12:02:32 AI - hchiramm will share the outcome of the non-mailinglist packagng discussions on the mailinglist (including the Board) 12:02:46 hchiramm__/hchiramm: any updates on this one? 12:03:03 hchiramm MIA, moving on 12:03:08 AI - hagarth will complete the feature page for (k)vm hyperconvergence 12:03:10 * tigert is here 12:03:17 * raghu is here 12:03:20 tigert: any update on the first AI ? 12:03:33 no :( 12:04:05 tigert: no worries, let us move this for next week 12:04:14 #action tigert to continue investigating the blog post duplication 12:04:30 I need help with this I think 12:04:36 because I dont dare to touch the current setup 12:04:51 tigert: whose assistance might be most useful for this? 12:04:51 maybe have a new vm with wordpress and that plugin to test whether the same happens there 12:05:05 or just think of doing a real planetplanet instance? 12:05:31 and maybe a blog next to it that also gets pulled in in case people write also in the actual blog itself 12:05:31 tigert: that is another option, we can discuss more on this during the website revamp topic 12:05:35 yeah 12:06:06 coming to my AI, I have a basic page for kvm hyperconvergence at http://www.gluster.org/community/documentation/index.php/Features/Ovirt_Hyperconvergence 12:06:16 pranith or me will fill more details there 12:06:29 #action pranithk and hagarth to update http://www.gluster.org/community/documentation/index.php/Features/Ovirt_Hyperconvergence 12:06:41 AI - spot to reach out to community about website messaging 12:06:59 hagarth: do you remember what that AI actually means? :) 12:07:11 the slogan? 12:07:22 spot: this was about what do we need instead of "Write Once, Read Anywhere" 12:07:22 is it just coming up with some new slogan ideas? 12:07:34 spot: yes 12:07:37 okay. I have nothing there, but I'll start working on it 12:07:47 well, the current slogans is wrong, it can be misunderstood too easily 12:07:57 * spot has been putting all of his time into Gluster Summit 12:08:08 ndevos: +1 12:08:12 if we discuss website messaging, it could also be "what should we have on the website" 12:08:23 tigert: sure, let us park it for there 12:08:28 tigert++ 12:08:32 carrying on the AI lest we forget it 12:08:41 #action spot to reach out to community about website messaging 12:08:45 "Unified, poly-protocol, scale-out, open source filesystem, serving petabytes of data." 12:08:49 as in news / blog, community section (coding, meetings etc), case studies, documentation 12:08:52 etc 12:08:55 AI - hagarth to carry forward discussion on automated builds for various platforms in gluster-infra ML 12:09:10 I haven't found time for this over the last few weeks .. anybody willing to take this over? 12:09:32 guess not, the AI stays with me :) 12:09:39 hehe 12:09:39 #action hagarth to carry forward discussion on automated builds for various platforms in gluster-infra ML 12:09:47 AI - ndevos should send out a reminder about Maintainer responsibilities to the -devel list 12:09:55 ndevos: any update on this one? 12:09:56 * msvbhat joins the meeting 12:09:56 oh, thats almost done 12:10:11 hagarth, on packaging , yet to conclude . 12:10:14 the email is almost ready, but I got pulled into an unexpect call 12:10:24 hchiramm: ok 12:10:28 ndevos: this week then? 12:10:29 I'll finish it during this meeting, or just a few minutes after 12:10:51 now is a good time to do that since we are feature freezing 3.7, more on 3.7 later 12:10:55 * ndevos was planning to send it before the meeting, but that failed :-/ 12:11:03 #action ndevos should send out a reminder about Maintainer responsibilities to the -devel list 12:11:11 AI - telmich will send an email to the gluster-users list about Gluster support in QEMU on Debian/Ubuntu 12:11:31 has anybody reached out telmich / Nico ? 12:11:52 he doesnt seem to be on irc atm 12:12:04 guess not, let us task JustinClift with this since he is not around :) 12:12:22 #action JustinClift to reach out to telmich for Gluster support in QEMU on Debian/Ubuntu 12:12:26 someone who knows a little about qemu on debian/ubuntu should get in touch? 12:12:50 ndevos: probably JustinClift can copy some of us who know a bit about that 12:13:06 AI - JustinClift to get JimJag the info he needs for progressing the board engagement 12:13:13 jimjag: any update on this one? 12:13:34 Haven't rec'd the info yet. Pinged JustinClift and JMW this am w/ a reminder 12:13:47 I am looking for dates and facilities for the f2f 12:14:08 would the board not attend the gluster summit too? 12:14:10 Likely location will be in Westford @ Red Hat 12:14:33 ndevos: Yes, they will attend, but the hope is to meet before that if possible 12:14:42 ah, ok 12:14:48 jimjag: ok, shall we persist this AI or drop it off the agenda? 12:15:01 persist for 1 week please 12:15:09 jimjag: ok, thanks 12:15:13 np 12:15:30 #action jimjag will continue engaging with the board 12:15:41 AI - hagarth will post more details about an overlay xlator (container targetted) when he has a bit more clarity (and post his hacks) 12:15:58 tbd, I plan to discuss more about our container strategy in the coming week 12:16:09 AI - firemanxbr to submit a patch for 3.6.3, change IP addr. 12:16:16 firemanxbr: any update on this one? 12:16:36 guess firemanxbr is not around atm. moving on. 12:16:39 AI - tigert will share practical plans for ReVamping the AweSUM next GlusterFS Web Presence 12:16:51 ok 12:17:07 tigert: discuss more on this in the agenda topic later? 12:17:13 my practical plan is to get people together to discuss what we want 12:17:19 so yeah, it wont be solved here 12:17:30 trying to have this on the mailing list is seemingly ineffective 12:17:39 tigert: let's do this a bit later, Debloper also has some ideas. 12:17:43 yes 12:17:45 AI - dlambrig to contact other devs about the spurious failures 12:18:03 dlambrig dropped me a note saying he won't be attending today's meeting but let us discuss this later 12:18:28 failing regression tests have been very painful .. especially more so when we are working towards meeting the feature freeze milestone. 12:18:39 that's it from the short AI list :) 12:18:44 #topic Gluster 3.6 12:18:45 hagarth, hey guys, I back... 12:18:55 firemanxbr: any update on your action item? 12:18:59 hagarth tigert, instead of discussing, let's just move ahead with some content for folks to look into - and give feedback on. 12:18:59 hagarth, no update, sorry my delay 12:19:16 I'll send in my staging URL in some times or early tomorrow. 12:19:17 firemanxbr: no problems, I will retain your AI 12:19:19 hagarth, I'm working in new Gerrit for infra, no more freetime for this. 12:19:38 firemanxbr: yes, that is very important considering the April 20th deadline 12:19:56 firemanxbr: thanks for all your efforts there! 12:20:03 Debloper: ok 12:20:07 hagarth, but I following steps sent for ndevos 12:20:32 firemanxbr: ok 12:20:45 raghu: any updates on gluster 3.6? 12:20:59 I have accepted patches from afr, quota. Some EC related patches are failing regressions. I want to take them in for 3.6.3. there are some rdma patches as well. They are dependent patches. Some of them have passed regressions and some have failed. I have asked rafi to take a look at it. But I am not sure whether el5 dependency issue got resolved or not. 12:21:32 raghu: what is the el5 dependency for rdma? 12:21:53 hagarth: Not sure. niels has some idea about it. 12:22:01 ndevos: ? 12:22:06 raghu: I think el5 should work now, maybe not in Fedora COPR for the nightly builds, but normal builds should succeed 12:22:30 ndevos: So, is it ok to make a beta2 and then GA 3.6.3? 12:22:32 I think it would be fair to say that rdma is not supported on el5 if it is too hard to address 12:22:54 raghu: I can build the packages on el5 for testing first 12:22:57 raghu: I certainly feel so 12:23:16 any known issues to be fixed in 3.6.3? 12:23:35 Then, I will be doing a beta2 this weekend and probably will GA it next week 12:24:05 raghu: cool, that sounds good 12:24:18 #info 3.6.3 to be GA next week 12:24:25 anything more on 3.6? 12:24:41 guess not, moving on 12:24:47 #topic Gluster 3.5 12:24:48 hagarth: I just want to make sure all the release-3.6 patches have been merged before making beta2. So triggering regression runs on the patches that have got an ack 12:24:54 raghu: ok 12:25:11 ndevos: updates on 3.5? 12:25:27 same el5 build issue as on 3.6, thats the only blocking point for doing a 3.5.4beta1 12:25:54 ndevos: since el7 is out, should we continue supporting el5? 12:25:58 I do not know of any patches that need to get in 12:26:12 well, yes, for 3.4, 3.5 and 3.6 we need to keep el5 support 12:26:27 ndevos: ok 12:26:37 we could maybe drop it for 3.7, but I would expect that we need client-side support for el7 for older releases 12:26:38 so we can drop el5 with 3.7? 12:26:43 ndevos: maybe do a beta1 without el5 support? 12:27:08 kkeithley: I am in favor of doing that unless the larger community feels it is important 12:27:13 hagarth: el5 may work, and the build issue is not so much el5-contained, but in the Fedora COPR buildsys 12:27:26 ndevos: ok 12:27:41 maybe we should poll the community about continued el5 support? 12:27:42 Well, we have other issues with the version of python in el5, right? 12:27:56 kkeithley: yes, for geo-replication IIRC. 12:28:00 for heal, among other things 12:28:07 right 12:28:19 we dont have geo-replication on el5, and I think we could drop all the server bits on el5 for 3.7 12:28:34 so maybe if 3.6 client-side works with 3.7 we can just tell el5 users to keep using 3.6? 12:28:49 hmm, yes, *if* 12:28:49 ndevos: sounds like a good idea, would you want to propose this plan on gluster-users? 12:29:01 kkeithley: I expect 3.6 client side to work with 3.7 12:29:07 hagarth: sure, sign me up for that 12:29:22 #action ndevos to poll the community about continued el5 support 12:29:32 ndevos: a beta later this week then? 12:29:50 * ndevos doesnt know about other legacy distributions, but he'll see the responses on- and off-list 12:29:59 hagarth: yep 12:30:18 #info Gluster 3.5.4beta1 to land later this week 12:30:27 anything more on 3.5? 12:30:40 not from me 12:30:48 moving on 12:30:51 #topic 3.4 12:30:58 raghu: fwiw, glusterfs-3.6.3beta1-0.24.git73835a0.el5.centos.src.rpm builds fine on non Fedora COPR 12:31:13 kkeithley: any updates here? 12:31:16 3.4.7beta2 is 12 days old. The RPMs have been available for 7 or eight days 12:31:44 How much longer do we want to give people to test? 12:31:58 * hchiramm probably 3.4.7 is the last 3.4 release :) 12:32:00 Do we have any testing feedback 12:32:06 Good point 12:32:09 kkeithley: maybe we should include one more patch .. the dht log flooding issue? 12:32:10 yes, 3.4.7 is likely to be the last 12:32:25 ndevos: cool. 12:32:45 kkeithley++ thanks :) 12:32:54 what is the BZ? has it been cloned for 3.4? 12:32:54 kkeithley: include that patch and do a beta3? announce a release schedule to the community saying 12:33:03 Lets make a bunch of noise about last 3.4.x release is in final beta testing. Please try it out now or forever hold your piece? 12:33:07 kkeithley: are you sad that you will not have anything to maintain anymore when 3.7 is out? 12:33:09 hagarth: ^ ? 12:33:15 "If we don't get any feedback, I am going to release by " 12:33:24 * JustinClift nods 12:33:26 sad kkeithley is sad 12:33:26 JustinClift: sounds like a plan 12:33:52 kkeithley: I know a way to make you happy then :D - raise your hand for the next topic! 12:33:55 March 31. April 1 not a good idea generally. I'm flying to BLR on April 2. 12:34:09 kkeithley: release 3.4.7 from BLR? :) 12:34:17 I could do that 12:34:30 ok cool 12:34:43 #info Gluster 3.4.7 to be released in the first week of April 12:34:52 anything more on 3.4? 12:34:54 Just not April 1 please. 12:34:54 Live, from Bannerghatta Road, it's Gluster 3.4.7 12:35:07 * spot aims the spotlights 12:35:16 jdarcy: I think kkeithley gets here on 4th or so. 12:35:24 Probably nobody gets the Tonight Show "Live From New York City, It's David Letterman" references 12:35:43 * ndevos definitely didn't 12:35:50 ok, moving on. 12:35:53 #topic Gluster next 12:35:59 I will go first on 3.7 12:36:13 3.7 is shaping up well. we have all patches for feature freeze. 12:36:17 so, well done everyone! 12:36:30 Cool 12:36:37 ++++ 12:36:40 nice! 12:36:49 Am I ok to shut down a bunch of Rackspace VM's then? 12:36:49 3.7 is looking to be one of our bigger releases in terms of features. 12:36:58 JustinClift: think so 12:37:20 :) 12:37:22 I will be dropping a note about having reached feature freeze and plans for branching release-3.7. 12:37:23 how long will you allow for stabilization and bug fixes before branching off release-3.7 ? 12:37:37 Has anyone done a performance comparison from before and after Merge Madness? 12:37:40 really appreciated if we can get the documentation patches for all features before the release 12:37:43 Code Freeze is April 15 (US Tax Day) 12:37:45 jdarcy: Good idea 12:38:02 ndevos: I have started running tests, will update based on what I see :) 12:38:05 oh, yes, indeed, documentation for the feaures is needed before the branching 12:38:08 Awesome work everyone! 12:38:15 I don't want our users to be the ones to tell us there's a major performance regression. 12:38:24 hagarth: Are we ok to make "having any spurious failures still existing" a blocker for code freeze for 2.7 ? 12:38:30 s/2.7/3.7/? 12:38:32 jdarcy: +1, I will try publishing some numbers between 3.6.3 and master soon. 12:38:55 hchiramm__: being the docs maintainer, can you send out a list of features that need documentation update? 12:39:04 JustinClift: +1 12:39:04 Is code freeze when we branch, or will we branch sooner? 12:39:27 kkeithley: I intend branching sooner once we get more feedback from testing 12:39:29 Cool 12:39:56 as soon as all maintainers are happy with their tests, I will branch release-3.7. 12:40:08 hagarth, well, all the features need documentation .. :) .. yes, I can send out an email requesting the same. 12:40:17 We should prob branch after the spurios regression are nuked then. Save us having to backport master to 3.7 branch then 12:40:39 #action hchiramm to send out a note on gluster-devel about features still needing documentation in 3.7. 12:40:53 JustinClift: sure, we could aim to do that. 12:41:00 for documentation I suggest you keep shaunm in the loop 12:41:07 JustinClift: you are curating a list of spurious regressions somewhere right? 12:41:21 hagarth: Hmmm, I can do 12:41:46 JustinClift, hagarth : identified a new one tests/bugs/distribute/bug-884455.t 12:41:48 JustinClift: that will be helpful.. I have a list of spurious failures too. We can consolidate our lists and send a note on gluster-devel. 12:41:53 I've more been just pointing out the major ones, but we can turn a proper hit list 12:41:54 tigert, these are the 3.7 feature documentation in GlusterFS source code 12:41:56 atinmu: yes, that is in my list. 12:42:07 hagarth, cool 12:42:29 ok 12:42:33 JustinClift: let us create an etherpad for this one and strike off issues as we fix 12:42:47 anything more on 3.7? 12:43:29 guess not, moving on. 12:43:33 #topic 4.0 12:43:40 #info https://public.pad.fsfe.org/p/gluster-spurious-failures 12:43:42 Things have been pretty quiet on the 4.0 front because of all the 3.7 activity. I'll schedule a catch-up meeting next week. 12:43:57 jdarcy: ok 12:44:02 JustinClift: fantastic! 12:44:20 #action jdarcy to schedule a 4.0 catch up meeting next week 12:44:33 anything more for now on 4.0? 12:45:00 guess not, moving on. 12:45:03 Nope. 12:45:04 #topic Other Agenda items 12:45:12 #topic Fix regression tests with spurious failures 12:45:19 we discussed this right now 12:45:26 Oops ;) 12:45:28 Early warning: I'll be in BLR the last week of April. 12:45:41 #action hagarth and JustinClift to send a list of spurious failures to gluster-devel. 12:45:47 jdarcy: look forward to that! 12:45:54 #topic docs 12:46:00 atinmu: Which branches does 884455.t happen in? 12:46:04 hchiramm: Is this your topic? 12:46:10 JustinClift: that happens on master 12:46:31 tx 12:46:42 as far as docs are concerned, schandra has staged some good content. 12:46:57 he is looking for more feedback. any help there would be welcome. 12:47:20 #link http://www.gluster.org/community/documentation/index.php/Staged_Docs 12:47:29 if you have feedback, please let us know. 12:47:39 #topic Awesum Web Presence 12:47:44 ok 12:47:54 Debloper: you had thoughts? 12:48:01 hagarth, not really 12:48:03 I agree the "divide and conquer" might work, as everyone is busy 12:48:04 but I can talk . 12:48:06 I can take a look at 884455.t since I might have written it. 12:48:21 tigert: would like to come back to this with more update next week 12:48:29 jdarcy: :) 12:48:43 Debloper: ok 12:48:46 prototyping what I can show instead of tell. 12:48:51 tigert, Debloper: I am thinking of doing a daily sprint style update on gluster-infra on website revamp. 12:49:13 hagarth: yes, that's sort of what it'll be from tomorrow onwards 12:49:22 ok 12:49:27 Debloper: great! 12:49:32 so you mean have a discussion going in the list? 12:49:48 for others who are reading this, please follow the website revamp on gluster-infra :) 12:50:03 tigert: I think Debloper intends showcasing daily progress on the revamp. 12:50:15 ok 12:50:17 tigert hagarth: yes, updates on list - feedback as github issues (and low-level discussion there) 12:50:29 hagarth: correct 12:50:33 Debloper: great, will look forward to this. 12:50:35 currently the site is not on github though 12:50:47 but in gitorious (forge) 12:50:58 tigert: I'm working on a separate repo - totally static website 12:51:13 Debloper: I do think this is not just a technical issue only 12:51:35 right, I'm looking for contents actually - and aesthetic feedback. 12:51:55 don't think it's much of a technical challenge 12:51:57 ie, the current static site works but lacks the content we want to have there 12:52:11 making yet another technical skeleton will likely not solve the problem 12:52:28 but looking forward to see what you have been doing 12:52:39 there won't be any skeleton - the current website tries to do too many things 12:53:18 I'm keeping the site as the landing page & all other content are either on docs.g or blog.g or in code.g 12:53:27 .g as in .gluster.org 12:53:41 yeah 12:53:44 Debloper: showcasing your work will help us, will look forward to that tomorrow. 12:53:47 that might make sense yeah 12:53:57 and splitting the things into lego bricks 12:54:20 let's see how it goes, thanks! :) 12:54:31 great update, thanks! :) 12:54:36 #topic Gluster Summit Barcelona, second week in May 12:54:39 spot: all yours! 12:55:03 I have a meeting in 30 minutes to discuss this with Red Hat event planning in EMEA 12:55:15 still no locked in date or venue, hopefully by the end of this week 12:55:34 budget paperwork is mostly done though. :) 12:55:46 spot: fantastic! 12:55:48 who has plans to go? 12:55:53 tigert: all of us ;) 12:56:00 pondering whether the web stuff could be discussed there 12:56:09 Definitely 12:56:14 would be nice to meet in person too to make things more fun :) 12:56:21 tigert: i think that would be a good topic for it 12:56:22 The weather should be nice too ;) 12:56:28 tigert++ 12:56:38 +1 12:56:39 Are we back to Barcelona? I heard it was prohibitively expensive 12:56:50 That's what I was told 12:56:59 yeah. shaunm and I do have some scheduling challenges for the proposed dates (12th->) so firming the dates would be appreciated 12:56:59 kkeithley: from whom did you hear this? 12:57:01 kkeithley: less than Paris or London, from my own visit around 12:57:15 what other options do we have? where are most of the participants based in? 12:57:18 spot: That's what Jen was saying in the weekly OSAS Comm meeting 12:57:29 I probably won't be able to do may, but I'll see if I can figure something out 12:57:30 * spot sighs 12:57:38 spot: lot many folks may need to get visa etc. done .. so a general heads up about the dates would be good. 12:57:45 does it _have to_ be in EU? 12:57:46 hagarth: understood 12:57:59 (not disagreeing, trying to understand) 12:58:03 if its in IN, the budget spikes for everyone else 12:58:05 Debloper: YES! :D 12:58:10 if we do it in the US< the budget spikes for everyone else 12:58:15 not saying IN either. :P 12:58:18 going in the middle is the only real option 12:58:26 and thats EU. :) 12:58:45 Right. Lets all go the other way and fly to Oz? ;p 12:58:49 ok :) 12:58:53 alright, Spain is comparatively cheaper than GER, FRA, UK et al 12:58:56 unless someone here has sponsorship money they havent told me about. ;) 12:59:00 :) 12:59:03 * ndevos proposed Amsterdam, it will save on his travel costs 12:59:12 JustinClift: I wouldn't mind being in Oz on the 29th for the World Cup finals ;) 12:59:13 plus, good enough beers (comparing GER) 12:59:20 Heh Heh Heh 12:59:27 Barcelona has people on the ground who are willing to help with logistics too 12:59:28 The 20-odd hour flight tho... 12:59:35 the office in BCN is quite small however 12:59:40 Amsterdam would be nice (not sure about weather, but it's may - so heck yeah) 12:59:52 misc: we'd not be in the RHT office 13:00:05 We'd be in some pubs/smoking-cafe's ;) 13:00:13 :) 13:00:22 spot: thanks, will look fwd to your update on this one. 13:00:24 moar smoking folks :D 13:00:28 JustinClift: that's a definition of a office :) 13:00:29 * Debloper will stop :P 13:00:36 last topic for today 13:00:40 #topic Gluster Summer of Code 13:00:52 we missed GSOC, so why not have a Gluster Summer of Code? 13:01:13 we can publish all the great ideas that we have and get some interns help build us features 13:01:20 * ndevos supports that idea 13:01:40 Name clash tho 13:01:43 "GSOC" 13:01:45 have enough gears in place for running the program & have enough participation in it, and understanding of how much to achieve? 13:01:53 we can probably have some goodies for the projects that have been implemented the best. 13:01:55 JustinClift: thats the point, right?! 13:01:55 you have funding for that? 13:01:57 How about something else catchy? Suggestions welcome type of thing 13:01:58 Ahh 13:02:00 GlSOC 13:02:17 shaunm: not as much as GSOC, but we can aim to start on a small scale. 13:02:23 GluSOC 13:02:25 Gluster's Dark Night of Winter Coding 13:02:33 if you want to steer clear of google's legal dept, avoid anything with "Summer of" 13:02:36 Sounds cooler eh? 13:02:45 JustinClift: of course, it will be winter in the southern hemisphere :D 13:02:51 :) 13:03:06 shaunm: no worries, Gluster Summer of Code is just an interim name for now. 13:03:25 worth noting that Fedora offered us one of their actual GSOC seats. 13:03:26 kshlm, spot: your thoughts on this as you folks were most active with the GSOC process? 13:03:30 (like last year) 13:03:51 i worry about trying to run a program with 'goodies' as the only participation perk. 13:04:30 but if people want to try, we can totally try. 13:04:46 spot: yeah, just see how it goes. 13:05:18 goodies, linkedin recommendations and your name on some pieces of code/documentation publicly available should help at least a little 13:05:32 and, work-from-anywhere ;) 13:05:35 Really, this is kshlm's project, so I'll defer on this one. 13:05:43 and help as needed. 13:05:58 let us propose this idea on our mailing lists/blog and see the interest? 13:06:38 ok, passing this AI to kshlm :) 13:06:44 #action kshlm to propose gluster winter of code ideas on blog/mailing lists. 13:06:49 Who was I talking to.... Someone noted that Ceph made t-shirts with the names/email addresses of every non-employee who contributed code or a patch or a BZ. Limited edition 13:07:01 We might do something similar 13:07:07 kkeithley: we can plan something like that for the Gluster summit. 13:07:14 any more topics for today? 13:07:25 kkeithley: yeah I did the design for that 13:07:28 kkeithley: indeed, I have that in my notes to send out too 13:07:37 kkeithley: they did a grep of everyone in git 13:07:53 looks like we're done. thanks everyone for attending and tty all next week! 13:07:58 #endmeeting