Hi Ray,
Thanks for raising this again, one of those short lived threads I missed on my brief vacation. As we are about to kick of committer at large elections to the TSC we will have a potentially different constituency of members at the end of the month. In conjunction, and aside from the pain it causes some of our members, we have not in my recollection ever failed to achieve quorum for a TSC call I have attended. I wonder if we can agree on your proposed plan of action? · Once we have our new TSC in place we can start a fresh thread among the TSC members on establishing a time sequence (and time zone) for TSC meetings. · This conclusion of which can be prepared and put in place hopefully by the time our TSC chair for 2017 is elected. I’ll raise it on Tuesdays meeting for any comments but it would be good to hear on the mailing list if there are concerns with this approach. / Chris From: <[email protected]> on behalf of Raymond Paik <[email protected]> Date: Tuesday 2 August 2016 at 20:32 To: "SULLIVAN, BRYAN L" <[email protected]> Cc: TECH-DISCUSS OPNFV <[email protected]> Subject: Re: [opnfv-tech-discuss] TSC Schedule thought All, I don't think there's been further any discussions/options presented on this. As few people noted, finding a second/alternative slot that works for people in Europe/Eastern Timezone in N. America is definitely a challenge. What I'd like to do is send a poll on once we have new committers-at-large TSC members join and see what kind of challenges we'll have for quorum if we alternate between 14h UTC and 04h UTC (for example as Dave Neary suggested). Thanks, Ray On Thu, Jul 21, 2016 at 2:31 PM, SULLIVAN, BRYAN L <[email protected]> wrote: To address the quorum issues related to votes, we could: - take votes out of the TSC calls altogether, and run them as doodle polls etc with notice at the TSC calls - allow the present TSC members to vote on the call they attend, and summarize the results after both TSC calls in a week These will slow things down a bit, but not a lot. Personally, I am open to any secondary rotation (adding to the existing call). One TSC call that I can attend per week is good enough. I assume that we need to also rotate the release planning meetings if not already. Thanks, Bryan Sullivan | AT&T -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Neary Sent: Wednesday, July 20, 2016 3:05 PM To: Raymond Paik; Dan Radez Cc: [email protected] Subject: Re: [opnfv-tech-discuss] TSC Schedule thought Hi, On 07/19/2016 08:54 PM, Raymond Paik wrote: > On the GTM chat, Larry shared this > link > http://www.timeanddate.com/worldclock/meetingtime.html?month=8&day=1&y > ear=2016&p1=37&p2=33&p3=224&iv=0 that shows times in > UTC/Berlin/Beijing/San Francisco... > > So the 2pm Pacific Time I suggested as an alternate slot is actually > 5am in China (not 6am as I thought). Julien noted that he preferred > 6am over 10pm, but 5am may be another story (Julien plus others in > China, let us know your thoughts). > > To make this exercise more interesting, not every country observes > Summer Time/Daylight Savings time, so come November, we'll be looking > at > http://www.timeanddate.com/worldclock/meetingtime.html?month=12&day=1&; > year=2016&p1=37&p2=33&p3=224&iv=0 > > When we return to "Standard" times in Europe/N. America 2pm Pacific > Time is actually 6am in China & 7am in Japan + Korea which maybe more > reasonable for people in Asia. > > If you have other ideas/suggestions, please chime in :-) I fear that whatever we do will cause issues. * It's clearly unfair to leave things as they are - we are forcing part of the TSC to attend at unsociable hours * If we move to rotating meetings, we may struggle to attain quorum. For many, it is difficult to attend at certain times (family dinner time, night time, etc), we will lose some attendees, and they will not always be the same people * Decisions made by the TSC if people are unable to attend may be called into question - do we have a mandate to decide something important (say, a scope expansion, a request for resources to the board, or a new project approval) if 30-40% of TSC members are absent? * Abandoning meetings (the radical alternative) will likely not be successful given the dynamic of the group - we are meeting-driven, agenda-driven, and I fear that "take it to the list" will not result in us getting very much done Adding the other cities where TSC members live, we have: http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160801&p1=37&p2=33&p3=224&p4=43&p5=101&p6=248 The best time is what we have currently. The best alternative is 11pm Eastern US time/5am Berlin time or midnight Eastern/6am Berlin. So the least painful of the proposals would be to alternate meetings between 14h UTC and 04h UTC - but you would probably lose several East Coasters and Central Europeans at that time. Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338 _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
