<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 2, 2018 at 4:51 PM, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@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 dir="ltr">This discussion sort of died, so I'm going to propose 1300 UTC and 1500 UTC on Mondays. If you cannot make it to *both* those times, please chime in.<br></div><div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Thanks for getting this back to life. Was in my todo list to finalize it. </div><div><br></div><div>If there are no voices, I would pick 1300 UTC on Monday and schedule events starting next week. </div><div>I don't have any concerns for 1500 UTC too. Would like to hear others.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div class="gmail_quote"><div dir="ltr">On Wed, Jun 20, 2018 at 12:09 AM Vijay Bellur <<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 19, 2018 at 3:08 AM Nigel Babu <<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I propose that we alternate times for every other meeting so that we can accommodate people across all timezones. We're never going to find one single timezone that works for everyone. The next best compromise that I've seen projects make is to have the edge timezones take a compromise every other meeting.<br></div></blockquote><div><br></div><div>+1. Other models that we can consider:</div><div><br></div><div>- Choose a time slot that works for the majority of maintainers. </div><div>- Have two different meetings to accommodate various TZs.</div><div><br></div><div>Thanks,</div><div>Vijay</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"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 19, 2018 at 2:36 PM Amar Tumballi <<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div>On the fun side, it seems that other than 2 people, not many people have noticed the end of recurring maintainer's meetings, on Wednesdays.</div><div><br></div><div>Overall, there were 20+ maintainers meeting in last 1 year, and in those meetings, we tried to keep all the discussion open (shared agenda before for everyone to make a point, and shared meeting minutes with even the BJ download link). This also helped us to take certain decisions which otherwise would have taken long time to achieve, or even help with some release related discussions, helping us to keep the release timelines sane.</div><div><br></div><div>I propose to get the biweekly maintainer's meeting back to life, and this time, considering some requests from previous thread, would like to keep it on Monday 9AM EST (would recommend to keep it 9AM EDT as-well). Or else Thursday 10AM EST ? I know it wouldn't be great time for many maintainers in India, but considering we now have presence from US West Coast to India... I guess these times are the one we can consider.</div><div><br>Avoiding Tuesday/Wednesday slots mainly because major sponsor for project, Red Hat's members would be busy with multiple meetings during that time. <br clear="all"><div><br></div><div>Happy to hear the thoughts, and comments.</div><div><br></div><div>Regards,</div><div>Amar</div>-- <br><div class="m_-7538462401368870040m_4873662759261363092m_760409577224242914m_5123327666182972370gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div></div>
______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="m_-7538462401368870040m_4873662759261363092m_760409577224242914gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
</blockquote></div></div>
</blockquote></div><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div dir="ltr" class="m_-7538462401368870040gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div></div>