Maintaince has been moved to February 20th

Excellent, please feel free to update the agenda :) Ed

Hi, I will be on flight tomorrow and I cannot join the TSC call. I will see if I can get a proxy for me. Thanks, George

Ed & Team, Some additional agenda items for tomorrow. Close out on the Scapy related IP concerns (Maciek & Ray). Discuss provisioning of a static analysis tool (Dave B & Ray). Co-locating FD.io

Excellent, thanks Luca. Longer term I still suggest option 4+3, and if you have “golden” releases (which in turn will work with released VPP versions) then you might put them under the

I'd like to add some items to the TSC agenda next week. More detailed review of the infrastructure support documentation https://wiki.fd.io/view/Infrastructure_Support

Andrew, Agree, this is just mitigation. 4+3 is something we could work on in ci-management and plan to deploy for the next release. Golden releases, as you say, is to be understood for hicn, we don't

FYI we have reduced the number of artifacts to 3200. https://packagecloud.io/app/fdio/release/ This should fix the problem. Luca

Hello Vanessa, Yes we talked about this and I am available to become a committer of the ci-management project. Regards, Mauro.

LFN Community: We hope that you are planning to attend the Open Networking & Edge Summit North America, April 20-21, in Los Angeles, California. Those in attendance at the last four ONS events will

Delighted to, will put it on tomorrows agenda :) Ed

The ci-management committers have voted to approve Dave Wallace as a committer. Can we add this to the TSC agenda for tomorrow please? Thank you, Vanessa -------- Forwarded

>Alberto takes care of the release update, so in that case it would be >his responsibility to take care of ci-management as well. >Mauro would take care of reviewing Alright then. @Vanessa

-------- Forwarded Message -------- Subject: Re: RPM_DPDK Questions Date: Thu, 30 Jan 2020 13:43:11

-------- Forwarded Message -------- Subject: RE: NSH_SFC Question Date: Fri, 31 Jan 2020 08:42:18

Alberto takes care of the release update, so in that case it would be his responsibility to take care of ci-management as well. Mauro would take care of reviewing ci-management for what concerns these

>In hicn it would be helpful to have a ci-management committer >to take care of our release management. In ci-management, Gerrit does not allow an owner of a contribution to vote +2 on it, even

Dear tsc members, (with hicn/cicn PTL's hat on) The current release repo https://packagecloud.io/fdio/release contains 20214 artifacts almost entirely from our projects. The current binary

LF Networking Community: The Open Networking & Edge Summit (ONES) enables collaborative development and innovation across enterprises, service providers/telcos and cloud providers to shape the future

+ Mauro yes of course, Mauro would be happy to become a committer in ci-management. Thanks Luca