15:06:50 <amye> #startmeeting Gluster Community Meeting October 10
15:06:50 <zodbot> Meeting started Wed Oct 10 15:06:50 2018 UTC.
15:06:50 <zodbot> This meeting is logged and archived in a public location.
15:06:50 <zodbot> The chair is amye. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:06:50 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:06:50 <zodbot> The meeting name has been set to 'gluster_community_meeting_october_10'
15:06:59 * amye is here
15:07:09 <amye> This might be short, but that's fine.
15:07:11 * sankarshan is
15:07:29 <amye> #topic What is the best way to update community on progress across different project?
15:07:48 <amye> Just to kick us off, it's the first topic on the agenda. I can hold for more folks to join.
15:08:14 * loadtheacc is here
15:08:28 <sunny> sunny is here
15:08:34 <sankarshan> i see that projects and subs have started email read outs to the list
15:08:43 <sankarshan> which is good.
15:09:21 <sankarshan> but then perhaps a date/time needs to be thought of where all the project/sub leads come together to say - you heard about the puzzle pieces, here's how the puzzle is coming along
15:09:44 <amye> I think email readouts are good, I would like to see 1) items for community meeting, that we're in right now, and 2) more content that can be put in the blog
15:10:07 <sankarshan> agree to both
15:10:16 <sankarshan> the agenda for this meeting has been lightweight a bit too long
15:10:34 <amye> But, and this leads me towards the next topic, how many of these projects are doing readouts, and how many should be?
15:11:15 <sankarshan> i would have thought all of them are going to do readouts
15:11:16 <amye> (the subtopic was: Should we accept a project only if there is at least once in a month update on the project to mailing list?)
15:11:35 <sankarshan> setting that expectation as a baseline is good
15:11:46 <sankarshan> for instance the CentOS SIGs are putting that in place I read
15:12:19 <amye> oh, cool! I will ask Rich about this next week!
15:12:49 <amye> I didn't have context for why the readouts were starting on the mailing lists, just that I appreciated they were happening.
15:13:16 <sankarshan> in a way it is linked to the GCS project of which the 0.1 announcement happened today
15:13:21 <sankarshan> which, by the way, needs a yay!
15:13:34 <amye> yes, yes it does. I am delighted to see GCS out in the wild.
15:14:10 <sankarshan> needs some more folks trying out the release, there are vagrant instruction sets
15:14:15 <sankarshan> but i digress
15:14:39 <amye> Ok, so it doesn't seem like we have quorum here around the project work, so I'll start a thread on the mailing list around monthly readouts and what we can improve.
15:15:20 <amye> Any other feelings about monthly reports, projects, puzzles?
15:15:34 <sankarshan> none from me.
15:15:46 <sankarshan> we did have a few more folks - they have gone silent
15:16:07 <amye> Not sure if the other topic is things that we have anyone who can speak to it
15:16:11 <amye> #topic How to not miss out backports of critical fixes on release branches
15:16:25 <sankarshan> that requires are fearless release manager
15:16:40 <sankarshan> and at least one of atin/amar
15:16:50 <sankarshan> we are indeed flat out of quorum
15:17:03 <amye> Ok, I will hold that one for next time and assign it to shyam + atin +amar
15:17:13 <amye> Next time  == October 24
15:17:26 <sankarshan> nice! thank you for chairing this
15:17:39 <amye> Happy to, I will chair for October 24 as well.
15:17:46 <amye> Any last thoughts?
15:18:02 <sankarshan> :D
15:18:14 <amye> Alright then!
15:18:17 <amye> #endmeeting