Input from the perspective of your ONAP Technical Program Manager:
Do the meetings need to be tightened up? Without question. Do the agendas need to be kept on track? Indeed, they do. Has your PM allowed discussions to go on-and-on? As it is technically not my meeting, yes, I have. Does this mean that your PM is going to become a royal pain in the side of the TSC going forward on all of the above? You bet it does. (the lack of a smiley here is intentional) I have no voting rights in this decision but I strongly recommend against introducing a new standing meeting in which the attendance of both the TSC members and the PTLs is expected and required. I very strongly recommend against any model where ad-hoc meetings of the same type are viewed as an alternative to a standing meeting. The facts are this: Currently there are roughly 45 ONAP meetings per week competing for time, personnel and bridge resources. Our agreed upon meeting window for this massively global Project falls between 6AM and 8AM Pacific half of the year and 6AM to 9AM the other half. There is only a 2-hour band that is accessible all year long. If we take into account honoring Friday for our Israeli contributors, as we should be, but have not been, then Monday through Thursday is our real meeting window. We already have 2 meetings a week, (Monday PTL & the Thursday TSC) where attendance of both TSC members and the PTLs is expected and required. We have never had a TSC quorum on the PTL meeting that I can recall. Often times we don't get PTL quorum until halfway through. On top of that is the ripple effect of meeting changes on the Community. A significant amount of churn in created as PTLs negotiate with one another to ensure that the right resources can be at the right meetings. On one occasion where the TSC introduced an ad-hoc mandatory meeting, I literally put in a full person day doing nothing but calendar and bridge changes. My time simply reflects the tangible cost of doing business; so be it. The cost to the Community however, in lost productivity due to PTLs scrambling to negotiate and set up any new meeting AND the time they will lose on an ongoing basis as a result of new standing meeting(s) means that the ripple effect has a significant and adverse impact across the Project. I do not believe that the TSC can effectively conduct business on a Project of this size with a weekly 1-hour meeting. The one hybrid option that I will throw out is the having an extended QBR type meeting something like this: Required attendance: TSC members Optional attendance: PTLs & Contributors with the following exceptions: Subcommittee Chairs, Marketing and Community Coordinators Purpose of meeting: Subcommittee Chairs, Marketing and Community Coordinators provide their detailed updates to the TSC Timing: Once per quarter Scheduling: Each QBR rotates time zones in a 2-out-of-3 fashion, meaning that every 3rd meeting will fall outside someone's 6AM-midnight slot. (I figure that it is reasonable for anyone deeply engaged in the Project to suck-it-up for one meeting every 9 months) Agenda: Specific timeslots assigned in advance which are to include presentation plus a 5 min Q&A period – Presenters would be expected to only attend their time slot during any 12AM- 6AM meeting in their time zone, and be optional during the rest of that call. My POV and suggestion only. I will of course support whatever decision the TSC makes on this. Thanks. Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation [email protected], 510.766.5945 San Francisco Bay Area, Pacific Time Zone From: <[email protected]> on behalf of Alla Goldner <[email protected]> Date: Thursday, June 28, 2018 at 10:21 PM To: onap-tsc <[email protected]>, "[email protected]" <[email protected]> Subject: [onap-tsc] TSC meetings: length, topics etc. Hi all, Following my AI from yesterday’s TSC meeting, I am sending this email out. We would want to make life easier for those in Asia who attend our (very late for them)TSC meetings on Thursday. Having said that, we should keep in mind that the only timeframe during which we can have our meetings without getting into 12 am-6 am night hours for any of the regions is these timeframe. One of the proposals raised by community was: TSC meeting time should be shorten to 1 hour - so people in China suffer less due to late evening hours. We should clearly define what are topics on agenda for TSC meetings, and then also: what can be discussed by some form of active chat (yet to be defined) What may be discussed in bi or 3 - weekly meetings, which are also scheduled in advance The other suggestion brought by Phill during our f2f meeting last week was to have separate meetings for a different regions. In any case, further work on the proposals is needed (in case there is a support for any of these), or, alternatively, a new proposal can be brought to the table. Please let us know what you think about 2 proposals above and bring your own suggestions, if you have some. Best regards, Alla Goldner Open Network Division Amdocs Technology This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3236): https://lists.onap.org/g/ONAP-TSC/message/3236 Mute This Topic: https://lists.onap.org/mt/22891952/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
