Hi, everyone. I would like to share what information we have at this time. Plastic 2.1.6 was able to release on Jan 29th. After that time, the staging repository has seemed to be reporting at least

Hi all, I have updated the project proposal for Guice on Friday and incorporated Robert's review comments too - https://wiki.lfnetworking.org/display/ODL/ODL+Guice+Project Please feel free to add more

FYI, I have found this in the ODL charter [1], it is about License violations rather than security vulnerabilities (I believe Nexus IQ detects both): Paragraph c and d in section 7. Intellectual

I think there is a mismatch between this and what Casey communicated last Thursday, I wish you were there. My understanding of ODL project governance is exactly what you described in your email,

I am sorry, but I just cannot agree with this point. Each normal[0] OpenDaylight project is created sovereign. That means that each project is completely and ultimately responsible for defining and

Hi, everyone. Some of our IT/RE management team are out of the office today so we have not yet completed a proper investigation. Please give us until end of day Monday to respond. Sorry for the

Well, that is what LF is investigating now per my understanding but this should not block Allan to use the security team avenue. BR/Luis

thanks Luis, Abhijit. Anil, Casey, still wondering about the v2.1.6 vs v2.1.7 weirdness that keeps getting unanswered. JamO On 3/6/20 3:18 PM, Abhijit

Also: Casey Cain to work with LF IT to address communications to the community regarding security issues. 06 Mar 2020 Casey Cain to follow up with Allan Clarke Thanh Ha and the community on Plastic

Hi Jamo, Few outcomes from yesterday TSC call (at least for me): 1) Thanh will open a ticket to LF to work on a new feature to notify users upfront if there is a security problem in the staging

I missed the TSC meeting last night. Can someone recap over email what came of this? I see one note in the minutes that Casey indicated that no change has occurred in the policy

The concerning thing here for me is LF deployed a new release process requiring someone or group of people to analyse and provide a security waiver to projects before allowing the project to be

Thanks for the reply, Anil. That did answer some questions I had. My questions: Why is there no link or docs connecting a built-but-not-available staging build to a vulnerability report? Why are

Greetings Allan: I understand the concerns on the delay in releasing Plastic, please find my response below. 1. The policy violations are security issues outside the scope of LF/RE's to determine if

Yes - let us discuss it tonight at the TSC meeting.

Abhijit, can we bring this topic in tonight’s TSC? BR/Luis Begin forwarded message: From: "Allan" <aclarke@...> Subject: [OpenDaylight TSC] Issue with Linux Foundation and expectations on ODL

Greetings! I have been trying to get a new release of the Plastic sub-project out for 3 weeks now and have been clogged up in LF helpdesk. *Summary* LF is not allowing newer release of

Next TSC meeting is March 5, 2020 at 10 pm Pacific Time. The zoom session for the meeting is: https://zoom.us/j/657152618. Agenda for this meeting is

Thanks for letting us know.

Thanks, JamO