<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 9 May 2016 at 23:56, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, May 9, 2016 at 2:01 PM, Amye Scavarda <<a href="mailto:amye@redhat.com">amye@redhat.com</a>> wrote:<br>
><br>
><br>
> On Sun, May 8, 2016 at 11:50 PM, Raghavendra Talur <<a href="mailto:rtalur@redhat.com">rtalur@redhat.com</a>><br>
> wrote:<br>
>><br>
>><br>
>><br>
>> On Mon, May 9, 2016 at 11:55 AM, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>><br>
>> wrote:<br>
>>><br>
>>> In the view of keeping the visibility of the work completed vs work in<br>
>>> progress and getting some fruitful feedback from the community we are<br>
>>> thinking of having a hangout/bluejeans session for 30-45 minutes once in<br>
>>> every month. The sessions will be concentrating on discussing the work<br>
>>> done over the last month and demoing few pieces of Gluster 4.0 projects<br>
>>> and what's the expectation for the coming month(s).<br>
>>><br>
>>> There are couple of options we have w.r.t scheduling these sessions.<br>
>>><br>
>>> 1. We use the weekly community meeting slot once in a month<br>
>>> or 2. Have a dedicated separate slot (probably @ 12:00 UTC, last<br>
>>> Thursday of each month)<br>
>><br>
>><br>
>> I would prefer dedicated time slot.<br>
>><br>
>>><br>
>>><br>
>>> I'd request you to vote for any of these two and based on that we can<br>
>>> move forward.<br>
>>><br>
>>> Thanks,<br>
>>> Atin<br>
><br>
><br>
> If we use a dedicated timeslot of 12:00 UTC, we'll never be able to have<br>
> folks from Pacific weigh in.<br>
> I'd suggest more of a rotating timeslot, but we've not had good luck getting<br>
> traction around that.<br>
> - amye<br>
><br>
<br>
</div></div>+1 to this. How about 1500 UTC? That should give time zones where we<br>
have more presence (North America, Europe, India) an equal chance to<br>
be present.<br></blockquote><div><br></div><div>+1 for dedicated time slot at 1500 UTC</div><div><br></div><div>Best Regards,</div><div>Vishwanath</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I think accommodating one more meeting in everybody's busy schedules<br>
might be tough. We already have 4 bug triage meetings and 4 community<br>
meetings in a month. Adding one more might cause us to spread<br>
ourselves thin across these meetings. How about not doing a community<br>
or bug triage meeting in the same week when we schedule this meeting?<br>
<br>
We could turn this meeting into a Gluster.next meeting so that<br>
everybody who is working on something new in Gluster gets a chance to<br>
showcase their work.<br>
<br>
Thanks!<br>
Vijay<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br></div></div>