I can't speak for anyone else, but this is exactly what I did. I looked at the TSC wiki page, saw that the meeting time was 8:00 Pacific Time, converted that to my local time and added an appointment

Big thanks to FD.io community contributors and supporters that enabled this data-rich publication. Great job everyone! Cheers, Maciek

Ole, I don't see how this actually changes anything about the daylight savings time issues... it just moves those issues around. If you enter your meeting in your calendar in PST (the timezone) it

I will be at the IETF meeting, IDR session during our call slot. Yours, Joel Sent via the Samsung Galaxy S20 FE 5G, an AT&T 5G smartphone Get Outlook for Android

The point of defining the meeting at a fixed time is to avoid the summer time issues. Largely caused by the US and Europe swapping at different times mind you. Look at this as a preemptive strike

It seems to me that we should define it in either CET or US Pacific and be done with it. We have done it in US Pacific. If folks want to change it to CET, so be it. Changing it to a time in UTC

Guys, According to the new fd.io Technical Community Doc: --- A Core Projects PTL may choose to appoint another committer from that Core Project to represent the core project in their stead. --- As

Ed, I think it is a misunderstanding that you need a time zone. You need a fixed reference point in time for when the meeting should happen. E.g. 1500UTC. Then it's up to local participants to

Ray, LOL... I'm OK with us making a choice of timezone to offset into. It just gets my hackles up when folks somehow pretend UTC+offsets are some universal answer to the problem: they

Thanks Ed, Given your prior experience then. Can you suggest then, an alternative that might work better? Ray K

Ole, Offset from UTC is not a timezone... it's an identifier of a point in time. It's intrinsically a *choice* of timezone, no better or worse than any other. Ed, who has had the grave misfortune of

Ray, do you mean GMT [1] or UTC [2], they are different [3]. And yes, I know, the world of time is confusing, so no surprise we get confused to :) Cheers, Maciek [1]

This issue has been resolved. If you have any other issues, please open a ticket at support.linuxfoundation.org Thank you, Vanessa

We are currently experiencing issues spinning up OpenStack executors due to an outage with our provider. This issue is impacting all projects. Our provider is treating this as a high priority. Thank

LFN Community: This is a reminder that we have a webinar with Orange coming up this week on Wednesday, November 10th, at 8:00 AM Pacific. Register for the event today to learn about how they deployed

Please take a look at: https://github.com/FDio/site/pull/111 https://deploy-preview-111--fdio.netlify.app/getinvolved/tsc/ Still missing bio's and pictures for: Damjan, Neale, Matt and Maciek. Best

I also remember suggesting getting rid of timezones and the entire world aligning on GMT. 😊 If we aligned on 15:00 hours UTC? Perhaps we can vote on it next week. Ray K

I'll repeat what I said last year when this happened, and what I said two years ago when this happened. Meetings with an international crowd should be set as an offset from UTC. Not some local time

Yes – Maciek, Neale, Vratko and I showed up 1 hour late. Apologies for that! Ray K

Given the DST change in Europe, today’s call was primarily attended by US based TSC members. It was agreed by at the meeting to skip this week given a lack of urgent agenda items in