[TOC Meeting][Public] 2024-09-17

[mrbobbytables]

Host: @nikhita
Note Taker:

(Note: @castrojo will fill in for Bob)

Recurring Items

• LF Antitrust Policy
• Review Open Votes (REMINDER: Check both Issues AND PRs)
• Review & Assign projects in moving levels backlog
• Review TOC Work Board

Agenda

• Linkerd Check-in Dave Z.

[mrbobbytables]

assigned @castrojo to act as host next week
@dzolotusky assigned you as well for the linkerd update

[TheFoxAtWork]

to clarify the linkerd check-in is largely to determine if there is anything further the TOC needs to close out the health of issue. If there is sufficient time after the discussion, i would recommend the group talk through the existing open health of issues and determine if any need follow up or closure. If there are other projects with Health of issues that need opened and discussed, lets queue them up.

I wont be in the meeting, as i'll be at OSS EU

[angellk]

I won't be in the meeting - I'll be at OSS EU as well

[wmorgan]

If there's anything I can provide to help characterize Linkerd's health, please let me know. A couple datapoints come to mind:

• Since February we've shipped 30 edge releases (one a week!), improved our user-facing guidance for edge releases, and seen some great examples of the power of edge releases for rapid bugfixing (e.g. Intermittent routing failures with HTTPRoute  linkerd/linkerd2#12610)
• We've shipped many features that had been languishing in the backlog, including IPv6 support, an authz policy audit mode, and a new implementation of retries, timeouts, and per-route metrics—some of the earliest code ever shipped in Linkerd—that fixes some long-standing corner case behavior in these features.
• The Linkerd community Slack hit 10,000 members 🎉
• There are 9 talks at Kubecon SLC with "Linkerd" in the title or description 🎉

Lots more to talk about but I am writing a retrospective blog post and don't want to spoil too much :)