2022-10-20 TSC Minutes

Owned by Guillaume Lambert
Last updated: Oct 21, 2022 by Kenny Paul
2 min read

TSC Meeting Zoom || TSC APAC Zoom || Meeting Recordings

TSC meetings are held weekly for one hour on Thursdays.  Meeting time alternates each week.  Standard: 9am Pacific and APAC: 10pm Pacific.

Attendees & Representation

TSC Members and Project representatives should mark their attendance below

X = Present | P = Proxy  (Indicate below table with @name for @name

TSC Members

TSC Members

@Robert Varga  Pantheon.tech

x

@Manoj Chokka Verizon



@Venkatrangan Govindarajan Rakuten Symphony

x

@Guillaume Lambert Orange

x

@Anil Shashikumar Belur Linux Foundation



@Ivan Hraško Pantheon.tech



@Cédric Ollivier Orange

x

Community Elected Roles:

@Daniel De La Rosa  (Release Manager)



Staff: @Kenny Paul 

Community: @Sangwook Ha 

Agenda

  • Start the Recording

  • We will start by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

  • Agenda Bashing, Roll Call, Action Items (all, 9:00-9:05 am)

  • Releases

  • LFN Updates

  • Marketing Update

  • TSC Grievance Tracking

  • General Topics

    •  

  • Any Other Topics

Minutes

Release

  • Chlorine is almost done. TPCE released some artifacts candidates that needs to be confirmed by int/dist team, so we can move forward towards distribution and documentations updates

  • Sulfur SR3 RC is not ready to be picked, so we will wait until next week to get it done. 

LFN Updates

Marketing Update

General Topic

  • Ongoing discussion at the ONAP TSC about the EPL license of the ODL fork (exception to ONAP ALv2 license recommendation).
    There are ONAP components in lack of maintainers and they rely on the old RESTCONF implementation.
    They try to adapt the old RESTCONF code deleted in Chlorine inside their own repo, the time they migrate.
    A new project was created to that purpose. Discussion on possible scenarii with @Cédric Ollivier and @Robert Varga 
    Creating a broker to manage the 2 RESTCONF versions was too hard indeed.



Action Items