Following up from the discussion on this topic. Here's a TZ based set (at an arbitrary date) <https://www.timeanddate.com/worldclock/meetingtime.html?day=18&month=2&year=2020&p1=54&p2=48&p3=179&iv=1800> And we were discussion whether <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=2&day=18&hour=9&min=0&sec=0&p1=54&p2=48&p3=179&iv=1800> works for participants from EMEA. On Sat, 8 Feb 2020 at 09:02, sankarshan <sankarshan@xxxxxxxxx> wrote: > > > > On Fri, Feb 7, 2020, 18:37 Sunny Kumar <sunkumar@xxxxxxxxxx> wrote: >> >> On Thu, Feb 6, 2020 at 11:47 AM sankarshan <sankarshan@xxxxxxxxx> wrote: >> > >> > On Thu, 6 Feb 2020 at 16:24, Yati Padia <ypadia@xxxxxxxxxx> wrote: >> > > >> > > Hi, >> > > In response to the discussion that we had about the timings of the community meeting, I would like to propose that we can have it at 3PM/4PM IST on 11th February to accommodate EMEA/NA zone and if it suits all, we can fix the timing for next meetings as well. >> > > If anyone has any objections regarding this, it can be discussed in this thread so that we can come up with a fixed timing for the meeting. >> > > >> > >> > I'm not remarkably inconvenienced by the proposed time. 1600 >> > (UTC+0530) is still 0530 EST (at present day) - so that's perhaps >> > early for those in that TZ. I'll defer to the participants from there >> > to have their feedback heard. >> > >> Agree with you Sankarshan; it will be too early for NA TZ. We can >> work for a balanced/overlapping time probably between 1800 to 2000 >> (UTC+530). >> I think in the past it was being hosted at the same time. >> >> We can discuss about it in upcoming meeting. > > > Now that we do have a regular participation at the meetings, we should think about making them more interactive than just a read out and reporting. Those parts can be handled through the meeting notes themselves. I'd like to see more information sharing about the process of production of the consumables for our users viz. health of tests, health of infrastructure, triage of outstanding issues, new work that is coming up in some time, keeping the documentation current and accurate etc > > If we look at the meetings from the perspective of making them useful for those who couldn't join, our updates and discussions would be very different. -- sankarshan@xxxxxxxxx | TZ: UTC+0530 kadalu.io : Making it easy to provision storage in k8s! _______________________________________________ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
