Page Comparison

•  Linux Foundation Anti-trust Policy
•  TSC Meetings are recorded! The recordings are retained to help fill gaps in the minutes until approval (1 week).
•  Agenda Bashing 
•  Attendance/Quorum (12/15)
•  Approval of previous meeting minutes 2021-12-14 TSC Agenda and Minutes

Gergely Csatari

•  Announcements

• June Developer Event - In-person - Porto, Portugal
  • June 13-16, 2022
  •  https://events.linuxfoundation.org/lfn-developer-testing-forum/
• OpenStack PTG - Virtual April 4-8
• https://www.openstack.org/ptg/
• https://openinfra-ptg.eventbrite.com/
• CNCF Telco Cloud Day - In-person - Valencia, Spain
  • May 16, 2022
  • https://events.linuxfoundation.org/cloud-native-telco-day-europe/
  • Registration to KubeCon EU is needed to participate
• Open Networking & Edge Executive Forum - April 12-14
  • https://events.linuxfoundation.org/open-networking-and-edge-exec-forum/
  • No cost. Register today!
• ONE Summit in November
  • Seattle Nov 14-18 
• DTF in November
  • Seattle Nov 19-20

Gergely Csatari

•  Marketing Update

Scot Steele

Beth Cohen

•  Moselle 
  • Full schedule
  • M2 Requirements
  • M3 scheduled for April 19

David McBride

Per Karine Sevilla During RM and RA1 last meetings, we discussed about the release milestones M3 (content freeze), M4 (proofreading) and M5 (release readiness).

The time period to reach M3 is too short and the time periods between M3-M4 and M4–M5 are too long and useless for us.

We would like to modify the milestones to adapt to the specification production needs.

 Our proposal is the following:

M3 May 17 (instead of  April 19)

M4  May 31  (instead of  May 17)

M5 June 7  (unchanged)

M6 June 14th (unchanged)

This proposal is validated by RA1 contributors and supported by Walter for RM.

The software workstreams would not change.  This proposal is only for the specification tasks.  David McBridenotes that this would require one additional milestone that would need to be tracked.

TSC supports this proposal. David McBridewill add the one additional milestone and update the process docs.

David McBride RC is still outstanding in the release schedule.

Cédric Ollivier The process for testing RC2 is on Jenkins/Gerrit/Github - there is a clear visibility what's selected by RC2, and then tested/covered via Jenkins automatically. RC2 is updated as soon as K8s releases a new version. Any new test cases must follow this RC's best practices before being integrated in RC2. Right now no new test case are being integrating. Hoping RA2 will add requirements about CNF onboarding to allow adding cnf-testsuite in RC2.

Gergely Csatari

•  CCC updates
  • Docs Project: revamp and develop a consistent place and process to manage documentation.  Discuss DTL Session plan
  • Review of CLA legal text and get sign off from participating companies

Scot Steele

Beth Cohen

• CCC will take the section of the charter that is the equivalent to the IP agreement and do the diff on that and the CLA doc. 
• David sent a link to the charter that contains the original OPNFV IP agreement to CCC. In OPNFV the IP agreement was embedded into the project charter. CCC will produce a delta of the IP agreement section of the OPNFV charter and the proposed Anuket CLA.

Sub-project Leaders

•  Technical Officer Updates
  
  • Tech Editor - Beth Cohen
  • EUAG - Beth Cohen
  • CNCF Tech Coordination - Gergely Csatari
  • ETSI NFV and MEC Tech Coordination - Ulrich Kleber
  • GSMA Tech Coordination - Walter.kozlowski
  • XGVela Tech Coordination - Pankaj.Goyal
  • Open Infrastructure Foundation -  Ildiko
  • ORAN - vacancy for WG 6
    
  • MEF - MEHMET TOY