Note: lists.openchainproject.org will be down for maintenance on Monday, September 26th, starting at 9AM Pacific Time (4PM Monday September 26, 2022 UTC), for approximately one hour.
[japan-wg] OpenChain meeting schedules - we have an orphaned invite issue again
I like the idea of "delete all and resend". What you can do is maybe fix a date for the "great resend"... So that everybody can ensure they've cleaned up their calendar before...
From: japan-wg@... <japan-wg@...> on behalf of Shane Coughlan via lists.openchainproject.org <scoughlan=linuxfoundation.org@...>
Sent: Thursday 23 June 2022 09:14
To: OpenChain Main <main@...>
Cc: OpenChain Korea <korea-wg@...>; OpenChain Japan <japan-wg@...>; OpenChain Taiwan <taiwan-wg@...>; OpenChain Germany <germany-wg@...>; OpenChain Germany <germany-wg@...>; OpenChain India <india-wg@...>
Subject: [japan-wg] OpenChain meeting schedules - we have an orphaned invite issue again
CAUTION:This email is received from an external domain. Open the hyperlink(s) & attachment(s) with caution.
OpenChain has various regular or semi-regular meetings throughout each month:
Our tooling work group
Our telco work group
Until recently we also had a bi-weekly global call, but consensus was to shift this fully into our mini-summit format. Attendance was higher and the monthly or six weekly cadence suites calendars.
However, it appears that we have some issues with calendar invites becoming orphaned on individual calendars. For example, when the Global Calendar is updated, those updates do not necessarily reflect in people’s clients.
Specifically, our announced move from bi-weekly global call to mini-summits was communicated on May 23rd and on that date the calendar invite was removed from the Global Calendar. However, six people have an active invite in their individual clients this week.
I want to solicit your feedback on the best way forward.
Ask everyone to delete all invites and resend (what we did in December to reboot)?
OpenChain General Manager
Book a meeting:
Internal to Wipro
+1 and a similar approach seemed to work well last time. Best,