Weekly meeting to work on revisions to the VNF security requirements – moved to avoid conflict with TSC meeting

Weekly meeting to work on revisions to the VNF security requirements – moved to avoid conflict with TSC meeting

+ spreadsheet

Thank you for your participation on today’s call. We made good progress – 6 requirements in one hour. Moving forward we will spend the first 10-15min reviewing the Jiras scheduled for final approval,

Thank you for your participation in the VNF requirements update. Attached is the spread sheet that we will use to update the VNF requirements and to assess whether the requirement can be tested. I’ve

Replaced by a Tuesday meeting following the weekly SECCOM call. Weekly meeting to work on revisions to the VNF security requirements.

Weekly meeting to work on revisions to the VNF security requirements – moved to avoid conflict with TSC meeting -- Do not delete or change any of the following text. -- Join Webex meeting Meeting numb

I forgot to send out the cancellation earlier. I need to reschedule this meeting because it now conflicts with the TSC> Proposal: Tuesdays after the SECCOM call. Does that work for the participants of

Java 12 is no longer supported and it is recommended that all users of Java SE 12 switch to Java SE 13.

Cancelling again because the meeting now conflicts with the TSC call. I will find a better time going forward. Weekly meeting to work on revisions to the VNF security requirements.

I am OOO on Thursday. We will resume Thursday, 14th November. Weekly meeting to work on revisions to the VNF security requirements.

I am OOO on Thursday. We will resume Thursday, 14th November. Weekly meeting to work on revisions to the VNF security requirements. -- Do not delete or change any of the following text. -- Join Webex

Unfortunately there is urgency, and considerable pushback. I propose that we investigate the "new code tested" feature of SONAR in the Frankfurt release, create a clear definition of "new code", find

I’ve used the sonar high level reports, but never drilled into detail. It looks as if we can look at metrics for new code. Pierre, are the numbers coming up 0 because we run the Sonar jobs as part of

I want to clarify that the VNF Security Requirements will meet at 9AM ET, 2PM CET meeting time on Thursday. The invitation is not tied to UTC. ​​​​​Amy Zwarico, LMTS Chief Security Office / Emerging S

Please review https://jira.onap.org/browse/REQ-207 updated based on feedback at the PTL call and discussion during the SECCOM meeting. I would like to finalize this requirement before the TSC call on

One the Monday, 21 October PTL call, Catherine Lefevre requested a formal SECCOM recommendation for the El Alto release based on the KPI data presented. On today’s SECCOM call (22 October) we reached

Canceling this week’s meeting in order to host an ODL call. We will resume on October 17. Weekly meeting to work on revisions to the VNF security requirements.

Unfortunately, I have to cancel this week because we are using this time slot to meet about the ONAP ODL package. Weekly meeting to work on revisions to the VNF security requirements.

Unfortunately, I have to cancel this week because we are using this time slot to meet about the ONAP ODL package. Weekly meeting to work on revisions to the VNF security requirements. -- Do not delete