Jenkins is being placed in shutdown mode for maintenance On 11/29/21 11:50 AM, Vanessa Valderrama wrote:

LFN Community: The next LFN Developer & Testing Forum is scheduled for January 10-13, 2022. Once again we will be virtually gathering the LFN project technical communities to progress our releases;

LFN Community: The next LFN Developer & Testing Forum is scheduled for January 10-13, 2022. Once again we will be virtually gathering the LFN project technical communities to progress our releases;

CORRECTION ON THE DATE On 11/29/21 11:45 AM, Vanessa Valderrama wrote:

What: LF will migrate Jenkins SSD volumes to NVME volumes as a cost reduction effort and to improve performance. When:

LFN Community: This is a notification that we have a webinar with the LFN End User Advisory Group (EUAG) coming up on Tuesday, November 30th, 7:00 AM Pacific Time. Register for the event today to

LFN Community: This is a notification that we have a webinar with the LFN End User Advisory Group (EUAG) coming up on Tuesday, November 30th, 7:00 AM Pacific Time. Register for the event today to

Dear TSC, The changes to the TSC members page is now updated: https://fd.io/getinvolved/tsc/ Feel free to create a PR for any changes desired. Cheers, Ole

LFN Community: The next LFN Developer & Testing Forum is scheduled for January 10-13, 2022. Once again we will be virtually gathering the LFN project technical communities to progress our releases;

As the principal technical event for the LF Networking projects, this bi-annual gathering, has on average attracted over 500 registrants, provides the opportunity for each participating community to

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

+1

Dear Ameen, pls see inline. Understand. My read is that folks are simply very busy, and number of people versed in ds-lite and other softwire technologies that VPP implements aplenty of, is not that

Dear Ameen, What specific statement in the email do you disagree with? This is not a research paper, it is FD.io CSIT release report capturing benchmarking and functional test data for v21.10

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