Andreas Geißler

Magnus Buhrgard (Unlicensed) 

Cédric Ollivier 

N.K. Shankaranarayanan 

Chaker Al-Hakim 

Paweł Pawlak 

Dan Xu 

Ram Krishna Verma 

Dong Wang

Seshu Kumar Mudiganti proxy Shashi v.h.

Gervais-Martial Ngueko 

Timo Perala

Keguang He 

Kenny Paul 

• #AGREED the TSC approve cl664y@att.com remaining as the TSC Chair in a non-voting capacity until the new Chair is elected.
  
  
• Vote for TSC Chair Election - Nomination Deadline: Monday. Oct. 31st @ 23:59 UTC

David McBride

• Weekly update
• Kohn RC - Oct 27
• London kickoff
• RAN Emulator - Source Code reviewed and merged by Lukasz Rajewski 

Jessica Gonzalez

• Tickets- Open showstoppers:
• Tickets- Waiting on Community:
• Migration Status / Upcoming Changes

• RELENG-4472 - Review Release Process and Documentation for ONAP
  • Matt and Jessica still working, no further updates for now
• Responsibility for http://www.onap.org ; outdated link to documentation ; Ticket IT-24654  still an internal action item
• Mend scan jobs under https://jenkins.onap.org/view/WhiteSource/
  • Are they still needed?
  • Can we deprecate them?
  • #AGREED Cancel the license and remove the jobs
• GitLab - taking longer to get the pipelines set up than expected only chained-ci now.

Paweł Pawlak 

Amy Zwarico 

SECCOM - new requirement as a follow up of unmaintained efforts: retirement of unmaintained repos – PROPOSAL FOR LONDON, but it does not make sense to apply to the new code (as per Best Practice state), as we consider old unused code, so we apply for Global Requirement.

• View file
  name London SECCOM Requirements.pdf height 250

• gerrit query to identify all the repositories that have been set to "Read only" - GET https://gerrit.onap.org/r/projects/?state=READ_ONLY The result will be captured in a *.json file
• Label is "unmaintained" in Jira
• For Kohn release, candidate repositories are tracked here:  https://wiki.onap.org/x/LQtHC

•  Paweł Pawlak New REQ Jira to be created for Retirement of Unmaintained Repos 21 Oct 2022 

• RELENG-4472 is the SBOM clean up

LFN Board

• 2023 ONAP Budget has been approved i.e. Flat in comparison to 2022 (Gitlab migration not included)
• Request to present ONAP Status to the board on Nov 14th in Seattle (4.30-6pm PST). Material to be submitted on Nov 4th, 2022. Previous presentations: Community Updates for the LFN GB
• Paweł Pawlak  will present to the LFN GB on Nov 14th.
  • Discussion over providing info on the "mainstream" work to the GB.
  • Update on the Mainstream work group next week.

TAC

-TAC Members will be able to nominate candidates soon for the following TAC Seats:

• 5G Super Blueprint: https://wiki.lfnetworking.org/x/1gpzB - 26 Oct 2022  17:00 PDT. 
• Security: https://wiki.lfnetworking.org/x/1ApzB - 26 Oct 2022  17:00 PDT. 
• New TSC will need to appoint a representative for TAC
  • TAC meeting info - https://wiki.lfnetworking.org/x/5AAF

-Need to provide a date to present ONAP to the TAC in November (9th or 23rd) or in December (9th or 23rd).

Georg Schweflinghaus 

Andreas Geißler 

New Project Proposal for a successor of the ONAP Portal (presented at the DDF https://wiki.lfnetworking.org/display/LN/2022-01-12+-+ONAP%3A+Deutsche+Telekom+Portal+presentation)

David McBride , Dan Timoney 

Vote on the ODL Code transfer to ONAP

• Discussed in the TSC on Sept 22
• Magnus had requested time for review
• Discussion - licensing exception needs to be timebound. suggestion of 12 months. 

•  cl664y@att.com  invite Dan Timoney to 27 Oct 2022 TSC meeting

• #VOTE:  Does the TSC approve a licensing exception for the ODL RESTCONF API code  in accordance with paragraph 7(c) of the ONAP charter?  

• To be discussed again next week.

Kenny Paul

• ONE Summit NA 

  • Nov. 15 & 16 2022 Seattle, WA, USA
  • Please Register
  • LF members receive a 20% discount with code ONE22LFNMEM
    
    

• LFN Developer & Testing Forum NA

  • Nov. 17 & 18 2022 Seattle, WA, USA
  • ONLY 2 days 
  • Slightly different format based upon the feedback we received from Porto
    • General
      • Very short kickoff
      • No daily summary sessions
      • No closing town hall
    •  Day 1
      • 1st hour to be a cross- project session where each project brings a problem to the community
      • Community brainstorming the rest of the day - 1 hour per problem/topic
    • Day 2
      • More traditional D&TF sessions
      • Content will be curated by the program committee more than usual given the short time available
      • Committee strongly recommends making demos available via YouTube rather than requesting sessions to demos and general project readouts.
  • Submission deadline: Friday, October 28th - Soliciting topics for LFN D&TF Nov 17-18 (onap.org)
  •  https://wiki.lfnetworking.org/x/YwNzB    
    • where should we discuss the ONAP's cross community topic for day 1
    • Add to PTL and TSC agendas for next week.  Input from ONAP workgroups also welcome
    • One slot per community, ONAP to decide which issue to present to LFN Community
    • ONAP Day 1 Topic Page 
    • Input to be provided by 26 Oct 2022 
    • TSC will chose the topic on 27 Oct 2022