15:01:51 <kshlm> #startmeeting Community Meeting 2017-11-08
15:01:51 <zodbot> Meeting started Wed Nov  8 15:01:51 2017 UTC.  The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:51 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:51 <zodbot> The meeting name has been set to 'community_meeting_2017-11-08'
15:01:51 * ivan_rossi hello
15:02:03 <kkeithley> Dobry den
15:02:14 <kshlm> Welcome everyone!
15:02:30 <kshlm> I'll be waiting for 3 more minutes.
15:02:31 <ndevos> Goede middag!
15:02:44 <kshlm> In that time , please think up of stuff to discuss.
15:02:55 * shyam is here!
15:02:57 <JoeJulian> #link https://github.com/gluster/community/issues
15:03:11 <amye> Yespls on the community issue queue.
15:03:34 <amye> Anything else that came out of Gluster Summit that we want to discuss?
15:04:27 <kshlm> Are we discussing the community issues queue, or the issues in the queue?
15:04:44 <amye> just the fact that there is one.
15:04:59 <amye> The issues in the queue - the new ones are things like 'docs.gluster.org has an invalid SSL cert'
15:05:05 <amye> because we're not self-hosting.
15:05:10 <JoeJulian> I kind-of expected talking about the issues in the queue.
15:05:31 * amye gets her coffee.
15:06:00 <amye> We can do that too. Anything on your mind, JoeJulian?
15:06:18 <JoeJulian> Always.
15:06:45 <kshlm> JoeJulian, If you have specific things, add them to https://bit.ly/gluster-community-meetings
15:07:09 <JoeJulian> Ah, there it is. I looked for that earlier.
15:07:40 <ndevos> it would be good to have a tag "Triaged" in the queue, that way we can easily skip the ones we do not need to look at this week
15:07:46 <kshlm> FYI, it's in the channel topic.
15:08:09 <JoeJulian> Heh, that makes it too easy. ;)
15:08:26 <kshlm> :)
15:08:32 <kshlm> Okay, let's start.
15:08:40 <amye> Well, I really wasn't intending the queue to be discussed in the meeting on the regular - the intent was to be able to let people know what's going on in the community.
15:08:52 <amye> Things that are happening, and giving people a place to talk about messaging, events, etc.
15:09:17 <amye> That being said, I'd like to know who's attending KubeCon, https://github.com/gluster/community/issues/4
15:09:44 <amye> and as well as FOSDEM: https://github.com/gluster/community/issues/6
15:09:45 <ndevos> I think obnox will be at KubeCon
15:09:52 <amye> Super, I'll add him to the ticket.
15:09:54 <kshlm> #topic KUBECON
15:10:40 <JoeJulian> Apparently I'm not. Samsung's only paying for 4 people to go, two of them are Ada recruits that had talks accepted.
15:11:10 <amye> We're going to be doing a demo of CNS at the Red Hat booth, and I'd like to do a Gluster BoF if at all possible.
15:11:16 <amye> JoeJulian, sad panda!
15:11:38 <amye> However, I hear that next year is back in Seattle, late in the year, so next year.
15:12:09 <amye> We can move on if no one else is dropping into Kubecon, FOSDEM is my big worry. :)
15:12:33 <kshlm> Okay. Let's move on.
15:12:37 <kshlm> #topic FOSDEM
15:13:00 <amye> We've put in for a joint stand with Ceph, I haven't heard back but I'm going to assume we're getting it.
15:13:15 <amye> ndevos, I see that you've put the devroom in, any updates there?
15:13:23 <amye> (in the community issue queue)
15:13:38 <ndevos> the CfP for the Software Defined Storage is still open until 26 November
15:13:54 <ndevos> <put DevRoom somewhere in there>
15:13:55 <amye> How's the status? Do we need to start promoting heavily?
15:14:19 <ndevos> there are currently 9 proposals, 4 Ceph, 4 Gluster, 1 OpenEBS
15:14:44 <kkeithley> I don't remember BOFs being a thing, per se, at FOSDEM, but maybe I'm wrong. Are we doing a BOF there?
15:14:46 <ndevos> we need to promote the CfP more to get some other projects to present
15:14:46 <amye> Ok. I can connect with Leo and have both Ceph and Gluster social media accounts start promoting.
15:14:53 <amye> kkeithley, KubeCon BoFS.
15:15:00 <kkeithley> FOSDEM BoFs
15:15:04 <ndevos> no BoF at FOSDEM
15:15:21 <amye> FOSDEM feels like all BoFs
15:15:40 <ndevos> yeah, FOSDEM is about the hallway tracks in any case
15:15:45 <kkeithley> hence prefacing my comment with BOFs not a thing at FOSDEM
15:16:03 <amye> ndevos, I'll see if we can't push the DevRoom more in various places. Any particular project you'd like to see?
15:16:27 <ndevos> if we have a stand at FOSDEM, we should really make some kind of office hours schedule and announce that (repeatedly) ina advance
15:16:32 <amye> I mention it now because American Thanksgiving is coming that week before.
15:16:52 <amye> ndevos, I've done that in the past on an internal to Red Hat page, would it be better to have that on the main website?
15:17:05 <ndevos> amye: anything related to storage really, Tendrl is something that is a MUST
15:17:34 * amye looks around for Tendrl folks in here
15:18:00 <ndevos> amye: yes, definitely public, and hopefully people find it before they come to FOSDEM and we have a sort of BoF during the office hours
15:18:10 <amye> Putting a note for myself into the issue.
15:18:26 <amye> Also: what demos are happening at what time during those office hours
15:18:43 <amye> We've not done super well on that in the past but with a little organization, we could be much better at it.
15:19:18 <kkeithley> can we get a monitor? Demos on a laptop screen are pretty lame
15:19:28 <amye> I can work with Brno to get a monitor.
15:19:53 <ndevos> yeah, I think so too, and depending on who will be there, we can have different hours with some topic or such (we should really get some oVirt guys there)
15:20:08 <amye> I'll add that to the issue too to make sure I don't forget. oVirt might? have their own stand, I have not heard yet.
15:20:26 <amye> I'll start by building out the schedule as soon as we're confirmed on a stand and we'll roll from there.
15:20:30 <amye> Anything else on FOSDEM?
15:20:38 <ndevos> I dont know if they have their own stand, but a combined office hour with oVirt would be great
15:21:24 <kkeithley> Can we share the Fedora and CentOS booth maybe, instead of being crammed into that space we've been in for the last 2+ years?
15:21:33 <kkeithley> That's really unpleasant IMO
15:22:09 <amye> kkeithley, no control over that, sorry.
15:22:37 <ndevos> I think CentOS has a shared booth now too, not their own one anymore
15:22:39 <amye> I'm with you on not being crammed into the corners, but I don't get a say in where we end up.
15:22:41 <kkeithley> especially when the other people try to take over our space in addition to their own
15:23:00 <amye> That's why we're starting off with a joint booth with Ceph so that the crowding is already complete. ;)
15:24:19 <amye> Other things?
15:24:51 <ndevos> we need a good statement about "why ceph, and not gluster?" (or the other way around)
15:25:14 <ndevos> that will be the most common question at the booth, better be prepared :)
15:25:16 <kkeithley> lol
15:25:22 <amye> That has been our most asked question of all time, yes.
15:26:01 <ndevos> something written would be cool, and as we share stands, that may even be possible
15:26:29 <amye> Like a poster or just a note?
15:26:43 <ndevos> just little handouts or such
15:27:41 <ndevos> also, would it be possible for the crew at the stand to get a Gluster branded t-shirt/polo/...
15:27:42 <amye> We try not to do printed material for FOSDEM because it ends up wasted, but let me think about it.
15:27:59 <amye> Yes, if you can tell me all who's going with a 6 week window. :D
15:28:15 <amye> Put your name on the issue and I'll set the cutoff for when we can make that happen.
15:28:20 <ndevos> need to get the submissions for talks first :)
15:28:41 <amye> Note: I am not likely to be at FOSDEM which is why I'm being particularly thorough about making sure we have good organization to make FOSDEM a success.
15:29:41 <kshlm> amye, Happy with progress on FOSDEM for the moment?
15:29:45 <amye> yes!
15:29:49 <amye> We can move on. :)
15:29:51 <kshlm> Cool!
15:30:06 <kshlm> Next up.
15:30:14 <kshlm> #topci Summit follow-up
15:30:21 <kshlm> #topic Summit follow-up
15:30:32 <JoeJulian> ?
15:30:48 <kshlm> Just catching up on stuff after summit.
15:31:13 <JoeJulian> Just curious as we skipped two items.
15:31:23 <kshlm> Oh!
15:31:27 <kshlm> Didn't see those.
15:31:33 <amye> Sorry, people started adding things. :D
15:31:37 <amye> We all got excited.
15:31:56 <kshlm> Let's go back.
15:31:59 <kshlm> #topic Slack
15:32:02 <kshlm> Do we need it?
15:32:04 <JoeJulian> But you're running this show. If you think we need to put those off 'till next time...
15:32:23 <JoeJulian> I prefer IRC, but there were some good points made at community BoFs.
15:32:32 <kshlm> It's the cool thing everyone is doing.
15:32:35 <JoeJulian> Mainly the ease of use from a phone.
15:32:48 <amye> My feelings on slack: I think we miss a lot of potential users by not having one. In my ideal world, we have a 'bridged' slack that mirrors IRC and vice versa.
15:33:22 <JoeJulian> It's theoretically possible...
15:33:22 <amye> Unfortunately, those are pretty brittle. I know Ceph has that solution but I'm not sure how happy they are with it.
15:33:23 <kshlm> I don't get slack all that much.
15:34:10 <kshlm> Possibly because I just use the IRC gateways.
15:34:14 <amye> A good second best: have some of us be active in the existing slacks that are already using Gluster heavily?
15:34:22 <amye> like Kubernetes, CNCF, OpenShift?
15:35:26 <kshlm> I don't think most of us here use slack all that much.
15:35:52 * amye is the only one.
15:35:54 <amye> So lonely.
15:35:54 <JoeJulian> Maybe not us, but a lot of people do.
15:35:55 <amye> :P
15:36:03 <JoeJulian> It's not a high barrier to entry to install slack.
15:36:24 <JoeJulian> And if it can get us more community involvement....
15:36:51 <ndevos> oh, right, I still wanted to see how slack for kubernetes works out...
15:37:05 <amye> ndevos, that slack is huuuuuuge
15:37:13 <JoeJulian> huuuuuuuuuuuuge
15:37:21 <amye> 24k in a single 'team'.
15:37:23 * ndevos *blinks*
15:37:34 <ndevos> almost 24k +1 then
15:37:38 <amye> Sorry, 24,640 as of 3 seconds ago.
15:38:17 <amye> and 1354 in their #sig-storage.
15:38:27 <amye> So, if we wanted to reach more people, that might be a good middle ground.
15:38:44 <amye> I'm feeling like this is a mailing list post to get more input?
15:39:11 <JoeJulian> +1
15:39:14 <amye> Just being mindful of time, we have other things on the agenda.
15:39:17 <amye> I can write it up.
15:39:38 <kshlm> FWIW, I wouldn't mind slack.
15:39:45 <kshlm> Shall we move on to the next topic?
15:39:48 <amye> ++
15:40:02 <JoeJulian> Also comment on the issue.
15:40:12 <kshlm> #topic Should we make the issues queue the replacement for this? Or a project board for better organization of those issues?
15:40:43 <kshlm> Replacement for what?
15:41:12 <amye> So Ansible uses a website to turn their issue queue into a trello board, I cannot for the life of me remember what it's called
15:41:13 <kshlm> +1 to have a github project board created for organization.
15:41:34 <amye> Once I remember what it is, we can certainly make a column of 'for discussion in community meeting'
15:41:49 <JoeJulian> replacement for hackmd
15:41:50 <kshlm> Is it actual trello?
15:41:59 <ndevos> right, a github project would be simple, everything at one place
15:42:19 <amye> kshlm, that, I might have remembered. I don't think it is.
15:42:36 <JoeJulian> I don't know trello, but I think so
15:42:39 <amye> I'm fine with having the hackmd pad be available, we link to 'things that need input' and roll from there.
15:42:39 <kshlm> I initially used waffle.io for gd2. Which did the github issue / kanban board thing,
15:42:44 <amye> THAT WAS IT
15:42:58 <amye> .. that poor startup that no one can remember.
15:43:02 <amye> kshlm++
15:43:28 <kshlm> JoeJulian, How would the replacement work?
15:43:33 <amye> If everyone's cool with having a kanban board style thing, I can set that up in time for next meeting.
15:43:45 <JoeJulian> +1
15:44:15 <kshlm> amye, I'm cool. And even if someone isn't, the issue queue is still available,
15:44:24 <amye> Not intended as a full replacement for HackMD because we might have more than just 'what's top of mind'
15:44:38 <amye> It'll help us organize this more, and also give people a chance to have their own input for community meeting.
15:44:43 <amye> We can move on.
15:46:33 <kshlm> Okay. I'm a little confused as to what we decided upon with the last topic. But let's move on.
15:46:39 <kshlm> #topic Summit follow-up
15:47:07 <ndevos> meeting attendance?
15:47:10 * ndevos *cough*
15:47:16 <amye> Yes that, ndevos.
15:47:17 <JoeJulian> The action item was that amy was going to set up a project board for next meeting to see what it would be like.
15:47:30 <amye> I've marked it on the agenda, no worries - kshlm.
15:47:47 <kshlm> Thanks JoeJulian, amye
15:47:51 <amye> Halping.
15:48:12 <kshlm> Back to summit.
15:48:27 <kshlm> ndevos, Well all the regulars showed up.
15:49:14 <amye> That's better than not. :)
15:50:30 <amye> Things that are top of mind from Summit: we're getting good followup from BoFs, is there anything we're really missing?
15:51:07 <ndevos> nigelb made some notes for some of the BoFs, I was expecting him to send them out - did he do that and did I miss it?
15:51:27 <amye> Nigel has been buried in infra tasks, I will ask him.
15:51:32 <amye> I believe he is just back this week.
15:52:09 <JoeJulian> Sounds like a survey question
15:52:09 <JoeJulian> Do you have a summit follow-up survey?
15:52:29 <amye> At the moment, I do not because the community survey is open.
15:52:49 <amye> However, the gluster.org website can do that pretty easily, and I can send that out today if that's something people are interested in.
15:52:57 <nigelb> (I will send them out this week, once I undig myself from everything else I need to do)
15:52:58 <amye> What questions would you want to ask?
15:53:09 <amye> nigelb, see, I knew you were slammed. :)
15:54:15 <JoeJulian> Let's add questions to be asked in a survey about the summit to https://github.com/gluster/community/issues/3
15:54:34 <kshlm> Not a question for the summit, but when are the summit videos gonna be posted?
15:54:53 <kshlm> s/for the summit/for the survey/
15:54:55 <amye> Shortly, that's on me, kshlm. I just got the uploads this morning.
15:55:06 <amye> Same with slides, I was waiting for everything all at once.
15:55:12 <amye> JoeJulian, ++
15:55:28 <kshlm> Cool. I would like to rewatch a couple. I might not have been paying attention during the actual presentation.
15:55:32 <amye> Deadline of End of Day tomorrow on survey questions, and I'll send it out Friday and publicize it again on Tuesday.
15:55:46 <amye> Awesome. Will send out an email when that's complete, kshlm.
15:56:02 <kshlm> Did I send the slide links to you? I don't remember doing that?
15:56:20 <amye> kshlm, if you haven't sent me your slides, please do. :)
15:56:28 <amye> Other things around summit? We're nearly at time.
15:56:40 <kshlm> Will do.
15:56:50 <kshlm> I don't have any other things.
15:57:06 <kshlm> Others in the channel?
15:57:08 <JoeJulian> Good enough. :D
15:57:33 <amye> We're good with the next meeting being 22 Nov?
15:58:05 <kshlm> Good with me.
15:58:20 <JoeJulian> +1
15:58:26 <kshlm> But before we end, anyone else want to host the meeting?
15:58:31 <amye> I can host.
15:58:41 <kkeithley> a lot of Americans might take PTO that day, but yeah
15:58:51 <amye> kkeithley, that's why I mentioned it.
15:59:03 <kshlm> Thanks amye!
15:59:12 <amye> ... except someone took my ops from this channel away :D
15:59:24 <amye> so that part I might need to fix but that's easy.
15:59:40 * loadtheacc is here. what did I miss?
15:59:44 <amye> even if I'm on PTO I can sign in
15:59:49 <amye> loadtheacc, all the things!
15:59:56 <amye> Timezones are a thing.
16:00:22 <loadtheacc> :-)
16:00:32 <kshlm> TImezones are okay. DST is not.
16:00:39 <amye> Miserable.
16:00:55 <kshlm> Okay. Let's end todays meeting.
16:01:06 <kshlm> See you all on the 22nd.
16:01:10 <amye> Thanks all!
16:01:10 <kshlm> #endmeeting