15:03:08 <kshlm> #startmeeting Gluster Community Meeting 2017-10-11
15:03:09 <zodbot> Meeting started Wed Oct 11 15:03:08 2017 UTC.  The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:09 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:03:09 <zodbot> The meeting name has been set to 'gluster_community_meeting_2017-10-11'
15:03:09 <misc> without '-'
15:03:20 <kshlm> Thanks misc!
15:03:30 <kshlm> Welcome everyone!
15:03:33 <kshlm> #topic Roll Call
15:03:47 * amye is here
15:03:49 * kkeithley is here
15:04:02 * loadtheacc is here
15:04:44 * kshlm is here
15:05:19 <amye> We can have more topics of discussion, I just wanted to get the community issue queue out and a note about the travel coordinating. :)
15:05:55 <kshlm> Let's start with what we have.
15:06:06 <amye> New Community Issue Queue: https://github.com/gluster/community/issues
15:06:07 <amye> Of particular note: community input needed for events strategy for next year, https://github.com/gluster/community/issues/7
15:06:08 <kshlm> Any other topics that come up can get added to the end\
15:06:12 <amye> :D
15:06:24 <kshlm> #topic New Community Issu Queue
15:06:50 <amye> If there's something that you'd like to have more community assistance on, it can go into the issue queue.
15:07:02 <amye> This is patterned after Ansible's community working group.
15:07:06 * shyam is here
15:07:06 <kshlm> This is cool!
15:07:35 <amye> It's heavy on events right now, but I would like to get people to sign up for more events through this, and I'll work with people on funding.
15:07:55 <amye> In short, welcome to our new community project management tool.
15:08:15 <amye> The one that's really important right now is the events for 2018-2019, there is an event scoring spreadsheet.
15:08:17 <shyam> amye: Looks good! :)
15:08:28 <amye> Tell me about the events we _should_ be at, there's a spreadsheet
15:08:35 <amye> https://docs.google.com/spreadsheets/d/10Kl7pUfluoDHMqtmqUfacvCwq-g10iPT9KsK6ZjOQCI/edit?usp=sharing - Event Scoring Spreadsheet: where should we be?
15:09:06 <amye> Imagine that we could choose the events that we wanted to be at, vs the ones we've just always done. What would you choose?
15:09:43 <amye> Other comments on this? Please treat this like a sandbox to play in. :)
15:11:21 <kshlm> I have nothing else now.
15:11:42 <amye> I'll send out an email to gluster-users@ letting people know this is here.
15:11:59 <kshlm> Just that this is a nice way to track stuff.
15:12:09 <amye> This also includes things like 'I am seeing a lot of 404s coming from people looking for the /community documentation from ages ago' - and we should fix that.
15:12:39 <kshlm> On 404s, shouldn't that be tracked on gluster/glusterweb?
15:12:45 <amye> It's a good way to track things that we should take care of. There's also 'board' for things that will need board input, and 'project' for metathings.
15:13:06 <amye> kshlm, when we have a plan to be able to actually fix that, yes, the plan will go into glusterweb.
15:13:19 <amye> This is a placeholder for 'I know this is a problem that we're able to track now'
15:14:45 <amye> I can drop to the next topic if we're good here.
15:15:10 <kshlm> Good with me.
15:15:16 <kshlm> Let's move on.
15:15:27 <kshlm> #topic Gluster Summit Travel Coordinating
15:15:37 <amye> By popular request, we've got a spreadsheet for folks to coordinate arrival/departure times: https://docs.google.com/spreadsheets/d/1Jde-5XNc0q4a8bW8-OmLC2w_jiPg-e53ssR4wanIhFk/edit?usp=drive_web
15:15:54 <amye> If you want to join other people in Prague, put your details on there.
15:16:12 <amye> (this was an AI from maintainers last week, so anyone who wants to connect can)
15:16:33 <amye> That's all from me :)
15:16:51 <kshlm> Cool!
15:16:56 <kshlm> I've put in my stuff.
15:17:00 <amye> ++
15:17:05 <loadtheacc> Awesome!
15:17:08 <shyam> I have updates the releases part before the meeting
15:17:21 <shyam> (ewww!) updated not updates
15:17:27 <kshlm> shyam, Thanks!
15:17:33 <kshlm> Anything you want to highlight?
15:17:34 <amye> well played, shyam
15:18:08 <shyam> Still looking for a running partner for 4.0 as release owner/maintanier
15:18:36 * shyam thinks unless someone volunteered and I forgot that
15:19:24 <shyam> Nothing else of note at present, from the releases section
15:21:08 <kshlm> I can help, just that I don't know how much effort I can spend on it.
15:21:13 <kshlm> Yet.
15:21:18 <shyam> No worries
15:21:23 <shyam> We will find someone! :)0
15:21:25 <amye> shyam, put out an email on maintainers?
15:21:32 <shyam> Have to... will do.
15:22:08 <kshlm> Thanks shyam.
15:22:16 <amye> Yeah, sorry about that.
15:22:40 <kshlm> Any other things that we need to discuss?
15:22:47 <amye> Nothing from my end.
15:22:59 <shyam> Nothing more from me.
15:23:07 <kshlm> Thank you both.
15:23:24 <kshlm> So the next meeting is on the 25th.
15:23:40 <kshlm> This falls on the day when a lot us would be travelling to the Summit.
15:23:53 <kshlm> I know, I will not be available at the time.
15:24:27 <kshlm> Should we hold the meeting for the 25th?
15:24:47 <amye> Probably not, if we have so many people travelling
15:25:03 <amye> Post-event wrapup for 8 Nov?
15:25:38 <kshlm> Okay with me.
15:26:24 <kshlm> Anyone else have objections to skipping the meeting on 25th?
15:26:31 <shyam> None
15:26:40 <amye> Works for me.
15:26:42 <kshlm> Okay.
15:27:03 <kshlm> That's all  I had.
15:27:16 <kshlm> And since there are no more topics, I will end the meeting.
15:27:32 <amye> Thank you kshlm
15:27:39 <kshlm> Thanks for attending today's meeting everyone.
15:27:40 <shyam> Thank you kshlm
15:27:42 <kshlm> #endmeeting