2025-06-12 TSC Minutes

TSC Meeting Zoom || TSC APAC Zoom ||

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

Staff: @Casey Cain

Community: 

Agenda

• Start the Recording

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

  • Antitrust Policy

• 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

1. Meeting Schedule Discussion & Attendance Analysis

Primary focus of the meeting was resolving TSC meeting scheduling challenges.

Current Attendance Issues

Detailed attendance statistics presented by Casey:

Daytime (US-friendly) Meeting:

• May: 3 attended, 2 out of 3 voting reps

• April: 4 attended, 3 out of 4 voting reps

• March: 5 attended

• Generally 15 people invited, 3-5 typically attend

• Better overall attendance than APAC meeting

APAC Meeting:

• May: 2 attended, 1 out of 2 voting reps

• April: 1 out of 2 voting reps attended

• Consistently lower attendance

• Different attendees than daytime meeting (Casey, Anil, Daniel typically)

Community Feedback on Current Schedule

Robert's Email Feedback (read verbatim by Casey):

• "Prime offender in terms of dropped attendance"

• Bi-weekly schedule throws off his rhythm - tends to miss which week has meetings

• Missing APAC meeting, then forgetting US meeting disrupts his cadence

• Preference: Shorter meetings on weekly cadence in friendly timezone

Venkatrangan's Issues:

• Problems with calendar transitions when meetings moved from Google Calendar

• Missed meetings due to copying errors between calendar systems

• Generally solid attendance before calendar issues

• Supports consistency over variation

Ivan's Perspective:

• Difficult to find convenient time for Australia, US, and Europe (covers whole world)

• Suggests moving APAC meeting 15 minutes later to improve his attendance

• Willing to attend both US time and APAC time meetings if scheduled properly

David's Input:

• Current daytime timing most convenient for majority

• Strongly supports consistency - bi-weekly at same time

• Believes previous weekly alternating schedule (US/APAC) was better strategy

• Emphasized Robert's point about consistency being key

Proposed Solutions & Discussion

Option 1: Single Consistent Meeting

• Every 2 weeks at fixed time (likely current daytime slot)

• Adjust time by ±15-30 minutes if needed for better global participation

• Pros: Maximum consistency, easier to remember

• Cons: Excludes APAC participants, may lose input from Daniel/Anil

Option 2: Slight Time Adjustment

• Keep current format but move meetings 15 minutes later

• Ivan indicated this would help his attendance

• Still maintain bi-weekly alternating schedule

Option 3: Return to Previous Weekly Alternating

• Week 1: US-friendly time

• Week 2: APAC-friendly time

• Pros: Geographic inclusion, consistent weekly rhythm

• Cons: Ruled out due to insufficient weekly content

Option 4: Hybrid Approach

• Official TSC meeting at consistent time every 2 weeks

• Separate "OpenDaylight APAC Office Hours" - informal community call

• APAC participants can attend optional sync or skip

• Concerns raised by Venkatrangan: Different people at different meetings means questions may not get answered

Technical/Logistical Considerations

Calendar Management:

• All meetings now on LFX community calendar

• Some participants experienced subscription/integration issues during transition

• Calendar link available on wiki for community access

Content Volume Assessment:

• Venkatrangan: "Week after week it was very less items to discuss" - justification for moving away from weekly

• Casey: Not enough community fluidity for weekly updates

• Agreement: Weekly meetings ruled out due to insufficient content

Stakeholder Input Needed:

• Critical missing voices: Daniel (release updates essential), Anil, Robert

• Casey emphasized need for Daniel's participation due to release update responsibilities

• Will explicitly seek feedback from these key participants

Decision Process

Immediate Actions:

1. Casey will draft comprehensive follow-up email with all discussed options

2. Email will include voting mechanism (possibly doodle poll)

3. Explicit outreach to Daniel, Anil, and Robert for input

4. Target resolution before next TSC meeting

Voting Options to Include:

• Single bi-weekly meeting at current time

• Single bi-weekly meeting at adjusted time (±15-30 minutes)

• Return to weekly alternating US/APAC schedule

• Hybrid official TSC + informal APAC office hours

Selection Criteria for Final Decision:

• Consistency and predictability (addressing Robert's concerns)

• Maximum participation from voting representatives

• Accommodation of release management needs (Daniel's input)

• Geographic inclusion balance

2. Linux Foundation Platform Updates

Zulip Migration

• Linux Foundation has signed contract with Zulip

• Andy Grimberg setting up single sign-on

• Will be deployed to all LF projects as official chat platform

• Migration from Slack will be optional, not mandatory

• Features: message retention, topic-based organization

• Default channels planned: project, support, admin, TSC-specific

LFX Insights Dashboard Updates

• New version launched with improved health scoring

• Currently experiencing bugs (some metrics not displaying)

• Based on OpenSSF standards for security and best practices

• Future plans: automated issue creation for governance concerns

• Confluence contributions not yet tracked

Community Calendar

• All meetings moved to LFX community calendar

• Some participants experienced issues during calendar transition

• Calendar subscription available for integration with personal calendars

3. Technical Discussion

David's SDN/OpenFlow Question

Problem: Need to simulate default gateway behavior in SDN environment

• Computers expect ARP responses from default gateway

• Controller needs to provide fake MAC address responses

• Looking for an OpenDaylight equivalent to the ONOS solution

Discussion:

• Ivan suggested checking Yang models and OpenFlow specifications

• Casey recommended exploring AI coding tools for solutions

• David will continue research with student assistance

• Agreed to share the solution with the community when found

Action Items